This article is based on reporting originally published by containerjournal.com.
Remote Kubernetes Management Gains Urgency
Platform9 has expanded the tier structure of its managed Kubernetes service, aiming to lower the barrier to entry for organizations that want enterprise-grade container orchestration without building large in-house teams. The timing of the announcement — made during the early months of the COVID-19 pandemic in early 2020 — coincided with a surge in demand for remote infrastructure management tools, as IT teams shifted to working from home.
According to Platform9, the core value proposition of a SaaS-based Kubernetes management platform is straightforward: an organization installs the Platform9 agent software inside its existing Kubernetes cluster, and from that point the cluster can be monitored and managed remotely through the Platform9 control plane. This model removes the need for on-site access and reduces operational overhead for distributed or remote teams.
Kubernetes Expertise Remains the Biggest Bottleneck
Despite growing adoption, the Kubernetes skills gap continues to be a significant obstacle for organizations trying to operationalize container orchestration at scale. Building a team capable of deploying, securing, upgrading, and troubleshooting production Kubernetes clusters requires specialist knowledge that is still relatively scarce in the broader IT workforce.
This gap is a primary driver behind the growth of managed Kubernetes services. Rather than hiring and retaining expensive specialists, organizations can delegate day-to-day cluster operations to a managed service provider (MSP) and redirect internal resources toward application development. Platform9 reported that adoption of its managed Kubernetes offering nearly quadrupled between 2018 and 2019, and the company cited a gross customer renewal rate of 92.7% in 2019.
Avoiding Vendor Lock-In Drives Adoption
A recurring theme among Platform9 customers, according to company leadership, is the desire to avoid dependency on a single Kubernetes distribution or cloud provider. Hyperscaler-managed services such as Amazon EKS, Google GKE, and Azure AKS offer tightly integrated experiences but can make workload portability difficult. Platform9 positions itself as a distribution-agnostic layer that can run on public cloud, private cloud, or bare-metal infrastructure, giving operators more flexibility over where and how workloads run.
A Competitive and Evolving Market
The managed Kubernetes space was already crowded in 2020 and has only grown more competitive since. Hyperscalers, independent software vendors, and specialist MSPs all compete for organizations that want to reduce the operational burden of running Kubernetes. Key differentiators typically include:
- Deployment flexibility: Support for on-premises, multi-cloud, and hybrid environments.
- Upgrade automation: Automated, zero-downtime cluster upgrades.
- Observability tooling: Built-in monitoring, alerting, and logging integrations.
- Support tiers: SLA-backed support with clearly defined response times.
- Pricing model: Per-node, per-cluster, or consumption-based billing.
Will Organizations Stick with MSPs as Their Expertise Grows?
One open question for the industry is whether organizations that initially adopt managed Kubernetes will eventually bring those operations in-house once they develop sufficient expertise. MSPs are betting that the answer is largely no — that the economics of focusing engineering talent on product development, rather than platform operations, will keep demand for managed services high even as Kubernetes skills become more widely distributed.
The DevOps model complicates this picture. In teams that practice DevOps, the boundary between application development and infrastructure management is intentionally blurred. Engineers who own their services in production may also own the platform those services run on, making full outsourcing of cluster operations less natural. Managed service tiers that offer a middle ground — handling upgrades and security patching while leaving developers in control of workload configuration — may be best positioned to serve this audience.
Key Takeaways for DevOps Teams Evaluating Managed Kubernetes
- A SaaS-based Kubernetes management plane can significantly reduce the operational overhead of running clusters, especially for remote or distributed teams.
- Managed Kubernetes adoption is accelerating, but the Kubernetes expertise gap remains a real constraint for many organizations.
- Avoiding lock-in is a genuine concern — evaluate whether a managed service supports workload portability across clouds and on-premises environments.
- Renewal rates and growth metrics from vendors should be treated as marketing claims; request independent references and proof-of-concept environments before committing.
- Consider how a managed service integrates with your existing CI/CD pipelines, GitOps workflows, and observability stack before selecting a tier.