Deckhouse Kubernetes Platform in a private environment

1
Selecting infrastructure
2
Installation information
3
Preparing for installation
4
Installation
5
Finishing installation
6
What can I do next?

This feature is available in Standard and Enterprise Edition only.

Configure cluster

Enter a domain name template containing %s, e.g., %s.domain.my or %s-kube.domain.my. Please don't use the example.com domain name. This template is used for system apps domains within the cluster, e.g., Grafana for %s.domain.my will be available as grafana.domain.my.
This tutorial assumes the use of a public domain pointing to a public cluster address. It is necessary to obtain Let's Encrypt certificates for Deckhouse services. If the existing certificates (including self-signed ones) are used, you need to adjust the modules.https section in the global settings.
We recommend using the sslip.io service (or similar) for testing if wildcard DNS records are unavailable to you for some reason.
Proxy address should match http://proxy.company.my or http[s]://[[USER][:PASSWORD]@]proxy.company.my[:PORT]. Please don't use the proxy.company.my domain name. Leave it blank if you don't use the HTTP proxy server.
Proxy address should match http://proxy.company.my or http[s]://[[USER][:PASSWORD]@]proxy.company.my[:PORT]. Please don't use the proxy.company.my domain name. Leave it blank if you don't use the HTTP proxy server.
The addresses must match the templates 127.0.0.1, 192.168.0.0/24, example.com and ".example.com". Please don't use the example.com domain name. Specify a list of IP addresses, networks, and domain names that can be accessed directly without using a proxy server. Also specify here the subnet of the cluster nodes if the cluster is supposed to have pods interacting with services located in the node network. For wildcard domains, use a domain name with a dot prefix, e.g., ".example.com". Leave it blank if there are no such exceptions.

Parameters for accessing the container image registry (or proxy registry)

Do not use the registry administrator account to access the registry from Deckhouse Kubernetes Platform. Create a separate account for Deckhouse Kubernetes Platform with read-only permissions and only within the required repository in the registry. Refer to an example of creating such an account.

For more information about configuring a third-party container registry, see the installation documentation.

Note that Deckhouse container images must be available at the specified address and path.
It is a string from the Docker client configuration file (in Linux it is usually $HOME/.docker/config.json), Base64-encoded.
Read more about the parameter in the InitConfiguration documentation. If using anonymous access to the container registry, do not fill in this field.
Enable it if the container image registry works over HTTP rather than HTTPS.
Leave it blank, if the container image registry uses an SSL certificate issued by a public CA.
Go back Next: Installation