Feat: Support configuring externalTrafficPolicy on the envoy service #2432
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 type of PR is this?
Adds possibility to configure externalTrafficPolicy on EnvoyProxy Service objects.
What this PR does / why we need it:
Currently there is no way to change the default "Local" externalTrafficPolicy, which is fine for the vast majority of use cases.
In our case, we run bare-metal without any cloud loadbalancer and rely on MetalLB and Cilium with "Cluster" externalTrafficPolicy to provide loadbalancing within the cluster. Without this, all requests arrive at one single envoy pod.
Which issue(s) this PR fixes: