You must connect to the correct host. Failure to do so may result in a zero score. Context: Your cluster 's CNI has failed a security audit. It has been removed. You must install a new CNI that can…

Question

Exhibits

Explanation

Explanation: 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 SH 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.

4 (Optional) 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

No community discussion yet for this question.