Ensure remotedialer kubelet connections use kubelet bind address #10480
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.
Proposed Changes
Ensure that connections to the kubelet through the egress-selector (either local or via remotedialer) use the correct kubelet bind address.
We have long overridden the kubelet address to the loopback address when dialing via the remotedialer tunnel, and ensured that the kubelet always binds to an ipv4 or ipv6 wildcard address. We broke this in #10019 when we wired the --bind-address flag up to the kubelet --address flag by way of the ListenAddress field.
This is blocked on:
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