Deckhouse Kubernetes Platform in a private environment

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

Installation scheme

This guide focuses on deploying a Kubernetes cluster using Deckhouse in a private environment from which there is no direct access to the public container image registry (registry.deckhouse.io) or public deb/rpm packages repositories.

Installation in a private environment is generally similar to installation on bare metal. The only difference is in some additional settings.

Scheme of Deckhouse installation in a private environment:

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.

   Requirements...

   • 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);

   • access to a proxy registry (read more about setting them up) or to a private container image registry containing Deckhouse images;
   • SSH key access to the node, the master node of the future cluster.

2. Physical server or virtual machine for the master node.

   Requirements...

   • at least 4 CPU cores
   • at least 8 GB of RAM
   • at least 60 GB of disk space for the cluster and etcd data on a fast disk (400+ IOPS)
   • supported OS
   • Linux kernel version >= 5.7
   • Unique hostname within servers (virtual machines) of the cluster
   • one of the package managers (apt/apt-get, yum, or rpm) should be installed

   • Python should be installed

   • access to a proxy registry or to a private container image registry containing Deckhouse images;
   • when using private image storage, you must first upload images of the Deckhouse Kubernetes Platform, vulnerability scanner database, and Deckhouse modules to the private storage;
   • access to the default OS package repositories (via a proxy server or an internal package repository server);
   • SSH key access from the personal computer (section 1)
   • network access from the personal computer (section 1) via port 22322/TCP
   • container runtime packages, such as containerd or docker, should not be installed on the node

3. Physical server or virtual machine for the worker node.

   The requirements are similar to the requirements for the master node but also depend on the applications running on the nodes.