github.com/argoproj/argo-cd/v2@v2.10.9/docs/operator-manual/upgrading/1.7-1.8.md (about)

     1  # v1.7 to 1.8
     2  
     3  ## The argocd-application-controller converted to StatefulSet
     4  
     5  The `argocd-application-controller` has been converted to StatefulSet. That means you need to manually delete `argocd-application-controller` Deployment after upgrading.
     6  Similarly if you decided to rollback to v1.7 don't forget to delete `argocd-application-controller` StatefulSet.
     7  
     8  
     9  ## Health assessment of argoproj.io/Application CRD has been removed
    10  
    11  The health assessment of `argoproj.io/Application` CRD has been removed (see [#3781](https://github.com/argoproj/argo-cd/issues/3781) for more information).
    12  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
    13  `argocd-cm` ConfigMap:
    14  
    15  ```yaml
    16  ---
    17  apiVersion: v1
    18  kind: ConfigMap
    19  metadata:
    20    name: argocd-cm
    21    namespace: argocd
    22    labels:
    23      app.kubernetes.io/name: argocd-cm
    24      app.kubernetes.io/part-of: argocd
    25  data:
    26    resource.customizations: |
    27      argoproj.io/Application:
    28        health.lua: |
    29          hs = {}
    30          hs.status = "Progressing"
    31          hs.message = ""
    32          if obj.status ~= nil then
    33            if obj.status.health ~= nil then
    34              hs.status = obj.status.health.status
    35              if obj.status.health.message ~= nil then
    36                hs.message = obj.status.health.message
    37              end
    38            end
    39          end
    40          return hs
    41  ```
    42  > To modify an existing installation with no existing `resources.customizations`, you can save the `data:` stanza to file and patch the configmap with e.g.: `kubectl -n argocd patch configmaps argocd-cm --patch-file argocd-cm-patch.yaml`
    43  
    44  ## gRPC metrics are disabled by default
    45  
    46  The gRPC metrics are not exposed by default by `argocd-server` and `argocd-repo-server` anymore. These metrics appear
    47  to be too expensive so we've decided to disable them by default. Metrics can be enabled using
    48  `ARGOCD_ENABLE_GRPC_TIME_HISTOGRAM=true` environment variable.  
    49  
    50  From here on you can follow the [regular upgrade process](./overview.md).