VTwinDude's Blog

rss

Thoughts and updates from VTwinDude


VMware - Kubernetes thoughts

I've been working with VMware a long time and it works really well when you want to separate environments (IE VMs, clusters), have a single management tool set and save money via server consolidation.

We are now turning a new leaf as we move away from datacenter centric environments to application centric environments. I think that Kubernetes potentially will become the gateway to infrastructure. Being able to take an action directly against the ESXi kernel that run Kubernetes removes a lot of complexity.  However, I do believe that VMs and containers will be here for a long time, apps aren’t that easy to refactor.

There are many ways of doing Kubernetes. I do think VMware got it right by making Kubernetes part of the vSphere platform natively (ESXi kernel). This makes Kubernetes containers a 'first class citizen' on infrastructure instead of Infra-VM-OS-Container-app. This new way allows applications to scale as the application requires. That means that we will be able to manage 'both 1st class citizens (VMs and containers)' with one tool (VC) on one platform (vSphere) that enables operations and developers to do their job more efficiently! VMware DRS will still to the resource placement for workloads-the scheduler is very good at what it does.

This means that automation will be built-in to the platform to simply scale based on application's needs via policies and configurations. Today we simply automate what humans are doing as repetitive tasks, scripting things to be more efficient. But what we don't do is script application needs. As an example, imaging an application that needs more resources. You can now 'spin up another VM/container' or script logic to spin up another VM on another host. This builds resiliency into the application layer while keeping configuration consistent. Now we will be able to simply configure a policy to always have 3 containers up and running in a pod which can be built across hosts (IE ESXi cluster) and scale up as the application requires. The new way of automation where we won't need other agents, or to react, but the system will simply do it based on the configuration/policy is the future.

Kubernetes has a logical construct called a namespace which can be a collection of many things including VMs, PODs, and services along with other objects. A namespace allows for polices to be applied to it just like if it was a VM or storage or network, awesome right! Think about Kubernetes cluster running beside a VM cluster in the same Virtual Center that allows developers to run API commands directly to Kubernetes – there’s no need to learn a new tool.

Also, I would like to note that Kubernetes will run across all of the cloud providers as VMware is on top of them today. This should allow for multi-cloud models that are app centric! What if we were able to run an application with a node on-prem and 2 nodes in different clouds?

There are a lot of things that will mature over the next year. It will be great to learn and grow as a powerful platform continues to enable organizations to build modernized applications and support them.


 



Comments are closed.
Showing 0 Comment