Closed carslen closed 11 months ago
No action required, as we're not using asterik in our project definitions, examples:
We, as Org admins, use ArgoCD default project permissions.
Helm version has been upgraded from 3.10.3 to 3.11.2.
Kustomize version has been upgraded from 4.5.7 to 5.0.1.
No obvious effects to our setup.
Internal change in ArgoCD images/container setup
Improvements to deep links.
helm.sh/resource-policy
annotationImprovement, new feature.
--redis
changesWe're using default config, no changes to redis server name in our setup.
argocd applicationset
CLI incompatibilities for ApplicationSets with list generatorsargocd cli had issues with applicationset in cli version < 2.7.3.
PR #417 merged to main. Start testing ArgoCD 2.7 on devsecops cluster. Move ticket back to in progress
DEVSECOPS-TESTING cluster has been updated to 2.7.
App creation incl. using AVP is working as expected. After approval I'll push the currently missing GH tag ArgoCD-v2.7.14-c0_AVP-v1.16.1
to main branch and update to other envs.
so far it seems to work. 😉
Pushed missing GH tag to main
branch. ArgoCD instances will be updated accordingly during the day.
Upgrade ReadMe
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/2.6-2.7/
Things to check
helm.sh/resource-policy
annotation--redis
changesargocd applicationset
CLI incompatibilities for ApplicationSets with list generators