-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors fetching secrets #20
Comments
Are you getting this on startup? Or when trying to get a secret from vault? Could you provide a bit more context? Thanks! |
Hi @stevesloka , My secrets are stored as following: secret/environment/SECRET_VALUE the value is the actual secret value. I don't know if this format is unsupported for this tool. Some logs:
|
Hey sorry for the delay getting back to you, been busy with a new baby, so time has been short recently. Let me try and simulate the same, seems like a parsing problem of sorts. What type of data is stored in the secret? |
We store strings but also certificates as base64. Maybe that could be causing problems? We store them as secret value=something. Every secret only has one value. We name them after our env variables. Everything is either a normal passphrase string or a base64 encoded certificate. |
@stevesloka any update on this? |
Hey @thecodeassassin I just ran through an example and it all seemed to work for me. I put the sample here: https://github.com/upmc-enterprises/kubernetes-secret-manager/blob/master/docs/deployment-guide.md#static-secrets Can you see maybe if your workflow is different? (Maybe I'm missing a step that you're doing). |
Hi all,
I'm getting the following error in the pod logs:
I'm saving my secrets as secret/staging/ENV_NAME. The value being the secret.
The text was updated successfully, but these errors were encountered: