crc VS Reloader

The issue is currently being worked on here is the link with the workaround.

Yessss . Just incase Git hub releases: https://github.com/crc-org/crc/releases

You can try running https://github.com/crc-org/crc with the podman preset (!) to test it. It would not be exactly the same how podman machine will use it eventualky, but might help to give an idea of performance or issues we can imorove on first. We have seen a lot of users being more than content as it also works in a vpn environment. Note that the CRC tool primarily aims at OpenShift deployment... This is a different preset (resource intensive). Only available as an installer with our tray (sorry about this).

The driver we use is https://github.com/crc-org/vfkit and I am sure Christophe could share a method to just run the VM with our driver. HMU by email if you prefer.

CodeReady Containers which allows you to spin up a reduced OpenShift node in a single VM on a desktop/laptop for getting familiar with the platform. It disables quite a few operators so it's not a full experience, but enough for a developer to get going. It doesn't have the lightest requirements but it works for the most part. By default it's recommended to have 4 cores, 12GB of memory and the disk expands to 35GB. These can be tweaked through the setup, though.

I'm having issues as described in https://github.com/code-ready/crc/issues/2945

GitHub - code-ready/crc: Red Hat CodeReady Containers is a tool that manages a local OpenShift 4.x cluster optimized for testing and development purposes

Appears to be possible but definitely more on the DiY side. https://github.com/code-ready/crc/issues/2480

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.