Update to ArgoCD 2.11.x

[whitfiea]

Is it possible to update this gitops-operator to pick up ArgoCD 2.11.x as it has a fix we require: https://github.com/argoproj/argo-cd/commit/e5c88c914b73e455f3f36dc24583e65c743da792

Is there a general process around when new versions in https://github.com/argoproj/argo-cd/releases will be picked up by this gitops-operator? or maybe a mechanism to allow users to state the ArgoCD version (within some boundary limits)?

[svghadi]

gitops-operator v1.13 will pick up ArgoCD 2.11.x. We bump up minor version of Argo CD in each minor gitops-operator version release. For example

gitops-operator 1.10.x -> Argo CD 2.8.x  
gitops-operator 1.11.x -> Argo CD 2.9.x
gitops-operator 1.12.x -> Argo CD 2.10.x
gitops-operator 1.13.x -> Argo CD 2.11.x (not released)
gitops-operator 1.14.x -> Argo CD 2.12.x (not released)

If you want to try out some new Argo CD feature which is not yet available in gitops-operator, you can set .spec.image & .spec.version in gitops-operator's ArgoCD CR to point to the upstream Argo CD image.

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: <your-argocd-instance>
spec:
  image: quay.io/argoproj/argocd
  version: v2.11.3

Note that the image upstream image is not built in Red Hat environment.

[appiepollo14]

When will 2.13 be released? I assume it will be a 1.15 version of the gitops operator.

[svghadi]

When will 2.13 be released? I assume it will be a 1.15 version of the gitops operator.

Yes. Tentatively by end of next month.

[appiepollo14]

@svghadi Is a release date for the version with Argo version 2.13.x available? If so, when will that be.

[svghadi]

Mostly it will be out in next 2 weeks.

[appiepollo14]

@svghadi What is the aimed for release date?

[svghadi]

It's out already. @appiepollo14

[svghadi]

https://docs.openshift.com/gitops/1.15/release_notes/gitops-release-notes-1-15.html

[appiepollo14]

@svghadi Great! Sorry for asking then. I've based my question on the assumption that the GitHub releases reflect the releases available. I think that's a wrong assumption?

[svghadi]

Your assumption is not entirely incorrect. We usually create GitHub releases once the downstream product is released. However, due to the holiday season and the absence of the right people with permissions, we missed it this time. I’ll follow up and get the release tagged on GitHub.