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

Manage secrets as code #29

Open
agaudreault opened this issue Mar 1, 2024 · 1 comment · May be fixed by #36
Open

Manage secrets as code #29

agaudreault opened this issue Mar 1, 2024 · 1 comment · May be fixed by #36

Comments

@agaudreault
Copy link
Member

agaudreault commented Mar 1, 2024

Some secrets used for different applications have been created manually in the cluster.
Using SealedSecrets seems like the best approach to manage them as code.

Another alternative would be External Secrets, but it would require a provider such as GCP Secret Manager at additional costs and secrets at this location would still need to be managed manually.

The list of the secrets that were applied manually are:

  • dex/dex
  • argocd/argocd-auth
  • prometheus-operator/prometheus-operator-grafana
    • Only the key admin-password
  • argo/argo-server-sso
  • argo/argo-workflows-webhook-clients

AC

  • Update the different README.md to reflect the changes
  • Manage secrets as code
@agaudreault
Copy link
Member Author

Starting to work on this

@agaudreault agaudreault linked a pull request Mar 8, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant