Skip to content
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.

Sign up for GitHub

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

Jump to bottom

mark QOSReserved as deprecated and enable by default #130022

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

mark QOSReserved as deprecated and enable by default #130022

wants to merge 1 commit into from

Conversation

pacoxu
Copy link
Member

@pacoxu pacoxu commented Feb 7, 2025 •
edited
Loading

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

deprecate the FG as it is alpha since v1.11.

When the FG is enabled, kubelet will respect qosReserved setting. So I just deprecate the FG and respect the qosReserved.

Which issue(s) this PR fixes:

Fixes kubernetes/enhancements#5046

Special notes for your reviewer:

I think there are two choices

  1. deprecated it: remove the qosReserved setting.
  2. deprecated it: respect the qosReserved setting. [This PR now]
  3. promote it to beta and then GA: respect the qosReserved setting
  4. remove the fg: keep the qosReserved setting
  5. remove the fg: remove the qosReserved setting

I think 2\3\4 are OK. I prefer 2 > 4 > 3.

Currently, I prefer to the second choice since this FG is merely a gate and you need to additionally specify the qosReserved to use this feature.

kubernetes/pkg/kubelet/cm/qos_container_manager_linux.go

Lines 348 to 377 in d36322f

if utilfeature.DefaultFeatureGate.Enabled(kubefeatures.QOSReserved) {
for resource, percentReserve := range m.qosReserved {
switch resource {
case v1.ResourceMemory:
m.setMemoryReserve(qosConfigs, percentReserve)
}
}
updateSuccess := true
for _, config := range qosConfigs {
err := m.cgroupManager.Update(config)
if err != nil {
updateSuccess = false
}
}
if updateSuccess {
klog.V(4).InfoS("Updated QoS cgroup configuration")
return nil
}
// If the resource can adjust the ResourceConfig to increase likelihood of
// success, call the adjustment function here. Otherwise, the Update() will
// be called again with the same values.
for resource, percentReserve := range m.qosReserved {
switch resource {
case v1.ResourceMemory:
m.retrySetMemoryReserve(qosConfigs, percentReserve)
}
}
}

Does this PR introduce a user-facing change?

Mark feature gate QOSReserved as deprecated

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: https://github.com/kubernetes/enhancements/issues/5046

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 7, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Feb 7, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pacoxu
Once this PR has been reviewed and has the lgtm label, please assign jsturtevant for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pacoxu pacoxu mentioned this pull request Feb 7, 2025
Open
4 tasks
@pacoxu
Copy link
Member Author

pacoxu commented Feb 7, 2025

/cc @haircommander @mtaufen
/assign @derekwaynecarr @sjenning

@pacoxu
Copy link
Member Author

pacoxu commented Feb 11, 2025

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@smarterclayton smarterclayton Awaiting requested review from smarterclayton

@soltysh soltysh Awaiting requested review from soltysh

@haircommander haircommander Awaiting requested review from haircommander

@mtaufen mtaufen Awaiting requested review from mtaufen

Assignees

@sjenning sjenning

@derekwaynecarr derekwaynecarr

Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/node Categorizes an issue or PR as relevant to SIG Node. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
SIG Node: code and documentation PRs
Status: Triage
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Allows resource reservations at the QoS level preventing pods at lower QoS levels
4 participants
@pacoxu @k8s-ci-robot @sjenning @derekwaynecarr