-
Bug
-
Resolution: Done
-
Blocker
-
GitOps 1.10, GitOps 1.11, GitOps 1.12, GitOps 1.13
-
None
-
devex docs #258 Jun 18- Jul 8
-
1
-
---
-
---
My first time filing a RHDEVDOCS bug, so let me know if anything is missing .
At present, all cases in the documentation where we refer to the apiVerison of the RolloutManager CR are incorrect, and need to be updated.
e.g.
apiVersion: argoproj.io/v1beta1 -> apiVersion: argoproj.io/v1alpha1
In context, that looks like this:
apiVersion: argoproj.io/v1beta1 kind: RolloutManager metadata: # (...)
should be
apiVersion: argoproj.io/v1alpha1 kind: RolloutManager metadata: # (...)
This needs to be updated in main branch, 1.13, 1.12, 1.11, and 1.10:
- 1.10: https://docs.openshift.com/gitops/1.10/argo_rollouts/using-argo-rollouts-for-progressive-deployment-delivery.html
- 1.11: https://docs.openshift.com/gitops/1.11/argo_rollouts/using-argo-rollouts-for-progressive-deployment-delivery.html
- 1.12: https://docs.openshift.com/gitops/1.12/argo_rollouts/using-argo-rollouts-for-progressive-deployment-delivery.html
v1.9 and prior are unaffected.
This bug is only related to RolloutManager. (For example, the ArgoCD CR uses v1beta1, which is correct for that kind.)
I've set this as a blocker, as it will fully break (and confuse) anyone trying to create a Rollouts install.
- links to