Open neolit123 opened 9 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
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.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
the new feature gate was added in a previous release and is planned for beta in 1.31: kubernetes/enhancements#4033
This is planned to be beta in this release cycle.
the new feature gate was added in a previous release and is planned for beta in 1.31: kubernetes/enhancements#4033
This is planned to be beta in this release cycle.
- We may use it if the FG is enabled and the cgroup driver can be detected from the CRI. And we can fall back to our previous logic if not.
i don't think we have any remaining logic for this, do we? we just set the cgroup driver to systemd.
KubeletCgroupDriverFromCRI went BETA in 1.31 https://github.com/kubernetes/kubernetes/pull/125828/
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
https://github.com/kubernetes/enhancements/issues/4033#issuecomment-2318800589
original k/k ticket: https://github.com/kubernetes/kubernetes/issues/99808
the new feature gate was added in a previous release and is planned for beta in 1.31: https://github.com/kubernetes/enhancements/issues/4033
once GA we should remove this page: https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/
perhaps SIG node and feature owners will update: https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cgroup-drivers
users would still be required to pick a driver and configure it on the side of container runtimes (e.g. containerd).