See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Update the Deployment YAML:
- Update the 'replicas' to 5.
- Define 'maxUnavailable: 2' and 'maxSurge: 0' in the 'strategy.rollingUpdate' section to control the rolling update process.
- Configure a 'strategy.type' to 'RollingUpdate' to trigger a rolling update when the deployment is updated.
- Set Always' to ensure that the new image is pulled even if
it exists in the pod's local cache.
- Add a 'spec.progressDeadlineSeconds: 480' to set a timeout of 8 minutes for the update process.
- Add a 'spec.template.spec.containers[0].lifecycle.postStart' hook to define a script that executes a health check script before the container starts accepting traffic.

2. Create the Deployment: - Apply the updated YAML file using 'kubectl apply -f frontend-deployment.yaml' 3. Verify the Deployment: - Check the status of the deployment using 'kubectl get deployments frontend-deployment' to confirm the rollout and updated replica count. 4. Trigger the Automatic Update: - Push a new image to the 'my.org/frontend:latest' Docker Hub repository. 5. Monitor the Deployment: - Use 'kubectl get pods -l app=frontend' to monitor the pod updates during the rolling update process. 6. Observe Rollback if Timeout Exceeds: - If the update process takes longer than 8 minutes to complete, the deployment will be rolled back to the previous version. This can be observed using 'kubectl describe deployment frontend-deployment' and checking the 'updatedReplicas' and 'availableReplicas' fields.,

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

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

See the solution below.
Explanation
solution

See the solution below.
Explanation
kubect1 get po nginx-dev -o
jsonpath='{.spec.containers[].image}{"\n"}'