Deckhouse Platform in Microsoft Azure
Only regions where
Availability Zones are available are supported.
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.
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.
Standard layout will be used during the installation.
- A separate resorce group is created for the cluster.
- By default, one external IP address is dynamically allocated to each instance (it is used for Internet access only). Each IP has 64000 ports available for SNAT.
- The NAT Gateway (pricing) is supported. With it, you can use static public IP addresses for SNAT.
- Public IP addresses can be assigned to master nodes and nodes created by Terraform.
- If the master does not have a public IP, then an additional instance with a public IP (aka bastion host) is required for installation tasks and access to the cluster. In this case, you will also need to configure peering between the cluster’s VNet and bastion’s VNet.
- Peering can also be configured between the cluster VNet and other VNets.
The presentation contains an overview of the actions required to install Deckhouse.
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+);
- HTTPS access to the
registry.deckhouse.iocontainer image registry;
- access to the API of the cloud provider, an account with rights to create resources, and a configured Azure CLI utility;
Cloud Provider Resources.
- 8 CPU cores
- 16 GB of RAM
- 100 GB of disk space