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

nethermind: adding secret name override #556

Merged
merged 3 commits into from
Jul 18, 2024

Conversation

kaplanmaxe
Copy link
Contributor

Big fan of this repo!

The current way secrets are handled in this repo is not the most ideal in my opinion. While the docs show an example of specifying the JWT token via an environment variable (which is not bad security wise), if one wanted to track their values.yaml file in git, the current chart requires .Values.global.JWTSecret to be tracked in code.

Additionally, it's very common for people to use external secret providers like Hashicorp Vault (which I have seen Stakewise supports in some areas already). To do this, one could use a SecretProviderClass (or the vault injector obviously).

This PR allows for:

  • The chart to reference a secret that is not managed by the chart
  • Adding additional volumes
  • Adding additional volumeMounts

@antares-sw
Copy link
Contributor

antares-sw commented Jul 17, 2024

Hey @kaplanmaxe, thanks for the PR, please up chart version here: https://github.com/stakewise/helm-charts/blob/main/charts/nethermind/Chart.yaml#L5

@kaplanmaxe
Copy link
Contributor Author

done!

@antares-sw antares-sw merged commit a7166e5 into stakewise:main Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants