Rootless mode also bind service nodePort to host for LoadBalancer type #9512
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
When creating a service, typically the service port is for pod-to-pod access whereas nodePort is used for external access. In non-rootless mode, I was able to access a service of type LoadBalancer via localhost on both its service port and nodePort.
However, in rootless mode, I was only able to access it via localhost on its service port but not its nodePort.
Types of Changes
Rootless mode should also bind service nodePort to host for LoadBalancer type, matching UX of rootful mode.
Verification
kubectl apply
a simple pod &LoadBalancer
service withnodePort
port
andnodePort
Linked Issues
nodePort
for rootless k3s #9511User-Facing Change