gpg 2.3.x compatibility issues when using gpg 2.x

When walking through the guide here https://repo1.dso.mil/platform-one/big-bang/customers/template/-/blob/1.9.0/README.md#multi-environment-workflow , and when I got to the point where I deployed bigbang and checked the status of the kustomization via

kubectl get -n bigbang kustomizations

I see the following error:

Events:
  Type     Reason  Age   From                  Message

  Warning  error   45s   kustomize-controller  decryption failed for 'common-bb-8f6cbmgbtd': DataWithFormat: AES decrypt: Error walking tree: Could not decrypt value: crypto/aes: invalid key

Following this guide - https://repo1.dso.mil/platform-one/onboarding/big-bang/engineering-cohort/-/blob/035edc3f84054f9f94609d5f9c2072a7dda63450/lab_guides/05-big-bang-prep-work/C-provision-gpg-encryption-keypair-and-configure-gitops-encrypted-secrets.md , the solution is, instead of generated the key via this way:

export fp=`gpg --quick-generate-key bigbang-sops rsa4096 encr | sed -e 's/ *//;2q;d;'`
gpg --quick-add-key ${fp} rsa4096 encr

to generate the key with the following args (so that if you are using gpg 2.3.x or 2.x), there will be no compatibility issues when using different versions of gpg:

export NAME=bigbang-sops
export KEY_NAME="$NAME"
export KEY_COMMENT="For use in $NAME's Big Bang dev environment"
gpg --batch --full-generate-key --rfc4880 --digest-algo sha512 --cert-digest-algo sha512 <<EOF
    %no-protection
    # %no-protection: means the private key won't be password protected 
    # (no password is a fluxcd requirement, it might also be true for argo & sops)
    Key-Type: RSA
    Key-Length: 4096
    Subkey-Type: RSA
    Subkey-Length: 4096
    Expire-Date: 0
    Name-Real: ${KEY_NAME}
    Name-Comment: ${KEY_COMMENT}
EOF

changed the description

Closing issue per the above solution.

closed