Upgrading to a new release is one of the most disruptive operations we regularly inflict on our Kubernetes clusters. There are multiple strategies for doing an upgrade, but they all require rescheduling workloads and restarting cluster components.
We started offering upgrades on our managed Kubernetes platform, DigitalOcean Kubernetes Service (DOKS), in May 2019. Since then, our customers have kicked off about 20,000 automated patch and minor release upgrades on their clusters. Most of those upgrades went well, but some didn’t and we’ve learned a few things from the ones that went wrong.
In this talk, we will share lessons from a year of automated Kubernetes upgrades: what we got right, what we got wrong, workloads that caused us trouble, and changes we’ve made to make the process smoother. We hope these lessons will help others avoid pain in their Kubernetes upgrades.
Knowledge of the components of a Kubernetes cluster and how applications are deployed.
Adam Wolfe Gordon is the tech lead for managed Kubernetes and container registry at DigitalOcean. He previously worked on block storage at DigitalOcean and EMC. Adam is a regular conference speaker and a frequent attendee of and presenter at local meetups in Edmonton, Alberta, Canada. He likes building and debugging microservices, observability, and occasional forays into lower-level software.
If you’ve enjoyed this tutorial and our broader community, consider checking out our DigitalOcean products which can also help you achieve your development goals.