Uploaded image for project: 'CoreOS OCP'
  1. CoreOS OCP
  2. COS-1926

Move RHCOS to RHEL 9.2 in OCP 4.13

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Blocker Blocker
    • openshift-4.13
    • None
    • RHCOS 9 in OCP 4.13
    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-507 - RHCOS based on RHEL 9.2
    • Impediment
    • OCPSTRAT-507RHCOS based on RHEL 9.2
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • 0
    • Approved

      This is the Epic to track the work to add RHCOS 9 in OCP 4.13 and to make OCP use it by default.

       

      CURRENT STATUS: Landed in 4.14 and 4.13

       

      Testing with layering

       

      Another option given an existing e.g. 4.12 cluster is to use layering.  First, get a digested pull spec for the current build:

      $ skopeo inspect --format "{{.Name}}@{{.Digest}}" -n docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev:4.13-9.2
      quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b4cc3995d5fc11e3b22140d8f2f91f78834e86a210325cbf0525a62725f8e099
      

      Create a MachineConfig that looks like this:

      apiVersion: machineconfiguration.openshift.io/v1
      kind: MachineConfig
      metadata:
        labels:
          machineconfiguration.openshift.io/role: worker
        name: worker-override
      spec:
        osImageURL: <digested pull spec>
      

      If you want to also override the control plane, create a similar one for the master role.
       
      We don't yet have auto-generated release images. However, if you want one, you can ask cluster bot to e.g. "launch https://github.com/openshift/machine-config-operator/pull/3485" with options you want (e.g. "azure" etc.) or just "build https://github.com/openshift/machine-config-operator/pull/3485" to get a release image.

          1.
          Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          PX Tracker Sub-task Closed Undefined Unassigned
          3.
          QE Tracker Sub-task Closed Undefined Unassigned
          4.
          TE Tracker Sub-task Closed Undefined Unassigned

              walters@redhat.com Colin Walters
              travier@redhat.com Timothée Ravier
              Votes:
              1 Vote for this issue
              Watchers:
              64 Start watching this issue

                Created:
                Updated:
                Resolved: