I have never commented on any RU-vid video before but this deserves it. The reason you stand out is because your explanation is absolutely clear and easy to understand, you don't use "Jargon" like others do. Kudos for that. Lastly, keep them coming and thank you for this piece! Cheers!
Awesome. I wonder who has guts to dislike tgis video. Have you produced something better for the community? I guess not. So appreciate what is freely given and well explained
Wow, what a wonderful way to explain about services, Mumshad!! A really appreciate the work that you are doing. I also have couple of your course in Udemy for Ansible, they are wonderful as well, Thanks a lot and keep it up!!
wow I went through lot of Kubernetes lectures including acloudguru and Linux academy no one explain in depth like you. great work.. I subscribed your kodecloud anyway.. put more courses there..
Excellent diagrams and really clearly explained! The main missing piece for an overview is to cover how traffic is distributed for a LoadBalancer type Service. This is an area I really struggled with when trying to wrap my head around k8s networking and the lack of clarity in documentation and instructional videos was a source of frustration for me. (I'm sorry to say your video would also have frustrated me if I didn't already know how it worked, because a) it's so wonderfully produced and b) you tease us at 4:41 by saying you're going to talk about each of the Service types in detail, and then proceed to talk about *only* NodePort. :)) Edit: ah, I just realized this is a snippet from a larger course. Perhaps that does fill in the gaps I mentioned?
Excellent insight , I have ever seen. .Block diagrams are really helpful to get the exact clarity. Please upload much more such video for us. Thank you very much.
Thank you so much sir! watched tons of videos and other references but couldn't understand this part of kubernetes, now after watching this video it crystal clear, and actually I tried it out in my lab and it works like a charm! as always many thanks for sharing this and making it simple to understand...!
Sir, suppose we have different application with the same port running inside the cluster, then how will the end user access any particular application ? Will there be different services to access different applications ? If so kindly explain.
Thanks for the wonderful explanation. I have a question, how do you get the Node IP? I am running kubernetes cluster on my laptop using minikube. When i try to look for the node ip, all i see is the internal IP. The external IP for a node (in my case only the master node) is none. When we are using service with "NodePort", we would hit the application http: : node_port /. But i don't know the node_ip, hence i am unable to hit my application.
Great video. I have one question, though. If you are doing this on the cloud, how do you know any of the node IP addresses? Won't they be different, depending on what server they are instantiated on? If you are constantly scaling and taking down services that are no longer functioning, the IP address would be very dynamic. Do you look it up on a service directory?
Great job...Really helpful. Could you please help me which software you used to create this videos? I'm in search of good software to create a tutorial content.
How does the load balancer in services distribute the traffic? considering you are not hitting one specific IP address for load balancer but multiple speicific IP for each pod. i just did not udnerstand that part
"TargetPort: The target port is the port number on the Pods that the Service will forward traffic to. It represents the port on the backend Pods where the application is listening. When a Service receives traffic on its own port, it forwards the traffic to the target port of the Pods. Port: The port is the port number that the Service listens on. It represents the port on the Service itself where it will receive incoming traffic. External clients or other Services within the cluster can communicate with the Service using this port. Inside the cluster, pods can communicate with each other with services, for this case we can connect to this service with the domain: myapp-service or myapp-service:80 So if you change the config port to 90, the domain may be: myapp-service:90"
so neat and clear..but I was lost the flow of request..where is the listener for nodeport .in which service the listening happens? and why do we need a port in the service ? if request comes to nodeport then will it not get forwarded to target port directly why do we need another port inbwtween? another question is service a service deamon that has listens on its “port”?
What if I don't define a service.yaml ? And I want that app to be accessible only within the Pod , not even pod to pod. Internal to Pod. Not Internal to Cluster.
"In Kubernetes, each Pod has an IP address. A Pod can communicate with another Pod by directly addressing its IP address, but the recommended way is to use Services. A Service is a set of Pods, which can be reached by a single, fixed DNS name or IP address. In reality, most applications on Kubernetes use Services as a way to communicate with each other. Using a Service is much more flexible than addressing another Pod directly, because Pods can be restarted frequently, which means that addressing them by name or IP is a very brittle approach."
Outstanding video, and I mean that! But am I the first person to note that the same sentence gets repeated twice at the 7 minute mark? I started to think I wasn't listening well enough for a moment there, because "it was all starting to sound the same"....
