In Kubernetes, managing configuration separately from application code is a critical practice that enables portability, flexibility, and scalability. Kubernetes provides powerful resources such as ConfigMaps and Secrets to inject configuration data into containers without hardcoding it into the application.
These resources support environment variables, volume mounts, and command-line arguments for dynamic configuration. Mastering configuration management is essential for deploying modern, secure, and maintainable applications in Kubernetes clusters.
1.) What is the purpose of a ConfigMap in Kubernetes?
2.) Which Kubernetes object is used to store sensitive information like passwords and API keys?
3.) How are ConfigMaps commonly injected into pods?
4.) Which encoding is used by Kubernetes Secrets?
5.) Are Kubernetes Secrets encrypted by default at rest?
6.) What is the maximum size for a ConfigMap or Secret key-value pair?
7.) Which command is used to create a ConfigMap from a file?
8.) Which field in a Pod definition allows you to reference a Secret as an environment variable?
9.) What happens if a pod tries to mount a non-existent ConfigMap?
10.) Which section in a deployment spec mounts a ConfigMap as a volume?