Focused, hands-on problems for sharpening your DevOps and server-side skills. Some teach specific concepts while others mirror real-world scenarios. Every challenge includes hints, feedback, and automated solution checks.
Challenges contributed by the community members sharing their knowledge and expertise.
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 service in the mesh namespace returns only a single IP during DNS lookup, preventing the peer-server pods from finding each other. Investigate why DNS does not return one address per pod and change the service configuration so that peer discovery works correctly.
Add a new, separate Service CIDR range for the dev team using the ServiceCIDR API object — without touching or restarting the cluster's default Service CIDR — then create a Service with an explicit ClusterIP inside that new range and verify DNS resolution.
Configure a Kubernetes Service so that requests from the same client IP are always routed to the same backend Pod for a sustained period, using ClientIP-based session affinity.
A web application is deployed but the website is not accessible. Investigate and fix the issue.
A Deployment with two nginx containers has a port conflict — both containers use port 80. Fix the conflict by updating the ConfigMap, mounting it into the second container, updating the containerPort, and exposing both containers via a NodePort Service.
Create a Deployment with specific scheduling, labels, and port configuration, then expose it externally using a NodePort Service.
Create a Pod with ConfigMap volume mount, expose it via ClusterIP Service, and test connectivity from another namespace. This combines multiple Kubernetes concepts.
An existing e-commerce frontend application is running in Kubernetes. Scale the deployment to handle increased traffic and expose it using a NodePort Service with proper labeling.
An existing application is running in Kubernetes. A new version must be rolled out using a canary deployment while ensuring traffic is properly distributed.