In programming, we use env files or separate configuration files to store settings, configurations, or variables that are required to execute the program. In Kubernetes, we can use ConfigMaps to achieve the same functionality.
To understand ConfigMap properly, you should have some knowledge of Kubernetes, pods, and basic Kubernetes cluster management.
(This article is part of our Kubernetes Guide. Use the right-hand menu to navigate.)
What is a ConfigMap?
A ConfigMap is a Kubernetes API object that can be used to store data as key-value pairs. Kubernetes pods can use the created ConfigMaps as a:
- Configuration file
- Environment variable
- Command-line argument
ConfigMaps provides the ability to make applications portable by decoupling environment-specific configurations from the containers.
Importantly, ConfigMaps are not suitable for storing confidential data. They do not provide any kind of encryption, and all the data in them are visible to anyone who has access to the file. (