-
Spike
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
5
-
False
-
None
-
False
-
SECFLOWOTL-93 - Promote Rollouts to GA
-
-
-
GITOPS Service EE Sprint 256, GITOPS Service EE Sprint 257, GITOPS Service EE Sprint 258, GITOPS Service EE Sprint 3254, GitOps Scarlet - Sprint 2261, GitOps Scarlet - Sprint 3257
This is a spike story.
As we decided to support we should verify if Argo Rollouts(using GitOps operator) can use OpenShift workload monitoring for Rollouts Analysis.
Example:
Users may want to use rollouts to implement canary deployment using the progressive deployment model. In which, A user would like rollouts to only increase the weight of the traffic to new deployment if a specific analysis is passed. In most of the cases, upstream users use prometheus for such analysis but our users might prefer OpenShift workload monitoring.
So, it is important to verify the support for rollouts with OpenShift workload monitoring.
Acceptance Criteria
A blog to support your research.
Acceptance Criteria:
- Google doc describing results of investigation, so we can decide next step:
- Presuming we want to go forward with it, we can then turn that document into documentation (and/or blog post)
- If we do go ahead, open corresponding story