-
Notifications
You must be signed in to change notification settings - Fork 1.5k
KEP-3751: Update release signoff Checklist before GA #5024
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
|
It looks like this PR does not contain this merged change: https://github.com/kubernetes/enhancements/pull/5028/files |
/retitle KEP-3751: Update release signoff Checklist before GA |
f1bfa08
to
4b306b5
Compare
/assign johnbelamaric |
4b306b5
to
37fdc1a
Compare
37fdc1a
to
17629e7
Compare
Stress tests still WIP: kubernetes/kubernetes#129918 It is set at a low rate though similar to our other stress tests(10 pods), and creating pod+volume, and then modify the volume. |
17629e7
to
e6cbc70
Compare
e6cbc70
to
e271c70
Compare
e271c70
to
478076c
Compare
0bfdef2
to
61c778e
Compare
Ok, I see the stress test is in progress, I would expect that do be done as part of this GA. The other PRR answers seem good. Once there is SIG approval, I can add the approval. |
f9bec7a
to
b9020e2
Compare
/lgtm |
b9020e2
to
0c99d4b
Compare
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.
couple of minor points, I will approve now but please make those small changes before LGTM
/approve
@@ -837,14 +857,37 @@ If the feature is rolled out partially on API servers, there will be no impact o | |||
be processed as if the feature is disabled, the external-provisioner/external-resizer is not acting on the event created yet - that means nothing happens and PVC | |||
will not be changed with the iops/throughput until external-provisioner/external-resizer is deployed. | |||
|
|||
###### How can a rollout or rollback fail? Can it impact already running workloads? |
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 already answered above?
Could enabling the feature cause api server, kcm, or the external provisioner to crash - I think it could if there were bugs. In that case, crashes in those should inform a rollback. Please add that here.
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.
Sorry I did not notice it is repeated. Removed this.
@@ -837,14 +857,37 @@ If the feature is rolled out partially on API servers, there will be no impact o | |||
be processed as if the feature is disabled, the external-provisioner/external-resizer is not acting on the event created yet - that means nothing happens and PVC | |||
will not be changed with the iops/throughput until external-provisioner/external-resizer is deployed. | |||
|
|||
###### How can a rollout or rollback fail? Can it impact already running workloads? | |||
|
|||
In general, rollout / rollback should not fail since the feature needs to be explicitly set in the PVC. | |||
|
|||
###### What specific metrics should inform a rollback? | |||
|
|||
A metric `controller_modify_volume_errors_total` will indicate a problem with the feature. |
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.
or crashes of ...
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johnbelamaric, msau42, sunnylovestiramisu 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 |
@sunnylovestiramisu Can you add the following content to our KEP? I found it in this PR. https://github.com/kubernetes/enhancements/pull/5333/files#diff-b665d199c610a17172a3409cff970858d9f4f51d01b9d5c59084e38ff6bdd235R846 I think it is good example
|
98846c8
to
0191c23
Compare
Done, added to the flag combination part. |
Discussed with @msau42 about this #5024 (comment). @sunnylovestiramisu will check with sig-architecture to confirm if this is the recommended approach. |
@SergeyKanzhelev pointed us to a reference page: https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/5241-beta-featuregate-promotion-requirements#proposal |
After promotion to GA, the feature is enabled by default but can still be disabled. | ||
Disabling is allowed because it could not be enabled by default during beta due to its | ||
dependency on the off-by-default API group. Immediately enabling it by default with no | ||
fallback option could be too risky. |
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 this reference page here? https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/5241-beta-featuregate-promotion-requirements#proposal
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.
Done
0191c23
to
5f5798f
Compare
/lgtm |
/assign @msau42