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)?

We want to provide a frictionless multi-cluster OpenShift upgrade experience, redefining operational excellence across the hybrid cloud. We aim to provide a unified, zero-friction, seamless upgrade, and consistent experience across all topologies (multi-node, single node, 2 node, Hosted Control Plane, etc.) and across connected and disconnected/air-gapped scenarios, as well as proactive coordinate the upgrade lifecycle of the OpenShift platform and every installed operator, and eliminate manual complexity and risk for every customer, everywhere. We want the disconnected/air-gapped upgrade experience for customers to have a similar and frictionless experience as that of the connected experience, which may include delivering seamless, guided content management for ultra-low bandwidth and air-gapped scenarios. We want to leverage pre-checks and remediation in the upgrade experience while ensuring predictability and continuity, driving proven increases in speed for even the most complex deployments. 

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.

• Cluster administrators no longer rely on home grown scripts, multiple CLI commands, manual research, disparate tools that are not integrated, or fragmented views to perform upgrades.
• Shifting customers' mindset for cluster upgrades from reactive troubleshooting to proactive predictability.
• We eliminate the friction currently experienced by our disconnected, air-gapped, and edge customers.
• We reduce the time to plan and complete an OpenShift upgrade. Specifically, there should be measurable reduction in time spent for upgrade planning, upgrade execution include getting content ready, pre-check includes operator and 3rd party operator compatibility, troubleshooting, status reporting, etc.
• Customers have easy access to a unified upgrade readiness view or information across one or more clusters.

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)

• Accelerate time-to-value and drive upgrade velocity by converting lengthy OpenShift upgrades into faster/rapid, predictable cycles.
• Increase customer resilience and reduce support costs by eliminating preventable upgrade failures that lead to expensive, time-consuming support escalations.
• Unblock sales and adoption in bandwidth constrained and edge environments by ensuring true operational parity for disconnected, limited-bandwidth customers.
• Enhance developer and operator (day 2) experience (day 2) by providing a consistent and/or unified "single pane of glass" to manage the combined upgrade lifecycle of the platform and all layered products.

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).