goleak VS Reloader

Didn't Uber have some leaky goroutine detector? I vaguely remember seeing something like that, 5 years ago...

Ah yeah it's here.

https://github.com/uber-go/goleak

The reason why I created this project is because they don't want to make the goleak more flexible: https://github.com/uber-go/goleak/pull/52

In the past, I had used https://github.com/uber-go/goleak . I hadn't looked into how it does it, but I think it's a different approach than what you wrote about. Do you have any idea what are the differences?

In the past, I have used this: https://github.com/uber-go/goleak . But it's not ideal, as AFAIK there isn't really a deterministic way to wait until a goroutine has actually stopped. That is, if you want to test that a goroutine has stopped, you'll end up with non-determinism, thus flaky tests.

https://github.com/uber-go/goleak - checks for tests

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.