-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
3
-
False
-
None
-
False
-
SECFLOWOTL-195 - RFEs 1.15
-
-
-
GitOps Scarlet - Sprint 3264, GitOps Scarlet - Sprint 6/3265, GitOps Scarlet - Sprint 7/3266
Story (Required)
Document new HA mode in OpenShift docs.
Acceptance Criteria (Mandatory)
- In the OpenShift GitOps docs, in the 'Using Argo Rollouts for progressive deployment delivery' page (https://docs.openshift.com/gitops/1.14/argo_rollouts/using-argo-rollouts-for-progressive-deployment-delivery.html#gitops-creating-rolloutmanager-custom-resource_using-argo-rollouts-for-progressive-deployment-delivery)
- A brief description of why it can be beneficial to enable HA
- We should add a new section which describes how to how to high availability mode for Argo Rollouts, by modifing '.spec' field of 'RolloutsManager' CR
- We should add a new 'Procedure:' which modifies the RolloutManager '.spec' to enable HA, then verifies that rollouts deployment is now running with 2 replicas.
- Write draft doc for above, and work with doc folks to get this into OpenShift docs