Major Customers can access full support for features that have been released as TP.
Timeline
- Target incremental GA releases, not making them all GA at the same time
- Over the next 5 releases
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
We have 7 features listed as Tech Preview right now. Customers have been asking for these features are were very enthusiastic to have them released - however, many customers have organisational restrictions around using non-GA features.
This is what we have in TP right now:
| Feature | When we released it |
| The custom must-gather tool | 1.9.0 |
| Argo Rollouts | 1.9.0 |
| ApplicationSet Progressive Rollout Strategy | 1.8.0 |
| Multiple sources for an application | 1.8.0 |
| Argo CD applications in non-control plane namespaces (apps in any namepaces) | 1.7.0 |
| Argo CD Notifications controller | 1.6.0 |
| The Red Hat OpenShift GitOps Environments page in the Developer perspective of the OpenShift Container Platform web console | 1.1.0 |
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.
- The GitOps engineering team is comfortable supporting the code of each feature (answering support questions, triaging bugs, fixing bugs, making improvements, implementing RFEs)
- Our CEE colleagues have the training and support they need to support our customers using these features
Expected Results (what, how, when)
What incremental impact do you expect to create toward the company's Strategic Goals by delivering this outcome?
- There is an increase in usage of the features that we already have the ability to track (e.g. we can report on the number of Rollout CRs that customers have on their clusters)
- We will take a baseline reading before each goes GA, and measure monthly after GA
- An increase in support questions about each feature once it has gone GA - this is one indicator that will show us that customers are using each feature
- We will take a baseline reading before each goes GA, and measure monthly after GA
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
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).