Harness the Power of Kubernetes with Pod Disruption Budgets

You might be doing Kubernetes wrong. Most customers I've worked with have applications running with only one replica.
You can gain unlimited access to my Kubernetes & DevOps courses here:
⚠️ mischavandenburg.com/skool - currently ON SALE for just $19
Join the thriving Skool community of 100+ learners and experts working with DevOps, Kubernetes & Cloud.
#cloudnative #devops #coding #vim #neovim #homelab #kubernetes #commandline #terminal #tmux #markdown #writer #zettelkasten

[@mischavandenburg]

You can gain unlimited access to my Kubernetes & DevOps courses here: ⚠ mischavandenburg.com/skool - currently ON SALE for just $19

[@tsiatt]

pod topology spread constraints comes to mind for resilience but I get why a pod disruption budget makes more sense in many cases. That way a developer doesn’t need to know any details about the Kubernetes update process and can just define the minimum requirements for their application. I learned something today.

[@WaylonWalker]

Mischa you are making amazing content here!

[@mischavandenburg]

Thank you! This definitely hasn't been getting the views it deserves. Well, it's there for the people who need it! :)