Linux Foundation Updated CKA Exam Questions and Answers by steven

Task Summary

You are managing a WordPress Deployment in namespace relative-fawn.

Deployment has 3 replicas.

Pods are not starting due to high resource requests.

Your job:✅ Adjust CPU and memory requests so that all 3 pods evenly split the node’s capacity.

Step-by-Step Solution

1️⃣ SSH into the correct host

bash

CopyEdit

ssh cka000058

???? Skipping this will result in a zero score.

2️⃣ Check node resource capacity

You need to know the node’s CPU and memory resources.

bash

CopyEdit

kubectl describe node | grep -A5 "Capacity"

Example output:

yaml

CopyEdit

Capacity:

cpu: 3

memory: 3Gi

Let’s assume the node has:

3 CPUs

3Gi memory

So for 3 pods, divide evenly:

CPU request per pod: 1

Memory request per pod: 1Gi

⚠️ In the actual exam, check real values and divide accordingly. If the node has 4 CPUs and 8Gi, you'd allocate ~1.33 CPUs and ~2.66Gi RAM per pod (rounded reasonably).

3️⃣ Edit the Deployment

Edit the WordPress deployment in the relative-fawn namespace:

kubectl edit deployment wordpress -n relative-fawn

Look for the resources section under spec.template.spec.containers like this:

resources:

requests:

cpu: "1"

memory: "1Gi"

If the section doesn’t exist, add it manually.

Save and exit the editor (:wq if using vi).

4️⃣ Confirm changes

Wait a few seconds, then check:

kubectl get pods -n relative-fawn

Ensure all 3 pods are in Running state.

You can also describe a pod to confirm resource requests are set:

kubectl describe pod -n relative-fawn | grep -A5 "Containers"

ssh cka000058

kubectl describe node | grep -A5 "Capacity"

kubectl edit deployment wordpress -n relative-fawn

# Set CPU: 1, Memory: 1Gi (or according to node capacity)

kubectl get pods -n relative-fawn

kubectl get po –all-namespaces > /opt/pods-list.yaml

solution

F:\Work\Data Entry Work\Data Entry\20200827\CKA\6 B.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\6 C.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\6 D.JPG

Solution:

vi pvc.yaml

storageclass pvc

apiVersion: v1

kind: PersistentVolumeClaim

metadata:

name: pv-volume

spec:

accessModes:

- ReadWriteOnce

volumeMode: Filesystem

resources:

requests:

storage: 10Mi

storageClassName: csi-hostpath-sc

# vi pod-pvc.yaml

apiVersion: v1

kind: Pod

metadata:

name: web-server

spec:

containers:

- name: web-server

image: nginx

volumeMounts:

- mountPath: "/usr/share/nginx/html"

name: my-volume

volumes:

- name: my-volume

persistentVolumeClaim:

claimName: pv-volume

# craete

kubectl create -f pod-pvc.yaml

#edit

kubectl edit pvc pv-volume --record