Road to OKD 4.8

[vrutkovs]

OCP code base is about to be frozen, so I'll keep a list of things to fix before we can put OKD 4.8 in stable

TODO:

• Branch installer in release-4.8-okd
• Branch machine-config-operator in release-4.8-okd
• Branch okd-machine-os in release-4.8
• Create release-controller configuration
• Reconfigure CI to use there branches, create necessary imagestreams
  • cluster-samples-operator
  • cluster-update-keys
  • installer
  • machine-config-operator
  • origin
  • ovn-kubernetes
  • operator-marketplace
• Update okd-machine-os release-4.8 branch to use stable fedora-coreos-config
• Setup promotion jobs
  okd-machine-os depends on submodule bumps, so no promotion jobs are available anymore
• Setup OKD 4.7 -> 4.8 periodic upgrade jobs
• Check 4.7 -> 4.8 upgrade jobs to evaluate stability
  • Fix bugs found in periodics:
    • e2e-*-ovn-upgrade are permafailing on service/ingress disruption - 4.9 bug
    • release-4.8 cherry-pick of ^
    • [sig-network-edge] Application behind service load balancer with PDB is not disrupted
      Worked it around by making an upgrade job without disruption tests
• Fix issues after first release
  • Rebase installer/machine-config-daemon
  • v2s1 images make release unmirrorable
  • Invalid kubelet used (1.22 instead of 1.21)
  • Bump image content to make sure latest fixes are included
  • Update marketplace image
• Update README in openshift/okd:
  • https://github.com/vrutkovs/installer/blob/fcos-master-devel/docs/user/overview.md#coreos-bootimages - how to find initial VM image
• Add upgrade edges after fixed 4.8 stable is released

[alibo]

@vrutkovs I know you're trying hard to release the new version soon and I really appreciate it. I just want to ask you is there any ETA (even a rough ETA) on when OKD 4.8 will be released?

[vrutkovs]

We can release 4.8 when 4.7 -> 4.8 upgrade jobs are setup and reliably pass. The former can be done quickly, the latter depends on found issues. Think couple of weeks for instance?

[alibo]

thank you for your reply and clarification 👍

[alibo]

I guess the last two items (Update this repo docs and Check 4.7 -> 4.8 upgrade jobs to evaluate stability ) and cluster-samples-operator are done? (considering the related PRs are merged)

[brianotte]

Is there any new news related to 4.8?

[m-yosefpor]

from Vadim's release notes:

Still no luck with safe 4.7->4.8 upgrade path, blocked by OVN bug #1929396. This prevents us from releasing OKD 4.8 stable

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

[m-yosefpor]

see full updates here: https://hackmd.io/YJBn04R5TDi5Sm9XbOGwZA

[brianotte]

Hello All,

I did not see any updates in the September 28th meeting on https://hackmd.io/YJBn04R5TDi5Sm9XbOGwZA related to OVN bug #1929396, which was blocking 4.8 upgrade from 4.7.

Is there any information that can be shared related to Openshift 4.8?

Please let us know.

Thank you.

Brian

[vrutkovs]

https://github.com/openshift/okd/releases/tag/4.8.0-0.okd-2021-10-01-221835 has been released.

the blocking bug was not resolved, but I found a way to work it around. Note, that router / LB connections may be disrupted (up to 30% of the time in our tests) during update, so plan upgrades accordingly.

[vrutkovs]

Next up - Road to OKD 4.9