Lab 11.1 has errors

In step 6, the PDF shows a "vip.yaml" that creates a SINGLE POD named "vip" that contains 4 busybox containers and a nodeselector that only allows the pod to run on the node which was previously labeled with "status=vip".
So far so good, the pod only runs on the "vip" node.
Step 8 has us delete the pod and change the pod spec to remove the nodeSelector.
Step 9 is where the correction is needed... it says that after recreatingc the pod "Containers should now be spawning on both nodes.".
IMPOSSIBLE! The smallest unit Kubernetes can schedule is a POD!
This lab needs to be changed so that more than one pod is being created so we can actually see something spawning on both nodes.
Comments
-
Hi,
Aside from understanding the scheduling of pods, and the impact of node selectors, understanding the concept of pod vs container is equally important.
In short, a pod encapsulates one or many containers.
The following links may help in clarifying the concepts:
https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/
https://kubernetes.io/docs/concepts/workloads/pods/pod/
To your point, in Kubernetes we manage and verify the pods with kubectl get pods, and in Docker we verify the containers with docker ps.
Also, when a pod is scheduled on a node in Kubernetes, the end result is one or more running containers on that same node.As you mentioned, in step 6 the vip.yaml file defines a Pod with 4 containers. In step 7, when the vip Pod is scheduled on the master because of the node selector, it creates the 4 containers on the master, which are then verified to be running on the master by issuing the docker ps command.
In step 8 by deleting the vip Pod, the 4 containers are also terminated and deleted. This can be verified again by running the docker ps command.
When editing the vip.yaml file and commenting out the node selector, the scheduler is no longer ignoring the worker, therefore the vip Pod and its 4 containers could be scheduled on either one of the available nodes in the cluster: master or worker.
In step 10 we are determining on which of the 2 nodes (master or worker) the 4 containers have been deployed, again with the use of docker ps command.I hope this helps.
Regards,
-Chris0 -
Chris, sorry i must not have made my point clear.
I know what is supposed to happen and fully understand the difference between pods and containers.
I have issue with the specific sentence in step 9 which contradicts your interpretation of the lab above.
Below is a quote from the lab, I have **bolded **the incorrect statement.- Delete the pod then edit the file, commenting out the nodeSelector lines. It may take a while for the containers to fully
terminate.
[email protected]:~$ kubectl delete pod vip
pod "vip" deleted
[email protected]:~$ vim vip.yaml
....
nodeSelector:
status: vip
- Create the pod again. Containers should now be spawning on both nodes. You may see pods for the daemonsets as
well.
[email protected]:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
vip 0/4 Terminating 0 5m
[email protected]:~$ kubectl get pods
No resources found.
[email protected]:~$ kubectl create -f vip.yaml
pod/vip created
1 - Delete the pod then edit the file, commenting out the nodeSelector lines. It may take a while for the containers to fully
-
We can make a suggestion to the course author and maintainer to revise that sentence prior to the next course update release.
Regards,
-Chris0
Categories
- 10.1K All Categories
- 35 LFX Mentorship
- 88 LFX Mentorship: Linux Kernel
- 504 Linux Foundation Boot Camps
- 279 Cloud Engineer Boot Camp
- 103 Advanced Cloud Engineer Boot Camp
- 48 DevOps Engineer Boot Camp
- 41 Cloud Native Developer Boot Camp
- 2 Express Training Courses
- 2 Express Courses - Discussion Forum
- 1.8K Training Courses
- 17 LFC110 Class Forum
- 5 LFC131 Class Forum
- 19 LFD102 Class Forum
- 148 LFD103 Class Forum
- 13 LFD121 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 569 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 23 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 45 LFS207 Class Forum
- 298 LFS211 Class Forum
- 53 LFS216 Class Forum
- 46 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 997 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 87 LFS260 Class Forum
- 126 LFS261 Class Forum
- 31 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 21 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 212 LFW211 Class Forum
- 154 LFW212 Class Forum
- 899 Hardware
- 217 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 749 Linux Distributions
- 88 Debian
- 64 Fedora
- 14 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 355 Ubuntu
- 473 Linux System Administration
- 38 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 63 Mobile Computing
- 22 Android
- 27 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 528 Off Topic
- 127 Introductions
- 213 Small Talk
- 20 Study Material
- 794 Programming and Development
- 262 Kernel Development
- 498 Software Development
- 923 Software
- 258 Applications
- 182 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 53 All In Program
- 53 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)