Move Enterprise gateway API rendering behind the extensions boundary - #5230
Open
caseydavenport wants to merge 1 commit into
Open
Move Enterprise gateway API rendering behind the extensions boundary#5230caseydavenport wants to merge 1 commit into
caseydavenport wants to merge 1 commit into
Conversation
caseydavenport
force-pushed
the
casey-gatewayapi-extension
branch
from
August 21, 2026 15:26
1deddca to
c2e7c4a
Compare
The base gateway API render produces the same objects for both variants. The Enterprise extension supplies the tigera envoy images, the WAF filter's RBAC and per-namespace identity, and the l7-log-collector alongside envoy.
caseydavenport
force-pushed
the
casey-gatewayapi-extension
branch
from
August 21, 2026 16:11
c2e7c4a to
1d75f81
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
3 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.
Description
Another variant-gating split. The gateway API render no longer branches on variant, and the Enterprise extension layers on what only Enterprise installs get:
Cleanup of the pre-namespaced install moves with it: the old service account in "tigera-gateway" and the two cluster role bindings that bound it are queued for deletion by the extension rather than the base render.
No behavior change for either variant. Test coverage for the Enterprise pieces moved into the new package alongside the code.
Related: CORE-13396
Release Note