-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supported argocd versions are unclear #1572
Comments
Hi @bo0ts, yes, you can deploy other Argo CD versions by using apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
name: <your-argocd-instance>
spec:
image: quay.io/argoproj/argocd
version: v2.12.3 The supported versions are
We are in the process of updating our documentation and automating our release process. We are hopeful that things will be better in the future. |
Do you know if Renovate supports updating the |
I have never used Renovate, nor have I heard of it being used with ArgoCD Operator, so I am not sure if it's supported. |
I got it to work by writing a custom manager in Renovate. |
Describe the bug
The operator installs a default version of argocd. It is not clear from the documentation if it is possible to also deploy other argocd versions with a given operator version. The argocd CRD has a version field, but the documentation is rudimentary.
Expected behavior
Clear documentation on which versions can be deployed with a given operator version (e.g. operator release 0.12.0, supports all argocd versions 0.12.X).
Additional context
There is a bugfix in a argocd minor release which I would like to deploy using the argocd-operator. Also the argocd-operator release cycle is much slower than the argocd release cycle and I would like to have an up-to-date argocd installation.
The text was updated successfully, but these errors were encountered: