Repository navigation
EXP: Backend Resource - #4488
Conversation
|
/cc |
Signed-off-by: Keith Mattix II <keithmattix@microsoft.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
|
Thanks @keithmattix this is an amazing step forward on Gateway API Leaving the lgtm to @mikemorris or @kflynn |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: keithmattix, rikatz The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
|
/lgtm Thanks! |
|
(Keith and I are meeting about this tomorrow, let's leave the hold in place till then at least.) |
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
|
OK, @keithmattix and I talked at some length this morning and my biggest concerns have been addressed. My remaining reservations are mostly around things coming in the future as we work on extending Backend beyond the immediate scope, so I'm OK landing this one as Implementable. (I may still argue for renaming /lgtm |
|
That lychee failure is a timeout on a page that for sure exists. /retest |
What type of PR is this?
/kind gep
What this PR does / why we need it:
This PR is an upstreaming of the Egress Backend resource proposal from WG AI Gateway. This GEP strips away a lot of the AI specific context and discussions (we can always resurrect them if needed) so that discussion here can focus on more core aspects of the resource's design (e.g putting TLS inline, namespace scoping, FQDNs, etc.). Disclaimer: I used Copilot to try and collate a lot of the discussion that's already occurred for this resource (mainly so folks wouldn't have to go around reading 5 different PRs, transcripts, Slack threads, etc.), but even my proofreading may have missed something, so please feel free to call out anything you see is missing.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: