Table of Contents
- Executive Summary
- Market Categories and Deployment Types
- Decision Criteria Comparison
- GigaOm Radar
- Solution Insights
- Analyst’s Outlook
1. Executive Summary
Kubernetes has become the dominant technology for orchestrating container-based software deployments outside of specific cloud environments. Developers, especially those accustomed to cloud-based deployments, now prefer to build applications using containers. Kubernetes provides a common and well-understood approach to managing those deployments for self-managed infrastructure.
What started with low-risk, non-critical, exploratory applications at a small scale has now moved to large-scale adoption for business-critical applications. Kubernetes has similarly moved from smaller proof-of-concept implementations to critical infrastructure supporting these microservices-based applications.
Yet, Kubernetes remains a complex platform to operate and one that is continuously changing. Updates are relatively frequent, providing bug fixes and new features, though the pace has slowed somewhat as Kubernetes matures as a platform. For IT organizations accustomed to the relative stability and slower pace of change of more established platforms, this complexity and rate of change presents significant challenges.
The reality is that most organizations are not prepared for the operational demands of the complex and constantly changing ecosystem that Kubernetes represents. Managing existing workload demands is already a challenge without the additional burden of learning new skills. Organizations are therefore faced with a difficult choice: reject Kubernetes completely and compromise developers’ desire to use microservices patterns, muddle through on their own as best they can with what they have, or look for outside assistance.
Managed Kubernetes is an attractive way to shift the operational burden of maintaining Kubernetes and its ecosystem away from the internal IT team. This can be achieved through automation—where vendor offerings manage the Kubernetes clusters for customers—or a managed service. Managed services are a known quantity commonly used in other areas of enterprises today.
There are multiple managed Kubernetes options to choose from, and the choice is made easier by the Cloud Native Computing Foundation’s early move to define a standard for Kubernetes interoperability. This standard helped to reduce the risk of Kubernetes splintering into multiple competing and incompatible variants, as in the early Unix market and later with Linux distributions. The core of Kubernetes is the same on all standard-compliant options, which differentiate themselves on value-added features and functions.
This is our fourth year evaluating the managed Kubernetes space in the context of our Key Criteria and Radar reports. This report builds on our previous analysis and considers how the market has evolved over the last year.
This GigaOm Radar report examines 15 of the top managed Kubernetes solutions in the market and compares offerings against the capabilities (table stakes, key features, and emerging features) and non-functional requirements (business criteria) outlined in the companion Key Criteria report. Together, these reports provide an overview of the category and its underlying technology, identify leading managed Kubernetes offerings, and help decision-makers evaluate these solutions so they can make a more informed investment decision.
GIGAOM KEY CRITERIA AND RADAR REPORTS
The GigaOm Key Criteria report provides a detailed decision framework for IT and executive leadership assessing enterprise technologies. Each report defines relevant functional and non-functional aspects of solutions in a sector. The Key Criteria report informs the GigaOm Radar report, which provides a forward-looking assessment of vendor solutions in the sector.