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

     1  # v1.6 to 1.7
     2  
     3  ## AppProject tokens moved to status field
     4  
     5  In order to address [argoproj/argo-cd#2718](https://github.com/argoproj/argo-cd/issues/2718) the JWT tokens stored in
     6  AppProject CRD have been moved from `spec` to `status` field. The migration is performed automatically during upgrade
     7  and might cause few seconds delay. No additional side effects besides the delay are expected. It is acceptable to
     8  rollback to previous version - no data loss is expected.
     9  
    10  ## Resources like ConfigMap might become out-of-sync due to YAML library upgrade
    11  
    12  As part of v1.7 release, the Kubernetes client library have been upgrade to v1.18.8 as well as we've started using
    13  https://github.com/kubernetes-sigs/yaml for YAML handling to be consistent with `kubectl` behavior.
    14  This introduced a change of multiline string handling in resource manifests. As a result, YAML manifests with multiline
    15  strings might become out-of-sync after upgrading and you might have to trigger the synchronization once to resolve it.
    16  
    17  Affected resource example:
    18  
    19  ```yaml
    20  ---
    21  apiVersion: v1
    22  kind: ConfigMap
    23  metadata:
    24    name: my-config-map
    25  data:
    26    value: |+ # block chomping indicator is dropped by Argo CD v1.7 ( same as kubectl apply)
    27    hello
    28  ```
    29  
    30  ## New RBAC rules for GnuPG related features
    31  
    32  The [GnuPG feature](../../../user-guide/gpg-verification) has introduced a new
    33  RBAC resource in Argo CD, `gpgkeys`.
    34  
    35  Please adapt your RBAC rules with the appropriate permissions. The least set of
    36  permissions every role should have is:
    37  
    38  ```
    39  p, <your-role>, gpgkeys, get, *, allow
    40  ```
    41  
    42  More information can be found in the
    43  [documentation](../../../user-guide/gpg-verification#rbac-rules-for-managing-gnupg-keys)
    44  
    45  From here on you can follow the [regular upgrade process](./overview.md).