Draft
Conversation
Adds flag-gated Gateway API resources to both nginx-ingress-services and the integration chart as an alternative to ingress-nginx for federation mTLS. Existing ingress-nginx paths are untouched when the flag is off. nginx-ingress-services changes: - New gateway-federator.yaml: EnvoyProxy, Gateway, ClientTrafficPolicy (mTLS), two HTTPRoutes (HTTPS + HTTP→HTTPS redirect), EnvoyPatchPolicy (%DOWNSTREAM_PEER_CERT% → X-SSL-Certificate header), and a conditional ReferenceGrant for cross-namespace CA secret access - ingress_federator.yaml: guarded by `not federator.gatewayAPI.enabled` - federation-test-helper.yaml: dual-mode pod selector (ingress-nginx labels vs. gateway.envoyproxy.io/owning-gateway-name=federator-gateway) - values.yaml: federator.gatewayAPI block (enabled, gatewayClassName, servicePort, serviceType, envoyContainerPort) integration chart changes: - New gateway-federator.yaml: EnvoyProxy (ClusterIP for in-cluster SRV discovery), wildcard Gateway, ClientTrafficPolicy, HTTPRoute loop over dynamicBackends, EnvoyPatchPolicy, conditional ReferenceGrant - ingress.yaml: guarded by `not gatewayAPI.enabled` - values.yaml: gatewayAPI block Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Adds flag-gated Gateway API resources to both nginx-ingress-services and
the integration chart as an alternative to ingress-nginx for federation
mTLS. Existing ingress-nginx paths are untouched when the flag is off.
nginx-ingress-services changes:
(mTLS), two HTTPRoutes (HTTPS + HTTP→HTTPS redirect), EnvoyPatchPolicy
(%DOWNSTREAM_PEER_CERT% → X-SSL-Certificate header), and a conditional
ReferenceGrant for cross-namespace CA secret access
not federator.gatewayAPI.enabledvs. gateway.envoyproxy.io/owning-gateway-name=federator-gateway)
servicePort, serviceType, envoyContainerPort)
integration chart changes:
discovery), wildcard Gateway, ClientTrafficPolicy, HTTPRoute loop over
dynamicBackends, EnvoyPatchPolicy, conditional ReferenceGrant
not gatewayAPI.enabledCo-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
Checklist
changelog.d