Lab 2.3: Confusion regarding NodePort service and Cluster IP

Although I'm able to complete Lab 2.3 - "Create a basic Pod", I am a bit confused about how the NodePort service works. After creating a service of type "NodePort":
- How come the "EXTERNAL-IP" Column of the service "basicservice" is "none", instead of the Node IP?
- I could query the nginx app through both the master-node IP AND the worker-node IP. I thought the pod is assigned to one of the nodes, so how come it is accessible through the external IP of either node?
- When people say "External Cluster IP", do they just mean one of the Node's IPs?
Comments
-
Hi @tianli,
Services are covered in detail in Chapter 7, but before reaching that chapter I may be able to provide some clarification:
- The EXTERNAL-IP property of the Service is not the Node IP, it is typically a Load Balancer's IP address, and it is populated for LoadBalancer type Services in Kubernetes clusters running as managed cloud services. We are running a self-managed cluster. If our node is configured to act as a Load Balancer, then its IP address may be assigned to EXTERNAL-IP. An example with additional details can be found here.
- You are correct, the Pod is assigned to one of the Nodes, but reviewing the "Pod-to-Pod Communication" page of the course should answer your question as to why a Pod running on any Node is accessible from either Node of the cluster.
- I am not sure, however, what is the "External Cluster IP" you are asking about. Did you find this in the course lectures or the lab exercises?
Regards,
-Chris1 -
Hi Chris,
I was able to figure out the difference between NodePort and ClusterIp service types. With NodePort I was able to curl from my local machine.
What I don't see it is the benefits we get in step 8 by creating a ClusterIp type service instead of just what we had with the pod:
"8. We will now create a simple service to expose the pod to other nodes and pods in the cluster."
I was already running curl from a different node (the cp node) while the pod was in the worker node. Also the pod-to-pod communication allows "All nodes can communicate with all pods".So I don't see why I would need a ClusterIp type service, instead of just a Pod.
Cheers.
0 -
Hi @runnergeek,
I just had an interesting conversation with another student, and one of the topics was the same as your question:
- Q: Why the need for a ClusterIP service if pods are assigned their own unique private IP addresses and can communicate with each other over the pod-to-pod network?
- A: A pod is ephemeral, meaning that both the pod's name and pod's IP address may change several times during the lifecycle of a containerized application running in the pod. A permanent solution is a service exposing the pods of an application, offering a permanent access interface with a consistent name and a stable ClusterIP address that integrate with the cluster's internal DNS that helps to remove any discovery overhead and communication complexity between pods.
Regards,
-Chris0
Categories
- All Categories
- 50 LFX Mentorship
- 103 LFX Mentorship: Linux Kernel
- 576 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 157 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 11 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 36 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 235 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 902 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 537 Off Topic
- 131 Introductions
- 217 Small Talk
- 21 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 62 All In Program
- 62 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)