Lab 12.1 purpose unclear
I'm working my way through lab exercise 12.1 and finding myself extremely confused about its purpose. For whatever reason, it's using a single pod containing 4 containers to demonstrate the effects of nodeSelector. There's also a line saying "Determine where the new containers have been deployed. They should be more evenly spread this time."
To the best of my understanding, given everything this and previous chapters have said, the containers will all be on the same node. But this lab exercise is doing a very good job of making me question that. It cannot demonstrate spread between nodes because there's only a single pod, but the multiple containers and wording implies the containers could be running on different nodes. Is there something I'm missing, or is this just confusing?
I understand that, likely because a bunch of system stuff is running on the cp node, the vip pod will likely run on the worker node once the selector is removed, but this isn't what the lab says is happening, and it's not really demonstrated by the exercise.
Comments
-
My understanding is: this lab is demonstrating the usage of "nodeSelector" to define which node(s) pods can be running on.
Actually, I found that, even if I remove "nodeSelector", all 4 containers always run from master-1 node. Only when I define "other" in nodeSelector as following, those 4 containers will run under work-1 node,
nodeSelector:
status: other
The lab says 4 containers can spread out running on both nodes with the deletion of "nodeSelector", but it is not I have found when I was doing the lab.0 -
Hi @caishaoping,
Without a
nodeSelector
property found in the Pod spec, the Scheduler assigns Pods to nodes while attempting to even out the resource (CPU and memory) utilization across the nodes of the cluster - keep in mind that the scheduling algorithm takes into account the resources consumed by the existing workload of the cluster at scheduling time.If one node is underutilized in comparison to other nodes of the cluster, that node will be targeted with several new workload Pods until its resources utilization reach a matching level of utilization to other nodes.
Regards,
-Chris1 -
Hi @chrispokorni,
Thanks for your explanation.
Regards
Shao0 -
I came to ask about this as well. This lab claims that containers will spread out when the node selector is removed, but pod containers will always be co-located with the pod will they not? I think the lab needs to be updated, should we not be spawning multiple pods to illustrated how the load is spread? Or at least not saying the containers will spread out?
From the PDF "9. Create the pod again. Containers should now be spawning on either node."
0 -
Hello,
You are correct. I will update the lab to create multiple pods instead, and fix the wording. IIRC the YAML changed to fix another issues five or six versions ago and it no longer makes sense.
Thank you for sending this in.
Regards,
0 -
Was wondering if anyone else ran across this. The lab has not been resolved as of 11/1/2022.
0 -
Lab 12.2: Using Taints to Control Pod Deployment also needs to be reviewed and corrected
Thanks,
Gilbert
0 -
To add up on my previous post
In my opinion, instead of counting the number of containers on each node (sudo crictl ps | wc -l
), better solution is to dokubectl get pods -o wide -n project-tiger
and look atNODE
column0
Categories
- 9.9K All Categories
- 29 LFX Mentorship
- 82 LFX Mentorship: Linux Kernel
- 469 Linux Foundation Boot Camps
- 267 Cloud Engineer Boot Camp
- 95 Advanced Cloud Engineer Boot Camp
- 43 DevOps Engineer Boot Camp
- 31 Cloud Native Developer Boot Camp
- 1 Express Training Courses
- 1 Express Courses - Discussion Forum
- 1.6K Training Courses
- 18 LFC110 Class Forum
- 4 LFC131 Class Forum
- 19 LFD102 Class Forum
- 133 LFD103 Class Forum
- 9 LFD121 Class Forum
- 60 LFD201 Class Forum
- LFD210 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 545 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 20 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 37 LFS207 Class Forum
- 296 LFS211 Class Forum
- 53 LFS216 Class Forum
- 45 LFS241 Class Forum
- 40 LFS242 Class Forum
- 33 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 967 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 85 LFS260 Class Forum
- 124 LFS261 Class Forum
- 29 LFS262 Class Forum
- 78 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 16 LFS268 Class Forum
- 14 LFS269 Class Forum
- 194 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 207 LFW211 Class Forum
- 148 LFW212 Class Forum
- 892 Hardware
- 213 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 206 Networking
- 100 Printers & Scanners
- 85 Storage
- 747 Linux Distributions
- 88 Debian
- 64 Fedora
- 13 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 354 Ubuntu
- 469 Linux System Administration
- 38 Cloud Computing
- 68 Command Line/Scripting
- Github systems admin projects
- 93 Linux Security
- 77 Network Management
- 107 System Management
- 48 Web Management
- 62 Mobile Computing
- 22 Android
- 26 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 524 Off Topic
- 127 Introductions
- 210 Small Talk
- 19 Study Material
- 783 Programming and Development
- 257 Kernel Development
- 492 Software Development
- 919 Software
- 255 Applications
- 181 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 46 All In Program
- 46 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)