Closed gorzek closed 5 years ago
Yeah, it was a bug with all version that was fixed recently (see #259). Which chart and Kamus version are you running?
I'm using chart 0.3.0 and app version 0.4.0.0. That's the latest in soluto/kamus, as far as I have seen.
I'm also doing the encryption calls using a container running the latest kamus-cli image.
You're right - I just opened a PR to update the chart to the latest version (Soluto/helm-charts#26). Can you please try to add --set image.version=0.4.5.0
to the install command?
That did the trick!! Thank you. I'll keep an eye out for an updated chart.
Happy to hear so and sorry for the inconvenience!
Hey, @gorzek a new chart version was just released (0.3.1). Can you please re-test and update?
Tested and confirmed to be working with Google Cloud KMS! Thank you!
Happy to hear so! Closing the issue, please re-open if relevant :)
I'm getting the following error when attempting to encrypt a key via Google Cloud KMS:
I've installed kamus via helm chart into a Kubernetes cluster. I have set up a keyring and service account which kamus has successfully created keys with in KMS. The CLI gets me an HTTP status 500 when attempting to encrypt a single string, and the text above is pulled from the pod logs coinciding with the error.
So, I don't think connectivity to the pod is an issue, though clearly something is amiss with how the Google credentials are being used to interact with KMS. Might be a misconfiguration on my part but I've ruled out as much as I can.
I appreciate any help anyone could offer on this.