Hi. I’m generating all my kube resources configs from another config system, so I don’t maintain kube resources directly.
I’m thinking about whether I should use config maps for keeping env data and then map them to deployments or just embed env values them into generated deployment config, anyway they are generated each time I do changes, so I just don’t see any advantages of having additional entity which I don’t see the actual value of.
If using config map for example, if some value is changed and even if multiple pods depend on it, I just update it my config system, and then update the state of all config maps on the cluster. Then I should still touch pods to make them see the changes.
If I don’t use config maps I just update/apply config for deployment with new env values and pod is restarted.
So I don’t see the actual value of involving of config maps in my setup.
Any thoughts about such case?