-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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-2400] Add the ability to set a system-reserved quantity of swap on a node #105019
Comments
/sig node |
/kind api-change |
I will work on it if my other tasks are not urgent. (I would like to be a backup.) |
/assign |
@pacoxu: GitHub didn't allow me to assign the following users: jonyhy96. Note that only kubernetes members, 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/test-infra repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/milestone v1.24 |
Hi 👋 . Checking in from bug triage for 1.24, there is no activity on this PR from last 2-3 weeks, Should we be tracking progress on this issue for 1.24 release? |
We are waiting on tests to be fixed before we merge the PR. It may have a little risk since the code freeze will come in two weeks. |
@pacoxu Hi 👋 Im checking in from bug triage team for release 1.24, we are very near to code freeze, would we be able to pull this in since you mentioned there is a little risk ? |
/milestone clear |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
This issue is labeled with You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
/triage accepted |
@iholder101: Closing this issue. 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/test-infra repository. |
What would you like to be added:
Add the ability to set a system-reserved quantity of swap on a node.
This should be a single PR.
Why is this needed:
See https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2400-node-swap#beta
The text was updated successfully, but these errors were encountered: