You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I'd like: I'd like Bottlerocket to use cgroup v2/the unified cgroup hierarchy. The general ecosystem is moving into this direction:
cgroup v2 has been considered stable for some time in the kernel already.
Kubernetes 1.25 declared support for cgroup v2 as GA with release 1.25.
systemd changed its default to cgroup v2.
Features such as Pressure Stall Information metrics from the kernel are available on a per-cgroup level with cgroup v2.
cgroup v2 support should be available for all variants of Bottlerocket per opt-in. Newly released variants should make cgroup v2 the default (with the chance to opt-out).
Any alternatives you've considered: I don't see any alternatives for the long term. cgroup v1 will receive less attention and testing as time goes by, and likely will be phased out of projects Bottlerocket relies on.
The text was updated successfully, but these errors were encountered:
What I'd like: I'd like Bottlerocket to use cgroup v2/the unified cgroup hierarchy. The general ecosystem is moving into this direction:
cgroup v2 support should be available for all variants of Bottlerocket per opt-in. Newly released variants should make cgroup v2 the default (with the chance to opt-out).
Any alternatives you've considered: I don't see any alternatives for the long term. cgroup v1 will receive less attention and testing as time goes by, and likely will be phased out of projects Bottlerocket relies on.
The text was updated successfully, but these errors were encountered: