Source: medium.com
ConfigMaps in Kubernetes: how they work and what you should rememberCategory: Software, Kubernetes, yaml, ansible, puppet
Please note that this is not a complete guide, but rather a reminder/tips collection for those who already use ConfigMap in Kubernetes or are in the middle of preparing their applications to use it. In the era of “classic system administration,” config files were usually stored next to the application itself (or in the repository, if you prefer).
Applications were taught to decide which config to use while passing them as runtime arguments or as environment variables.
They are stored in YAML, and a K8s resource called ConfigMap is responsible for handling them.
If you’re fine with Helm, the solution to this problem is given in Helm Chart Development Tips and Tricks: Here, the hash of the config is included in the pod’s template (spec.template) as an annotation.
Applications were taught to decide which config to use while passing them as runtime arguments or as environment variables.
They are stored in YAML, and a K8s resource called ConfigMap is responsible for handling them.
If you’re fine with Helm, the solution to this problem is given in Helm Chart Development Tips and Tricks: Here, the hash of the config is included in the pod’s template (spec.template) as an annotation.
Related Articles
Community Partners
DevOps Careers