Over at the Enterprisers Project, Kevin Casey has laid out an excellent set of five common misunderstandings about Kubernetes. For some light reading before the Americans out there go on holiday, we felt this was an excellent explanation of the existential state of Kubernetes, from a higher perspective than perhaps those of you in the trenches of hybrid cloud work may be used to. We hope this helps you communicate these concepts to the powers that be inside your organizations. To get started, we present misunderstanding number 1, followed by a link to the entire article.
Misunderstanding #1: Kubernetes is only for public cloud
Reality: Kubernetes is commonly referred to as a cloud-native technology, and for good reason. The project, which was first developed by a team at Google, currently calls the Cloud Native Computing Foundation home. (Red Hat, one of the first companies to work with Google on Kubernetes, has become the second-leading contributor to Kubernetes upstream project.)
“Kubernetes is cloud-native in the sense that it has been designed to take advantage of cloud computing architecture [and] to support scale and resilience for distributed applications,” says Raghu Kishore Vempati, principal systems engineer at Aricent.
Just remember that “cloud-native” is not wholly synonymous with “public cloud.”
“Kubernetes can run on different platforms, be it a personal laptop, VM, rack of bare-metal servers, public/private cloud environment, et cetera,” Vempati says.
Notes Red Hat technology evangelist Gordon Haff, “You can cluster together groups of hosts running Linux containers, and Kubernetes helps you easily and efficiently manage those clusters. These clusters can span hosts across public, private, and hybrid clouds.”
For the rest of the article, click here.