Deckhouse Platform in a private environment
Caution! The settings for working through a proxy server have changed in Deckhouse 1.42 (issue). The guide is for Deckhouse 1.42+.
The presentation contains an overview of the actions required to install Deckhouse.
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:
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);
- 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.
Physical server or virtual machine for the master node.
- at least 4 CPU cores
- at least 8 GB of RAM
- at least 40 GB of disk space for the cluster and etcd data
- access to a proxy registry or to a private container image registry containing Deckhouse images
- access to a proxy server for downloading deb/rpm OS packages (if necessary)
- SSH key access from the personal computer (section 1)
- container runtime packages, such as containerd or docker, should not be installed on the node