Kubernetes vs. Oracle VM VirtualBox

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

It is best suited when you want to have different operating systems on your laptop or desktop. You can easily switch between operating systems without the need to uninstall one. In another scenario, if you expect some application to damage your device, it would be best to run the application on the VM such that the damage can only be done to the virtual machine. It is less appropriate when time synchronization is very important. At times the VMs run their own times differently from the host time and this may cause some losses if what you doing is critical. Another important thing to take note of is the licensing of the application you want to run your VM. Some licenses do not allow the applications to be run on virtual servers so it is not appropriate to use the VM at this time.

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

• It is simple to install - there is no advanced knowledge required to begin building virtual computers
• It is easy to use - adding new virtual machines is simple with wizard-based deployment
• It enables easy portability - moving virtual machines from one host to another is straight-forward and simple
• It is free

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

• I have had issues in the past when it has come to resizing VM disk storage. The issue is entirely detailed here: https://www.virtualbox.org/ticket/9103 -- the problem was caused because of having existing snapshots (which error message output was not detailing). I haven't had to deal with the issue due to my dynamic disk sizes not being small from the start anymore (this is mostly an issue for my Windows VMs where the base disk may need significant size for the OS). It looks like, for a resize, that a merge of all snapshots has to occur first -- one user on that list details a workaround to maintain snapshots by cloning the VM. (Note: 5.2 was just released a few weeks ago, and looks like it should prevent the problem happening in the future by properly informing users that it isn't possible with snapshots).
• Certain scenarios, like resizing disks, required dropping into a terminal as there were no options to previously do so via the GUI. According to some recent posts, I've seen that v5.2 has added disk management stuff like that to the GUI (or will be adding it). I'm comfortable with dropping into the terminal, but in a teaching scenario or when evaluating the learnability of the tools, it complicates things.

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.

I give this rating because virtual box is inexpensive but there is another product such as vm ware that can also be used

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 love using the Graphical User Interface. The VirtualBox Manager is very easy to understand and use. You can quickly create, configure and manage all your virtual machines in one window. It makes operating virtual machines easy and simple. When using VBoxManage it gives the user comprehensive control over VirtualBox so that you can use automation and scripting at the command-line interface

Incentivized

Dependency on the Host OS means it is as reliable as it is possible to be. Application errors are beyond the purview of the application.

Incentivized

No issues, especially with the extensions addons.

Incentivized

Oracle have a very fast response rate and a strong user community. One can geet help from many sources if they choose to research for themselves.

Incentivized

We really enjoy using virtual box. We do not require to buy expensive hardware but instead we can minimize costs and maximize profits.

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

VirutalBox is very similar to using Vmware with the slight difference in appearance and what might be considered a less polished look. However, what it lacks in polish and looks it makes up for in functionality, easy of use and the wide range of operating systems and features it supports without the need of buying the full professional edition

Incentivized

The only problem I have found is that the deployment is dependent and intrinsically linked to the Host OS. This is different from bare metal solutions which remove that dependency on a Host OS. The latter is more reliable and removes a layer of potential failure.

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

• Minimal-to-no support needed from the DevOps team.
• Provides a direct and an easy way to access multiple VMs inside the same machines which enables performing various testing and QA tasks without the need to switch hardware.
• Automatic provisioning using tools (esp. Vagrant) which enables developing a base image once, and allows for exporting/importing anywhere across the developers team.
• Very cost-effective (no fees or monthly subscriptions).

Incentivized