MENU
Score: 4%
Task
Set the node named ek8s-node-1 as unavailable and reschedule all the pods running on it.
Suggested Answer: A
Get Premium CKA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
RE
Rene
10 months ago
Wait, does draining really delete local data? That sounds risky!
TA
Tawna
11 months ago
Totally agree, draining can be risky if you're not careful.
CE
Celestina
11 months ago
Just a reminder, don't forget to check for any critical pods before draining!
PE
Pearline
11 months ago
I thought you had to uncordon the node after rescheduling.
DE
Dewitt
11 months ago
This is the standard procedure, nothing surprising here.
GE
German
11 months ago
I definitely recall the `--ignore-daemonsets` flag, but I can't remember if I need to include `--force` every time.
BI
Billye
12 months ago
I feel like I might have mixed up the order of the commands. Should I cordon first or drain first?
SO
Sommer
12 months ago
This question seems similar to one we did in class about managing node availability. I think I need to use `kubectl` for this.
NI
Nikita
1 year ago
I remember practicing the cordon and drain commands, but I'm not entirely sure about the flags needed for the drain command.
YV
Yvette
1 year ago
Hmm, I'm a bit unsure about this one. I know I need to mark the node as unavailable and reschedule the pods, but I want to make sure I don't accidentally cause any disruptions. I'll need to review the documentation carefully before executing the commands.
DI
Diane
1 year ago
I've got this! I'll just follow the steps in the solution and run the commands to cordon the node and drain the pods. Easy peasy!
FR
Francene
1 year ago
Whoa, this is a new one for me. I'm not too familiar with the `kubectl cordon` and `kubectl drain` commands. I'll need to double-check the syntax and make sure I don't accidentally delete any important data or services.
NO
Nobuko
1 year ago
Okay, I think I understand the task. I'll need to use the `kubectl cordon` command to mark the node as unschedulable, and then the `kubectl drain` command to evict the pods running on that node. I'll need to be careful with the `--delete-local-data` and `--ignore-daemonsets` flags.
CA
Carmelina
1 year ago
Hmm, this looks straightforward. I'll start by checking the node status and then use the `kubectl cordon` and `kubectl drain` commands to mark the node as unavailable and reschedule the pods.
PA
Paulene
1 year ago
Ah, the joys of node maintenance. Just remember, don't let the pods get too comfortable on their new digs. Shake things up a bit!
TR
Tracey
1 year ago
Okay, let's mark ek8s-node-1 as unavailable.
LA
Lauran
1 year ago
Yes, the explanation provided gives a step-by-step guide on how to achieve the task.
WI
Wilburn
1 year ago
I believe the solution involves using kubectl commands to cordon and drain the node.
AN
Angella
1 year ago
I agree, setting a node as unavailable can be challenging.
MA
Marge
1 year ago
Hmm, I wonder if the pods will find a new home as swiftly as my cat finds a new napping spot. Gotta love those furry friends!
AL
Alesia
1 year ago
This is a classic move. Cordon, drain, and let the pods find a new home. Easy-peasy, lemon squeezy!
SI
Silva
1 year ago
Easy peasy, just like my morning coffee! Although, I'd probably avoid the --force unless I'm feeling spicy today.
LA
Latosha
1 year ago
I might skip the --force option too, better safe than sorry.
LA
Lauryn
1 year ago
Yeah, just follow the steps provided in the solution and you'll be good to go.
MA
Maryrose
1 year ago
I agree, setting a node as unavailable and rescheduling pods is pretty straightforward.
HE
Herman
1 year ago
I think this question is tricky.
BR
Brandon
1 year ago
Looks straightforward, but I'd double-check the --force flag. Might cause issues with DaemonSets.
MI
Mila
1 year ago
I'll make sure to be careful with the --force flag.
BI
Billy
1 year ago
Good point, thanks for the heads up!