feat: add multi-ingress-support for envoy gw#5307
Open
siberijah wants to merge 2 commits into
Open
Conversation
zebot
added
the
ok-to-test
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.
Ticket: https://wearezeta.atlassian.net/browse/WPB-25475
Adds multi-domain support to the wire-ingress (Envoy Gateway) chart.
Set config.domains (a list) instead of the scalar config.dns to serve several backend domains from one release. You designate one domain as the primary; each additional domain gets its own Gateway listener, certificate, suffixed HTTPRoutes, and an injected per-domain CSP header (replacing the old nginx renderCSPInIngress). federator stays single-domain.
Backwards compatible: with config.dns (no config.domains), output is unchanged.
Checklist
changelog.d