MENU
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.
Suggested Answer: A
Get Premium CKS Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
DO
Dortha
11 months ago
I’m not sure about switching all pods at once, could cause issues.
BE
Beula
11 months ago
All pods are running smoothly now, nice!
AR
Arminda
12 months ago
Wait, is not-trusted really a good name? Sounds sketchy!
MA
Matthew
12 months ago
Totally agree, runsc is the way to go for better isolation!
YO
Yoko
1 year ago
Just created a RuntimeClass named not-trusted with runsc!
NO
Noah
1 year ago
The YAML structure for the RuntimeClass seems familiar, but I need to double-check the handler name before applying it.
VI
Virgina
1 year ago
I recall a similar question where we had to switch contexts first. I hope I don't forget that part!
AL
Alethea
1 year ago
I think the command to apply the RuntimeClass is straightforward, but I might mix up the steps for editing the deployment.
DA
Dana
1 year ago
I remember we practiced creating a RuntimeClass, but I'm a bit unsure about the exact command syntax for updating the Pods.
LE
Leontine
1 year 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.
ST
Stephaine
1 year 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.
RE
Refugia
1 year 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?
PA
Paris
1 year 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.
AR
Arthur
1 year 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.
BE
Bettina
2 years ago
Runsc, huh? Sounds like a new superhero in town, ready to save the day from... I don't know, containerized supervillains?
DE
Desmond
2 years 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!
BE
Becky
2 years ago
Georgene: Agreed, better safe than sorry.
EL
Ellsworth
2 years ago
User 3: We should keep an eye on it just in case.
GE
Georgene
2 years ago
User 2: I hope it doesn't cause any trouble for the cluster.
LO
Lonna
2 years ago
User 1: I know, right? 'Not-trusted' sounds sketchy.
BE
Bernardo
2 years ago
Wait, we have to create a RuntimeClass now? I thought the good old 'docker run' was simpler, but I guess we're in the future now.
KA
Katie
2 years ago
Ah, the joys of runtime configuration! Gotta love those extra layers of complexity in our Kubernetes clusters.
OR
Oren
2 years ago
And once you have it all set up, it's so satisfying to see everything running smoothly in the cluster.
VE
Veta
2 years ago
Absolutely! It's like solving a puzzle, making sure everything fits together perfectly.
CR
Crista
2 years ago
I know, it can be a bit overwhelming at times, but it's all about getting those configurations just right.
CL
Clarinda
2 years ago
I believe following the provided explanation and commands should help us complete the task successfully.
MA
Margarita
2 years ago
Yes, I agree. We can update all Pods in the namespace server to run on the new runtime after creating the RuntimeClass.
CL
Clarinda
2 years ago
I think the task is clear, we need to create a RuntimeClass named not-trusted using runsc handler.