helm-secrets VS Reloader

helm plugin install https://github.com/databus23/helm-diff helm plugin install https://github.com/aslafy-z/helm-git helm plugin install https://github.com/jkroepke/helm-secrets

I use Helm secrets which integrates Mozilla Sops to handle secrets in my Helm charts.

Use Helm Secrets.

ArgoCD users would have to build container images with SOPS baked in using Helm chart extensions or Kustomize extensions. Flux allows configuring sops directly into the Flux manifests.

There is also the helm secrets plugin, which can also be used in ArgoCD with manual configuration.

Not sure if this is applicable for your use case, but you could use helm-secrets to fetch remote value files from https or git: https://github.com/jkroepke/helm-secrets/wiki/Values

$ helm plugin install https://github.com/jkroepke/helm-secrets --version v3.14.0

https://github.com/jkroepke/helm-secrets powered by sops

SOPS is great, and there are a lot of GitOps tools that either integrate with SOPS directly or make it relatively painless to integrate into your workflow, e.g. helm-secrets.

SOPS and helm-secrets: https://github.com/jkroepke/helm-secrets

You can combine this approach with something like https://github.com/stakater/Reloader to automatically restart pods when a certain secret value changes. So if your static code needs to be rebuilt when certain values change, you can use an init container to run the build on startup.

This is not a cron job? I'm not sure if it helps, but you can have pods do a rolling restart on secret updates: https://github.com/stakater/Reloader that would clear the resources each run, but I'm not entirely clear on what you're looking to achieve.

If you use secrets as Environment Variables you will need to use something to make workloads get the new credentials, if they just loose connection. You can use the Reloader project for that.

Reloader is designed to simplify the process of updating application configurations in Kubernetes. It monitors ConfigMaps and Secrets for changes and triggers rolling upgrades for associated resources such as Deployments, StatefulSets, DaemonSets, and more. Reloader eliminates the need for manual intervention and reduces the risk of errors during the configuration update process.

The go k8s packages are pretty bloated - this may also just be a niche case. If you are looking to get secrets with hot reloading, you might also consider mounting a file or setting env vars and coupling it with this reloading operator: https://github.com/stakater/Reloader

For the auto restart this has been a staple install in all clusters for years for me: https://github.com/stakater/Reloader

If you didn't want to use SOPS, for some reason, you can certainly take advantage of external secrets as another commenter proposed, but you won't be able to accomplish (2) without an external tool adding to the mix, like Reloader: https://github.com/stakater/Reloader – that's because something has to update the HelmRelease in order to trigger it to upgrade. (You could just wait for the reconciler to come along, but the tendency is to set the polling interval longer than the default, so Helm won't be re-trying as often, in case something goes wrong...)

You can install https://github.com/stakater/Reloader And then it's just matter of a single annotation and it restarts automatically when there are changes.