We discuss how Kubernetes has won the war as a leader in orchestration. However, it is still not easy to use or maintain. We explore what organizations need to consider in order to build operational efficiencies around the technology. Kubernetes, Docker, and containers are very different from something like VMware and Amazon in terms of adoption. When organizations adopt new technologies, they typically become an IT-led project. On the other hand, containers pop up in clusters around the organization, started directly by DevOps teams, developers, and users. A lot of times they already exist scattered around an organization and need a framework or logic to manage all of it. Rancher Labs acts as a services platform to help manage many clusters.
Key Considerations for Kubernetes
We talk about the key considerations organizations need to think about when trying to deploy Kubernetes across multiple clusters, in a multi-cloud environment. Some key points are:
- Understanding expectations of scale
- Where you will be running it
- How to make it highly available
- Understanding your organization’s tolerance for failure
What many don’t realize is that organizations are often running Kubernetes in conjunction with legacy technologies. Many organizations still use legacy technology like VMs and only make small incremental changes. The two biggest place Rancher runs containers is on VMware and on Amazon. In summary, Kubernetes may prolong the life of legacy technologies like VMware.