Schedule a Maintenance Pod with Host Namespace Access Using Taints, Tolerations, and NodeSelector
Learn how to taint a node, schedule a Pod using nodeSelector and tolerations, and share the host network, PID, and IPC namespaces with the Pod.
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.
Challenges contributed by the community members sharing their knowledge and expertise.
Learn how to taint a node, schedule a Pod using nodeSelector and tolerations, and share the host network, PID, and IPC namespaces with the Pod.
Create a Deployment with specific scheduling, labels, and port configuration, then expose it externally using a NodePort Service.
A Kubernetes cluster has an existing database Deployment running. Configure a new web Deployment to schedule its pods only on nodes where the database pods are already running using required pod affinity.
A Kubernetes cluster has tainted nodes to restrict pod scheduling. Configure a Deployment to schedule pods exclusively on a specific tainted node using both tolerations and required node affinity.