List all persistent volumes sorted bycapacity, saving the fullkubectloutput to
/opt/KUCC00102/volume_list. Usekubectl 's own functionality forsorting the output, and do not manipulate it any further.

Correct Answer:

See the solution below.
Explanation
solution

Comment: *

Name: *

Email: *

Verification: *

Create 5 nginx pods in which two of them is labeled env=prod and
three of them is labeled env=dev

• A.kubectl run nginx-dev1 --image=nginx --restart=Never --
  labels=env=dev
  kubectl run nginx-dev2 --image=nginx --restart=Never --
  labels=env=dev
  kubectl run nginx-prod1 --image=nginx --restart=Never --
  labels=env=prod
  kubectl run nginx-prod2 --image=nginx --restart=Never --
  labels=env=prod
• B.kubectl run nginx-dev1 --image=nginx --restart=Never --
  labels=env=dev
  kubectl run nginx-dev2 --image=nginx --restart=Never --
  labels=env=dev
  kubectl run nginx-dev3 --image=nginx --restart=Never --
  labels=env=dev
  kubectl run nginx-prod1 --image=nginx --restart=Never --
  labels=env=prod
  kubectl run nginx-prod2 --image=nginx --restart=Never --
  labels=env=prod

Comment: *

Name: *

Email: *

Verification: *

Print pod name and start time to "/opt/pod-status" file

Comment: *

Name: *

Email: *

Verification: *

You need to configure CoreDNS to resolve DNS queries for services in different namespaces within your Kubernetes cluster. You want to ensure that pods in one namespace cannot resolve the names of services in other namespaces unless explicitly allowed.

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1 . Configure CoreDNS with Namespace-Specific DNS:
- In the CoreDNS ConfigMap, configure the 'kubernetes' plugin to restrict DNS resolution based on namespaces.

2. Use Network Policies for Cross-Namespace Communication: - If you need pods in one namespace to communicate with services in another namespace, use network policies to explicitly allow the communication.

3. Test Namespace-Specific DNS: - Deploy pods in different namespaces and try to resolve service names from those pods. You should only be able to resolve names of services in the same namespace or namespaces that have been explicitly allowed using network policies.

Comment: *

Name: *

Email: *

Verification: *

A Kubernetes worker node, named wk8s-node-0 is in state NotReady. Investigate why this is the case, and perform any appropriate steps to bring the node to a state, ensuring that any changes are made permanent.
You can ssh to the failed node using:
[student@node-1] $ | ssh Wk8s-node-0
You can assume elevated privileges on the node with the following command:
[student@w8ks-node-0] $ | sudo -i

Correct Answer:

See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\20 C.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\20 D.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\20 E.JPG

Comment: *

Name: *

Email: *

Verification: *