White Papers

White Paper: How Kubernetes Saved OpenStack

Issue link: https://read.uberflip.com/i/1387901

Contents of this Issue

Navigation

Page 1 of 1

© 2020 Mirantis Inc. All Rights Reserved. Information is subject to change. | www.mirantis.com But even seven years after its initial release, nothing in Kubernetes-space has stepped in to replace OpenStack. While various efforts to run virtual machine-like things on Kubernetes have been fielded, there's no satisfactory generally-accepted standards for how this should work. Still, the need for Inf rastucture as a Service (IaaS) remains and grows. Kubernetes' efficiencies, alone, aren't enough to solve for the problem of high public cloud costs, need for utilization efficiency, and so on. For that matter, Kubernetes itself needs somewhere to run, and VMs are most often the answer,. And yet there was still this thought that containers were better than VMs, and there was even an effort to containerize OpenStack, with the thought that this might solve the installation problem. But then someone realized that Kubernetes — designed for running big, complex applications — is itself a good host for OpenStack. OpenStack, after all, consists of a large number of independent services. With Kubernetes, it's possible to architect OpenStack as a microservices application that can be easily deployed, operated, and managed. If a service goes down, Kubernetes instantly restarts it. Kubernetes can manage multiple service instances, leading to a robust, highly available architecture. But perhaps the most important thing Kubernetes has done to save OpenStack is to solve that one seemingly intractable problem: upgrades. Running OpenStack as a collection of services on Kubernetes enables you to easily upgrade between versions, because Kubernetes itself manages the process. After all, it's specifically designed to replace one container (or Pod, in this case) with another in case of failure, so Kubernetes can use that capability to upgrade to a new version of that service without breaking the entire architecture — and while leaving workloads largely intact. So instead of replacing OpenStack, Kubernetes has made it possible for organizations to more confidently continue using it, saving them f rom having to re-architect legacy applications or force new applications into models for which they are not appropriate, while improving uptime easing operations, and making f requent upgrades not only possible but probable. Long live OpenStack — on Kubernetes! Learn more at Mirantis.com

Articles in this issue

Links on this page

view archives of White Papers - White Paper: How Kubernetes Saved OpenStack