kubernetes-reflector VS Reloader

In one of the comments it lead us to https://config-syncer.com/docs/v0.14.7/setup/install/ which had a comment about another tool emberstack/kubernetes-reflector.

You should have you app deployed from a git repo using something like ArgoCD, Flux, or fleet. You would then make your changes in git to have the synced to your target clusters. I've never used it, but you could also look at https://github.com/emberstack/kubernetes-reflector

You mean this? Isn't it kinda hacky? I mean, it feels like every solution for shared imagePullSecret is a total hack.

Is there any good alternative for https://github.com/emberstack/kubernetes-reflector ?

We are using reflector: https://github.com/emberstack/kubernetes-reflector

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.