kubectl run busybox --image=busybox -it --rm --restart=Never --

/bin/sh -c ' echo hello world '

kubectl get po # You shouldn ' t see pod with the name " busybox "

Kubectl logs frontend | grep -i “started” > /opt/error-logs

Solution:

kubectl describe nodes | grep ready|wc -l

kubectl describe nodes | grep -i taint | grep -i noschedule |wc -l

echo 3 > /opt/KUSC00402/kusc00402.txt

#

kubectl get node | grep -i ready |wc -l

# taints、noSchedule

kubectl describe nodes | grep -i taints | grep -i noschedule |wc -l

#

echo 2 > /opt/KUSC00402/kusc00402.txt

solution

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

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

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

solution

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

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

F:\Work\Data Entry Work\Data Entry\20200827\CKA\23 E.JPG

solution

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

kubectl run nginx --image=nginx --restart=Never --port=80

Task Summary

Create an HPA named apache-server in the autoscale namespace.

Target an existing deployment also named apache-server.

CPU target: 50%

Pod range: min 1, max 4

Downscale stabilization window: 30 seconds

Step-by-Step Answer

???? Step 1: Connect to the correct host

This is critical, as shown in the warning image.

ssh cka000050

???? Skipping this may result in zero for this question!

???? Step 2: Verify the deployment exists

kubectl get deployment apache-server -n autoscale

Make sure it’s there before creating the HPA. If it’s missing, the HPA won ' t bind correctly.

⚙️ Step 3: Create the HPA

We will use the kubectl autoscale command for a quick setup, then patch it to add the stabilization window (since kubectl autoscale doesn ' t include it).

kubectl autoscale deployment apache-server \

--namespace autoscale \

--cpu-percent=50 \

--min=1 \

--max=4

???? Step 4: Add the downscale stabilization window

You’ll need to patch the HPA to include the stabilization window of 30s.

Create a patch file called hpa-patch.yaml:

spec:

behavior:

scaleDown:

stabilizationWindowSeconds: 30

Apply the patch:

bash

CopyEdit

kubectl patch hpa apache-server \

-n autoscale \

--patch " $(cat hpa-patch.yaml) "

✅ Step 5: Confirm your work

bash

CopyEdit

kubectl describe hpa apache-server -n autoscale

Look for:

Min/Max Pods: 1/4

Target CPU utilization: 50%

Stabilization window: should appear under Behavior > ScaleDown

ssh cka000050

kubectl get deployment apache-server -n autoscale

kubectl autoscale deployment apache-server \

--namespace autoscale \

--cpu-percent=50 \

--min=1 \

--max=4

# Patch to add stabilization window

cat < < EOF > hpa-patch.yaml

spec:

behavior:

scaleDown:

stabilizationWindowSeconds: 30

EOF

kubectl patch hpa apache-server -n autoscale --patch " $(cat hpa-patch.yaml) "

Task Summary

SSH into cka000054

Install a CNI plugin that supports NetworkPolicies

Two CNI options provided:

Flannel v0.26.1 (❌ does NOT support NetworkPolicies)

Calico v3.28.2 ✅ (does support NetworkPolicies)

❗ Decision Point: Which CNI to choose?

✅ Choose Calico, because only Calico supports enforcing NetworkPolicies natively. Flannel does not.

✅ Step-by-Step Solution

1️⃣ SSH into the correct node

ssh cka000054

⚠️ Required. Skipping this results in zero score.

2️⃣ Install Calico CNI (v3.28.2)

Use the official manifest provided:

kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.28.2/manifests/tigera-operator.yaml

This installs the Calico Operator, which then deploys the full Calico CNI stack.

3️⃣ Wait for Calico components to come up

Check the pods in tigera-operator and calico-system namespaces:

kubectl get pods -n tigera-operator

kubectl get pods -n calico-system

✅ You should see pods like:

calico-kube-controllers

calico-node

calico-typha

tigera-operator

Wait for all to be in Running state.

✅ (Optional) 4️⃣ Confirm CNI is enforcing NetworkPolicies

You can check:

kubectl get crds | grep networkpolicy

You should see:

networkpolicies.crd.projectcalico.org

This confirms Calico ' s CRDs are installed for policy enforcement.

Final Command Summary

ssh cka000054

kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.28.2/manifests/tigera-operator.yaml

kubectl get pods -n tigera-operator

kubectl get pods -n calico-system

kubectl get crds | grep networkpolicy

A screen shot of a computer AI-generated content may be incorrect.