Revert to previous kubelet bind address logic #10475
Closed
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.
This is a backup PR, in case we can't get a change made to dynamiclistener. I would prefer to allow users to bind the kubelet to a specific IP, but that requires:
Proposed Changes
Revert to previous kubelet bind address logic
The kubelet bind address should always be a wildcard address selected based on the primary node-ip; don't pass the bind-address value through directly.
Types of Changes
bugfix
Verification
--bind-address
on a server or agent nodekubectl logs
works properly to retrieve logs from pods on that nodeTesting
Linked Issues
User-Facing Change
Further Comments