CORRECT TEXT

Perform the following tasks:

✑ Add an init container to hungry-bear (which has been defined in spec file /opt/KUCC00108/pod-spec-KUCC00108.yaml)

✑ The init container should create an empty file named/workdir/calm.txt

✑ If /workdir/calm.txt is not detected, the pod should exit

✑ Once the spec file has been updated with the init container definition, the pod should be created

Reveal Solution Hide Solution

CORRECT TEXT

Create a deployment spec file that will:

✑ Launch 7 replicas of the nginx Image with the labelapp_runtime_stage=dev

✑ deployment name: kual00201

Save a copy of this spec file to /opt/KUAL00201/spec_deployment.yaml

(or /opt/KUAL00201/spec_deployment.json).

When you are done, clean up (delete) any new Kubernetes API object that you produced during this task.

Reveal Solution Hide Solution

CORRECT TEXT

From the pod label name=cpu-utilizer, find pods running high CPU workloads and write the name of the pod consuming most CPU to the file /opt/KUTR00102/KUTR00102.txt (which already exists).

Reveal Solution Hide Solution

CORRECT TEXT

Create a Kubernetes secret as follows:

✑ Name: super-secret

✑ password: bob

Create a pod named pod-secrets-via-file, using the redis Image, which mounts a secret named super-secret at /secrets.

Create a second pod named pod-secrets-via-env, using the redis Image, which exports password as CONFIDENTIAL

Reveal Solution Hide Solution

CORRECT TEXT

Score: 7%

Task

Create a new nginx Ingress resource as follows:

• Name: ping

• Namespace: ing-internal

• Exposing service hi on path /hi using service port 5678

Reveal Solution Hide Solution

CORRECT TEXT

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 Ready 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 Ci

Reveal Solution Hide Solution

CORRECT TEXT

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.

Reveal Solution Hide Solution

CORRECT TEXT

Create and configure the service front-end-service so it’s accessiblethrough NodePort and routes to the existing pod named front-end.

Reveal Solution Hide Solution

CORRECT TEXT

Scale the deployment webserver to 6 pods.

Reveal Solution Hide Solution

CORRECT TEXT

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

Reveal Solution Hide Solution