Skip to content
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

Usage of deprecated external secrets manager #107

Open
brunoluiz opened this issue Jun 19, 2023 · 1 comment
Open

Usage of deprecated external secrets manager #107

brunoluiz opened this issue Jun 19, 2023 · 1 comment

Comments

@brunoluiz
Copy link

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:

  1. Should this project consider the new external-secrets apis?
  2. If so, how would you keep up with new api releases or changes?
@brunoluiz
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant