Task Summary

SSH into the correct node: cka000037

Modify existing deployment synergy-leverager

Add a sidecar container:

Name: sidecar

Image: busybox:stable

Command:

/bin/sh -c " tail -n+1 -f /var/log/synergy-leverager.log "

Use a shared volume mounted at /var/log

Don ' t touch existing container config except adding volume mount

Step-by-Step Solution

1️⃣ SSH into the correct node

ssh cka000037

⚠️ Skipping this will result in a zero score.

2️⃣ Edit the deployment

kubectl edit deployment synergy-leverager

This opens the deployment YAML in your default editor (vi or similar).

3️⃣ Modify the spec as follows

???? Inside the spec.template.spec, do these 3 things:

✅ A. Define a shared volume

Add under volumes: (at the same level as containers):

volumes:

- name: log-volume

emptyDir: {}

✅ B. Add volume mount to the existing container

Locate the existing container under containers: and add this:

volumeMounts:

- name: log-volume

mountPath: /var/log

???? Do not change any other configuration for this container.

✅ C. Add the sidecar container

Still inside containers:, add the new container definition after the first one:

- name: sidecar

image: busybox:stable

command:

- /bin/sh

- -c

- " tail -n+1 -f /var/log/synergy-leverager.log "

volumeMounts:

- name: log-volume

mountPath: /var/log

spec:

containers:

- name: main-container

image: your-existing-image

volumeMounts:

- name: log-volume

mountPath: /var/log

- name: sidecar

image: busybox:stable

command:

- /bin/sh

- -c

- " tail -n+1 -f /var/log/synergy-leverager.log "

volumeMounts:

- name: log-volume

mountPath: /var/log

volumes:

- name: log-volume

emptyDir: {}

Save and exit

If using vi or vim, type:

bash

CopyEdit

wq

5️⃣ Verify

Check the updated pods:

kubectl get pods -l app=synergy-leverager

Pick a pod name and describe it:

kubectl describe pod < pod-name >

Confirm:

2 containers running (main-container + sidecar)

Volume mounted at /var/log

ssh cka000037

kubectl edit deployment synergy-leverager

# Modify as explained above

kubectl get pods -l app=synergy-leverager

kubectl describe pod < pod-name >

kubectl get pods -o=jsonpath= " {.items[*][ ' metadata.name ' ,

' metadata.namespace ' ]} "

Solution:

Task should be complete on node k8s -1 master, 2 worker for this connect use command

[student@node-1] > ssh k8s

kubectl create clusterrole deployment-clusterrole --verb=create --resource=deployments,statefulsets,daemonsets

kubectl create serviceaccount cicd-token --namespace=app-team1

kubectl create rolebinding deployment-clusterrole --clusterrole=deployment-clusterrole --serviceaccount=default:cicd-token --namespace=app-team1

Task Summary

You are given a host to prepare for Kubernetes:

Use dpkg to install cri-dockerd

Enable and start the cri-docker service

Set net.bridge.bridge-nf-call-iptables to 1 via sysctl

Step-by-Step Instructions

1️⃣ SSH into the correct node

bash

CopyEdit

ssh cka000051

⚠️ Required — failure to connect to the correct host = zero score.

2️⃣ Install cri-dockerd

You are told the .deb file is already located at:

bash

CopyEdit

~/cri-dockerd_0.3.9.3-0.ubuntu-jammy_amd64.deb

Install it with dpkg:

bash

CopyEdit

sudo dpkg -i ~/cri-dockerd_0.3.9.3-0.ubuntu-jammy_amd64.deb

???? If any dependencies are missing (e.g., golang or containerd), you might need:

bash

CopyEdit

sudo apt-get install -f -y

But usually, the exam system provides a pre-validated .deb environment.

3️⃣ Enable and start cri-docker service

Start and enable both services:

bash

CopyEdit

sudo systemctl enable cri-docker.service

sudo systemctl enable --now cri-docker.socket

sudo systemctl start cri-docker.service

Check status (optional but smart):

bash

CopyEdit

sudo systemctl status cri-docker.service

You should see it active (running).

4️⃣ Configure the sysctl parameter

Set net.bridge.bridge-nf-call-iptables=1 immediately and persistently.

Step A: Apply immediately:

sudo sysctl net.bridge.bridge-nf-call-iptables=1

Step B: Persist it in /etc/sysctl.d:

Create or modify a file:

echo " net.bridge.bridge-nf-call-iptables = 1 " | sudo tee /etc/sysctl.d/k8s.conf

Reload sysctl:

sudo sysctl --system

Verify:

sysctl net.bridge.bridge-nf-call-iptables

Should return:

net.bridge.bridge-nf-call-iptables = 1

✅ Now the system is ready for kubeadm with Docker (via cri-dockerd)!

ssh cka000051

sudo dpkg -i ~/cri-dockerd_0.3.9.3-0.ubuntu-jammy_amd64.deb

sudo systemctl enable cri-docker.service

sudo systemctl enable --now cri-docker.socket

sudo systemctl start cri-docker.service

sudo sysctl net.bridge.bridge-nf-call-iptables=1

echo " net.bridge.bridge-nf-call-iptables = 1 " | sudo tee /etc/sysctl.d/k8s.conf

sudo sysctl --system

kubectl create namespace development

kubectl run nginx --image=nginx --restart=Never -n development

kubectl get pods --sort-by=.metadata.name

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