Orchestrate VMs with
Kubernetes & deploy

Fast track your digital transformation

Put VMs inside a container and connect with
any workload anywhere

Connectivity with the Slice overlay network
enabling the support for all communication
protocols not just HTTP

What is VMKubed?

Getting VMs into a container orchestration platform is just half the battle. Once your VM is inside a Kubernetes pod, how does it communicate with other Pods in and out of the cluster. Avesha VMKubed offers the complete solution starting from VMs to easy application networking between VMs & containers.

One platform to manage K8s workloads and VM workloads

KubeSlice enables you to run a single platform for both VM workloads and container workloads for scaling on demand, resiliency and disaster recovery design patterns.

Multi cloud & On-prem support

The VM workloads can be connected to any cloud workload or any workload in a private data center.

Easy to use interface and low costs

VMKubed comes with KubeSlice which has easy steps to connect heterogeneous workloads be it VMs or containers. All this at a fraction of a cost.

DevOps service to convert VMs to container workloads

Avesha offers DevOps support through its partners to design and implement modernization of VMs workloads starting with dependency mapping, conversions with KubeVirt & connectivity & segmentation with KubeSlice.

Ecosystems & Integrations

Kubernetes, AWS, Azure, GCP, OpenShift, Prometheus, Kiali, HELM

Who needs VMKubed?

Any enterprise that has a need to modernize in an easy, cost effective & complete manner needs VMKubed.

VMs get the benefits of Kubernetes orchestration

  • autoscaling
  • bin packing
  • reduced footprint costs

Once VM workloads are in the the cloud they can be multi-tenant for better visibility, ie be segmented based on product functionility or teams.

VM workloads in dataceneters & container workloads in cloud can communicate each other through east-west communication tunnels using an protocol.

Avesha VMKubed Architecture

Application Slice is an “overlay” because it works with existing K8S deployments and does not require any significant change to existing code – only an annotation needs to be added to a pod spec to enable its inclusion into an Application Slice.

How does it work?

Here are the steps used by Avesha VMKubed to modernize your VMs and get them on a Kubernetes platform ready to communicate with other microservices

Step 1

Prepare your VMs to be moved to Kubernetes/Kubevirt orchestration. Kubevirt supports several VM image formats (Kubevirt Image Formats) and others can be translated into those formats.

Step 2

Define the KubeVirt .yaml files to specify to Kubernetes how it should manage your VM-based services.

Step 3

Onboard applications onto Avesha KubeSlice to ensure app to app connectivity between VM pods and traditional microservices.