Mount a ConfigMap and Secret into a Single Directory Using a Projected Volume
Combine an existing ConfigMap and Secret into one volume and mount them at a single path inside a Pod — using only one volume definition.
Focused hands-on problems designed to help you hone your DevOps or Server Side skills. Some challenges are more educational, while others are based on real-world scenarios. The platform provides hints and feedback for each challenge, including automated solution checks.
Combine an existing ConfigMap and Secret into one volume and mount them at a single path inside a Pod — using only one volume definition.
A Deployment is stuck with Pods in ContainerCreating state because the required ConfigMap was not created. Fix the issue to make the application accessible.
A Deployment is failing because application configuration is missing. Mount only specific keys from an existing ConfigMap as files inside the Pod at the correct path so the application can start successfully.
A Pod is failing in the japan namespace. Investigate the issue, identify the root cause, and fix it to get the Pod running.
Create a Pod with ConfigMap volume mount, expose it via ClusterIP Service, and test connectivity from another namespace. This combines multiple Kubernetes concepts.
Create a ConfigMap, mount it into a Deployment as individual files, and validate the mounted values using a readiness probe.
Inject ConfigMap values as environment variables into a Kubernetes Pod.