Looks like validation issue @Vijin Palazhi @Mumshad Mannambeth Q7 in Mock exam . . .

Kubernetes-Slack Discussions
#1

Gowtham Chinta:
looks like validation issue @Vijin Palazhi @Mumshad Mannambeth

Q7 in Mock exam 1: It fails though I give proper gvisor, It only expects runtimeClassName: gvisor
whereas the gvisor name is already been used for another runtimeclass in this environment.

---------------------my gvisor details---------------------

apiVersion: <http://node.k8s.io/v1|node.k8s.io/v1>
kind: RuntimeClass
metadata:
  name: mygvisor 
handler: gvisor

-------------------my pod.yaml file----------------------------

apiVersion: v1
kind: Pod
metadata:
  labels:
    run: busy-rx100
  name: busy-rx100
  namespace: production
spec:
  runtimeClassName: mygvisor
  containers:
  - image: nginx
    name: busy-rx100


---------------------answer pod.yaml-------------------

apiVersion: v1
kind: Pod
metadata:
    labels:
        run: busy-rx100
    name: busy-rx100
    namespace: production
spec:
    runtimeClassName: gvisor
    containers:
        -
            image: nginx
            name: busy-rx100
#2

Vijin Palazhi:
For this question, I believe the runtime class is already created and in the question, it is specifically asked to secure the pod by recreating it using the runtimeClass called gvisor.

You have to stick to the name specified in the question, same goes for the actual exam.

#3

Vijin Palazhi:
you do not have to create a new runtime class as its already created for you.

#4

Gowtham Chinta:
sure @Vijin Palazhi thankyou for clarifying