This repository is used to track all work for the BCGov Platform Services Team (This includes work for: 1. Platform Experience, 2. Developer Experience 3. Platform Operations/OCP 3)
Describe the epic
Top level epic to track all OCP 4.13 upgrade work separate of quarters or sprints. Sub tasks may end up in multiple epics for better tracking and grouping.
Proposed Implementation Schedule
This schedule is subject to change until we have completed the first LAB upgrade to OPC 4.13. Currently we do feel that the timelines for PROD clusters have enough lee-way to not likely need extension.
First LAB cluster is estimated to be completed prior to September 20th
Second LAB cluster will be completed the week of October 9th
RFC for SILVER - CHG0052476 & CHG0052425 - MCS SILVER - 2023 Q4 Patching - Upgrade to OCP 4.13.12 planned for October 15 - Nov 3
RFC for GOLD - CHG0052477 & CHG0052479 - MCS GOLD - 2023 Q4 Patching - Upgrade to OCP 4.13.12 planned for November 5 -10
RFC for GOLDDR CHG0052478 & CHG0052480 - MCS GOLDDR - 2023 Q4 Patching - Upgrade to OCP 4.13.12 planned for November 19 - 24
Some lee-way between doing the upgrades for the two LAB clusters accounts for some staffing level changes due to vacations, and also allows us to reach out to Matt Robson one last time to make sure there's not a new 4.13.x release about to drop that we absolutely want to include, and thus need to quickly go through LAB upgrades again.
Definition of done
[x] All clusters upgraded to OCP 4.13 and all post-upgrade tasks completed.
Describe the epic Top level epic to track all OCP 4.13 upgrade work separate of quarters or sprints. Sub tasks may end up in multiple epics for better tracking and grouping.
Additional context https://docs.openshift.com/container-platform/4.13/release_notes/ocp-4-13-release-notes.html Tool for checking upgrade matrix: https://access.redhat.com/labs/ocpupgradegraph/update_path/
Proposed Implementation Schedule This schedule is subject to change until we have completed the first LAB upgrade to OPC 4.13. Currently we do feel that the timelines for PROD clusters have enough lee-way to not likely need extension.
Some lee-way between doing the upgrades for the two LAB clusters accounts for some staffing level changes due to vacations, and also allows us to reach out to Matt Robson one last time to make sure there's not a new 4.13.x release about to drop that we absolutely want to include, and thus need to quickly go through LAB upgrades again.
Definition of done