Linux Foundation CKS Exam - Topic 6 Question 65 Discussion

Actual exam question for Linux Foundation's CKS exam

Question #: 65
Topic #: 6

[All CKS Questions]

Context: Cluster:gvisor Master node:master1 Worker node:worker1

You can switch the cluster/configuration context using the following command:

[desk@cli] $kubectl config use-context gvisor

Context:This cluster has been prepared to support runtime handler, runsc as well as traditional one.

Task: Create a RuntimeClass namednot-trustedusing the prepared runtime handler namesrunsc. Update all Pods in the namespace server to run onnewruntime.

AExplanation:

Explanation
[desk@cli] $vim runtime.yaml
apiVersion: node.k8s.io/v1
kind: RuntimeClass
metadata:
name: not-trusted
handler: runsc
[desk@cli] $k apply -f runtime.yaml
[desk@cli] $k get pods
NAME READY STATUS RESTARTS AGE
nginx-6798fc88e8-chp6r 1/1 Running 0 11m
nginx-6798fc88e8-fs53n 1/1 Running 0 11m
nginx-6798fc88e8-ndved 1/1 Running 0 11m
[desk@cli] $k get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
nginx 3/3 11 3 5m
[desk@cli] $k edit deploy nginx

Show Suggested Answer

Suggested Answer: A

by Desirae at Sep 19, 2024, 11:57 AM

Limited Time Offer

25%

Off

Get Premium CKS Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Dortha

4 months ago

I’m not sure about switching all pods at once, could cause issues.

upvoted 0 times

...

Beula

4 months ago

All pods are running smoothly now, nice!

upvoted 0 times

...

Arminda

4 months ago

Wait, is not-trusted really a good name? Sounds sketchy!

upvoted 0 times

...

Matthew

4 months ago

Totally agree, runsc is the way to go for better isolation!

upvoted 0 times

...

Yoko

5 months ago

Just created a RuntimeClass named not-trusted with runsc!

upvoted 0 times

...

Noah

5 months ago

The YAML structure for the RuntimeClass seems familiar, but I need to double-check the handler name before applying it.

upvoted 0 times

...

Virgina

5 months ago

I recall a similar question where we had to switch contexts first. I hope I don't forget that part!

upvoted 0 times

...

Alethea

5 months ago

I think the command to apply the RuntimeClass is straightforward, but I might mix up the steps for editing the deployment.

upvoted 0 times

...

Dana

5 months ago

I remember we practiced creating a RuntimeClass, but I'm a bit unsure about the exact command syntax for updating the Pods.

upvoted 0 times

...

Leontine

5 months ago

Wait, do I need to update all the pods in the namespace, or just the deployment? I want to make sure I'm doing this correctly.

upvoted 0 times

...

Stephaine

5 months ago

This looks straightforward enough. I'll just create the RuntimeClass, then use kubectl to update the deployment to use the new runtime. Shouldn't be too tricky.

upvoted 0 times

...

Refugia

5 months ago

Hmm, I'm a bit confused about the context switching part. Do I need to do that before creating the RuntimeClass? And how do I know which namespace the pods are in?

upvoted 0 times

...

Paris

6 months ago

Okay, let's break this down step-by-step. First, I'll create the RuntimeClass using the provided YAML. Then I'll update the deployment to use the new runtime.

upvoted 0 times

...

Arthur

6 months ago

Hmm, this looks tricky. I'll need to carefully compare the GTID information from the master and slave to figure out which statement is true.

upvoted 0 times

...

Bettina

1 year ago

Runsc, huh? Sounds like a new superhero in town, ready to save the day from... I don't know, containerized supervillains?

upvoted 0 times

...

Desmond

1 year ago

Hmm, the 'not-trusted' runtime, eh? I wonder what kind of shenanigans that one gets up to. Hopefully it doesn't try to hack the master node while we're not looking!

upvoted 0 times