-
Outcome
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
Product / Portfolio Work
-
38% To Do, 19% In Progress, 44% Done
-
False
-
-
False
-
None
Outcome Overview
Once all Features and/or Initiatives in this Outcome are complete, what tangible, incremental, and (ideally) measurable movement will be made toward the company's Strategic Goal(s)?
To maximize efficiency, operational consistency, and customer satisfaction, we want to achieve full feature and operational parity between ROSA with Hosted Control Planes (ROSA-HCP) and ROSA Classic (based on classic/standalone OpenShift) deployments.
This simplifies management across large-scale hybrid or multi-cloud environments, and ensures all use cases, integrations, and compliance requirements supported in classic OpenShift are also available and equally robust in the hosted control plane model. By aligning capabilities in areas such as API management, authentication, cluster lifecycle operations, Operator support, and security, we will unlock broader adoption of HCP, streamline governance, and ensure a uniform user experience regardless of deployment model.
Success Criteria
What is the success criteria for this strategic outcome? Avoid listing Features or Initiatives and instead describe "what must be true" for the outcome to be considered delivered.
- All major core OpenShift features (such as networking, storage, RBAC, monitoring, logging, auto-scaling, upgrades, cluster operators, and security boundaries) are available and function similarly in hosted control plane clusters as in classic/standalone OpenShift clusters.
- User experience for cluster administrators and app developers is consistent between hosted and standalone environments (same APIs, lifecycle management, troubleshooting, and automation workflows).
- Multi-cluster management operations (creation, scaling, backup, recovery) deliver the same outcome and reliability as classic clusters.
- Completion of HCP Priority Asks for ROSA
Expected Results (what, how, when)
What incremental impact do you expect to create toward the company's Strategic Goals by delivering this outcome? (possible examples: unblocking sales, shifts in product metrics, etc. {}{} provide links to metrics that will be used post-completion for review & pivot decisions). {}For each expected result, list what you will measure and +when you will measure it (ex. provide links to existing information or metrics that will be used post-completion for review and specify when you will review the measurement such as 60 days after the work is complete)
- Completion of HCP Priority Asks for ROSA.
Post Completion Review – Actual Results
After completing the work (as determined by the "when" in Expected Results above), list the actual results observed / measured during Post Completion review(s).
- incorporates
-
OCPBUGS-38245 AllowedCIDRBlocks is not enforced on PrivateLink AWS clusters
-
- New
-
-
HOSTEDCP-1442 Create separate SGs for VPC endpoint and Workers
-
- Closed
-
-
OCPSTRAT-1615 [Observability] Enhanced Debuggability for HyperShift Cluster NodePool Failures
-
- New
-
-
-
- Backlog
-
-
-
- Backlog
-
-
-
- In Progress
-
-
-
- In Progress
-
-
-
- In Progress
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is caused by
-
-
- Backlog
-
-
-
- Backlog
-
-
-
- Backlog
-
-
-
- Approved
-
-
-
- In Progress
-
- links to
