-
Initiative
-
Resolution: Unresolved
-
Critical
-
None
-
None
Feature Overview
Hosted Control Planes (aka HyperShift) is an OpenShift form factor that optimizes for cost and time-to-provision as well as portability cross-cloud with a strong separation of concerns between management and workloads(for more information about HyperShift, check [1]). While HyperShift is OpenShift, it is still a different technical architecture, as a result, it becomes achieves functional parity with existing standalone OpenShift architecture and part of this effort is to ensure that HyperShift deployed OpenShift is compatible with existing layered operators.
Main Story
When deploying and life cycling OpenShift clusters with Hosted Control Planes (aka HyperShift), I want to deploy any supported OpenShift layered operator to fully utilize OpenShift value-add.
Requirments
- Important layered operators are supported first (operators included in OKE/OCP/OPP)
- All other layered operators should be qualified on HyperShift by their respective teams
Outcome
The compatibility of all layered operators is documented in [2]. Also results of operator using RBAC to read/write to MachineConfig/MachineConfigPool thanks to the operator framework team.
References
- is related to
-
CMP-1234 HyperShift Support for Compliance Operator
- Closed
-
PODAUTO-65 Failed to install Vertical Pod Autoscaler Operator on Hypershift guest cluster
- To Do
- relates to
-
OCPBUGS-3410 Failed to install File Integrity Operator on Hypershift guest cluster
- New
-
OCPSTRAT-127 Continued STS enablement for selected OLM-managed operators
- Backlog
-
OCPSTRAT-6 Tokenized Auth Enablement for OLM-managed Operators on Cloud Providers
- In Progress
-
OCPSTRAT-103 Ensuring the Control Plane is Fully Decoupled for Hosted Control Planes
- Closed
- links to