-
Notifications
You must be signed in to change notification settings - Fork 26
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
Provide a Helm chart for SecretsManager deployment #6
Comments
how does this go on? Almost one year has passed |
I made my own here. You will still need to provide your own image. Which can be over written here.
I also created a secret creation chart here. These are all first passes and may not include all args and env vars. |
I created a Helm chart for Secrets-Manager and we have been using it in production for several months without issues. I can create a PR to merge this into this repo if you want. Let me know. |
I tried to use same steps what you used here to prepare latest chart version from tag v2.1.0. But i am facing issue after deployment, i am preparing chart using kustomize build config/default -o /temp/
|
Was able to resolve issue after removing type from SecretsDefinition file |
@a-thorat is it related to the version of your kubernetes cluster? |
Thanks for your response. No it was not related to kubernetes cluster version. Found issue in one of SecretDefiniation file where Secret type was mentioned explicitly as Opaque. After removing it everything seems to be working. |
Include (inside a
deployment/
folder, according to the recommendations in golang-standards/project-layout) a Helm Chart that installs SecretsManager in K8s.The text was updated successfully, but these errors were encountered: