-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
5
-
False
-
None
-
False
-
-
-
GitOps Scarlet - Sprint 3264, GitOps Scarlet - Sprint 6/3265, GitOps Scarlet - Sprint 7/3266
Story (Required)
Updates to OpenShift GitOps docs based on changes made for this feature.
Acceptance Criteria (Mandatory)
- On 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) in the OpenShift docs:
- We should document how to enable traffic/metrics plugins in Argo Rollouts
- This should include a brief description of traffic/metrics plugins, and their use
- A procedure which enables a specific traffic manager plugin, for example, Gateway API (https://argo-rollouts.readthedocs.io/en/stable/features/traffic-management/plugins/#gateway-api)
- A link to upstream docs list of traffic/metrics plugins: https://argo-rollouts.readthedocs.io/en/stable/features/traffic-management/plugins/ and https://argo-rollouts.readthedocs.io/en/stable/analysis/plugins/
- Provide a draft doc, and work for doc folks to get this into OpenShift GitOps docs