v1.7 to 1.8
The argocd-application-controller converted to StatefulSet
The argocd-application-controller has been converted to StatefulSet. That means you need to manually delete argocd-application-controller Deployment after upgrading. Similarly if you decided to rollback to v1.7 don’t forget to delete argocd-application-controller StatefulSet.
Health assessment of argoproj.io/Application CRD has been removed
The health assessment of argoproj.io/Application CRD has been removed (see #3781 for more information). You might need to restore it if you are using app-of-apps pattern and orchestrating synchronization using sync waves. Add the following resource customization in argocd-cm ConfigMap:
---apiVersion: v1kind: ConfigMapmetadata:name: argocd-cmnamespace: argocdlabels:app.kubernetes.io/name: argocd-cmapp.kubernetes.io/part-of: argocddata:resource.customizations: |argoproj.io/Application:health.lua: |hs = {}hs.status = "Progressing"hs.message = ""if obj.status ~= nil thenif obj.status.health ~= nil thenhs.status = obj.status.health.statusif obj.status.health.message ~= nil thenhs.message = obj.status.health.messageendendendreturn hs
To modify an existing installation with no existing
resources.customizations, you can save thedata:stanza to file and patch the configmap with e.g.:kubectl -n argocd patch configmaps argocd-cm --patch-file argocd-cm-patch.yaml
gRPC metrics are disabled by default
The gRPC metrics are not exposed by default by argocd-server and argocd-repo-server anymore. These metrics appear to be too expensive so we’ve decided to disable them by default. Metrics can be enabled using ARGOCD_ENABLE_GRPC_TIME_HISTOGRAM=true environment variable.
From here on you can follow the regular upgrade process.