This article is based on a VMware survey of 247 executives and IT professionals from larger organizations, examining enterprise Kubernetes and container adoption patterns. Disclosure from the original source: the article’s author has performed independent research work for VMware but was not involved in this specific survey.
Technology Is the Easy Part
Container technology has a clear value proposition: faster software delivery, better resource utilization, and improved application portability. Kubernetes, the open-source container-orchestration platform originally developed at Google and now maintained by the Cloud Native Computing Foundation (CNCF), has become the de facto standard for managing containerized workloads at scale. Enterprise adoption is growing steadily.
But technology adoption is rarely a purely technical challenge. According to the VMware survey, organizational culture and internal misalignment are proving to be more formidable obstacles than any technical limitation. As the DevOps community has long observed: containers won’t fix your broken culture.
Where Enterprises Stand on Kubernetes Adoption
The survey findings paint a picture of adoption that is broad but still relatively shallow in many organizations:
- 57% of respondents are running fewer than 10 Kubernetes clusters.
- 60% are running less than half of their containerized workloads on Kubernetes.
- Despite this, the majority of enterprises report that they are now using Kubernetes to manage and align container environments.
This suggests that most enterprises are past the proof-of-concept stage but have not yet achieved full-scale production rollouts. Kubernetes is present, but it has not yet become the universal runtime for containerized applications within most of these organizations.
On-Premises Deployments Lead, Defying Expectations
One of the more surprising findings from the survey concerns where Kubernetes is actually being deployed. Despite its strong association with cloud-native architecture, most enterprise Kubernetes deployments are not in the public cloud:
- 64% of respondents have deployed Kubernetes on-premises.
- 42% run Kubernetes within a single public cloud environment.
The survey authors acknowledge this outcome was unexpected. Their interpretation: enterprises most often begin their Kubernetes journey on existing infrastructure, taking advantage of already-established virtualized environments rather than migrating to public cloud first. This is consistent with the broader pattern of incremental infrastructure modernization seen across many large organizations.
Importantly, Kubernetes’ hybrid capabilities make this a practical path. Because Kubernetes can run clusters both on-premises and in the cloud, organizations can containerize workloads on existing infrastructure and move them to the cloud progressively, rather than committing to a full cloud migration upfront.
Reported Benefits of Kubernetes in Production
Among respondents already running Kubernetes, the reported business and operational benefits are significant:
- 56% cite improved resource utilization.
- 53% report shortened software development cycles.
- 50% are using Kubernetes to containerize legacy monolithic applications.
- 42% say it makes cloud migrations easier.
- 33% report reduced public cloud costs.
The cost-reduction finding is notable. Running Kubernetes on public cloud infrastructure allows organizations to use compute resources efficiently and elastically, scaling down when demand is low rather than maintaining fixed capacity. For workloads with variable traffic patterns, this can meaningfully reduce cloud spend.
Where Culture Creates Friction
Despite the clear benefits, organizational culture is consistently identified as a top barrier to effective Kubernetes adoption. Several survey findings illustrate this:
Internal Alignment Is a Major Problem
40% of respondents cited a lack of internal alignment as a problem specifically when selecting a Kubernetes distribution. Choosing a Kubernetes platform should be a technical decision, but in practice it often becomes a cross-functional negotiation involving multiple stakeholders with different priorities.
Multiple Teams Are Involved in Every Decision
83% of respondents say more than one team is involved in selecting a Kubernetes distribution. This is not inherently problematic — broad input can improve decisions — but when combined with poor alignment, it leads to the familiar pattern of many meetings that fail to produce a clear decision.
Who ultimately drives the decision depends on context:
- When Kubernetes is deployed for development only, development teams are the primary decision-makers 38% of the time.
- In production environments, infrastructure teams are primary decision-makers 23% of the time.
- C-level executives are directly involved in the decision 18% of the time — a reflection of the strategic weight organizations place on selecting their next-generation platform.
Executives and Developers See Completely Different Obstacles
Perhaps the most operationally significant finding is a sharp disconnect between what executives think developers struggle with and what developers actually report:
- 46% of executives believe the biggest developer obstacle is integrating new technology into existing systems.
- Developers themselves rank waiting for central IT to provision infrastructure access as their top obstacle — cited by 29% of developer respondents.
- Only 6% of executives identify infrastructure access delays as a meaningful obstacle for developers.
This gap matters operationally. When leadership misdiagnoses the problem, investments go toward integration tooling and training when the actual bottleneck is an internal provisioning process. Developer velocity suffers not because of technical complexity, but because access to infrastructure is controlled through slow, centralized workflows.
Kubernetes Has Not Yet Closed the Dev–Ops Divide
One of the aspirational promises of Kubernetes is that it creates a common operational layer that brings development and operations teams closer together — a shared platform with consistent abstractions for deploying, scaling, and managing applications. In practice, the survey suggests this convergence has not fully materialized in most enterprises.
The organizational structures, decision-making processes, and cultural norms that existed before Kubernetes tend to persist after adoption. Kubernetes can reduce technical friction, but it does not automatically restructure how teams collaborate, who controls what, or how priorities are set.
What Organizations Can Do
The survey authors conclude that organizations adopting Kubernetes and other cloud-native technologies may need to make deliberate adjustments to their organizational structure and culture to realize the full potential of the technology. Some practical areas to address:
- Reduce provisioning friction. If developers are waiting on central IT for infrastructure access, self-service provisioning models — with appropriate guardrails — can eliminate a significant source of delay.
- Clarify decision ownership. Define in advance which teams own which decisions for Kubernetes platform selection, cluster configuration, and workload onboarding. Ambiguity drives the meeting-heavy, decision-poor dynamic the survey describes.
- Bridge the executive–developer perception gap. Regular, structured channels for developers to surface operational obstacles to leadership can help ensure investments target actual bottlenecks rather than assumed ones.
- Treat platform selection as a product decision. When C-level executives are involved 18% of the time in Kubernetes distribution selection, the organizational stakes are high. Treat the evaluation with appropriate rigor — defined criteria, time-boxed analysis, and a clear decision owner.
- Invest in cross-functional enablement. Kubernetes spans development, operations, security, and networking. Training and enablement programs that cut across these silos can reduce the alignment problems that slow adoption.
Key Takeaway
Kubernetes is becoming a standard part of the enterprise infrastructure stack, delivering measurable improvements in resource utilization, development velocity, and cloud cost management. But the technology alone does not resolve the organizational challenges that have historically slowed IT modernization. Cultural resistance, misaligned incentives, and siloed decision-making remain the hardest problems to solve — and they require deliberate organizational change, not just better tooling.
As the survey puts it: containers won’t fix your broken culture. But understanding where the cultural friction points are is a useful starting point for addressing them.