Deckhouse Kubernetes Platform on OpenStack

The minimal preset will be used during the installation:

  • The cluster consists of one master node and one worker node.
  • Kubernetes Control Plane and Deckhouse controller run on the master node.
  • Deckhouse deploys non-system components (Ingress Controller, Prometheus, cert-manager, etc.) on the worker node.
  • Your applications should run on the worker node.

Used layout...

Layout is the way how resources are located and communicate in the cloud. There are several pre-defined layouts, which you can learn more about in the documentation.

The Standard layout will be used during the installation.


In this scheme, an internal cluster network is created with a gateway to the public network; the nodes do not have public IP addresses. Note that the floating IP is assigned to the master node.

Caution! If the provider does not support SecurityGroups, all applications running on nodes with floating IPs assigned will be available at a public IP. For example, kube-apiserver on master nodes will be available on port 6443. To avoid this, we recommend using the SimpleWithInternalNetwork placement strategy.

The presentation contains an overview of the actions required to install Deckhouse.

Installation requirements

  1. Personal computer. The computer from which the installation will be performed. It is only needed to run the Deckhouse installer and will not be part of the cluster.


    • OS: Windows 10+, macOS 10.15+, Linux (e.g. Ubuntu 18.04+, Fedora 35+);
    • installed docker to run the installer (here are the instructions for Ubuntu, macOS, Windows);

    • HTTPS access to the container image registry;
    • access to the API of the cloud provider, an account with rights to create resources, and a configured management utility via CLI;
  2. Cloud Provider Resources.

    Minimum recommended resources...

    • 8 CPU cores
    • 16 GB of RAM
    • 100 GB of disk space