-
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
kep-4622: promote topologyMnagaer policy: max-allowable-numa-nodes to GA #5166
base: master
Are you sure you want to change the base?
Conversation
cyclinder
commented
Feb 12, 2025
- One-line PR description: topologyMnagaer policy: max-allowable-numa-nodes to GA(1.33)
- Issue link: KEP-4622: Add a TopologyManager policy option for MaxAllowableNUMANodes #4622
- Other comments:
- it was created in 1.31 as a beta feature: KEP-4622: New TopologyManager Policy: max-allowable-numa-nodes #4624
- The GA graduation would mean:
- the max-allowable-numa-nodes option will graduate to GA
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cyclinder The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
initial review. We're very close to the deadline, but let's try to have this in
|
||
<!-- | ||
**Note:** This checklist is iterative and should be reviewed and updated every time this enhancement is being considered for a milestone. | ||
--> | ||
|
||
[kubernetes.io]: https://kubernetes.io/ | ||
[kubernetes/enhancements]: https://git.k8s.io/enhancements | ||
[kubernetes/kubernetes]: https://git.k8s.io/kubernetes |
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.
why was this removed?
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.
vscode remove it😅, revert it now
For GA: | ||
|
||
- degrading the node and checking the node is reported as degraded | ||
|
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.
why was this removed?
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 kinda don't remember the context here, do we need this e2e to test it?
@@ -249,7 +244,7 @@ For GA: | |||
|
|||
#### GA | |||
|
|||
- Add a metrics: `kubelet_topology_manager_admission_time`. | |||
- Add a metric: `kubelet_topology_manager_admission_time`. |
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 add a note documenting we can use an existing metric
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.
updated.
- `TopologyManagerPolicyBetaOptions` | ||
- `TopologyManagerPolicyOptions` | ||
- `TopologyManagerPolicyOptions` - going to be locked to true once GA |
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.
no need to mention the locking, it's the standard process for each 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.
removed.
|
||
# The following PRR answers are required at alpha release | ||
# List the feature gate name and the components for which it must be enabled | ||
feature-gates: | ||
- name: "TopologyManagerPolicyBetaOptions" | ||
components: |
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.
why was this removed?
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'm curious too, maybe vscode's markdown linter removed it, revert it now.
Signed-off-by: Cyclinder Kuo <[email protected]>
I am supportive of graduating features to GA but not sure if we will get PRR in time as this came in late. |
same. I'll still be helping here with the reviews and cleaning up the feature, but if we miss the deadline (as unfortunately seems likely) is not too bad: we can prepare and be ready for a early 1.34 merge. |