-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
2
-
False
-
None
-
False
-
OCPSTRAT-1579 - Integrate Cluster API (CAPI) in standalone OCP-Phase 3
-
-
-
CLOUD Sprint 264, CLOUD Sprint 265, CLOUD Sprint 266
The current ClusterOperator status conditions—Available, Progressing, Upgradeable, and Degraded—are set by the corecluster controller independently of the status of other controllers.
This approach does not align with the intended purpose of these conditions, which are meant to reflect the overall status of the operator, considering all the controllers it manages.
To address this, we should introduce controller-level conditions similar to the top-level ones. These conditions would influence an aggregated top-level status, which a new controller (the ClusterOperator controller) would then consolidate into the Available, Progressing, Upgradeable, and Degraded conditions.
Moreover, when running `oc get co` against the cluster-capi-operator, only the name and version are returned. The status is not rolled up into the additional columns as expected.
Before GA, this state information should be visible from `oc get co`
- links to