Kubernetes vs. Red Hat Virtualization (discontinued)

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

RHEV is well suited for organizations that need a cost-effective and flexible solution for their environment. As its vendor-independent software, easily install on any type of hardware. RHEV provides a GUI interface to manage the software, which makes the management of the software easier for the end-user. RHEV is best for non-production or less critical applications. RHEV can be easily integrated with other REDHAT software.

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

• RHV issues/bugs can be reported via Bugzilla to RH support. The service is great and typically responds soon.
• Red Hat distribution integration is seamless as it is integrated into the kernel.
• OpenStack support enables more customized VM templates and network configuration control.

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

• 1- RHVM API is pretty slow, especially after creating a VM it is not possible to retrieve the VM details (i.e VM's MAC Address) fast enough, where we need to place a pause in our Ansible Playbook, make the automation process slow.
• 2- RHV is still using collected to monitor the hypervisors which is deviating from Red Hat policy for other RHEL based applications to use PCP to monitor, which is richer in features.
• 3- It will be great if it is possible to patch the hypervisors using other tools such as satellite and not only via RHVM.
• 4- In the past Red Hat used to present patches in the z release (i.e. 4.3.z), and features in the y release (i.e 4. y), but starting from 4.4 that is mixed together wherein the Z release you get both patches and features, that is not good because that requires a lot of time to test when we patch as it includes features as well.
• 5- Engineering team has to be more reactive when new feature is requested.

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.

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

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

RHEV is an excellent product, includes more features, is less expensive, and has rock solid reliability and is backed with the best Red Hat Support in the industry. RHEV uses KVM under the hood which is used by all the big players in the industry (AWS, Rackspace, etc) to lower their overall costs and improve efficiency and profits and that's why RHEV is an excellent solution!

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

• RHEV has provided a positive ROI as our customers are not experiencing as many outages during maintenances.
• We have not experienced any catastrophic failures as a result of vsphere losing connection to the ntp.
• There has been a level of stability in our environment that was not previously experienced with our previous vendor.

Incentivized