Road to OKD 4.10

[vrutkovs]

• Branch machine-config-operator in release-4.10-okd
  Fork is no longer required

• Branch okd-machine-os in release-4.10

• Create release-controller configuration
  release-okd-4.11.json: add verify jobs for OKD 4.11 nightlies openshift/release#25808

• Reconfigure CI to use there branches, create necessary imagestreams (can be completed later)

  • cluster-samples-operator
  • cluster-update-keys
  • origin
  • origin-branding
  • ovn-kubernetes
  • operator-marketplace

• Update okd-machine-os release-4.10 branch to use stable fedora-coreos-config
  [release-4.10] Switch fedora-coreos-config to stable openshift/okd-machine-os#296

• Setup upgrade readiness jobs
  OKD: add upgrade jobs for 4.9->4.10 and 4.10->4.11 openshift/release#26165

• Monitor upgrade job

  • Successful upgrade

• Fix found upgrade issues

  • https://bugzilla.redhat.com/show_bug.cgi?id=2058729

• Wait for first OCP 4.10 to be released

• Rebase okd-machine-os

• Release a new stable

• Bump FCOS version in openshift-installer

• Docs: add a note that BM IPI is now available

• Update Assisted Instaler okd-configmap to use OKD 4.10

[alibo]

Is it also possible to upgrade directly from 4.8 to 4.10?

[vrutkovs]

No, your control plane needs to be updated from 4.8 to 4.9 to 4.10. You can upgrade workers from 4.8 to 4.10 directly though - see https://docs.openshift.com/container-platform/4.8///updating/preparing-eus-eus-upgrade.html

[bdlink]

Resolving the CEPH issue in a way that does not require recreating PVs and PVCs is important for upgrades. Perhaps that should be added here?

[vrutkovs]

That would require us downgrading the kernel to 5.15, which is too significant imo. Lets discuss it in the bug - if the workaround is too complicated for most users we may consider it

[fortinj66]

unfortunately the 'fix' is destructive to the currently existing PVC/PVs... I'll be backing up and volumes that have data I need to keep and then restoring after the fix.

Only other option (besides downgrading the kernel) is to see if there is a kernel fix down the road. That could be a long time coming though.

[vrutkovs]

Road to 4.11