Exhibit:

Context
You are tasked to create a ConfigMap and consume the ConfigMap in a pod using a volume mount.
Task
Please complete the following:
* Create a ConfigMap named another-config containing the key/value pair: key4/value3
* start a pod named nginx-configmap containing a single container using the
nginx image, and mount the key you just created into the pod under directory /also/a/path

• A.Solution:
  
  
  
  
  
  
• B.Solution:
  
  
  
  
  

Comment: *

Name: *

Email: *

Verification: *

Exhibit:

Context
A user has reported an aopticauon is unteachable due to a failing livenessProbe .
Task
Perform the following tasks:
* Find the broken pod and store its name and namespace to /opt/KDOB00401/broken.txt in the format:

The output file has already been created
* Store the associated error events to a file /opt/KDOB00401/error.txt, The output file has already been created. You will need to use the -o wide output specifier with your command
* Fix the issue.

• A.Solution:
  Create the Pod:
  kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/exec-liveness.yaml
  Within 30 seconds, view the Pod events:
  kubectl describe pod liveness-exec
  The output indicates that no liveness probes have failed yet:
  FirstSeen LastSeen Count From SubobjectPath Type Reason Message
  --------- -------- ----- ---- ------------- -------- ------ -------
  24s 24s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
  23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "gcr.io/google_containers/busybox"
  kubectl describe pod liveness-exec
  At the bottom of the output, there are messages indicating that the liveness probes have failed, and the containers have been killed and recreated.
  FirstSeen LastSeen Count From SubobjectPath Type Reason Message
  --------- -------- ----- ---- ------------- -------- ------ -------
  37s 37s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
  36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "gcr.io/google_containers/busybox"
  36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "gcr.io/google_containers/busybox"
  36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
  36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
  2s 2s 1 {kubelet worker0} spec.containers{liveness} Warning Unhealthy Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory
  Wait another 30 seconds, and verify that the Container has been restarted:
  kubectl get pod liveness-exec
  The output shows that RESTARTS has been incremented:
  NAME READY STATUS RESTARTS AGE
  liveness-exec 1/1 Running 1 m
• B.Solution:
  Create the Pod:
  kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/exec-liveness.yaml
  Within 30 seconds, view the Pod events:
  kubectl describe pod liveness-exec
  The output indicates that no liveness probes have failed yet:
  FirstSeen LastSeen Count From SubobjectPath Type Reason Message
  --------- -------- ----- ---- ------------- -------- ------ -------
  24s 24s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
  23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "gcr.io/google_containers/busybox"
  23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "gcr.io/google_containers/busybox"
  23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
  23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
  After 35 seconds, view the Pod events again:
  kubectl describe pod liveness-exec
  At the bottom of the output, there are messages indicating that the liveness probes have failed, and the containers have been killed and recreated.
  FirstSeen LastSeen Count From SubobjectPath Type Reason Message
  --------- -------- ----- ---- ------------- -------- ------ -------
  37s 37s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
  36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "gcr.io/google_containers/busybox"
  36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "gcr.io/google_containers/busybox"
  36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
  36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
  2s 2s 1 {kubelet worker0} spec.containers{liveness} Warning Unhealthy Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory
  Wait another 30 seconds, and verify that the Container has been restarted:
  kubectl get pod liveness-exec
  The output shows that RESTARTS has been incremented:
  NAME READY STATUS RESTARTS AGE
  liveness-exec 1/1 Running 1 m

Comment: *

Name: *

Email: *

Verification: *

Exhibit:

Context
You have been tasked with scaling an existing deployment for availability, and creating a service to expose the deployment within your infrastructure.
Task
Start with the deployment named kdsn00101-deployment which has already been deployed to the namespace kdsn00101 . Edit it to:
* Add the func=webFrontEnd key/value label to the pod template metadata to identify the pod for the service definition
* Have 4 replicas
Next, create ana deploy in namespace kdsn00l01 a service that accomplishes the following:
* Exposes the service on TCP port 8080
* is mapped to me pods defined by the specification of kdsn00l01-deployment
* Is of type NodePort
* Has a name of cherry

• A.Solution:
  
  
  
  
• B.Solution:
  
  
  

Comment: *

Name: *

Email: *

Verification: *

Exhibit:

Task
You have rolled out a new pod to your infrastructure and now you need to allow it to communicate with the web and storage pods but nothing else. Given the running pod kdsn00201 -newpod edit it to use a network policy that will allow it to send and receive traffic only to and from the web and storage pods.

• A.Pending

Comment: *

Name: *

Email: *

Verification: *

Exhibit:

Context
A container within the poller pod is hard-coded to connect the nginxsvc service on port 90 . As this port changes to 5050 an additional container needs to be added to the poller pod which adapts the container to connect to this new port. This should be realized as an ambassador container within the pod.
Task
* Update the nginxsvc service to serve on port 5050.
* Add an HAproxy container named haproxy bound to port 90 to the poller pod and deploy the enhanced pod. Use the image haproxy and inject the configuration located at /opt/KDMC00101/haproxy.cfg, with a ConfigMap named haproxy-config, mounted into the container so that haproxy.cfg is available at /usr/local/etc/haproxy/haproxy.cfg. Ensure that you update the args of the poller container to connect to localhost instead of nginxsvc so that the connection is correctly proxied to the new service endpoint. You must not modify the port of the endpoint in poller's args . The spec file used to create the initial poller pod is available in /opt/KDMC00101/poller.yaml

• A.Solution:
  apiVersion: apps/v1
  kind: Deployment
  metadata:
  name: my-nginx
  spec:
  selector:
  matchLabels:
  run: my-nginx
  replicas: 2
  template:
  metadata:
  labels:
  run: my-nginx
  spec:
  containers:
  - name: my-nginx
  image: nginx
  ports:
  - containerPort: 90
  This makes it accessible from any node in your cluster. Check the nodes the Pod is running on:
  kubectl apply -f ./run-my-nginx.yaml
  kubectl get pods -l run=my-nginx -o wide
  NAME READY STATUS RESTARTS AGE IP NODE
  my-nginx-3800858182-jr4a2 1/1 Running 0 13s 10.244.3.4 kubernetes-minion-905m
  my-nginx-3800858182-kna2y 1/1 Running 0 13s 10.244.2.5 kubernetes-minion-ljyd
  Check your pods' IPs:
  kubectl get pods -l run=my-nginx -o yaml | grep podIP
  podIP: 10.244.3.4
  podIP: 10.244.2.5
• B.Solution:
  apiVersion: apps/v1
  kind: Deployment
  metadata:
  name: my-nginx
  spec:
  selector:
  matchLabels:
  run: my-nginx
  - name: my-nginx
  image: nginx
  ports:
  - containerPort: 90
  This makes it accessible from any node in your cluster. Check the nodes the Pod is running on:
  kubectl apply -f ./run-my-nginx.yaml
  kubectl get pods -l run=my-nginx -o wide
  NAME READY STATUS RESTARTS AGE IP NODE
  my-nginx-3800858182-jr4a2 1/1 Running 0 13s 10.244.3.4 kubernetes-minion-905m
  my-nginx-3800858182-kna2y 1/1 Running 0 13s 10.244.2.5 kubernetes-minion-ljyd
  Check your pods' IPs:
  kubectl get pods -l run=my-nginx -o yaml | grep podIP
  podIP: 10.244.3.4
  podIP: 10.244.2.5

Comment: *

Name: *

Email: *

Verification: *