Deckhouse makes it possible to run the Kubernetes cluster on any supported infrastructure and in the same manner:
- on clouds (for more info, see the section for the specific cloud provider);
- on virtual or bare metal machines (including on-premises);
- on a hybrid infrastructure.
Deckhouse facilitates non-trivial operations with control-plane and cluster nodes, such as:
- migrating between single-master and multi-master schemes;
- scaling master nodes;
- updating versions of the components.
All these tasks are based on smart and safe algorithms (the user can monitor/manage the ongoing processes).
Also, Deckhouse takes care of the certificates used when working with the control plane. It automatically issues certificates, renews them and configures the kubectl.
kube-proxy resources (DaemonSets, ConfigMaps, RBAC) by their tailor-made analogs.
A high level of integration between Deckhouse modules ensures effective monitoring and provides an acceptable level of security. For example, you can safely access the cluster’s API server from a public IP address and use an external authentication provider.
Docker images of all Deckhouse components (including
control plane) are stored in a highly available and geo-distributed Docker registry. The latter is accessible from a limited set of IP addresses (to ease access from isolated environments).