sops 3.8.1 (latest) encrypted files are not working in kubernetes cluster.

Hi Team,

We have a problem with the SOPS 3.8.1 version. We are generating the encrypted keys and updating them in our Kubernetes (1.25.11) cluster, which was built on Red Hat servers.

Also, we have another set of AKS (Azure Kubernetes) clusters, and it also has the 1.25.xx Kubernetes version.

3.8.1 - encrypted files are working in AKS clusters.
3.8.1 - not working in on-prem (redhat servers) kubernetes clusters.
3.7.3 - version only working in on-prem clusters.

In my current system, I installed the 3.8.1 version of sops.
why I am  not able to decrypt the file, which was generated using the 3.7.3 sops version.

sops binary is: 3.8.1
File: cps.enc.yaml (3.7.3)

Error:
sops -d cps.enc.yaml > cps.dec.yaml
Failed to get the data key required to decrypt the SOPS file.

Group 0: FAILED
932AB836D93621F24E37F: FAILED
- | could not decrypt data key with PGP key:
| github.com/ProtonMail/go-crypto/openpgp error: could not
| load secring: open /Users/sli/.gnupg/pubring.gpg: no
| such file or directory; GnuPG binary error: failed to
| decrypt sops data key with pgp: gpg: encrypted with 4096-bit
| RSA key, ID C041A, created 2023-02-25
| "aks-test-team"
| gpg: decryption failed: No secret key

Start with cps.enc.yaml and reproduce sops -d cps.enc.yaml > cps.dec.yaml using SOPS 3.8.1, comparing the on-premises Red Hat Kubernetes environment with AKS and the reported 3.7.3 behavior. Review the full PGP/GnuPG error, including the missing keyring and “No secret key” message; done means the version or environment difference is isolated and the decryption behavior is explained.