Running Kubernetes on bare-metal nodes increases security, control, performance and may reduce costs. However, getting the most out of bare-metal Kubernetes requires more than simply provisioning physical servers as nodes and going from there. This blog provides tips on how to truly take advantage of bare-metal K8s. Access it here.
The seemingly binary decision between less infrastructure and more infrastructure is a false choice.
Kit Colbert | Jun 03, 2021
Kit Colbert is CTO of VMware Cloud
When you deploy Kubernetes and containers, it may seem as though you can get by without virtualization. After all, the stripped-down route, often called “bare metal” which is really Linux without virtualization appears to promise less complexity and overhead.
The issue may seem binary: Less infrastructure or more infrastructure which do you want? But that’s a false choice: It’s about whether you get better infrastructure out of the box or do it yourself.
Bare-metal Linux has the allure of engineering from a clean slate. Besides, Kubernetes and containerization already include the basic properties of virtualization. With process isolation, application packaging, and abstraction all built in, what’s there to worry about? Why