Kubernetes vs. VMware vCenter

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

Incentivized

The VMware vCenter server is very useful in maintaining the CPU/RAM/datastore resources are balanced when there are multiple ESX/ESXi host servers. It is clear what resources are being used, and it is easy to migrate VMs to different ESX/ESXi hosts. Being able to remotely connect to the VM servers in vCenter when you cannot have other remote connections helps in maintenance and troubleshooting.

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• VSAN storage management and redundancy - high performance IO with built in fault tolerance across the cluster, not reliant on a single hardware item
• VM fault tolerance. The ability to relocate a running VM and restart VMs from failed or isolated nodes
• Resource management and alerting. Tracking load across physical systems and allowing us to rebalance for better utilisation

Incentivized

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

• Currently, the HTML 5-based vSphere Client lets you manage the essential functions of vSphere from any browser, however, it would be nice if they would port all management functions over to the HTML 5-based Client.
• Performing updates and upgrades to the infrastructure is a bit challenging for someone that may not be as intimate with vSphere. I think the updates/upgrades should be more integrated into the UI and provide the ability to push to the hosts, etc...
• It would also be nice to have a more robust snapshot management tool to prevent snapshot overgrowth. It would be nice to be able to set a lifespan for the snapshot(s)

Incentivized

The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.

We are very dependent on this software, it has become a much needed tool to perform the daily tasks that are required to maintain the virtual server environment. VMware has become very pricey over the years, so we are looking for alternatives for cost savings strategy, but nothing has been found to be on par to what we are currently using

Incentivized

It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself

Incentivized

I work with vCenter for 10+ years and i love it. I can find my way around and can help building and expanding the platform. It is easy to use and there are a lot good communities for the extra support when needed. Even the Homelab community is of great value.

Incentivized

VMware support has always been fantastic and they have been invaluable in solving tougher issues that have been run into. Most of the time, any oddities encountered are fixed by available updates. This can be deduced by support quickly with logs within vCenter. We have not run into something yet that support was unable to help with. They either have a solution already, or they are able to find one quickly.

Incentivized

Since moving away from the Windows Server hosting the vCenter application and instead using a virtual appliance, it has become much easier to implement and deploy the new versions. We can easily create a snapshot or clone of the vCenter vApp to ensure any problems encountered during the upgrade can be mitigated with a fall back to the old version to prevent unscheduled downtime.

Incentivized

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

Incentivized

Citrix Xen Server.... Great Hypervisor but very limited in terms of functionality

MS Hyper-V... [VMware vCenter Server] is better for almost everything and appliance form makes a clear winner for security and ease of deployment

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized

• The positive impact of vcenter is definitely felt in larger organisations in terms of being able to manage multiple servers all in one environment
• It will decrease the amount of time your server engineers will have to spend in the server room or datacenter.

Incentivized