Feature Overview (aka. Goal Summary)  

CgroupV2 is GA as of OCP 4.13 . 

RHEL 9 is defaulted to V2 and we want to make sure we are in sync 

V1 support in system d will end by end of 2023

Goals (aka. expected user outcomes)

1. Default for new clusters 
2. non default for upgrading clusters means customer with cgroup v1 upgrading from 4.13 to 4.14 they will still have cgroup v1 ( it will not be a force migration)
3. Upgrading customers will have option to upgrade to V2 as day 2 

What need to be done 

1. Default in 4.14
2. Change 4.13Z so that so upgraded cluster to 4.14 stays on V1
3. NTO changes to default to v1
4. Test with cgroupv1 (where cgroupv2 were previously)
5. Release notes on applications that are effected 
6. If you run third-party monitoring and security agents that depend on the cgroup file system, update the agents to versions that support cgroup v2.
7. If you run cAdvisor as a stand-alone DaemonSet for monitoring pods and containers, update it to v0.43.0 or later.
8. If you deploy Java applications, prefer to use versions which fully support cgroup v2:
9. OpenJDK / HotSpot: jdk8u372, 11.0.16, 15 and later
10. IBM Semeru Runtimes: jdk8u345-b01, 11.0.16.0, 17.0.4.0, 18.0.2.0 and later
11. IBM Java: 8.0.7.15 and later
12.  

1. Announcement blog (and warning about force upgrade in the future)
2. Reach out to TRT

https://docs.google.com/document/d/1i6IEGjaM0-NeMqzm0ZnVm0UcfcVmZqfQRG1m5BjKzbo/edit