Migrate ingress to Envoy Gateway - #126
Merged
Merged
Conversation
stefanprodan
force-pushed
the
envoy-gateway
branch
from
April 18, 2026 08:21
cefc095 to
4ad0908
Compare
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
stefanprodan
force-pushed
the
envoy-gateway
branch
from
April 19, 2026 10:45
4ad0908 to
736ee61
Compare
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
2 participants
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 replaces the deprecated Ingress Nginx with Envoy Gateway. Both cert-manager and the demo app are now configured for Kubernetes Gateway API.
Note that Envoy Gateway Helm chart prior to 1.8.0-rc.0 is broken due to CRDs size going over the 1MB limit of the Helm storage. xref: envoyproxy/gateway#8283