Resource quotas per namespace in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Check current resource quotas in a namespace

You run the command kubectl get resourcequota -n dev. What output do you expect if no resource quotas are set in the dev namespace?

Kubernetes

kubectl get resourcequota -n dev

A

NAME      AGE
cpu-quota  10d

B No resources found in dev namespace.

C Error from server (NotFound): resourcequotas "dev" not found

D

NAME      CPU    MEMORY
quota1    2      4Gi

💡 Hint

Think about what kubectl shows when no resource quotas exist in a namespace.

If no resource quotas exist in the specified namespace, kubectl shows a message indicating no resources found. It does not show errors or quota details.

❓ Configuration

intermediate

Define a resource quota limiting CPU and memory

Which YAML snippet correctly defines a resource quota named limit-quota in namespace test that limits CPU to 2 cores and memory to 4Gi?

A

apiVersion: v1
kind: ResourceQuota
metadata:
  name: limit-quota
  namespace: test
spec:
  hard:
    cpu: 2 cores
    memory: 4Gi

B

apiVersion: v1
kind: ResourceQuota
metadata:
  name: limit-quota
spec:
  hard:
    cpu: 2
    memory: 4Gi
  namespace: test

C

apiVersion: v1
kind: ResourceQuota
metadata:
  name: limit-quota
  namespace: test
spec:
  limits:
    cpu: "2"
    memory: 4Gi

D

apiVersion: v1
kind: ResourceQuota
metadata:
  name: limit-quota
  namespace: test
spec:
  hard:
    cpu: "2"
    memory: 4Gi

💡 Hint

Check the correct placement of namespace and the 'hard' field format.

The namespace is set under metadata. The resource limits go under spec.hard with values as strings. CPU is specified as "2" (string), not 2 (number) or '2 cores'.

❓ Troubleshoot

advanced

Why is a pod creation failing due to resource quota?

You have a resource quota limiting pods to 5 in namespace prod. You try to create a 6th pod and get this error: pods "mypod" is forbidden: exceeded quota: pod-quota, requested: pods=1, used: pods=5, limited: pods=5. What is the root cause?

A The namespace has reached the maximum allowed pods defined by the resource quota.

B The pod spec requests more CPU than allowed by the quota.

C The pod name conflicts with an existing pod in the namespace.

D The resource quota is not applied to the namespace.

💡 Hint

Look at the error message details about pods and quota limits.

The error clearly states the pod count requested exceeds the quota limit of 5 pods in the namespace, so the creation is blocked.

🔀 Workflow

advanced

Steps to update an existing resource quota

You want to increase the CPU limit in an existing resource quota named cpu-quota in namespace dev from 2 to 4 cores. Which sequence of commands is correct?

A

kubectl get resourcequota cpu-quota -n dev -o yaml > quota.yaml
Edit quota.yaml to set cpu: "4"
kubectl apply -f quota.yaml -n dev

B

kubectl edit resourcequota cpu-quota -n dev
Change cpu to 4
Save and exit

C All of the above sequences are correct

D kubectl patch resourcequota cpu-quota -n dev --type='merge' -p '{"spec":{"hard":{"cpu":"4"}}}'

💡 Hint

Consider different ways kubectl allows editing resources.

All three methods (export-edit-apply, kubectl edit, and kubectl patch) are valid ways to update resource quotas in Kubernetes.

✅ Best Practice

expert

Why use resource quotas per namespace in a multi-team cluster?

What is the main benefit of applying resource quotas per namespace in a Kubernetes cluster shared by multiple teams?

A It prevents any single team from using more than their fair share of cluster resources, ensuring fair resource distribution.

B It automatically scales pods up and down based on team usage.

C It encrypts all data stored in the namespace to secure team data.

D It allows teams to bypass cluster-wide security policies.

💡 Hint

Think about resource fairness and limits in shared environments.

Resource quotas limit resource consumption per namespace, preventing teams from exhausting cluster resources and ensuring fair sharing.