Add provisional GEP-4748: EgressGateway Resource#4749
Open
usize wants to merge 1 commit intokubernetes-sigs:mainfrom
Open
Add provisional GEP-4748: EgressGateway Resource#4749usize wants to merge 1 commit intokubernetes-sigs:mainfrom
usize wants to merge 1 commit intokubernetes-sigs:mainfrom
Conversation
k8s-ci-robot
added
release-note-none
k8s-ci-robot
added
the
do-not-merge/hold
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: usize The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
k8s-ci-robot
added
cncf-cla: yes
Proposes a dedicated `EgressGateway` resource derived from `Gateway` for L7 reverse-proxy egress. Companion to GEP-4747. A coding assistant (Opus 4.6) was used to review grammar, citations, and alignment with upstream GEP formatting and terminology. It was also used to fact-check prior art claims against implementation documentation.
usize
force-pushed
the
provisional-egressgateway-gep
branch
from
52d3176 to
996e75a
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.
/kind gep
Provisional GEP for a dedicated
EgressGatewayresource for L7reverse-proxy egress in Gateway API, focused on "What?"/"Why?"/"Who?".
GEP-4748 proposes a dedicated
EgressGatewayresource derived fromGateway, providing RBAC separation, UX clarity, and design space foregress-specific concerns. This is a companion to GEP-4747 (PR #4746),
which proposes reusing the existing
Gatewayresource for egress.Community feedback on both approaches is explicitly requested.
This GEP depends on the Backend resource (PR #4488) and originates from the
WG AI Gateway egress proposal.
What this PR does / why we need it:
Adds a provisional GEP proposing a dedicated
EgressGatewayresource asan alternative to Gateway reuse for egress.
Which issue(s) this PR fixes:
Fixes #4748
Does this PR introduce a user-facing change?: