Pod Disruption Budget in Kubernetes: What You Need to Know | AKS tutorials

Did you know that there are two types of Pod disruptions in Kubernetes?
Involuntary disruptions occur due to hardware or system errors, while voluntary disruptions are initiated by application owners or cluster administrators.
To help plan for voluntary disruptions, Kubernetes provides pod disruption budgets (PDB). PDB ensures that deployments remain available during these events by defining how many pods must always be available or how many can be unavailable.
By using PDB, you can ensure high availability of your applications even during maintenance or scaling events. It's essential to understand the two ways in which PDB can be defined
minAvailable - Specified number of Pods must always be available, even
during a disruption.
maxUnavailable - Specified number of Pods can be unavailable during a
disruption.
0:00 What is Pod Disruption Budget?
3:44 Pod Disruption Budget- Demo
Join the group: t.me/sqlbrainbox
Book 1:1 Call: topmate.io/nirav_gandhi
Follow me on LinkedIn: / niravgandhisql
#aks #k8s #kubernetes

[@kbrajeshwaran]

Awesome.Much appreciate your efforts

[@Niravgandhi]

Thanks a ton

[@Chathumal2011]

Nice explanation. Can you mention the tool that is used to monitor the k8s cluster resources in the video.

[@Niravgandhi]

Lens

[@nileshjejurkar7839]

Nice video

[@Niravgandhi]

Thanks

[@kbrajeshwaran]

Can you please make video for azure dynamic volume with azure disk for jenkins deployment

[@Niravgandhi]

Sure

[@oldmonk5600]

can you please share all files which you was used for all these demos, you did very good work

[@Niravgandhi]

Thanks