What is 𝐜𝐨𝐧𝐟𝐢𝐠 𝐦𝐚𝐩 and how to use it ?

𝐂𝐨𝐧𝐟𝐢𝐠𝐌𝐚𝐩𝐬 in Kubernetes are a way to manage configuration data separately from the application code. They allow you to decouple configuration settings from your application's containers, making it easier to update configuration values without changing your application's code.

𝐂𝐫𝐞𝐚𝐭𝐞 𝐚 𝐂𝐨𝐧𝐟𝐢𝐠𝐌𝐚𝐩:

Here's an example of a YAML file to create a ConfigMap:

 apiVersion: v1
 kind: ConfigMap
 metadata:
 name: my-config
 data:
 key1: value1
 key2: value2

Apply this YAML file using kubectl apply -f my-configmap.yaml, and it will create a ConfigMap named my-config with key-value pairs key1: value1 and key2: value2.

𝐀𝐜𝐜𝐞𝐬𝐬𝐢𝐧𝐠 𝐂𝐨𝐧𝐟𝐢𝐠𝐌𝐚𝐩 𝐃𝐚𝐭𝐚 𝐟𝐫𝐨𝐦 𝐏𝐨𝐝𝐬:

Your application code within the pod can access the ConfigMap data using various methods, such as reading environment variables,command-line arguments, or reading configuration files from the mounted volume.

☑️ 𝐀𝐬 𝐞𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭 𝐯𝐚𝐫𝐢𝐚𝐛𝐥𝐞𝐬:

 apiVersion: v1
 kind: Pod
 metadata:
 name: my-pod
 spec:
 containers:
 - name: my-container
 image: my-image
 env:
 - name: KEY_FROM_CONFIGMAP
 valueFrom:
 configMapKeyRef:
 name: my-config
 key: key1

In this example, the value of the environment variable KEY_FROM_CONFIGMAP is set to the value of key1 from the my-config ConfigMap.

☑️ 𝐀𝐬 𝐕𝐨𝐥𝐮𝐦𝐞𝐬:

You can also use ConfigMaps as volumes to inject configuration files into pods. This is useful when you need to provide configuration files to applications. Here's an example:

 apiVersion: v1
 kind: Pod
 metadata:
 name: my-pod
 spec:
 containers:
 - name: my-container
 image: my-image
 volumeMounts:
 - name: config-volume
 mountPath: /etc/config
 volumes:
 - name: config-volume
 configMap:
 name: my-config

In this case, the contents of the my-config ConfigMap will be mounted as files in the /etc/config directory in the pod.

They help you keep your configuration separate from your application logic, making it easier to manage, update, and maintain your containerized applications.