We have an external webserver running on student-node which is exposed at port 9999. We have created a service called external-webserver-cka03-svcn that can connect to our local webserver from within the kubernetes cluster3 but at the moment it is not working as expected.
The nginx service is running on the port 80 but not 9999. So when I run the following I get this error and don’t get the error when I don’t specify the port.
student-node ~ ➜ curl student-node:9999
curl: (7) Failed to connect to student-node port 9999: Connection refused
This is another question:
One of our Junior DevOps engineers have deployed a pod nginx-wl06 on the cluster3-controlplane node. However, while specifying the resource limits, instead of using Mebibyte as the unit, Gebibyte was used.
As a result, the node doesn’t have sufficient resources to deploy this pod and it is stuck in a pending state
Fix the units and re-deploy the pod (Delete and recreate the pod if needed).
I edited the pod which it created a file under /tmp dir, and then created the pod with kubectl replace --force -f /tmp/…yaml file but in the answers section it says that I see that the memory is not fixed.
I assume this is the “Ultimate Mock Exams” for CKA – please tell me if otherwise. Also: it helps, and helps a lot, if you say which question numbers these are, so we can find them. Thanks!
For this question, please set the context to cluster3 by running:
kubectl config use-context cluster3
One of our Junior DevOps engineers have deployed a pod nginx-wl06 on the cluster3-controlplane node. However, while specifying the resource limits, instead of using Mebibyte as the unit, Gebibyte was used.
As a result, the node doesn’t have sufficient resources to deploy this pod and it is stuck in a pending state
Fix the units and re-deploy the pod (Delete and recreate the pod if needed).
- 17 / 20
For this question, please set the context to cluster3 by running:
kubectl config use-context cluster3
We have an external webserver running on student-node which is exposed at port 9999. We have created a service called external-webserver-cka03-svcn that can connect to our local webserver from within the kubernetes cluster3 but at the moment it is not working as expected.
Fix the issue so that other pods within cluster3 can use external-webserver-cka03-svcn service to access the webserver.
For Q1, not sure what the problem is, since the cluster allows the pod to run on a request for 260Gi, yet it does. The Q does not seem to verify either.
For Q17, this is a known issue and is in our bug base; looks like an engineer was recently assigned to it.