ConfigMaps & Secrets Interview Questions

Why ConfigMaps and Secrets Matter in Interviews

ConfigMaps and Secrets represent a fundamental cloud-native pattern: separating configuration from application code. Interviewers use this topic to evaluate whether candidates can build portable, secure deployments rather than hardcoding values into container images.

Basic questions ask you to create a ConfigMap and consume it in a Pod. Intermediate questions explore the differences between mounting as a volume versus injecting as environment variables, including the live-update behavior of volume mounts. Advanced questions focus on security: candidates must recognize that Kubernetes Secrets are only base64-encoded (not encrypted) and articulate how to enable encryption at rest, use RBAC to restrict Secret access, and integrate external secret management solutions.

Interviewers also look for awareness of operational concerns like immutable ConfigMaps for large-scale clusters, the 1 MiB size limit on ConfigMap and Secret data, and strategies for rolling Pods when configuration changes. Being able to discuss these nuances signals readiness for production operations.