Hot config reload

[lc-guy]

Is hot reload of configuration supported with the k8s operator?

I'm interested in dynamically changing some parts of the configuration (notably adding new users, or adding new databases), but currently the only way this seems possible is by doing helm install again for the main config, and I'm not sure if the change would be detected afterwards by the running instances. Same with users.toml which is already externalized through secrets atm -- will a change in the secret be picked up on the fs level and then updated with a RELOAD in pgdog?

[levkk]

The chart (or K8s) doesn't run RELOAD automatically, mostly because it's not something this tech can do. We would need to write an actual operator that detects config changes and reloads them, atomically, across instances. For now, you need to connect to each container and run RELOAD manually or synchronize it with a script.

[w3irdrobot]

@levkk could this be done with a helm post-install hook?