Open MohammedFadin opened 5 years ago
I had the same issue. In my case the api-key in the secret had a corrupted value. Don't know how it got corrupted. Could be I forgot to base64 encode it before creating the secret. Originally, the secret was created with the command. Deleted the corrupted secret and recreated with YAML using stringData so it is easier to tell what the secret values are.
Hi,
We keep getting the below error every time we create the PVC for COS. Although the secret is 100% correct, and even my colleagues from the IBM pre-sales team faced the issue.