-
Feature
-
Resolution: Done
-
Major
-
None
-
Strategic Portfolio Work
-
False
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
-
0
Feature Overview
One of the benefits of HyperShift's externalized control-plane is the decoupled life-cycle of the CP and the DP. However, since this model is different from the standalone version of OpenShift, some questions need to re-asked:
- cs?
Goal(s)
- Sync with upstream CAPI on how upgrades / in-place updates of workers are handled.
- Involve the MCO team to identify whether it would be possible to add HyperShift functionality to the code-base Vs. forking/re-writing a new component.
- Identify the process for integration with the Cincinnati graph.
- Adapt the HyperShift APIs to reflect any changes required to support control-plane and workers upgrades.
- is related to
-
OCPSTRAT-417 Hypershift update phase 2 - Conditional updates should work for self-managed hosted control planes (HCP)
- Closed
-
OCPSTRAT-326 Implement HyperShift Infrastructure & Machine Management Models
- Closed
- relates to
-
OTA-791 Hosted control planes (HyperShift) should consume recomended updates from OSUS
- Closed
-
HOSTEDCP-72 Support running control planes of different versions on the same management cluster
- Closed
-
HOSTEDCP-72 Support running control planes of different versions on the same management cluster
- Closed