workaround: cluster->lb traffic w/ TLS/ProxyProto #206
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 PR excludes traffic with Layer7 rules from a kube-proxy optimization.
The kube-proxy optimization intercepts and redirects cluster egress traffic
destined for the LB to the backing services, avoiding the DigitalOcean LB
entirely. If the DO LB is providing L7 services like TLS termination, Proxy
Protocol, or StickySessions this breaks access to LB-hosted services
from within the cluster. This PR opts out of the optimization by returning
the IP address in the Hostname field rather than IP. The IP will be reported
to the user in the same way via tools like kubectl, but is interpreted differently
by kube-proxy.
kubernetes/kubernetes#66607