Customers using any aspect of the OpenShift product suite (OCP, MicroShift, ROSA etc) on any platform (Hypershift, BM, cloud providers etc) have access to a tested and supported version of OpenShift GitOps

Timeline

Timeline put in place for when this outcome will be achieved with the information at hand. (Subject to change). 

All features required to deliver on this outcome to be linked to the outcome and discussion with teams to be had before the timeline is set. Review of timeline to take place regularly - any changes to be communicated.

• Start working towards these in Q4 '23
• Continue to Q1 and Q2 '24
• Review at the end of each quarter, with the post-completion review targeted for the end of Q2 '24
• Subject to QE availability

Update in Q2 '24 - continuing into Q3 to address the ROSA on HyperShift requirements and MicroShift GA  

Dependencies

All known teams that have a dependency on this Outcome should be listed in the description or notified. They can link to this Outcome or add themselves as a watcher to track risks.

Other dependent Outcomes should also be linked.

Customer Need

Specific customer need (external/internal) that this outcome will solve.

• Most of our customers are using OpenShift as well as other public clouds
  • From HATSTRAT-196: “OCP self-managed (on-prem or cloud), OCP managed (ROSA, ARO, OSD), non-OCP (*ks) are registered in an inventory that can then be used by other parts of the stack.”
  • XCM/ACM may be managing clusters and deploying to any of these places, we need to make sure that we've tested and resolved any bugs with any of these combinations

• MicroShift and customers with other Edge environments want to be able to manage their application lifecycles on those edge devices
  • Contributing to HATSTRAT-201 
  • Customers who have specifically requested GitOps support: ABB, SBB, LMCO

• OpenShift is going GA with HyperShift
  • GitOps hasn’t been tested on anything on top of Hypershift yet
• Dev Sandbox
  • Support may be possible after we have a suitable solution deployable on MicroShift
  • Sandbox gets screen-recording data from their users, we would get that for Argo CD if we were able to run GitOps in there - this would be valuable for product planning

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.

• There is a productised and supported version of OpenShift GitOps that successfully runs on MicroShift within their resource limits

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)

• An increase in how many customers are using GitOps on ROSA and ARO
• MicroShift team can add GitOps to their sales content

Metrics

Possible Measurements / Observable Results: Detailed overview of what will be measured to identify progress on that outcome.

 Explicit KPIs and Metrics tied to goals/outcomes

• Number of installs on each platform - tracked in Tableau already

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