Services | ClusterIP vs NodePort vs LoadBalancer Service | Load Balancing Hands-on
ฝัง
- เผยแพร่เมื่อ 16 พ.ค. 2024
- n this video we will be discussing everything you need to know about services.
We'll be understanding the different Service types and their use cases:
1. ClusterIP Service
2. Multi-Port Service
3. NodePort Service
4. LoadBalancer Service
So by the end of the video, you’ll have a great understanding of Kubernetes Services and will be able to use them in practice
Please give a Like and Subscribe - bit.ly/pavanelthepu
Timestamps:
00:00 - Intro
00:55 - Why do we need services?
02:34 - What is a service?
03:16 - Advantages of services
04:02 - Services in action
06:13 - ClusterIP Service
11:55 - Load Balancing Hands-on
15:15 - Multi-Port Services
16:18 - NodePort Services
19:10 - LoadBalancer Services
My other courses:
Docker Complete Course: • Docker Tutorial | Ful...
Thank you very much!
#kubernetes #services #loadbalancing #fullstackdevelopment
You rarely see people proving the points with practical cases. Thank you pal found this very helpul.
Thank you so much. Please subscribe and share with your friends and colleagues
hats off to you bro, you made the trickiest part of k8 so simple, i got the complete idea about service types, Thanks a lot 😍😍
A rare gem for sure
I have watched many videos on kubernetes but Your videos most usefull to learn. thankyou for these videos.
Got so many new things as a beginner. Thank you so much for beginner friendly tutorial sir ♥
Described this confusing topic in a easy way. Thank you Pavan👍
I really like how you diagrams together the node/pod/container and associated it with what values in the various yaml files they are related to...
asking/hoping, have you done a video showing the implementation for ingress on AWS / EKS. a recent version. bringing all of this together.
Thanks for video❤
Thanks
very helpful!!
Easy to follow. Very nice explanation. Thanks Pavan. Keep it up 👍
Thanks man, been following your K8s playlist and loving it. Everything is explained in crisp manner.
Thank you Shrikhar. Please subscribe and share with your friends and colleagues
Thx
Thankyou Pavan Elthepu. Now I've understand the services in k8s.
Stay tuned for more such videos Auno Gohe
thanks for the great content. I have a question: What enables a pod to be port-forwarded? can all the pods be port forwarded? some jumpbox running as pods does not support port-forwarding.
Thanks Pavan, your explanation is both detailed and crisp. I learned more from this than paid Udemy courses. Good work!!
Means a lot! Thank you so much. Please subscribe and share with your friends and colleagues
Thank you Pavan for this easy-to-understand video on K8s services. Your explanation has been spot on and made the concept clear.
Thank you Sandeep. Please subscribe and share with your friends and colleagues
I watched may tutorial on K* , yours are really one of best and really hands on . Thakn you !
Thank you so much Saleem. Means a lot. Please subscribe and share with your friends and colleagues. Happy Learning!
Pavan, Simply superb. the entire K8S story in 20 minutes you explained. Your video is FAR FAR BEST than Nana video. God bless you . thank you. I wish you to make more such videos . thank you again
Wow, really overwhelmed with your love. Thank you so much Raghu Vardhan. Please subscribe and share with your friends and colleagues.
Easy and in detail explanation ❤❤
Thanks a lot😊. Please subscribe and share with your friends and colleagues
This cleared up so many questions I had after watching a bunch of other videos. Great job!
Question: can I have both a LB service and a nodeport service to the same app? I want a VIP to my whole Openfire cluster, but also be able to log into the individual nodes' web console
Awesome work, you save my time.
Thank you, please subscribe and share with your friends and colleagues
With ClusterIP-type service, you showed load balancer runs properly by running your script since kube-proxy does as a load balancer. With Load Balancer-type service, the kube-proxy load balancer runs or not? The kube-proxy load balancer runs ONLY when ClusterIP or NodePort-type service is configured?
sir you really did a very good job after listening your classes i have cracked interview thank you very much..i owe you.
Wow, that’s great to hear. Many congratulations💐💐
Thank you
Thank you so much. Please subscribe and share with your friends and colleagues
This explanation was too good pavan♥️♥️
Thank you 🙏. Please subscribe and share with your friends and colleagues
Nice Pavan ..Simple and elegent.
Thank you so much. Please subscribe and share with your friends and colleagues🙏
Hi Pavan, quick question on node port service, let say we have two worker nodes, with ips: 1.1.1.1, 1.1.1.2 respectively, pod1 is on node1. If we have to use node port service ( say 3000) we must also know which node is running the pod . In our case it is worker node1, if node1 goes down, Pod1 will be run on worker node2 but external users does not know that. they continue to use 1.1.1.1:3000. Right?
Much appreciated!!
bro how to create local host in linux could you plz explain
Your way of explanation and especially the pictorial representation is like awesome
Anyone who watch this session will have no further doubts
Good work , keep it up
Thanks for this
Thank you so much Naveen. Please subscribe and share with your friends and colleagues
Sure i will
I can curl from pod1 to pod2 using clusterIP successful but curl using service name gives response " could not resolve host ... "
What could be the reason please suggest
How service port and pod port is same?
Excellent Sir
Thank you. Please subscribe and share with your friends and colleagues
@@PavanElthepu subscribed..!!
Y could not we access application on master node when we do curl cluster IP
Curl cluster IP:port
Above command I run on master node
But didnot access
Hi Bro, your videos are very informative and heart touching and please make videos regarding real time tasks in kuberntes that how we will resolve it, if you will make this type of videos then we feel proud and lots of help so please bro....🙏🙏
Sure Jalandhar
Thanks Pavan for the videos, clear explanations. can you please the GIT repo so that it will be easier to practice.
Hi Praveen, you can find all the resources here: github.com/pelthepu/Kubernetes/tree/master/resources
@@PavanElthepu Am able to ping the pods without getting into the pods, with curl : i can get the pods response
Nice explanation with easy way to understand hard topics ..Thankyou ..please Add Head less service also??..
Thank you so much Rakesh. I'll cover it in some other video when we get a use case.
Hi Rakesh, I uploaded Statefulset video and that will cover headless
th-cam.com/video/eUa-IDPGL-Q/w-d-xo.html
could you please explain how nodePort works in multiple node scenario.
Sure Mohanty. I’ll try to make a video on it
can you plan for series for isio
Sure👍
sir can you please explain multi-port service?
I'll try to see if I can make a short video on it
@19:52 though we change the type: Loadbalance we still kept nodePort: 30000 👈 No problem If we place it over there?
No problem
@@PavanElthepu thanks Pavan Sir
Hi, Pawan when I am trying to access Nodeport service from browser it doesn't work any suggestions. I followed exactly what you did in the video.
yes same is happening with me as well
Good video but you need a new microphone. Hard to understand you.
how can i get local cluster ip using kind , i am not using minikube (minikube ip -p local-cluster)
in Kind, you can use the kubectl get nodes -o wide command to get the IP address of the control-plane node, which is the IP address of the Kubernetes cluster
*istio
Hi Pavan, I have created my own k8s cluster with one master and one worker nodes using kubeadm. I deployed my spring boot application and exposed a NodePort service for my spring boot deployment. My master node IP is 192.168.254.xx and my worker node IP is 192.168.254.yy, my node port service port is 30000, now could you please guide me on how to access my spring boot on the internet?
Hi Srinivasan,
If your node is reachable from outside of the Kubernetes cluster, you can access it with 192.168.254.yy:30000