Gone through various Kubernetes paid courses too. But this series is best so far. It is helping me to understand each and every smaller components and configuration of K8S in a very practical manner. Thanks for your effort and time you have devoted to making this course. :)
@davidajirotutu7560
3 жыл бұрын
Your Kubernetes videos is one of the best i have seen on KZitem. thanks for the great job
@benjamn8557
4 жыл бұрын
Love how you put the picture next to the command line as you explained the ports
@basunilkanthe2589
4 жыл бұрын
I am really getting confident after watching your videos on kubernetes Srikanth , you have explained basis understanding on kubernetes in better way.. Thank you for your effort for preparing such free video.
@zmxn007
Жыл бұрын
Amazing explanation of the topic sir. Moreover your visuals help to understand the concept better. Thank you.
@Revathi5
4 жыл бұрын
you are amazing... I have searched many tutorial videos to understand kubernetes ...finally i got you videos ..it's really great way of teaching...Thanks for sharing your knowledge...
@chytrak4060
4 жыл бұрын
your course explains K8s in a crystal clear way. Thank you very much
@jayadevpentapati1091
4 жыл бұрын
Your series on kubernetes is too good. Made my understanding more better and closed those small gaps as well. Keep up your spirit. :)
@sajib217
2 жыл бұрын
Excellent demonstration...Thank you very much
2 жыл бұрын
Very professional presentation, thank you very much
@nayabsyed4062
5 жыл бұрын
I watched your videos on kubernetes pod networking, kubeadm & architecture. Before starting this videos to watch. I would like appreciate your excellent explanation for this video too in advance.
@konstantinasfalkovskis5814
4 жыл бұрын
Man, You are just AWESOME!!!! About two weeks spend on it with externalIPs and smt., but with no luck. Yours SUPER.B. simple to understanding video helps me for sure... Suffering gone :)
@mukulbadonia
5 жыл бұрын
Amazing effort Srinath! Thanks so much, this clarify.. Exactly what I was looking for.
@stefanw8203
3 жыл бұрын
Thank you very much for the good explanation. This covers questions that are not handled by others! Great
@srikrishnansubramanian2735
Жыл бұрын
Hi , can you also upload a detailed step to step video along with demo on taints & tolerations
@vijaykumar-qp6qj
5 жыл бұрын
Super,really very clear explanation tq sooo much
@lakshmimaha5716
5 жыл бұрын
Awesome as always..simple and very clear..could you please provide a video on ingress as well
@anthonydelagarde3990
3 жыл бұрын
Thank you I got value from this presentation!
@ramakris
4 жыл бұрын
Good Job Srinath. What happens if a new node joins the cluster? Would the respective service object take the new node into consideration?
@ramrachuri3328
3 жыл бұрын
Hi I am aws as cloud and i just wanted to check the node port external ip to access the application from browser. How can i get the ip and how can i see the list of instances in aws as you shown for gcloud
@rajabmur4311
3 жыл бұрын
thank you so much, incredible explanation , that was really helpful
@akashhudge5735
4 жыл бұрын
I think with nodport service you can use any worker node to access the respective target service, even though your pod is not running in that node. Service will automatically redirect user to respective target pod. Please clarify this
@ramprasath3496
2 жыл бұрын
sir from outside, how you are able to access pod IP and service IP? They are internal to the cluster right and private IPs right? According to me, you can access nginx via service IP/pod IP only if you have logged in to the node If you have to access from outside via internet, then only nodeIP:nodePort is the right> Correct me if i am wrong sir.
@tejas115
2 жыл бұрын
can you access the service with nodeport and internal node ip instead of external ip?
@stevenvalvoda848
2 жыл бұрын
Great video
@shubhamgupta-lk9ld
2 жыл бұрын
Best
@chintangandhi4500
4 жыл бұрын
At 21:57 nodeIp = X.X.X.X.31000, you are missing one 0
@harishkolanu
5 жыл бұрын
sir, i am not able to access with node-ip:31000, service-ip:80, pod-ip:80 please can tell what's the problem. i can access with external-ip in type LoadBalancer..... but type in nodePort i am not able access.
@basunilkanthe2589
4 жыл бұрын
what URL you have been accessing
@venkataramanaiahgonagodugu4408
2 жыл бұрын
Sir may I know difference between loadbalance service and nodeport service?
@nishu199123
5 жыл бұрын
Hi, Can you please explain how requests are forwarded to different nodes in case of multi instance multi nodes scenario. Some detail about how Kube-Proxy works here.
@shivajinaga7893
5 жыл бұрын
Hey Nishu, interesting question!! The answer to your question would be Load Balancing Service. *** We go for services, to expose the application to internet or customers *** If the pod instances are running on the same Node, we go for NodePort service, where the application can be access with NodeIP and Node Port. *** If the pod instances are running on different Nodes in the Cluster, we can access the application by creating the Load Balancing Service, which generates an external IP. For detailed information about this Load Balancing Service, watch the next video.. Cheers, Shivaji
@ernestpugazh9716
4 жыл бұрын
@@shivajinaga7893 Load Balancing would be help full for frontend POD / Services ! but what if the backend service /POD are in different worker node ? . Example : Frontend "http" in worker node 1 and Backend "DB" in worker node 2 , how these two instance will be connected ?
@UnknownSend3r
2 жыл бұрын
@@ernestpugazh9716 I think they are connected by the ClusterIP
@itzsrikanth
4 жыл бұрын
Sir, can you suggest an alternative procedure for prod environment since it was mentioned that it is not suitable for it?
@basunilkanthe2589
4 жыл бұрын
you should try with load balancing approach in the production considering restriction of NodePort.. Considering Node Port stick with specific service
@jerrycheung8158
4 жыл бұрын
Great video. Thanks a lot. But I am a bit confused by how Node Port work across multiple node. In the video, there are 3 nodes with different Node IP and port and each node has 1 pod MyApp. If all requests go to only 1 Node IP, will the service load balancing the requests to different Pod?
@rahulmam5653
4 жыл бұрын
Thats why we don't use NodePort for Production. We can use type=Loadbalancer for that.
@bhanusachdeva2136
4 жыл бұрын
Superb effort.!!!. I have a 2-questions, say there are 2 pods pod1 on w1(10.10.10.1) and pod2 on w2(20.20.20.1) and node-port=31000. question1, Is there a single service which runs on either of nodes (w1 or w2)? question2, If I access application using w1 ip as (10.10.10.1:31000) then will the request every land on pod2 on w2. If how request will go to pod2-w2 if I always use w1 IP?
@bready8415
4 жыл бұрын
To my understand, yes either through W1 or W2, if the request hit the service, then service can invoke, any pod on both worker nodes. Correct me, if my understanding is wrong.
@shivaburade4059
4 жыл бұрын
I don't think nodeport load balances the requests. To load balance use type=loadbalancer or use ingress.
@basunilkanthe2589
4 жыл бұрын
@@bready8415 Yes Reddy, once request hit to service, it takes care of redirecting request to available pods either of worker node... It does based on pod labels.but running multiple pods on multiple worker nodes in nodePort service approach is not recommended.. Yes it works but this is not good solution when you want to run multiple pods so ideal way you can have multiple pods on single nodes considering development or demo environments and testing application with nodePort scenario.. Or best to way to handle load across multiple nodes and multiple pods should be using load balancer service approach..
@nidhindev5235
4 жыл бұрын
Srinath can you please share me the present Coupon ?
@puneetsaneja3007
4 жыл бұрын
What if i delete node and create new node and create deployment on that node. Then node external ip would be change and end user would not be able to access it from old node ip.
@shivaburade4059
4 жыл бұрын
That is nodeport is used only for testing purposes and not on production. In nodeport we manually have to manage nodes.
@isshwar7
5 жыл бұрын
Can service be described inside the deployment yaml as we can do this for deployment and pods?
@lakshmimaha5716
5 жыл бұрын
Yes you can
@sahajrajmalla
4 жыл бұрын
what will we do when we have to deploy our app in production, sir ?
@basunilkanthe2589
4 жыл бұрын
you should try with load balancing approach in the production considering restriction of NodePort.. Considering Node Port stick with specific service
@rahulmam5653
4 жыл бұрын
Still I am in doubt. Is targetPort the port of Pod or container? When you say service Port , does it mean the container Port?
@basunilkanthe2589
4 жыл бұрын
Service port is for listening service and target port is for listening pod container.. Ideally Both service and pod listen on same port... This is what Srinath explained in the video..
@rahulmam5653
4 жыл бұрын
@@basunilkanthe2589 Thanks for your reply. My question was ,is targetPort a port of Pod or is it a port for container?
@basunilkanthe2589
4 жыл бұрын
@@rahulmam5653it should be port of container as container process run on pod and it listening on specific port to serve request.. In other word. In other word if you deploy two application on one virtual machine and both application run on specific port on same virtual machine. Both application listen on specific ports.. Similarly Pod is like environment where you can run multiple container applications
@rahulmam5653
4 жыл бұрын
@@basunilkanthe2589 Then why does he say "This is the port of actual pod" at 6:17 referring to target port.
@basunilkanthe2589
4 жыл бұрын
@@rahulmam5653 you need to understand context here Rahul.. When i say tableau server running on virtual machine on port 443 and it should be your application which has deployed on VM.. when container running on port 80 on Pod means you can say it as pod port or you can say containerPort..This is what i have understood from video.. I dont think container port and pod port both different.. you get details from below blog.. Written to understand what are different type of port.. medium.com/@deepeshtripathi/all-about-kubernetes-port-types-nodeport-targetport-port-containerport-e9f447330b19
@devopstechy
4 жыл бұрын
Suppose Node 2 gets down then what will happen, as node port service is running on node 2.
@basunilkanthe2589
4 жыл бұрын
Thats why we should have multi node approach where kubecontroller create another node if primary node goes down.. To achieve this you need use service type Load Balancer
@UnknownSend3r
2 жыл бұрын
@@basunilkanthe2589 do you really need a service type load balancer, I thought fault tolerance such as a node down is something ku ernetes does by default and all that’s needed is multiple nodes, but nothing to do with services (like loadbalmer) I just started learning so could be wrong.
@rohitpandey3603
4 жыл бұрын
Hi Srinath, I have installed kubernetes cluster on AWS using kops. So if I expose my pods to the outside world using service node port. Then external IP is the IP address of the node on which my pod is running. And I need to allow 31000 port in the inbound rules right.
@bready8415
4 жыл бұрын
To my understanding Yes
@basunilkanthe2589
4 жыл бұрын
your pod is running on pod ip address and it is not running on node ip address but yes pod and service both running node(virtual machine) but not with node IP address.. Using NodePort service approach, you are just exposing your pod application to outside world on port range 30000 -32767 so you can access pod application from nodeIP and nodePort.. NodeIP will redirect your request to serviceIP and Port and then you know service IP will interact with pods based on pod label..
Пікірлер: 66