Pavan, this is an awesome tutorial. I am task with adding probes to a few containers and this helped tremendously! You are a natural born Teacher! Namaste
Did you managed to figure it out @biswaranjanbiswal8918. Am equally stuck with same question and would be nice if @PavanElthepu finds time to respond. Nice content though.
He actually created only one pod. The other two pods were created prior . Check the timings. First two were created 11 mins ago. If were also created with same manifest, even they would fail too. I hope it got cleared!
Thanks Pavan. Nice Video and great explanation like other videos. One question, you gave all 4 parameters same vaue for al probes. what is the best values of each parameter for each probe (start up probe is optional) simple application like spring boot which starts in 15seconds
@@PavanElthepu sure Plz do videos on networking As we don't see in depth videos on k8's networking The way you explain is great, looking forward to next one's
In Kubernetes, if a liveness probe fails, it results in the container being restarted, not the entire pod. The liveness probe is used to determine whether the container is still running and healthy. When it fails, Kubernetes will kill the container and start a new instance within the same pod. On the other hand, if a readiness probe fails, the container is not restarted. Instead, the pod is marked as unready, meaning it is temporarily removed from service and won't receive any traffic until the readiness probe passes again. This does not cause a container or pod restart; it only affects the pod's availability for handling requests.
As I have seen in multiple places if both in Liveness and startUp probe if we fail the last attempt then POD will stopped? But you have mentioned in the liveness probe last attempted failed pod will restart again. Which is correct ?
Hi bro Readiness probe issue one of the pod is getting error with Readiness Prodbe failed: HTTP Probe failed statuscode:503. i could not get much error details by describing command , how to triage the issue ? advise eme
A 503 status code on a Readiness Probe typically means that the application running in the container is not ready to serve traffic. This could be due to several reasons. Like, application has a bug to start, or readiness probe is timing out before application is started. Please check if your application is started before readiness probe is fired
HI Pavan, I have one question from Probes, when liveness probe fails, 3 pods got restarted but when readiness probe fails, only one pod connection got disconnected from services.... why it is like ?
hi brother @@PavanElthepu i am also having same question in this video when you shown rediness probe you applied rediness probe in statefull set but only one pod is in not ready state how?
you are the only instructor for which I dont increase playback speed because every second of the bootcamp is meaningful and useful
"I became a fan of you, bro! Thanks for your effort to create content like this and make it available to everyone."
Thank you very much🙂. Please subscribe and share with your friends and colleagues
Yes, HELM this Sunday
Before seeing this video...i was too confused about these 3 kind of probs...now i understood very well....thank you so much pavan...
I dont know why are u so much underrated. Your k8s course should be sold on such udemy/coursera platforms.
Thank you! Means a lot❤️. Please subscribe and share with all your friends and colleagues.
Pavan, this is an awesome tutorial. I am task with adding probes to a few containers and this helped tremendously! You are a natural born Teacher! Namaste
This is the best video so far on TH-cam regarding probes, Thanks
Thank you RK. Please subscribe and share the channel with your friends and colleagues
This explaination has made me to understand the probes.
Now I clearly understood the difference between these 3 probes.
Thank so much
wonderful explanation, crisp, no hurry business, logically,
excellent
Thank you so much Aef Won. Please subscribe and share with your friends and colleagues.
Great and detail explanation, Thanks bro
Thanks for making videos and valuable content on the public online platform. Great 👏
Thank you Krishna🙏
Fantastic Simply and way to go ! Awesome content .
excellent, lucid explanation. thanks for efforts!
Excellent video with live example please do such videos on k8 concepts we ❤ this
Thank you. Please subscribe and share with your friends and colleagues
Thank you . These vids are really helpful.
Thank you so much. Please subscribe and share with your friends and colleagues
thank you sir, u explained it very clear way it helped me alot.. god bless u
Thank you. Please subscribe and share with your friends and colleagues
excellent explanations.. good work bro.
Thank you so much. Please share with all your friends and colleagues🙏
Very detailed.Thanks for ur efforts
Thank you. Please subscribe and share with your friends and colleagues
Excellent work 💯
Excellent explanation. thankyou.
Thank you. Please subscribe and share with your friends and colleagues
Good explanation Pavan
Pls upload Vedios on real-time for docker and kubernetes Pavan
Sure Vamsi, I'll plan once the K8s course is completed
excellent explanation ji
Excellent, thanks
Good much informative and explained well 👏
Nice explanation.....
Play: 10:53 sec why only one pod failed the readiness probe and the other two succeed.
Did you managed to figure it out @biswaranjanbiswal8918. Am equally stuck with same question and would be nice if @PavanElthepu finds time to respond. Nice content though.
i got the same doubt there ...
He actually created only one pod. The other two pods were created prior . Check the timings. First two were created 11 mins ago. If were also created with same manifest, even they would fail too. I hope it got cleared!
@@abhimj8526 Yes You are right. But there are three pods. You can see these pods in the readiness probe.
Thanks Pavan. Nice Video and great explanation like other videos. One question, you gave all 4 parameters same vaue for al probes. what is the best values of each parameter for each probe (start up probe is optional)
simple application like spring boot which starts in 15seconds
Setup ingress in Eks...
Please Provide those
brilliant
Good bro 🎉❤️
I am waiting for this video.....
I hope you liked it Jalndhar
Yes bro 🥰
You are the one and only that you understand deeply with practical.... It's really informative very much Bro 🙏
Great explanation thanks👍
Thank you Sushant. Please share with your friends and colleagues
@@PavanElthepu sure
Plz do videos on networking
As we don't see in depth videos on k8's networking
The way you explain is great, looking forward to next one's
Sure. Stay Tuned
thank u for the video! btw you pronounce the word "unhealthy" as "LD", i was so confused
the explanation was very helpfull , but I want to ask if the pod is getting restarted or the containers, after a failing Liveness or Startup Probes?
In Kubernetes, if a liveness probe fails, it results in the container being restarted, not the entire pod. The liveness probe is used to determine whether the container is still running and healthy. When it fails, Kubernetes will kill the container and start a new instance within the same pod.
On the other hand, if a readiness probe fails, the container is not restarted. Instead, the pod is marked as unready, meaning it is temporarily removed from service and won't receive any traffic until the readiness probe passes again. This does not cause a container or pod restart; it only affects the pod's availability for handling requests.
As I have seen in multiple places if both in Liveness and startUp probe if we fail the last attempt then POD will stopped? But you have mentioned in the liveness probe last attempted failed pod will restart again. Which is correct ?
Awesome
Hi bro
Readiness probe issue
one of the pod is getting error with Readiness Prodbe failed: HTTP Probe failed statuscode:503. i could not get much error details by describing command , how to triage the issue ? advise eme
A 503 status code on a Readiness Probe typically means that the application running in the container is not ready to serve traffic. This could be due to several reasons.
Like, application has a bug to start, or readiness probe is timing out before application is started. Please check if your application is started before readiness probe is fired
@@PavanElthepu
Hi bro
The same image tag deployed on different environment It's working fine without the probe issue
HI Pavan, I have one question from Probes, when liveness probe fails, 3 pods got restarted but when readiness probe fails, only one pod connection got disconnected from services.... why it is like ?
It’s deployment or statefulset?
@@PavanElthepu statefulset
Hi @Pavanelthepu , please can you respond to this question.
Possible to share your manifests?
hi brother @@PavanElthepu i am also having same question in this video when you shown rediness probe you applied rediness probe in statefull set but only one pod is in not ready state how?
Nice bro
Hi I am getting connection refused.
😍😍
Will you provide online training on K8s
Please send an email to pavan.elthepu@gmail.com
excellent :)
Thank you. Please share with your friends and colleagues
Pavan, 🤔by default Kubernetes will bring up the pods when they are down, so why these Probes?
best
How to add authentication in startup probe ?
Hi Haritha, may I know why you want to add authentication in startup probe?
PSP Please!!
Hi Joy, sorry! I didn’t get this.
@@PavanElthepu Please Provide a Video For Pod Security Policy Brother
@@joymiah1038 sure
@@PavanElthepu We will be Waiting for It
Sure Joy. Let me add it to my queue