We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently this helm chart is enabling users to use external secrets through two means. The externalSecretsOperator though is using a deprecated external secret api, available through https://github.com/external-secrets/kubernetes-external-secrets.
externalSecretsOperator
The new project is now https://github.com/external-secrets/external-secrets, which comes under the api external-secrets.io/v1beta1.
external-secrets.io/v1beta1
My question is:
external-secrets
The text was updated successfully, but these errors were encountered:
The way I sorted in the project I am working on is by:
a. Declaring the external secret referencing outside of the helm chart b. Passing the key reference using
externalSecrets: enabled: true name: retool-default
Not sure what the plans for the OP questions, but keeping up with external CRDs can always become tricky.
Sorry, something went wrong.
No branches or pull requests
Currently this helm chart is enabling users to use external secrets through two means. The
externalSecretsOperator
though is using a deprecated external secret api, available through https://github.com/external-secrets/kubernetes-external-secrets.The new project is now https://github.com/external-secrets/external-secrets, which comes under the api
external-secrets.io/v1beta1
.My question is:
external-secrets
apis?The text was updated successfully, but these errors were encountered: