Deckhouse Platform in a private environment

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 change the global settings in the modules.https section.
We recommend using the nip.io service (or similar) for testing if wildcard DNS records are unavailable to you for some reason.
Enable it if you cannot directly retrieve deb or rpm packages on your network or if a proxy server is used.
Some Deckhouse components need Internet access (more info about what data does Deckhouse send). Internet access may also be required if you configure modules to send data outside the private environment (metrics, logs, etc.). Enable it if Deckhouse modules need a proxy server in your network to access the Internet.

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

Read more about configuring a container image storage, if necessary.

Note that Deckhouse container images of the corresponding edition (CE or EE) must be available at the specified address and path.
It is a string from the Docker client configuration file (by default, the configuration file is ~/.docker/config.json), Base64-encoded.
Read more about the parameter in the documentation.
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.