Uploaded image for project: 'OpenShift Node'
  1. OpenShift Node
  2. OCPNODE-1715

Default cgroup v2 in 4.14

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • openshift-4.14
    • None
    • None
    • Default cgroup v2 in 4.14
    • BU Product Work
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-696 - Make CgroupV2 default in 4.14
    • OCPSTRAT-696Make CgroupV2 default in 4.14
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      New OpenShift installs use Control Groups version 2 by default, also known as cgroup2 or cgroupsv2. This includes many bug fixes, performance improvements, and the possibility of integration with new features. cgroupsv1 are still used in upgraded clusters which have install born dates prior to 4.14. and can still be used by changing the CgroupMode of the Node Config object to be 'v1'.
      Show
      New OpenShift installs use Control Groups version 2 by default, also known as cgroup2 or cgroupsv2. This includes many bug fixes, performance improvements, and the possibility of integration with new features. cgroupsv1 are still used in upgraded clusters which have install born dates prior to 4.14. and can still be used by changing the CgroupMode of the Node Config object to be 'v1'.
    • Feature

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Make cgroup v2 default in 4.14

      Why is this important?

      • To bring the advantages of cgroup v2 to users of 4.14+

      Scenarios

      1. As a cluster owner I want to run my system using cgroup v2 for it's added benefits. 

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              harpatil@redhat.com Harshal Patil
              harpatil@redhat.com Harshal Patil
              Sunil Choudhary Sunil Choudhary
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: