-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update KEP template with comment wrt to enablement/disablement tests in PRR section #3206
Conversation
keps/NNNN-kep-template/README.md
Outdated
|
||
Additionally, for features that are introducing a new API field, unit tests that | ||
are exercising the `switch` of feature gate itself (what happens if I disable a | ||
feature gate after having objects written with the new field) is also critical. |
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.
feature gate after having objects written with the new field) is also critical. | |
feature gate after having objects written with the new field) are also critical. |
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.
Fixed.
are exercising the `switch` of feature gate itself (what happens if I disable a | ||
feature gate after having objects written with the new field) is also critical. | ||
You can take a look at one potential example of such test in: | ||
https://github.com/kubernetes/kubernetes/pull/97058/files#diff-7826f7adbc1996a05ab52e3f5f02429e94b68ce6bce0dc534d1be636154fded3R246-R282 |
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.
Not sure if we need the example? Or maybe we should add an example to the first comment block too?
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.
Multiple people were telling me that they have no idea how to do that - after I was giving them a link it seems that it's actually happening. So I think it's useful.
Regarding the first block, we're much less prescriptive there - I'm fine with updating that, but maybe we can do that in a separate PR?
Adding a hold - I don't think the KEP template should be changing before the enhancements collection period ends. /hold |
e10afc8
to
628974b
Compare
Sure - this can (and should) absolutely wait until then (given it's more-or-less almost now). |
looks good /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johnbelamaric, wojtek-t 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 |
/lgtm I'll leave it to another reviewer to remove the hold |
I think change will help people. /hold cancel |
/assign @deads2k @ehashman @johnbelamaric