Closed AkihiroSuda closed 2 months ago
/sig testing
cc @BenTheElder
In a sig-node meeting a few weeks back, we did talk about making cgroups v2 the default. cc @dchen1107 @SergeyKanzhelev
It is possible to get a cgroupv2 cluster but you may have to target it specifically. We have examples of cgroupv2 jobs.
This is also /sig k8s-infra
We have https://github.com/kubernetes/k8s.io/issues/5276
In a sig-node meeting a few weeks back, we did talk about making cgroups v2 the default. cc @dchen1107 @SergeyKanzhelev
It is possible to get a cgroupv2 cluster but you may have to target it specifically. We have examples of cgroupv2 jobs.
This issue is about the cluster on which we run the prowjob pods, so that nested local clusters (like KIND, hack/local-up-cluster.sh) run on cgroupsv2.
We could create a cgroupsv2 node-pool or cluster on GKE and run some jobs there ^1, someone else from k8s infra will have to chime in for the EKS clusters. @xmudrii
fyi all the ci jobs wiht al2023
in their names are cgroupsv2
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
/remove-lifecycle stale
We're still going to want to sort this out at some point, eventually this will be the default even ...
we have a lot of cgroupv2 jobs now ... https://prow.k8s.io/?job=*cgroupv2*
we have a lot of cgroupv2 jobs now ... https://prow.k8s.io/?job=*cgroupv2*
Yes, and that's probably more than enough for now, but at some point the prow clusters will also wind up migrating, and we could make sure kind etc are tested that way.
For now, I guess the cloudy E2E are enough and we can track this https://github.com/kubernetes/k8s.io/issues/5276 instead
Currently
k8s-infra-prow-build
andeks-prow-build-cluster
are still using cgroup v1, although many users should have already switched to cgroup v2. It is still possible to create a custom cluster with Boskos, but this is often complicated and hard to test on laptop.Any chance to have cgroup v2 node pool in community clusters, or just have a new cluster dedicated for cgroup v2?