Feature Overview (Goal Summary)

Enable independent reporting of Hosted Control Plane (HCP) status outside of Cluster Version Operator (CVO) to simplify upgrade status assessments. This feature enhances reporting for control plane upgrades, providing an easier way to evaluate upgrade readiness and isolate control plane upgrades from nodepool dependencies. It ensures that control planes can be upgraded in the absence of NodePools and that the health status of other operators does not hinder control plane upgrades or report a misleading status.

Goals (Expected User Outcomes)

Primary user: Cluster Service Consumer persona

• Users can independently verify the upgradeability status of the Hosted Control Plane without relying on CVO status.
• API users retain access to critical upgrade statuses, such as ClusterVersionProgress, ClusterVersionUpgradeable, and ClusterVersionAvailable.
• Allows users to upgrade Hosted Control Planes even when no NodePools exist or worker nodes are scaled to zero.
• Enables rapid assessment of upgradeability for Hosted Control Planes, even when customer-side Cluster Operators are unhealthy.

Use Cases

• Hosted Control Plane Upgrade Without Worker Nodes: Control plane upgrade assessments should operate independently when worker nodes are absent or scaled down.
• Upgradeability Assessment with Unhealthy Operators: Enable upgrade path assessments even if customer-side operators report unhealthy states, isolating Hosted Control Plane upgrade concerns from unrelated operator health.

Requirements (Acceptance Criteria)

• Status Reporting: Hosted Control Plane upgrade status must be reportable independently of CVO.
• Upgradeability Checks: Must indicate if the Hosted Control Plane is upgradeable, regardless of NodePool presence