Skip to content

node: fg: remove DisableCPUQuotaWithExclusiveCPUs - #141758

Open
ffromani wants to merge 1 commit into
kubernetes:masterfrom
ffromani:remove-disable-quota-fg
Open

node: fg: remove DisableCPUQuotaWithExclusiveCPUs#141758
ffromani wants to merge 1 commit into
kubernetes:masterfrom
ffromani:remove-disable-quota-fg

Conversation

@ffromani

@ffromani ffromani commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

The FG removal was planned for 1.38, so delete it

Which issue(s) this PR is related to:

Related to #127525

Special notes for your reviewer:

Do we need to obey to emulation support for kubelet-only FGs? see #141758 (comment)

Does this PR introduce a user-facing change?

NONE

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

N/A

It was slated for removal in 1.38, so we can remove it.

Signed-off-by: Francesco Romani <fromani@redhat.com>
@kubernetes-prow kubernetes-prow Bot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. 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 Sep 1, 2026
@kubernetes-prow

Copy link
Copy Markdown
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.

Details

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.

@kubernetes-prow kubernetes-prow Bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Sep 1, 2026
@ffromani

ffromani commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

/sig node

@kubernetes-prow kubernetes-prow Bot added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Sep 1, 2026
@kubernetes-prow kubernetes-prow Bot removed the do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 1, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

Details 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

@ffromani

ffromani commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

turns out we need to wait more than anticipated?

$ ./hack/update-featuregates.sh 
found 234 features in FeatureSpecMap var defaultVersionedKubernetesFeatureGates in file: /home/fromani/go/src/k8s.io/kubernetes/pkg/features/kube_features.go
found 3 features in FeatureSpecMap var defaultVersionedKubernetesFeatureGates in file: /home/fromani/go/src/k8s.io/kubernetes/staging/src/k8s.io/apiextensions-apiserver/pkg/features/kube_features.go
found 38 features in FeatureSpecMap var defaultVersionedKubernetesFeatureGates in file: /home/fromani/go/src/k8s.io/kubernetes/staging/src/k8s.io/apiserver/pkg/features/kube_features.go
found 3 features in FeatureSpecMap of func featureGates in file: /home/fromani/go/src/k8s.io/kubernetes/staging/src/k8s.io/component-base/logs/api/v1/kube_features.go
found 1 features in FeatureSpecMap of func featureGates in file: /home/fromani/go/src/k8s.io/kubernetes/staging/src/k8s.io/component-base/metrics/features/kube_features.go
found 2 features in FeatureSpecMap of func featureGates in file: /home/fromani/go/src/k8s.io/kubernetes/staging/src/k8s.io/component-base/zpages/features/kube_features.go
found 3 features in FeatureSpecMap var versionedCloudPublicFeatureGates in file: /home/fromani/go/src/k8s.io/kubernetes/staging/src/k8s.io/controller-manager/pkg/features/kube_features.go
Failed to update versioned feature list: 
feature DisableCPUQuotaWithExclusiveCPUs cannot be removed until version 1.40 (required for emulation support)exit status 1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it needs to be removed in 1.40 (GA+3)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe just update the comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but does the kubelet support feature emulation? IIRC still not

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, it's a kubelet-only FG. Yeah you are right I don't think kubelet supports emulation

Should the script somehow detect when a FG is used only by kubelet and skip this check if so? Sounds a bit complicated

@ffromani

ffromani commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

/hold

see comments about emulated version

@kubernetes-prow kubernetes-prow Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 1, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

@ffromani: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubernetes-verify d01f1d9 link true /test pull-kubernetes-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/kubelet cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Development

Successfully merging this pull request may close these issues.

2 participants