-
Notifications
You must be signed in to change notification settings - Fork 4
docs: add initial egress gateway proposal #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just approving for now so others have time to review. Big +1 from me; I think this is the foundation use-case for this WG, and this doc covers the AI-oriented aspects of the "What" and "Why" very well
/approve
|
/approve the main aspects of eagress gw are well covered and this looks good to me as a first iteration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: david-martin, keithmattix, nirrozenbaum, shaneutt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Shane Utt <[email protected]>
First pass a #10, focusing on building consensus on the "What?" and "Why?" before worrying about how we're going to implement it, and which SIGs and sub-projects we will propose to (those will come in follow-up PRs).