There are six Kubernetes distributions that lead the container revolution TECHNOLOGY

Kubernetes has become the resource that project developers resort to for the orchestration of containers at scale. The open source orchestration system of Google is well considered, has good support and continues to evolve.

También es extenso, complejo y difícil de instalar y configurar. No solo eso, sino que gran parte del trabajo pesado se deja al usuario final. Por lo tanto, el mejor enfoque no es agarrar los bits e intentar hacerlo solo, sino buscar una solution de contener completa que incluya Kubernetes como un componete compatible y mantenido.

Canonical Kubernetes

Canonical, manufacturer of Ubuntu Linux, provides its own distribution of Kubernetes. One of the great selling points of Canonical Kubernetes is the operating system Ubuntu Linux amply respected, well understood and commonly implemented. Canonical affirma que su pila funciona en cualquier implementation local o en la nube, con soporte incluido para cargas de trabajo impulsadas por CPU y GPU. Los clientes que pagan pueden hacer que su cluster de Kubernetes sea administrado de forma remote por ingenieros de Canonical.

Canonical’s Kubernetes distribution is also available in a miniature version, Microk8s. Developers and newcomers to Kubernetes can install Microk8s on a portable or desktop computer and use it for testing, experimentation or even low-profile hardware production.

Canonical and Rancher Labs coproduce the Kubernetes Cloud Native Platform, which combines Canonical’s Kubernetes distribution with Rancher’s container administration platform. The idea is to use Kubernetes to administer the containers that are running in each cluster and use Rancher to administer multiple clusters of Kubernetes. Cloud Native Platform is available as of Rancher 2.0.


Para muchos de nosotros, Docker son contenderes. And since 2014, Docker has its own grouping and orchestration system, Docker Swarm, which has barely competed with Kubernetes.

Then, in October 2017, Docker announced that it would add Kubernetes, in its standard state without modification, as a standard package with Docker Community Edition and Docker Enterprise 2.0 and later editions. Docker Enterprise 3.0 added Docker Kubernetes Service, and an integration of Kubernetes that keeps the versions of Kubernetes consistent between developers’ desks and production implementations.

Keep in mind that Docker Desktop only includes the latest version of Kubernetes, so even though it is useful to start with the current edition on a local machine, it is less useful to activate local clusters that require previous versions (for example, clone reducido de algunos cluster de production).

VMware Tanzu Kubernetes Grid

VMware’s Tanzu applications platform is used to create modern cloud-native applications in Kubernetes and various infrastructures. Tanzu Kubernetes Grid (TKG) I donde figure Kubernetes.

The core of TKG is a certified distribution of Kubernetes, with integration for vSphere 8 and other current products from VMware. Todas las cargas de trabajo en contenores están destinado en executarse en TKGpero las aplicaciones que pueden usar niveles de abstraction más altos que las metáforas de Kubernetes pueden usar Tanzu Application Service PaaS (formerly Pivotal Application Service). If you need granular control over resources provided by Kubernetes, use TGK; for more generic tasks, the Tanzu application service should do the work.

Mirantis Kubernetes Engine

Previously known as Docker Enterprise UCP (Universal Control Plane), Mirantis Kubernetes Engine (MKE) is more aligned with its origins in Docker than some of the other Kubernetes distributions discussed here. Por un lado, le permite administrar contenadores Docker y Docker Swarm. This is convenient because Swarm is the container orchestration technology originally developed for Docker, and it is inherently less complex than Kubernetes.

MKE es exclusively un producto de Linux, pero no proporcia una distribución de Linux para instalar. Mirantis recommenda usar Ubuntu Server, ya sea en bare metal o en una máquina virtual.

For those who want the least possible Kubernetes experience, Mirantis also offers k0s, a distribution of Kubernetes delivered as a unique binary that can be executed in systems with only one CPU coreand GB de RAM y unos pocos gigabytes de espacio en disco.

The company also develops Lens, an open source IDE for managing Kubernetes, although you can use Lens with any distribution of Kubernetes, no solo with MKE.

Rancher Kubernetes Engine

Rancher Labs incorporated Kubernetes into its container management platform, called Rancher, with version 2.0.

Rancher also comes with its own distribution of Kubernetes, Rancher Kubernetes Engine (RKE). RKE is intended to eliminate the monotony of the process of configuring a cluster of Kubernetes and customize Kubernetes for a specific environment, without allowing these customizations to interfere in the way of fluid updates of Kubernetes. Esa es una consideration clave para un proyecto tan rápido y constantly updated.

RKE also stands out because it uses containers as part of the compilation and updating process. The only part of the Linux underlying system with which Rancher interacts is the motor of the container. Eso es todo lo que RKE necesita para configurar y executar, y para retroceder a una edición previous si las cosas salen mal.

Rancher also offers a minimal distribution of Kubernetes called K3s. Optimized for low-profile implementations, the K3s requires only 512 MB of RAM per server instance and 200 MB of disk space. Se mete en esta huella al omitir todas las funciones heredadas, de grado alfa y no esenciales, así como muchos complementos que se usan con menos frecuencia.

Red Hat OpenShift

Red Hat OpenShift, el producto PaaS de Red Hat, originally used “cartuchos” type paquete de compilación Heroku to pack applications, que luego se implementaban en contenores called gears. Then, Docker appeared and OpenShift was reformulated to use the new container image and the execution time standard. Inevitably, Red Hat also adopted Kubernetes as an orchestration technology within OpenShift.

OpenShift was created to provide abstraction and automation for all components of a PaaS. This abstraction and automation also extends to Kubernetes, which still imposes a large amount of administrative burden. OpenShift puede aliviar esa carga como parte de la mission más amplia de implementar una PaaS.

OpenShift 4, the last version, adds some improvements obtained from Red Hat Enterprise Linux CoreOS, such as the immutable infrastructure of this platform. It also allows the operators of Kubernetes and customized automation of the most profound level in all Kubernetes.


Leave a Comment

Your email address will not be published. Required fields are marked *