KEP-4033: fulfill beta criteria#125828
Conversation
Signed-off-by: Peter Hunt <[email protected]>
|
hm it seems containerd 2.0 isn't prevelant enough to do the second commit https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/125828/pull-kubernetes-node-e2e-containerd/1807858650790760448/artifacts/tmp-node-e2e-036c16d4-ubuntu-gke-2204-1-29-v20240627/kubelet.log |
|
/triage accepted AFAIR we want this work in 1.31, setting priority accordingly |
|
/retest |
|
I think we're not ready to remove the fallback, maybe we should retarget that to GA |
|
@haircommander Can we update the user facing change note if we aren't dropping the fallback? |
|
good point, updated |
|
LGTM label has been added. DetailsGit tree hash: 67b48543a0c0276705ea41092f0fa5d69f830a15 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, mrunalp The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
Changelog suggestion -Bump the KubeletCgroupDriverFromCRI feature gate to beta and true by default. The kubelet will continue to use its KubeletConfiguration field as a fallback if the CRI implementation doesn't support this feature.
+Promoted CRI communication of cgroup driver mechanism, to beta.
+The `KubeletCgroupDriverFromCRI` feature gate is now beta and enabled by default. This means that the kubelet
+queries the container runtime using CRI to discover the mechanism for cgroup management that the kubelet
+will use; if the container runtime doesn't support this, the kubelet falls back to loading this from its configuration
+file (you can also use the deprecated `--cgroup-driver` command line argument). |
|
Also, make sure to update https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/; the text
has become stale. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
bump the feature gate to beta, and remove fallback, as described in the KEP
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: