You must connect to the correct host.
Failure to do so may result in a zero score.
[candidate@base] $ ssh Cka000056
Task
Review and apply the appropriate NetworkPolicy from the provided YAML samples.
Ensure that the chosen NetworkPolicy is not overly permissive, but allows communication between the frontend and backend Deployments, which run in the frontend and backend namespaces respectively.
First, analyze the frontend and backend Deployments to determine the specific requirements for the NetworkPolicy that needs to be applied.
Next, examine the NetworkPolicy YAML samples located in the ~/netpol folder.
Failure to comply may result in a reduced score.
Do not delete or modify the provided samples. Only apply one of them.
Finally, apply the NetworkPolicy that enables communication between the frontend and backend Deployments, without being overly permissive.

Comment: *

Name: *

Email: *

Verification: *

Undo the deployment to the previous version 1.17.1 and verify Image has the previous version

Comment: *

Name: *

Email: *

Verification: *

You have a 'NodePort' service named 'my-service' exposed on port 30000. You need to configure a NetworkPolicy to only allow access to the service from specific nodes in the cluster based on their node labels.

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create a NetworkPolicy:
- Define a NetworkPolicy that allows traffic from nodes with specific labels to the service.

2. Apply the NetworkPolicy: - Apply the YAML file using 'kubectl apply -f networkpolicy.yaml'. 3. Verify the NetworkPolicy: - Check the status of the NetworkPolicy using 'kubectl get networkpolicies allow-specific-nodes -n . 4. Test: - Access the service using the 'NodePort' on a node with the specified label. You should be able to access the service. - Access the service using the 'NodePort' on a node that does not have the specified label. You should not be able to access the service. Note: - Replace with the actual namespace where your service is located. - Replace the CIDR values with the actual CIDRs of your nodes or the node labels that you want to use for filtering.,

Comment: *

Name: *

Email: *

Verification: *

Create a Cronjob with busybox image that prints date and hello from kubernetes cluster message for every minute

• A.CronJob Syntax:
  * --> Minute
  * --> Hours
  * --> Day of The Month
  * --> Month
  * --> Day of the Week
  */1 * * * * --> Execute a command every one minutes.
  vim date-job.yaml
  apiVersion: batch/v1beta1
  kind: CronJob
  metadata:
  name: date-job
  spec:
  schedule: "*/1 * * * *"
  jobTemplate:
  spec:
  template:
  spec:
  containers:
  - name: hello
  image: busybox
  args:
  - /bin/sh
  - -c
  - date; echo Hello from the Kubernetes cluster
  restartPolicy: OnFailure
  kubectl apply -f date-job.yaml
  //Verify
  kubectl get cj date-job -o yaml
• B.CronJob Syntax:
  * --> Minute
  * --> Hours
  * --> Day of The Month
  * --> Month
  * --> Day of the Week
  */1 * * * * --> Execute a command every one minutes.
  vim date-job.yaml
  apiVersion: batch/v1beta1
  kind: CronJob
  metadata:
  name: date-job
  spec:
  schedule: "*/1 * * * *"
  jobTemplate:
  spec:
  template:
  - /bin/sh
  - -c
  - date; echo Hello from the Kubernetes cluster
  restartPolicy: OnFailure
  kubectl apply -f date-job.yaml
  //Verify
  kubectl get cj date-job -o yaml

Comment: *

Name: *

Email: *

Verification: *

Check to see how many worker nodes are ready (not including nodes tainted NoSchedule) and write the number to /opt/KUCC00104/kucc00104.txt.

Correct Answer:

See the solution below.
Explanation
solution

Comment: *

Name: *

Email: *

Verification: *