Create a deployment as follows:
Name: nginx-random
Exposed via a service nginx-random Ensure that the service & pod are accessible via their respective DNS records The container(s) within any pod(s) running as a part of this deployment should use the nginx Image
Next, use the utility nslookup to look up the DNS records of the service & pod and write the output to
/opt/KUNW00601/service.dns and /opt/KUNW00601/pod.dns respectively.
Solution:
Solution:
F:WorkData Entry WorkData Entry20200827CKA17 C.JPG
F:WorkData Entry WorkData Entry20200827CKA17 D.JPG
F:WorkData Entry WorkData Entry20200827CKA17 E.JPG
Does this meet the goal?
Correct Answer:
A
Scale the deployment webserver to 6 pods.
Solution:
solution
F:WorkData Entry WorkData Entry20200827CKA14 B.JPG
Does this meet the goal?
Correct Answer:
A
List all the pods showing name and namespace with a json path expression
Solution:
kubectl get pods -o=jsonpath="{.items[*]['metadata.name', 'metadata.namespace']}"
Does this meet the goal?
Correct Answer:
A
Ensure a single instance of pod nginx is running on each node of the Kubernetes cluster where nginx also represents the Image name which has to be used. Do not override any taints currently in place.
Use DaemonSet to complete this task and use ds-kusc00201 as DaemonSet name.
Solution:
solution
F:WorkData Entry WorkData Entry20200827CKA3 B.JPG
F:WorkData Entry WorkData Entry20200827CKA3 C.JPG
F:WorkData Entry WorkData Entry20200827CKA3 D.JPG
F:WorkData Entry WorkData Entry20200827CKA3 E.JPG
Does this meet the goal?
Correct Answer:
A
Check to see how many worker nodes are ready (not including nodes tainted NoSchedule) and write the number to /opt/KUCC00104/kucc00104.txt.
Solution:
solution
F:WorkData Entry WorkData Entry20200827CKA15 B.JPG
F:WorkData Entry WorkData Entry20200827CKA15 C.JPG
Does this meet the goal?
Correct Answer:
A
