-
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 random pod scaledown KEP for stable #4649
Update random pod scaledown KEP for stable #4649
Conversation
|
Welcome @MinpengJin! |
Hi @MinpengJin. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
a3075ba
to
0ad54c7
Compare
/ok-to-test |
Could you please review this PR? @wojtek-t @alculquicondor |
/assign |
/assign @soltysh |
0ad54c7
to
ec1b2ba
Compare
keps/sig-apps/2185-random-pod-select-on-replicaset-downscale/README.md
Outdated
Show resolved
Hide resolved
keps/sig-apps/2185-random-pod-select-on-replicaset-downscale/README.md
Outdated
Show resolved
Hide resolved
keps/sig-apps/2185-random-pod-select-on-replicaset-downscale/README.md
Outdated
Show resolved
Hide resolved
1587750
to
2dd4fbc
Compare
I have already revised it; could please review it again? @alculquicondor |
/lgtm |
/assign @wojtek-t |
/approve PRR /assign @soltysh - for SIG-level approval |
@wojtek-t: GitHub didn't allow me to assign the following users: -, for, SIG-level, approval. Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
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 document hasn't been touched in a while, so it's not up-to-date with the current template, available here: https://github.com/kubernetes/enhancements/blob/master/keps/NNNN-kep-template/README.md
Mostly, it's missing a more detailed testing section (with units, integration and e2e explicitly listed out with coverage and links to testgrid).
But that's not a blocking thing to merge this KEP.
/lgtm
/approve
from sig-apps pov
/hold
for addressing the missing bits
@@ -208,7 +208,7 @@ Beta (v1.22): | |||
- Enable LogarithmicScaleDown feature gate by default | |||
- Enable `sorting_deletion_age_ratio` metric | |||
|
|||
Stable (v1.23): | |||
Stable (v1.31): | |||
- Remove LogarithmicScaleDown feature gate |
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.
Nit, we're not removing the feature gate, yet. We're only locking it to true.
Assumptions that the newest pod will be deleted first may break. | ||
|
||
* **Are there any tests for feature enablement/disablement?** | ||
###### Are there any tests for feature enablement/disablement? | ||
Tests for feature disablement shouldn't be necessary, as this is already an assumed | ||
(but not documented) controller behavior. | ||
|
||
### Rollout, Upgrade and Rollback Planning | ||
|
||
_This section must be completed when targeting beta graduation to a release._ |
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.
You can drop this line entirely.
|
||
* **Is the rollout accompanied by any deprecations and/or removals of features, APIs, | ||
fields of API types, flags, etc.?** | ||
###### Is the rollout accompanied by any deprecations and/or removals of features, APIs, fields of API types, flags, etc.? | ||
No | ||
|
||
### Monitoring Requirements | ||
|
||
_This section must be completed when targeting beta graduation to a release._ |
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.
Similarly - drop this line entirely.
Describe the metrics themselves and the reasons why they weren't added (e.g., cost, | ||
implementation difficulties, etc.). | ||
###### Are there any missing metrics that would be useful to have to improve observability of this feature? | ||
No, we didn't find any other gaps that could be covered by metrics. | ||
|
||
### Dependencies | ||
|
||
_This section must be completed when targeting beta graduation to a release._ |
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.
Again, drop this line, not needed.
@@ -329,28 +336,27 @@ _For beta, this section is required: reviewers must answer these questions._ | |||
_For GA, this section is required: approvers should be able to confirm the | |||
previous answers based on experience in the field._ |
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 line and the above up until title can be safely dropped.
@@ -359,14 +365,14 @@ details). For now, we leave it here. | |||
|
|||
_This section must be completed when targeting beta graduation to a release._ |
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.
Again - remove.
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 have locked the feature gate to true, and removed the unnecessary content @soltysh
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MinpengJin, soltysh, 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 |
2dd4fbc
to
1c2d21c
Compare
/lgtm |
Ref: #2185