-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-2837: Beta Graduation Criteria for 1.34 #5362
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-2837: Beta Graduation Criteria for 1.34 #5362
Conversation
|
Skipping CI for Draft Pull Request. |
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.
If a user attempts to configure scope=container for such a pod
Topology Manager scope (container/pod) is a node level setting.
3da0389 to
471221b
Compare
|
/sig autoscaling |
b776557 to
3f3e191
Compare
|
/assign @tallclair |
3f3e191 to
5e556cc
Compare
5b51362 to
1d8e4df
Compare
|
Can we summarize in the description and/or the commit message the proposed changes (some are lost in the discussion threads)? |
|
/lgtm |
1d8e4df to
83bf364
Compare
soltysh
left a comment
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.
The 3 PRR questions (tests for enablement/disablement, upgrade->downgrade->upgrade and new fields estimation) are the remaining blocking items.
| - [VPA](#vpa-1) | ||
| <!-- /toc --> | ||
|
|
||
|
|
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.
Please make sure to include the second one in the release, it's currently missing lead-opted-in label and milestone set. This needs to be done by sig-node leads.
| * Resource Allocation Managers i.e. Topology, Memory and CPU managers support with | ||
| Pod-level resources is past alpha. | ||
| ### Upgrade / Downgrade 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.
- In
###### Are there any tests for feature enablement/disablement?you're describing tests that were planned for alpha, can you add there links to those tests? ###### Were upgrade and rollback tested? Was the upgrade->downgrade->upgrade path tested?is missing answers, it currently mentions only that it will be tested? Was it? Can you describe the steps?- In
###### Will enabling / using this feature result in increasing size or count of the existing API objects?you're missing estimated size increase, and amount of new objects (see comments above that section)
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.
Addressed the concerns.
raywainman
left a comment
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.
LGTM for SIG-Autoscaling
83bf364 to
88c0e23
Compare
@sanposhiho lgmt'd PR after @ndixita resolved the review feedback
88c0e23 to
a088c6e
Compare
Signed-off-by: ndixita <ndixita@google.com>
a088c6e to
e8c51a7
Compare
|
/lgtm |
soltysh
left a comment
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.
/approve
the PRR section
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jackfrancis, mrunalp, ndixita, sanposhiho, soltysh 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 |
Uh oh!
There was an error while loading. Please reload this page.