You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using a different ArgoCD version than the default version set by the operator, we set spec.version in the CR.
Documentation states for spec.version: "The tag to use with the container image for all Argo CD components." (https://argocd-operator.readthedocs.io/en/latest/reference/argocd/#version)
The repo server, however, does not respect this value but only looks at spec.repo.version or falls back to defaults
Create an ArgoCD instance and set spec.version to 2.2.5
Observe repo server deployment - it has the image SHA digest of ArgoCD image 2.3.3
Expected behavior
Repo Server falls back to spec.version if spec.repo.version ist not set
The text was updated successfully, but these errors were encountered:
benruland
changed the title
Repo Server Image should use spec.version if this is set
Repo Server Image should use spec.version if spec.repo.version is not set
Apr 21, 2022
This is still an issue in the latest version, we encountered this due to a helm bug that was fixed in the newer bundled helm version with argo however the repo server pod which actually generates the manifests was still running into the bug.
Workaround is possible by specifically setting spec.repo.version as mentioned but it would be nice for the repo version (if not set) would fallback to the set version instead of the default version. Will see if I can provide a PR for this later.
Describe the bug
When using a different ArgoCD version than the default version set by the operator, we set spec.version in the CR.
Documentation states for spec.version: "The tag to use with the container image for all Argo CD components." (https://argocd-operator.readthedocs.io/en/latest/reference/argocd/#version)
The repo server, however, does not respect this value but only looks at spec.repo.version or falls back to defaults
argocd-operator/controllers/argocd/util.go
Lines 149 to 159 in 68e1197
argocd-operator/controllers/argocd/util.go
Lines 168 to 172 in 68e1197
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Repo Server falls back to spec.version if spec.repo.version ist not set
The text was updated successfully, but these errors were encountered: