node: fg: remove DisableCPUQuotaWithExclusiveCPUs - #141758
Conversation
It was slated for removal in 1.38, so we can remove it. Signed-off-by: Francesco Romani <fromani@redhat.com>
|
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The DetailsInstructions 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. |
|
/sig node |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ffromani The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
turns out we need to wait more than anticipated? |
There was a problem hiding this comment.
Yeah it needs to be removed in 1.40 (GA+3)
There was a problem hiding this comment.
maybe just update the comment
There was a problem hiding this comment.
but does the kubelet support feature emulation? IIRC still not
There was a problem hiding this comment.
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
|
/hold see comments about emulated version |
|
@ffromani: The following test failed, say
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. DetailsInstructions 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. |
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?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
N/A