Diagnose Why a DaemonSet Skips the Control Plane Node
Troubleshoot and update a Kubernetes DaemonSet so that its Pods run on all nodes in the cluster, including the control plane.
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.
Troubleshoot and update a Kubernetes DaemonSet so that its Pods run on all nodes in the cluster, including the control plane.
Observe the Delete and Retain reclaim policies in action, recover a Released PV by patching claimRef, and recover data by creating a new PV pointing to the same storage directory.
Explore how the DefaultStorageClass admission controller injects storage classes, explicitly name a StorageClass, switch the cluster default, and inspect where local-path stores volumes on the node.
Learn the three static PV binding patterns - generic match, label selector, and bidirectional claimRef - then use a no-provisioner StorageClass with WaitForFirstConsumer to pin storage to a specific node.
The cluster is broken again. Get the Klustered deployment healthy and serving a quote, then ship the v2 image to unlock the victory dance.
Make sure the Klustered deployment is running the v2 tag and that you can visit the application to see a lovely quote and a video of me dancing.
A deployment is failing because the application cannot load its TLS certificate. Create the missing secret and mount it into the deployment so the Flask app can serve TLS traffic.
Add a sidecar container to an existing Deployment that tails a shared log file written by the main application container. Use a shared volume to make the log file available to both containers.
Implement a canary deployment strategy using the Kubernetes Gateway API. Route the majority of traffic to a stable version of a service while gradually shifting a small percentage to a new canary version.
Configure a Kubernetes Gateway API setup with the Gateway in a dedicated infrastructure namespace and HTTPRoute in the application namespace, using path-based routing to expose railway platform services.