3.2.1 easyregistry.yaml pod created in worker node not cp node
Hi Guys,
I'm up to 3.2.1.
now whenever I run kubectl create [....sample.yaml....]
unlike the documentation in LAB, all pods get created in 'Worker' node hence I fail to curl to the registry or service.
here is the cmd
adminuser@lfclass-aks-cp:~/app1$ kubectl create -f easyregistry.yaml
service/nginx created
service/registry created
deployment.apps/nginx created
persistentvolumeclaim/nginx-claim0 created
deployment.apps/registry created
persistentvolumeclaim/registry-claim0 created
persistentvolume/vol1 created
persistentvolume/vol2 created
adminuser@lfclass-aks-cp:~/app1$ kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx-688c5c8689-8lr72 1/1 Running 0 17s 192.168.125.75 lfclass-aks-worker
registry-7f9b448c88-frzmn 1/1 Running 0 17s 192.168.125.76 lfclass-aks-worker
see the NODE, it's using lfclass-aks-worker node. but I want to get them created in cp node.
what needs to be done in the easyregistry.yaml file so it targets to the cp not worker
and is there any global setting that i can do to avoid this situation moving forward. I still got heaps LABs to go
by the way I have done taint thing as well from 2.2.15
adminuser@lfclass-aks-cp:~/app1$ kubectl describe nodes | grep -i taint
Taints:
Taints:
Answers
-
Hi @docklander,
The nginx and registry pods can be scheduled on any desired node by adding the
nodeName
property to each Deployment definition - see a sample in the documentation.EDIT: The failed curl indicates that the networking between your cluster nodes may be misconfigured. In a healthy cluster, one should be able to curl a Service IP address from either one of the nodes (control plane or worker), regardless where the Pod gets scheduled. After completing the Repo configuration from Lab exercise 3.2, the container runtimes from both nodes are expected to be able to communicate with the registry, regardless of the node where it is running.
Regards,
-Chris0 -
[SOLUTION] anyone who is using Azure Linux VM, having some challenges for networking.
This is what I did and it fixed my issue.when you install k8scp.sh install canl.yaml instead of calico.yaml as below
Line 98 # kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml -> comment this
Line 99 kubectl apply -f https://projectcalico.docs.tigera.io/manifests/canal.yaml -> use thisthis makes CP node communicate with WORKER node without an issue. This has been working in 2022 July
0
Categories
- All Categories
- 112 LFX Mentorship
- 112 LFX Mentorship: Linux Kernel
- 604 Linux Foundation IT Professional Programs
- 315 Cloud Engineer IT Professional Program
- 139 Advanced Cloud Engineer IT Professional Program
- 52 DevOps Engineer IT Professional Program
- 67 Cloud Native Developer IT Professional Program
- 3 Express Training Courses
- 3 Express Courses - Discussion Forum
- 5.3K Training Courses
- 17 LFC110 Class Forum - Discontinued
- 8 LFC131 Class Forum
- 30 LFD102 Class Forum
- 178 LFD103 Class Forum
- LFD110 Class Forum
- 24 LFD121 Class Forum
- LFD133 Class Forum
- 2 LFD137 Class Forum
- 62 LFD201 Class Forum
- 2 LFD210 Class Forum
- 1 LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 127 LFD232 Class Forum - Discontinued
- LFD233 Class Forum
- LFD237 Class Forum
- 22 LFD254 Class Forum
- 643 LFD259 Class Forum
- 107 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 4 LFD273 Class Forum
- 1 LFS101 Class Forum
- LFS112 Class Forum
- LFS116 Class Forum
- LFS118 Class Forum
- LFS144 Class Forum
- 2 LFS145 Class Forum
- LFS151 Class Forum
- LFS157 Class Forum
- LFS158 Class Forum
- LFS162 Class Forum
- LFS167 Class Forum
- 28 LFS200 Class Forum
- 735 LFS201 Class Forum - Discontinued
- 1 LFS201-JP クラス フォーラム
- 13 LFS203 Class Forum
- 98 LFS207 Class Forum
- 299 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 36 LFS243 Class Forum
- 12 LFS244 Class Forum
- LFS245 Class Forum
- 41 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 141 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 2 LFS256 Class Forum
- LFS257 Class Forum
- 1.1K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 109 LFS260 Class Forum
- 144 LFS261 Class Forum
- 39 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 20 LFS267 Class Forum
- 18 LFS268 Class Forum
- 26 LFS269 Class Forum
- 198 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 254 LFW211 Class Forum
- 173 LFW212 Class Forum
- 9 SKF100 Class Forum
- SKF200 Class Forum
- 781 Hardware
- 198 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 174 Networking
- 87 Printers & Scanners
- 83 Storage
- 742 Linux Distributions
- 80 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 23 openSUSE
- 143 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 347 Ubuntu
- 450 Linux System Administration
- 31 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 101 System Management
- 46 Web Management
- 51 Mobile Computing
- 18 Android
- 23 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 355 Off Topic
- 109 Introductions
- 167 Small Talk
- 18 Study Material
- 504 Programming and Development
- 283 Kernel Development
- 203 Software Development
- 844 Software
- 210 Applications
- 180 Command Line
- 3 Compiling/Installing
- 107 Games
- 308 Installation
- 51 All In Program
- 51 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)