Enforce TLSv1.3-Only Policy on a Production NGINX Deployment
Update a production NGINX ConfigMap to restrict TLS to v1.3 only, then verify the change enforces the security policy.
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.
Update a production NGINX ConfigMap to restrict TLS to v1.3 only, then verify the change enforces the security policy.
A Deployment is using a disk-backed emptyDir volume. Convert it to a memory-backed tmpfs volume for better performance — but make sure to set a size limit to prevent the Pod from exhausting the node's RAM.
A distroless pod running in the cherry namespace has no shell or debugging tools. Use kubectl debug to attach an ephemeral container, test connectivity to the request-logger service, and verify the request was received in its logs.
A Deployment is stuck with Pods in ContainerCreating state because the required ConfigMap was not created. Fix the issue to make the application accessible.
Create a Pod in the processing namespace that runs a short task and exits successfully, reaching a Completed status without using a Job controller.
Troubleshoot a Deployment where containers are repeatedly OOMKilled. Inspect Vertical Pod Autoscaler (VPA) recommendations and manually apply the recommended memory request and memory limit to stabilize the workload.
Create a Kubernetes Job template for Team Aurora that runs a busybox command across multiple completions in parallel, with specific pod labels and container configuration.
Create a Pod that uses a postStart lifecycle hook to write a custom message to the nginx welcome page, expose it via a NodePort Service, and verify the hook ran successfully.
A Pod is running nginx and exposed via NodePort. Copy a local HTML file into the running Pod so NGINX serves it as the default homepage using only imperative commands.
A Service exists in a namespace. Use a temporary Pod to resolve DNS, save the output, and confirm the Pod is automatically removed after the tasks complete.