Open kfox1111 opened 3 months ago
Running with cggroups v2 is now by default https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cgroup-drivers minikube should already be doing this. I dont think there should be any issue.
/kind support
Looks like its probably just switching the kvm image to use v2. Right now its v1. according to https://kubernetes.io/docs/concepts/architecture/cgroups/#check-cgroup-version tmpfs means v1.
minikube ssh -- stat -fc %T /sys/fs/cgroup/
tmpfs
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
What Happened?
Would like to test with cgroups v2 enabled
Attach the log file
It seems to only support cgroups v1
Operating System
Redhat/Fedora
Driver
KVM2