Releases: projectsyn/component-argocd
Releases · projectsyn/component-argocd
v8.5.7
v8.5.6
v8.5.5
v8.5.4
v8.5.3
4 changes since v8.5.2
🔗 Dependency Updates
- chore(deps): update docker.io/kapicorp/kapitan docker tag to v0.33.1 (#146)
- chore(deps): update quay.io/argoprojlabs/argocd-operator docker tag to v0.10.1 (#163)
- chore(deps): update quay.io/argoproj/argocd docker tag to v2.11.4 (#147)
- chore(deps): update docker.io/hashicorp/vault docker tag to v1.17.2 (#171)
v8.5.2
4 changes since v8.5.1
🔗 Dependency Updates
- chore(deps): update docker.io/hashicorp/vault docker tag to v1.17.1 (#159)
- chore(deps): update gcr.io/kubebuilder/kube-rbac-proxy docker tag to v0.16.0 (#160)
- chore(deps): update docker.io/bitnami/kubectl docker tag to v1.30.2 (#143)
- chore(deps): update docker.io/library/redis docker tag to v7.2.5 (#169)
v8.5.1
v8.5.0
v8.4.0
v8.3.0
1 changes since v8.2.1
This release includes a newer default version of ArgoCD. The new ArgoCD fixes a sync error "project syn does not exist" if the customers deploys their own cluster scoped ArgoCD.
While we not yet have a definitive explanation for the issue we assume the two ArgoCDs override each others status and trigger each others reconciles.
The bug is present in ArgoCD v2.9.10
and fixed in v2.9.11
+. (diff)
🔗 Dependency Updates
- chore(deps): update quay.io/argoprojlabs/argocd-operator docker tag to v0.9.1 (#156)