Schedule Pods Using Required Pod Affinity
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.
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.
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.
Deploy a multi-container Kubernetes Deployment and ensure that no more than one Pod runs on the same worker node, without using a DaemonSet.
Troubleshoot and update a Kubernetes DaemonSet so that its Pods run on all nodes in the cluster, including the control plane.