Why resource management matters in Kubernetes - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why set resource limits in Kubernetes?

What is the main reason to set CPU and memory limits on containers in Kubernetes?

A To automatically scale the number of pods based on resource usage

B To speed up container startup time by reserving resources in advance

C To allow containers to use unlimited resources when needed

D To prevent a container from using more resources than allocated, avoiding node instability

💡 Hint

Think about what happens if one container uses too much CPU or memory.

Setting resource limits prevents a container from consuming excessive CPU or memory, which can cause other containers or the node to become unstable or crash.

💻 Command Output

intermediate

Check resource usage of pods

What is the output of the command kubectl top pod in a Kubernetes cluster?

Kubernetes

kubectl top pod

A Lists pods with their current CPU and memory usage

B Shows the status of nodes in the cluster

C Displays the logs of all pods

D Shows the YAML configuration of all pods

💡 Hint

Think about what 'top' means in Linux commands.

The kubectl top pod command shows the current CPU and memory usage of each pod, helping monitor resource consumption.

🔀 Workflow

advanced

Order the steps to prevent resource starvation in Kubernetes

Put the steps in the correct order to prevent resource starvation by managing pod resources properly.

A 1,2,3,4

B 2,1,4,3

C 1,3,2,4

D 2,3,1,4

💡 Hint

Think about defining limits first, then checking usage, then adjusting and redeploying.

First, define resource requests and limits. Then monitor usage to see if adjustments are needed. Next, update limits accordingly. Finally, redeploy pods with new settings.

❓ Troubleshoot

advanced

Identify the cause of pod eviction

A pod in your Kubernetes cluster was evicted with the message 'The node was low on resource: memory'. What is the most likely cause?

A The pod image failed to download

B The pod exceeded its memory limit causing the node to run out of memory

C The pod's CPU usage was too high causing eviction

D The pod was deleted manually by an admin

💡 Hint

Eviction due to low resource usually relates to memory or CPU pressure on the node.

When a node runs low on memory, Kubernetes evicts pods that use more memory than their limits to free resources and keep the node stable.

✅ Best Practice

expert

Choose the best practice for resource requests and limits

Which practice helps ensure efficient resource use and cluster stability in Kubernetes?

A Do not set any resource requests or limits to let Kubernetes manage automatically

B Set very high limits and low requests to allow pods to burst resources freely

C Set resource requests equal to limits for predictable scheduling and avoid overcommitment

D Set requests higher than limits to reserve more resources than allowed

💡 Hint

Think about how Kubernetes schedules pods and manages resources.

Setting requests equal to limits helps Kubernetes schedule pods reliably and prevents resource overcommitment that can cause instability.