How to Sell Kubernetes to the Hypervisor-Minded – InApps 2025

Main Contents:

How to Sell Kubernetes to the Hypervisor-Minded – InApps is an article under the topic Software Development Many of you are most interested in today !! Today, let’s InApps.net learn How to Sell Kubernetes to the Hypervisor-Minded – InApps in today’s post !

Key Summary

Context: Kubernetes (K8s) is a container orchestration platform that can be challenging to pitch to IT professionals accustomed to hypervisor-based virtualization (e.g., VMware, Hyper-V).
Key Selling Points:
- Efficiency: Kubernetes optimizes resource usage by running containers, which are lighter than virtual machines (VMs), reducing overhead and improving scalability.
- Portability: Containers ensure consistent app deployment across diverse environments (cloud, on-premises), unlike VMs, which may face compatibility issues.
- Automation: Kubernetes automates deployment, scaling, and management of containerized apps, simplifying tasks compared to manual VM management.
- Microservices Support: Aligns with modern microservices architectures, enabling faster development and updates, unlike monolithic VM-based systems.
Addressing Hypervisor Concerns:
- Familiarity: Explain Kubernetes as a “next-generation hypervisor” that manages containers instead of VMs, emphasizing familiar concepts like resource allocation and workload management.
- Security: Highlight Kubernetes’ role-based access control (RBAC) and container isolation, comparable to VM security models.
- Learning Curve: Acknowledge the shift but emphasize tools like Helm and Kubeadm, which simplify Kubernetes adoption, similar to vSphere for VMs.
Benefits for Stakeholders:
- Cost Savings: Reduced infrastructure costs due to efficient resource utilization.
- Agility: Faster deployment cycles and easier scaling for dynamic workloads.
- Ecosystem: Access to a robust community and tools (e.g., Docker, Helm) for ongoing support.
Strategies to Convince:
- Use analogies (e.g., Kubernetes as a “VM orchestrator for containers”).
- Showcase case studies of successful Kubernetes adoption in similar organizations.
- Offer pilot projects to demonstrate tangible benefits with minimal risk.
Challenges: Address resistance due to complexity by recommending training and managed Kubernetes services (e.g., AWS EKS, Google GKE) to ease the transition.

Read more about How to Sell Kubernetes to the Hypervisor-Minded – InApps at Wikipedia

You can find content about How to Sell Kubernetes to the Hypervisor-Minded – InApps from the Wikipedia website

Throughout 2016, the community around the open source Kubernetes container orchestration tool has continued to grow at a pace that surprised many.

“Probably the biggest defining moment for the Kubernetes community right now is that other communities are communities of vendors more so than Kubernetes. I think Kubernetes is more a community of developers, operators, and users than it is of vendors. It’s up to us as users and developers in that community to continue to keep that feeling,” Intel Vice President and General Manager of Cloud and Infrastructure Technologies Jonathan Donaldson said on the 114th edition of the InApps Analysts podcast, a special “Pancake Breakfast Podcast” recorded during the CoreOS Tectonic Summit, held in New York this week.

Donaldson was joined by SAP Director of Cloud Architecture & Engineering Nishi Davidson, CoreOS Vice President of Engineering Mike Saparov, and Tigera CEO Andy Randall:

#123: Tectonic Summit Pancake Breakfast – How to Sell Kubernetes to the Hypervisor-Minded

Listen to all TNS podcasts on Simplecast.

According to Davidson, SAP has been working with Kubernetes for 11 months and has experienced its fair share of challenges in doing so. Davidson noted that the most beneficial part of the Kubernetes community was its overall helpfulness and communication. Regardless of the time of day, she did not have to wait long for a community member to respond to a question she had while building out the SAP engineering and operations pilots.

“The beautiful thing about the open source community is any portion of the architecture that you want to build and improve on is easily accessible,” said Davidson, adding that, “The open source community helped us. We didn’t have to sit and struggle trying to find articles. The community helps you build whatever you need to build.”

In coming up with a variety of pilots to showcase why moving SAP from its hypervisor-focused infrastructure over to Kubernetes would be beneficial for the company, Davidson was met with questions such as, “Why do we need this?” and “What’s the point of another orchestration layer?” to which she set about creating pilots that would display the many improvements Kubernetes could offer SAP in an aim to take it into production.

Davidson and her team built a business case, one that showed that a container architecture on bare metal would yield a 10-12 percent performance boost. “We have proved the end-to-end use case on the pilot. We’re moving into an operational pilot, and hopefully, within the next five months we can get there,” she said.

It is the continued support and education of the community as a whole that has led to organizations both large and small to take notice of Kubernetes. “There is more education around what to use containers for and how to use them. It starts giving developers the ability to use containers and different technology in parallel and figure out what they want to migrate and what they don’t at this point.” Saparov noted.

For the majority of the Kubernetes community, despite its size, there is a continued commitment to keeping it a small, centralized group that remains helpful and responsive to all, not just company vendors with questions. “It should not become something where vendors have a huge influence. I think that would be contradictory to everything Kubernetes stands for. It scares the hell out of me to think of a future like that,” said Davidson.

As the conversation drew to a close, Donaldson offered sage parting advice to conference attendees. “Any time you have an open source community that’s generating as much interest as this one we have, is you’re going to have vendors seeing value and coming into that space. I think any time you let any of the large open source project become big you’re going to have the same kind of issue happening.”

Intel sponsored this podcast. CoreOS is a sponsor of InApps.

Feature image: (Left to right) Mike Saparov, Andy Randall, Johnathan Donaldson, Nishi Davidson. Photo by Ben Hider, courtesy of CoreOS.

InApps is a wholly owned subsidiary of Insight Partners, an investor in the following companies mentioned in this article: Tigera.

Source: InApps.net

Rate this post

Phu Nguyen

As a Senior Tech Enthusiast, I bring a decade of experience to the realm of tech writing, blending deep industry knowledge with a passion for storytelling. With expertise in software development to emerging tech trends like AI and IoT—my articles not only inform but also inspire. My journey in tech writing has been marked by a commitment to accuracy, clarity, and engaging storytelling, making me a trusted voice in the tech community.