SOLUTION:
[student@node-1] > ssh ek8s
kubectl cordon ek8s-node-1
kubectl drain ek8s-node-1 --delete-local-data --ignore-daemonsets --force

See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\14 B.JPG

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Install the Ingress Controller:
- If you haven't already, install an Ingress controller. Common options include:
- NGINX Ingress Controller: [https://kubernetes.github.io/ingress-nginx/](https://kubernetes.github.io/ingress- nginx/)
- Traefik Ingress Controller: [https://traefik.io[](https://traefik.io/)
2. Create an Ingress Resource:
- Create a new Ingress resource using the following YAML structure, replacing the placeholders with your actual values:

3. Configure DNS: - Create a DNS record for your domain 'my-app.example.com' pointing to the IP address of your Ingress controller. This can be either a LoadBalancer service IP or the Ingress controller's pod IP if you're using NodePort. 4. Verify Ingress Setup: - Once the DNS records are propagated, you should be able to access your web application through the configured domain name 'my-app.example.com'.

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Update the PVC Access Mode:
- Modify the access mode in the PersistentVolumeClaim YAML file to 'ReadWriteMany'.

2. Update the Deployment: - Update the Deployment YAML to reflect the change in access mode:

3. Apply the Changes: - Apply the updated PVC and Deployment YAML files using 'kubectl apply -f wordpress-pvc.yaml' and 'kubectl apply -f wordpress-deployment.yamr , respectively. 4. Verify the Changes: - Use 'kubectl describe pvc wordpress-pvc' to verify that the access mode has been updated to ReadWriteMany'. - Check the deployment status using 'kubectl get deployments wordpress-deployment' to confirm that the deployment is running with the updated PVC.

solution