The News
At KubeCon + CloudNativeCon Europe 2026, Portworx by Everpure outlined how it is extending its Kubernetes data platform to support a broader mix of workloads, including VMs and future AI/ML use cases, while helping enterprises navigate the shift away from legacy virtualization stacks. Alongside that message, the company announced Portworx Enterprise 3.6 and Portworx Backup 2.11, adding Kube Datastore Dynamic Pools, secure boot support, stronger secrets management, observability improvements, and more granular backup and restore capabilities for Kubernetes and KubeVirt environments.
Analysis
Kubernetes Is Expanding From Cloud-Native Destination to Virtualization Platform
Portworx’s KubeCon + CloudNativeCon Europe 2026 briefing was built around a simple but important market signal: Kubernetes is no longer only the destination for net-new cloud-native applications. It is increasingly being asked to serve as a platform for existing VMs, stateful applications, and eventually AI workloads too. In the briefing, the team said Kubernetes has long been “the de facto destination for new and cloud native applications,” but that Portworx has now “expanded our support to legacy and monolithic applications” so they can run alongside containers in the same environment.
Our research shows that 61.8% of organizations operate primarily in hybrid environments, while 60.7% prioritize cloud infrastructure and 68.3% prioritize security and compliance in the next 12 months. At the same time, 46.5% say deployment requirements have accelerated by 50% to 100% compared with three years ago, with another 24.7% saying the acceleration requirement is 2x or more. That combination is pushing enterprises toward fewer, more flexible operating models rather than maintaining separate platforms for every workload type.
Portworx is trying to position itself directly in that shift. The company’s message is not just that Kubernetes can host more workloads, but that data management becomes the real control point once customers decide to put VMs and containers on the same platform.
Portworx Is Framing Data Management as the Missing Layer in VM-to-Kubernetes Moves
One of the most useful parts of the briefing was that Portworx did not present the VMware market disruption as a simple lift-and-shift opportunity. Instead, it emphasized that the bigger issue is how customers manage performance, recovery, migration, governance, and storage behavior once they decide to run VMs on Kubernetes. That is a more grounded message.
In the briefing, the team said many enterprises are now “actively seeking alternatives” and that one of the biggest problem areas emerging in these migration efforts is “managing the data across all of these environments.” They also noted that the internal skills gap is becoming one of the primary challenges because VMware-era administrative models do not translate cleanly to Kubernetes-based operations. That is consistent with the broader market. Skill gaps remain one of the top obstacles in cloud-native adoption and infrastructure operations, while organizations continue to balance modernization goals against operational complexity .
Portworx’s answer is to collapse some of that complexity into one data platform. What customers need is not just storage, but a way to shrink the operational surface area. The company noted that if customers try to piece together Kubernetes data management solely through open source, they may end up dealing with “30 plus open source projects” across “12 different functional domains,” whereas the point of Portworx is to bring those functions together under a single platform. That positioning matters because the buyer problem is often less about raw feature count and more about operational coherence.
The customer references the company shared also reinforce that message. Portworx said it is now seeing more than 45 customers adopting VMs on Kubernetes as a core strategy, with one global automotive manufacturer running over 90,000 volumes tied to roughly 19,000 VMs across more than 25 plants, and SiriusXM using the platform across on-premises, cloud, and edge scenarios. Even more telling, Everpure itself has moved roughly 20,000 VM cores onto Kubernetes internally and is migrating hundreds more daily, with only a small internal team supporting the project. Whether or not every enterprise will move at that pace, the point is clear: the concept is no longer hypothetical.
Market Challenges and Insights
Developers and infrastructure teams have handled these business challenges by keeping virtualization, containers, backup, storage, and DR in separate operational tracks. That was manageable when Kubernetes was mostly for new applications and VMware handled the legacy estate. But once organizations start consolidating onto Kubernetes, those boundaries become a liability.
Portworx’s announcements speak directly to that problem. Kube Datastore Dynamic Pools are meant to reduce the mismatch between Kubernetes’ shared-nothing assumptions and the shared storage architectures enterprises already use. The company argues that many current approaches create unnecessary storage and network overhead when layered on top of SAN-backed environments. Kube Datastore is designed to align Kubernetes storage management more closely with those existing backends rather than forcing enterprises into inefficient workarounds.
That is a meaningful point for the market because infrastructure modernization is increasingly constrained by what already exists. Customers do not want to discard shared arrays, existing DR practices, or hybrid deployment patterns just to fit a new architectural ideal. They want a path that makes those assets usable inside a Kubernetes-centric operating model.
Security is another major part of that story. Portworx Enterprise 3.6 adds UEFI Secure Boot support, tighter HashiCorp Vault integration, support for multiple secrets providers, and safeguards against unauthorized Azure cloud drive deletion. Those features are not flashy, but they line up with where buyers are spending. Security and compliance are a top priority for 68.3% of organizations, and regulatory requirements are the top factor influencing future security spend for 35.9% of respondents. As more VMs and regulated workloads move onto Kubernetes, those controls stop being optional checkboxes and become part of platform selection.
Backup 2.11 follows the same logic. Granular VM file-level restore, namespace and resource-specific restore, flexible scheduling, and editable backup scope all reflect a more mature operational requirement. Enterprises do not just need Kubernetes backup. They need the same kind of selective, policy-driven recovery behavior they are used to in more traditional environments, but adapted for mixed VM and container estates.
Why This Matters Going Forward
The broader implication of the Portworx story is that modernization is becoming less about choosing containers over VMs and more about finding a data layer that can support both while preserving governance, locality, and recovery expectations. That is why the company’s framing around “modern virtualization” is useful. It acknowledges that the future is not container-only. It is mixed, and increasingly it is Kubernetes-managed.
For developers, that could matter in a few ways. First, it may reduce friction between legacy and cloud-native application teams by bringing their workloads under a more common platform model. Second, it could make it easier for platform engineering teams to support self-service workflows with stronger governance, instead of forcing developers through separate infrastructure processes depending on workload type. Everpure’s own internal story hinted at that, with the team describing a move away from a multi-system ticketing model toward more automated self-service with governance.
For the industry, this matters because it suggests that Kubernetes data platforms may become more strategic as the market sorts out what comes after traditional virtualization dominance. Storage vendors that can show not only persistence, but migration support, backup, performance benchmarking, observability, and policy-driven operations, may have an advantage in that transition. Portworx’s new open source VertBench tool is a smart example of that. By making benchmarking and readiness testing easier and community-accessible, the company is trying to reduce one of the biggest barriers to migration: uncertainty.
Looking Ahead
The market for VMs on Kubernetes is moving from curiosity to execution, but it is still early enough that customers are looking for proof, tooling, and repeatable patterns rather than bold promises. That is why Portworx’s KubeCon + CloudNativeCon Europe 2026 story is more compelling than a simple feature launch. It is trying to show that Kubernetes can become a serious platform for mixed enterprise workloads, provided the data layer is ready for it.
Portworx Enterprise 3.6 and Backup 2.11 suggest the company understands that the next phase of Kubernetes adoption will be shaped by migration confidence, operational familiarity, and regulatory readiness as much as by raw innovation. If Portworx can keep turning its customer migration experience into practical frameworks, open tooling, and day-two operational capabilities, it could strengthen its role as a key enabling layer for enterprises trying to modernize virtualization without fragmenting their future platform strategy.
Platform Engineering Becomes the Control Layer for AI-Ready Kubernetes
Modern Virtualization Finds Its Kubernetes Data Layer
Runtime Security Meets Reality as Isolation Expands to KVM
Edge Intelligence Moves From Experimentation to Production Scale
Open Kubernetes Meets AI Infrastructure in a More Composable Stack
