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
KEP-1672: add alpha graduation criteria #2065
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.
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.
Thanks for the work on this! If you haven't already, do you mind adding some notes about the risks involved in this KEP and how we'll need to cautiously roll this out? (Basically just a summary of our earlier discussion).
|
||
* EndpointSlice API includes `Terminating` condition. | ||
* `Terminating` condition can only be set if feature gate `EndpointSliceTerminatingCondition` is enabled. | ||
* Unit tests in endpointslice controller and API validation/strategy. |
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.
Can you add a bit more detail here around what these would cover?
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.
This is covered under the "Test Plan" section https://github.com/kubernetes/enhancements/blob/0af741e352e8f498a8aeda0fa423b66ca09de836/keps/sig-network/1672-tracking-terminating-endpoints/README.md#test-plan
I admit though that what's written in the KEP today is off from the tests I ended up writing in kubernetes/kubernetes#92968, will update that now
I was planning on a larger update around this for the Beta graduation crtieria, which I was planning to write in the v1.21 cycle in case there were any other gotchas we might discover. I don't think anything we discussed is going to impact the initial Alpha stage since it would be off by default. Would it be acceptable to address that in a follow-up PR given the v1.20 deadline for KEPs is tomorrow? |
👍 That's reasonable, just trying to make sure we don't forget about it. |
Signed-off-by: Andrew Sy Kim <kim.andrewsy@gmail.com>
Signed-off-by: Andrew Sy Kim <kim.andrewsy@gmail.com>
Thanks! /lgtm |
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.
Approving this, but we'll need to resolve kubernetes/kubernetes#92968 (comment)
Thanks! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewsykim, thockin 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 |
Thanks Tim, I'll make sure to update the KEP for beta around that topic |
Add alpha graduation criteria for EndpointSlice API tracking terminating condition.
Signed-off-by: Andrew Sy Kim kim.andrewsy@gmail.com