-
Feature
-
Resolution: Done
-
Major
-
None
This Feature covers effort in person-weeks of meetings in #wg-managed-ocp-versions where OTA helped SD refine how their doing OCM work would help, and what that OCM work might look like https://issues.redhat.com/browse/OTA-996?focusedId=25608383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-25608383.
Background.
Currently the ROSA/ARO versions are not managed by OTA team.
This Feature covers the engineering effort to take the responsibility of management of OCP version management in OSD, ROSA and ARO from SRE-P to OTA.
Here is the design document for the effort: https://docs.google.com/document/d/1hgMiDYN9W60BEIzYCSiu09uV4CrD_cCCZ8As2m7Br1s/edit?skip_itp2_check=true&pli=1
Here are some objectives :
- Managed clusters would get update recommendations from Red Hat hosted OSUS directly without much middle layers like ClusterImageSet.
- The new design should reduce the cost of maintaining versions for managed clusters including Hypershift hosted control planes.
Presentation from jeder@redhat.com :
- is cloned by
-
OCPSTRAT-1695 Change Management and Maintenance Schedules for Standalone OCP
- Refinement
- relates to
-
HIVE-2366 Expose ClusterVersion status upgrade fields on the hub
- In Progress
- links to