Request: cgroup v2 node pool in community clusters

[AkihiroSuda]

Currently k8s-infra-prow-build and eks-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?

[AkihiroSuda]

/sig testing

[ameukam]

cc @BenTheElder

[kannon92]

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.

[BenTheElder]

This is also
/sig k8s-infra

We have kubernetes/k8s.io#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 ¹, someone else from k8s infra will have to chime in for the EKS clusters. @xmudrii

Footnotes

1. https://cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#cgroup-mode-options ↩

[dims]

fyi all the ci jobs wiht al2023 in their names are cgroupsv2

• https://testgrid.k8s.io/amazon-ec2-al2023
• https://testgrid.k8s.io/amazon-ec2-node