Hyperconvergence and Kubernetes

Jake Levins September 16, 2020 5 No Comments


Stay on Top of Emerging Technology Trends

Get updates impacting your business by our GigaOm Research Community

Hyperconverged infrastructure (HCI) has rapidly earned a spot at the datacenter, largely on account of the guarantee of infrastructure simplification. HCI has already worked really nicely for virtualized infrastructures, but will this be the situation with Kubernetes? There’s reason for optimism, and that I provide a few ideas here as to why.

HCI is one of several tactics to construct your calculating stack. The thought would be to virtualize and fall a number of components of this pile, such as storage and networking, together with compute tools (virtual machines). The strategy trades off some functionality for improved flexibility and simplicity of use. In its early iterations, HCI was a great match for largely small-to-medium sized businesses (SMBs) and vertical applications like virtual desktop (VDI). Now the performance difference has narrowed and HCI could be leveraged across a broader variety of applications. Some IT organizations have made HCI their go-to technologies, together with 90percent of the data centres assembled around HCI!

Kubernetes and HCI

The query before us today is: “Is HCI good for Kubernetes?” The short answer is yes, however, there are a couple of elements to consider .

Kubernetes is a container orchestrator that typically runs Linux operating systems. Applications are deployed in containers which are then arranged in Pods (a pod function as minimum allocation component for Kubernetes and that may contain one or more containers). Unlike virtualized infrastructures, in which every single VM has another operating system, the container stocks most of its fundamental components together with the underlying operating system. From this point of view virtualization is unnecessary and costly, but (and there’s always a however ), the reality is much more complicated for two reasons.

First, few enterprises can migrate into some 100% container surroundings overnight. This implies that VMs and containers need to reside together for a lengthy time. In some situations the application will be hybrid indefinitely. Some components will continue being virtualized–a classic business database at a VM such as –obtained by the containerized application. This could occur for many reasons, sometimes simply since the virtualized component can not be set up in a container or it’s too expensive to migrate.

Second, Kubernetes is only an orchestrator. Additional components are required to generate the Kubernetes audience able to react adequately to business requirements. This comprises data storage and networking, particularly when the applications are stateful. And handling stateful applications was believed non-existent in the start, but that is becoming a standard for most Kubernetes deployments.

So, at the conclusion, we’ve got two demands: direction of a hybrid environment and infrastructure simplification. Again, HCI appears more intriguing than in this circumstance.

HCI for Kubernetes

There have been at least three examples I Can make to describe why HCI could be advantageous for your Kubernetes plan:

  1. VMWare. You likely already know about VMware’s attempts around Kubernetes (here is a free report I wrote long ago around VMware Tanzu Portfolio). VMware just integrated Kubernetes using its hypervisor. Even though this can be considered an aberration by Kubernetes purists, there are advantages in getting VMs and containers incorporated. The price of this VMware licenses could be hard however, if we believe in terms of TCO, then it’ll be simpler to handle than a intricate hybrid atmosphere.
  2. Nutanix. Nutanix has a solution which lets you execute Kubernetes transparently in addition to its hypervisor (and cloud now). It requires another approach to the issue than VMware, but the advantages to the consumer are alike.
  3. Diamanti. Diamanti moves in a totally different direction, together with storage and networking components which are incorporated in the system and optimized for Kubernetes. This design surpasses a number of these constraints of this orchestrator and enhances its overall efficacy to deliver simplicity and performance to the table. If you intend to spend greatly in Kubernetes, Diamanti provides a legitimate alternative to both general-purpose HCI and bare-metal Kubernetes.

Here a video regarding the Diamanti Architecture and also how it’s different from others.

Closing that the Circle

Enterprises must start looking into HCI for Kubernetes to precisely the exact same reason they adored HCI to get virtualization. There are just two strategies to consider: One that expands the present HCI platform to comprise Kubernetes, along with another which uses a committed HCI to get Kubernetes. Both strategies have advantages and pitfalls and your selection will depend on how crucial Kubernetes will be to your entire IT plan now and for another few years. Other significant elements to consider include the reach of your own infrastructure and the degree of efficiency you want to attain out of it.

The VMware and Nutanix options are equally strong and can help you handle a seamless transition out of virtualization into your hybrid (VMs + containers) environment. Meanwhile, options such as Diamanti could combine the ease of HCI together with the efficacy of a dedicated alternative.

fbq('init', '1157339287680303'); fbq('init', '172929499778809'); Fbq('monitor', "PageView");

Leave a Reply

Your email address will not be published. Required fields are marked *