Pending on Purpose, Pending by Mistake

medium 20 XP ~8 minHands-on lab

The worker nodes reserved for the reports team's batch work carry a label for it. The team's wishlist Deployment is meant to run only on those nodes, but its Pods have been Pending since it was created.

Task

  • Both replicas of wishlist in reports run, and only on the nodes reserved for the team's batch work.
  • The Deployment must keep requiring the node label the team uses for batch work, so its Pods can never land on any other node.
  • Don't change any node's labels or taints.

Start with kubectl get nodes --show-labels and kubectl describe pod -n reports -l app=wishlist.

About this machine

Ubuntu 24.04 with a private practice cluster: a real Kubernetes API server, scheduler and controllers, and three nodes (controlplane, node01, node02). Containers are simulated, so images never download and kubectl logs/exec are not available. k is an alias for kubectl, with completion. The grader checks the cluster's final state, not the commands you typed.

TerminalNot started

Your machine is ready to start

Create a free account to open a machine and get graded.