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
Add KEP for ingress API group move #749
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.
I am OK with the general thrust. Give it some time to accumulate notes.
I think this is a necessary recognition of reality, as Ingress does have a number of implementations and users, and we need a stable L7 API by EOY. |
FYI, the deadline for merging and marking implementable got extended to monday because the originally documented requirements were unclear. Are there any other questions about the work being proposed for 1.14? |
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.
@bowei this looks like a good plan to me, given what we've got to work with!
Looks like there are just a couple of comments to clean up.
a4d15ca
to
dfb4460
Compare
@caseydavenport -- updated incorporating comments. Note: had to move the file to match new KEP guidelines, so the existing github PR comments will probably be stale... |
dfb4460
to
8e5af5d
Compare
8e5af5d
to
f4ec2e3
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bowei, caseydavenport 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 |
cc: @thockin @liggitt