Allow Envoy Gateway to use cloud LoadBalancer providers and be deployed in arbitrary clusters - #778
Open
wtripp180901 wants to merge 3 commits into
Open
Allow Envoy Gateway to use cloud LoadBalancer providers and be deployed in arbitrary clusters#778wtripp180901 wants to merge 3 commits into
wtripp180901 wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In Kubernetes clusters containing cloud-specific providers for provisioning LoadBalancers instead of the default MetalLB provider, modifications to the LoadBalancer service deployed by EnvoyProxy are often required. To accommodate these requirements this change
kuberentes.envoyService.annotationsto allow injecting provider specific annotationskubernetes.envoyService.patchto make arbitrary patches to the underlying Service manifestAlso makes RKE2 and cluster-bloom specific config optional to allow envoy-gateway-config to be deployed in existing clusters where routing config for loadbalancing is handled elsewhere