Node selectors for simple scheduling in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does a node selector do in Kubernetes scheduling?

In Kubernetes, what is the primary purpose of using a nodeSelector in a Pod specification?

A It restricts the Pod to be scheduled only on nodes that have matching labels specified in the nodeSelector.

B It automatically scales the number of Pods based on node CPU usage.

C It assigns a static IP address to the Pod within the cluster network.

D It encrypts the Pod's data at rest on the node's disk.

💡 Hint

Think about how Kubernetes decides where to place Pods based on node labels.

A nodeSelector is a simple way to constrain Pods to run only on nodes with specific labels. It filters nodes during scheduling.

💻 Command Output

intermediate

Output of kubectl get pods with nodeSelector applied

You have a Pod with the following nodeSelector:

nodeSelector:
  disktype: ssd

After applying this Pod manifest, what will kubectl get pods -o wide show in the NODE column?

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: test-pod
spec:
  containers:
  - name: nginx
    image: nginx
  nodeSelector:
    disktype: ssd

A An error message indicating invalid nodeSelector.

B The name of any node in the cluster, regardless of labels.

C <none> because the Pod is pending and not scheduled.

D The name of a node that has the label 'disktype=ssd'.

💡 Hint

Check how nodeSelector affects Pod scheduling and node assignment.

The Pod will be scheduled only on nodes labeled with 'disktype=ssd', so the NODE column shows such a node's name.

❓ Configuration

advanced

Correct nodeSelector syntax in Pod manifest

Which of the following Pod YAML snippets correctly uses nodeSelector to schedule the Pod on nodes labeled zone: us-east-1?

A

spec:
  nodeSelector:
    - zone: us-east-1
  containers:
  - name: app
    image: myapp

B

spec:
  nodeSelector:
    zone: "us-east-1"
  containers:
  - name: app
    image: myapp

C

spec:
  nodeSelector:
    zone: us-east-1
  containers:
  - name: app
    image: myapp

D

spec:
  nodeSelector:
    zone: [us-east-1]
  containers:
  - name: app
    image: myapp

💡 Hint

Remember that nodeSelector expects a map of key-value pairs with string values.

Option B correctly uses a string value for the label. Option B misses quotes but is valid YAML; however, quotes are recommended for clarity. Option B uses a list which is invalid. Option B uses a list as value which is invalid.

❓ Troubleshoot

advanced

Pod stuck in Pending state with nodeSelector

You created a Pod with this nodeSelector:

nodeSelector:
  gpu: "true"

The Pod remains in Pending state indefinitely. What is the most likely cause?

A No nodes in the cluster have the label <code>gpu=true</code>.

B The Pod image is invalid and cannot be pulled.

C The nodeSelector syntax is incorrect and causes a scheduling error.

D The Pod's resource requests exceed the node capacity.

💡 Hint

Check if any node matches the nodeSelector labels.

If no node has the label gpu=true, the scheduler cannot place the Pod, so it stays Pending.

✅ Best Practice

expert

Best practice for nodeSelector usage in multi-environment clusters

You manage a Kubernetes cluster shared by multiple teams and environments. Which approach is best to use nodeSelector for simple scheduling to isolate workloads by environment?

A Use nodeSelector with random labels to distribute Pods evenly across all nodes.

B Avoid nodeSelector and rely only on resource requests for scheduling decisions.

C Label nodes with environment names (e.g., <code>env=dev</code>, <code>env=prod</code>) and use matching nodeSelectors in Pod specs.

D Label Pods with environment names and use nodeSelector to match Pod labels.

💡 Hint

Think about how nodeSelector matches node labels, not Pod labels.

NodeSelector matches node labels, so labeling nodes by environment and using nodeSelector in Pods to match those labels is a simple and effective isolation method.