-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
[kubelet] Auto-discover node IP if neither cloud provider exists and IP is not explicitly specified #29907
Conversation
Is this worthy a release note? |
GCE e2e build/test passed for commit 25d9779. |
@k8s-bot node_e2e test this please github issue: #IGNORE |
@k8s-bot node e2e test this please github issue: #IGNORE |
This LGTM. Thanks for the cleanup @luxas |
lgtm |
@luxas I updated the PR title to make it suitable for release notes. PTAL |
Great! Seems like the auto-lgtm-bot isn't active yet, so adding I'm the labels now |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 25d9779. |
Automatic merge from submit-queue |
One example where the earlier implementation failed is when running kubelet on CoreOS (bare-metal), where the nameserver is set to
8.8.8.8
. kubelet tries to lookup the node name agains Google DNS, which obviously fails. The kubelet won't recover after that.The workaround hsa been to set
--hostname-override
to an IP address, but it's quite annoying to try to make a multi-distro way of getting the IP in bash for example. This way is much cleaner.Refactored the function a little bit at the same time
@vishh @yujuhong @resouer @Random-Liu