Lab 9.2 curl
I'm following lab 9.2. I have the nginx deployment, and I set up the NodePort service the way the lab told me to. However, the lab says I should be able successfully curl my controlplane endpoint with the NodePort IP and it does not work for me. I'm logged into my control plane node. The pods are running on my worker node. From my CP node, I can successfully curl the following:
- The worker node's private IP and nodeport
- The worker node's public IP and nodeport
However, the following curl commands will time out: - Control plane endpoint (public Azure Load Balancer which is forwarding the nodeport to the backend pool)
- The private IP of the control plane node and the nodeport
- The public IP of the control plane node and the nodeport.
Running the commands from the worker node doesn't make a difference either.
I tried allowing all traffic in my Azure Network Security Group attached to my subnet and that didn't help.
This feels like a problem with my cluster, but I'm not sure what it would be. Any guidance or thoughts?
Best Answer
-
Hello,
Indeed when using a properly configured network one would be able to connect to a NodePort on any node in a cluster and the network plugin and kube-proxy would ensure the traffic is sent to a node with a pod of matching label and connected to a particular port of a pod.
There is a reason we do not support labs that are running on Azure. Also, if you add or remove steps your lab outcomes will probably be different.
Regards,
0
Answers
-
Hi @brianmoore,
Since Azure networking is less seamless in comparison to AWS, GCP, and even local type 2 hypervisors, the Azure cloud infrastructure is not recommended nor supported for this class. However, you may be able to find a few forum discussions where students have documented possible solutions around the challenges faced when running these lab exercises on Azure.
However, to help isolate the root cause, let's try to determine if your cluster is properly configured. Is the CP node tainted? Was the workload ever deployed to the CP node? If you scale the nginx deployment to 10 or 20 replicas, are any of the replicas assigned to the CP node? Are all the control plane pods running in the cluster?
Regards,
-Chris0 -
Thank you for your help! The CP is tainted, and all its infrastructure pods are running. The nginx workload was never deployed to the CP node. 2 pods are running on my worker. I scaled the deployment to 20 and all 20 pods still run on the worker.
I searched the forums like you recommended and it does seem like Calico won't work on Azure. Ugh.
I do plan to convert my Terraform to AWS at some point, but for the CKA exam my voucher and course are going to expire in 30 days, so it's a tight window for me (and I already was granted a complimentary extension, so I guess this is my last chance).
Maybe I could do the conversion to AWS without too much trouble, I just hope it doesn't interfere with me getting ready for the exam in time.
0 -
Hi @brianmoore,
The taint is the reason why your pods only run on the worker node. In case it was missed earlier, Step 3 of Lab 3.3 describes the taint removal process. Once removed, your pods should be distribute evenly between the two nodes (cp and worker).
However, the
curl
issues may still persist on Azure. On EC2 with fully open VPC SG, or on GCE with fully open VPC Firewall rule,curl
should work as expected.As you made progress through the course, did you notice any discrepancies or similar connectivity issues in any of the prior chapters?
Regards,
-Chris0 -
Ah, I see. I do remember that taint removal process. I didn't realize I was supposed to permanently remove my CP's taint, because I figured that the pods should generally just run on the worker and not the CP. And yes, I did get the same confusion in Lab 3.4 when I created a ClusterIP but I wasn't able to curl it from the CP.
Theoretically, though (and disregarding the crappy Azure networking)... if all my pods are deployed to the worker, and I have a nodeport service, then should I be able to curl my control plane node's public IP address and the node port, and then the nodeport service would forward the traffic to the worker node's endpoint? Maybe I'm just misunderstanding how the NodePort service works. I thought that every node listens on that same high-number random port and then forwards the traffic to the nginx pod on the worker. Please correct me if I'm wrong.
0
Categories
- All Categories
- 207 LFX Mentorship
- 207 LFX Mentorship: Linux Kernel
- 735 Linux Foundation IT Professional Programs
- 339 Cloud Engineer IT Professional Program
- 167 Advanced Cloud Engineer IT Professional Program
- 66 DevOps Engineer IT Professional Program
- 132 Cloud Native Developer IT Professional Program
- 122 Express Training Courses
- 122 Express Courses - Discussion Forum
- 5.9K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 66 LFC131 Class Forum
- 39 LFD102 Class Forum
- 221 LFD103 Class Forum
- 17 LFD110 Class Forum
- 33 LFD121 Class Forum
- 17 LFD133 Class Forum
- 6 LFD134 Class Forum
- 17 LFD137 Class Forum
- 70 LFD201 Class Forum
- 3 LFD210 Class Forum
- 2 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 1 LFD233 Class Forum
- 3 LFD237 Class Forum
- 23 LFD254 Class Forum
- 689 LFD259 Class Forum
- 109 LFD272 Class Forum
- 3 LFD272-JP クラス フォーラム
- 10 LFD273 Class Forum
- 109 LFS101 Class Forum
- LFS111 Class Forum
- 2 LFS112 Class Forum
- 1 LFS116 Class Forum
- 3 LFS118 Class Forum
- 3 LFS142 Class Forum
- 3 LFS144 Class Forum
- 3 LFS145 Class Forum
- 1 LFS146 Class Forum
- 2 LFS147 Class Forum
- 8 LFS151 Class Forum
- 1 LFS157 Class Forum
- 13 LFS158 Class Forum
- 5 LFS162 Class Forum
- 1 LFS166 Class Forum
- 3 LFS167 Class Forum
- 1 LFS170 Class Forum
- 1 LFS171 Class Forum
- 2 LFS178 Class Forum
- 2 LFS180 Class Forum
- 1 LFS182 Class Forum
- 4 LFS183 Class Forum
- 30 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 2 LFS201-JP クラス フォーラム
- 17 LFS203 Class Forum
- 116 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 49 LFS241 Class Forum
- 43 LFS242 Class Forum
- 37 LFS243 Class Forum
- 13 LFS244 Class Forum
- 1 LFS245 Class Forum
- 45 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 145 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 6 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 116 LFS260 Class Forum
- 154 LFS261 Class Forum
- 41 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 23 LFS267 Class Forum
- 18 LFS268 Class Forum
- 29 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 7 LFW111 Class Forum
- 257 LFW211 Class Forum
- 178 LFW212 Class Forum
- 12 SKF100 Class Forum
- SKF200 Class Forum
- 791 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 98 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 754 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 147 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 351 Ubuntu
- 465 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 91 Linux Security
- 78 Network Management
- 101 System Management
- 47 Web Management
- 56 Mobile Computing
- 17 Android
- 28 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 366 Off Topic
- 114 Introductions
- 171 Small Talk
- 20 Study Material
- 534 Programming and Development
- 293 Kernel Development
- 223 Software Development
- 1.1K Software
- 212 Applications
- 182 Command Line
- 3 Compiling/Installing
- 405 Games
- 311 Installation
- 79 All In Program
- 79 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)