Never override the hostname on AWS nodes #372
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Never override the hostname on AWS nodes.
Kube-Proxy uses the
hostname= to lookup thecorev1.Nodeobject its running on. On AWS nodes, the name of thecorev1.Node` is always the private dns name in AWS.This is a requirement of the AWS code in kubernetes. Thus, manually overriding the hostname in the OS is not useful.
Instead if leads to the error messages: