Lessons Learned from Upgrading Kubernetes
At our parent company, Qbox, we had many Kubernetes clusters that we upgraded from a pre-1.0 version to v1.5. Because of this, they did not fit the same configuration as v1.5 clusters newly created fr …
| Talk Title | Lessons Learned from Upgrading Kubernetes |
| Speakers | Aaron Teague (Software Engineer, Supergiant) |
| Conference | Open Source Summit + ELC North America |
| Conf Tag | |
| Location | San Diego, CA, USA |
| Date | Aug 19-23, 2019 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
At our parent company, Qbox, we had many Kubernetes clusters that we upgraded from a pre-1.0 version to v1.5. Because of this, they did not fit the same configuration as v1.5 clusters newly created from standard provisioning tools like kubeadm or kops.I was tasked with upgrading from v1.5 of Kubernetes to v1.13. With v1.5 being two years old in a rapidly expanding technology, replacing the pieces in a way that customers would not notice was no small order.We successfully powered through this process and would like to share with the community the lessons we learned from doing so. When the options aren’t simply “build a new cluster,” finding a solution becomes key.
