-
Notifications
You must be signed in to change notification settings - Fork 39.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Same internal and external ip for vSphere Cloud Provider #45201
Conversation
/unassign @dims |
Address: ip, | ||
}, | ||
) | ||
for _, ip := range v.IpAddress { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is PR in review from @BaluDontu touching the same code - #45181
Can we merge both PRs to reduce cherry pick the resolve conflict effort?
We have e2e test which uses common func from https://github.com/kubernetes/kubernetes/blob/master/test/e2e/framework/util.go#L4506, this returns first address in the range Can we ssh into node using any returned IP address? |
@divyenpatel Yes, we can ssh into node using any returned IP address as long as you are running tests from the external network defined for the VMs. |
@bprashanth Can you please review this PR? |
lgtm |
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abrarshivani, luomiao
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@bprashanth can you help removing "do-not-merge" label. |
/release-note |
Automatic merge from submit-queue |
…-upstream-release-1.6 Automatic merge from submit-queue Automated cherry pick of #45201 upstream release 1.6 Cherry pick of #45201 on release-1.6. #45201 : Same internal and external ip for vSphere Cloud Provider. @BaluDontu @tusharnt
When a node IP is set and a cloud provider returns the same address with several types, on the first address was accepted. With the changes made in PR kubernetes#45201, the vSphere cloud provider returned the ExternalIP first, which led to a node without any InternalIP. The behaviour is modified to return all the address types for the specified node IP. Issue kubernetes#48760
When a node IP is set and a cloud provider returns the same address with several types, on the first address was accepted. With the changes made in PR kubernetes#45201, the vSphere cloud provider returned the ExternalIP first, which led to a node without any InternalIP. The behaviour is modified to return all the address types for the specified node IP. Issue kubernetes#48760
Automatic merge from submit-queue (batch tested with PRs 51728, 49202) Fix setNodeAddress when a node IP and a cloud provider are set **What this PR does / why we need it**: When a node IP is set and a cloud provider returns the same address with several types, only the first address was accepted. With the changes made in PR kubernetes#45201, the vSphere cloud provider returned the ExternalIP first, which led to a node without any InternalIP. The behaviour is modified to return all the address types for the specified node IP. **Which issue this PR fixes**: fixes kubernetes#48760 **Special notes for your reviewer**: * I'm not a golang expert, is it possible to mock `kubelet.validateNodeIP()` to avoid the need of real host interface addresses in the test ? * It would be great to have it backported for a next 1.6.8 release. **Release note**: ```release-note NONE ```
When a node IP is set and a cloud provider returns the same address with several types, on the first address was accepted. With the changes made in PR kubernetes#45201, the vSphere cloud provider returned the ExternalIP first, which led to a node without any InternalIP. The behaviour is modified to return all the address types for the specified node IP. Issue kubernetes#48760
When a node IP is set and a cloud provider returns the same address with several types, on the first address was accepted. With the changes made in PR kubernetes#45201, the vSphere cloud provider returned the ExternalIP first, which led to a node without any InternalIP. The behaviour is modified to return all the address types for the specified node IP. Issue kubernetes#48760
Currently, vSphere Cloud Provider reports internal ip as container ip addresses. This PR modifies vSphere Cloud Provider to report same ip address as both internal and external that is provided by vmware infrastructure.
cc @pdhamdhere @tusharnt @BaluDontu @divyenpatel @luomiao