-
Epic
-
Resolution: Done
-
Blocker
-
None
-
None
-
Designate nodes for hosting control-plane to avoid charging
-
BU Product Work
-
False
-
None
-
False
-
Green
-
To Do
-
OCPSTRAT-591 - HyperShift Core Component Readiness for GA - Part I
-
Impediment
-
OCPSTRAT-591HyperShift Core Component Readiness for GA - Part I
-
0% To Do, 0% In Progress, 100% Done
-
0
-
0
-
0
-
Approved
Overview
Hosted control planes allow hosting OpenShift cluster control planes on hosting service clusters (aka management clusters). We don't want to charge customers owning the hosting service clusters to provide CPaaS for control planes.
Goal
Be able to distinguish control-plane from workloads even when the hosting service cluster is a HyperShift hosted cluster, and make sure subscription-manager does not count control-planes as workloads.
Hypershift should have the ability to land control plane resources in particular Nodes targeted with a label i.e "infra".
- is documented by
-
ACM-4338 Designate nodes for hosting control-plane to avoid charging
- Closed
- relates to
-
OCPSTRAT-103 Ensuring the Control Plane is Fully Decoupled for Hosted Control Planes
- Closed
1.
|
Docs Tracker | Closed | Laura Hinson | ||
2.
|
PX Tracker | Closed | Unassigned | ||
3.
|
QE Tracker | Closed | Jie Zhao | ||
4.
|
TE Tracker | Closed | Unassigned |