Why You Should Empower ConfigMaps in Your Kubernetes Deployments?
Discover the capabilities and use-cases of ConfigMaps in Your Cloud-Native Developments
ConfigMaps is one of the most known and, at the same time, less used objects in the Kubernetes ecosystem. It is one of the primary objects that has been there from the beginning, even if we tried so many other ways to implement a Config Management solution (such as Consul, Spring Cloud Config, and others).
Based on its own documentation words:
A ConfigMap is an API object used to store non-confidential data in key-value pairs.
A ConfigMap is an API object used to store non-confidential data in key-value pairs. Pods can consume ConfigMaps as…
Its motivation was to provide a native solution for configuration management for cloud-native deployments. A way to manage and deploy configuration focusing on different code from the configuration. Now, I still remember the WAR files with the application.properties file inside of it.
ConfigMap is a resource as simple as you can see in the snippet below:
ConfigMaps are objects that belong to a namespace. They have a strong relationship with Deployment and Pod and enable the option to have different logical environments using namespace where they can deploy the same application. Still, with a specific configuration, so they will need a particular configMap to support that, even if it is based on the same resource YAML file.
From a technical perspective, the content of the ConfigMap is stored in the etcd database as it happens for any information that is related to the Kubernetes environment, and you should remember that etcd by default is not encrypted, so all the data can be retrieved for anyone that has access to it.