Cgroups version 2 on Red Hat OpenShift Container Platform: general information

Solution Verified - Updated -

Environment

  • Red Hat OpenShift Container Platform (RHOCP).
    • 4.

Issue

  • What are the advantages of Cgroups version 2 over version 1?
  • Which Cgroups versions are supported for every RHOCP release?
    • What are the deprecation and removal dates of Cgroups 1?
    • If the nodes of a cluster are running Cgroups 1 and it is tried to upgrade it to a RHOCP version only compatible with Cgroups 2, what would be the consequences? Would the upgrade be blocked?
  • Can the Cgroups version in an existing cluster be upgraded or downgraded?
  • Is it supported to mix nodes with Cgroups version 1 and version 2 in the same cluster?

Resolution

Application workloads perspective

RHOCP 4.19 and later versions

clusteroperator/machine-config is not upgradeable because Cluster is using deprecated cgroup v1, which is removed in 4.19.  Please update the ‘cgroupMode’ in the ‘cluster’ object of nodes.config.openshift.io resource type to ‘v2’. This can be changed back to ‘v1’ while on 4.18, but must be ‘v2’ before you update to 4.19.  Once updated to 4.19, cgroup v1 is no longer an option. Please refer to https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html-single/nodes/index#nodes-clusters-cgroups-2_nodes-cluster-cgroups-2
  • On RHOCP 4.19 and later versions, Cgroups cannot be downgraded to version 1.

RHOCP 4.13 to 4.18 versions

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments