Deckhouse Platform in existing cluster

The in-cluster documentation module will be the only module with a WEB interface that runs after completing the Deckhouse installation (unless you have enabled other modules in the Deckhouse configuration). If you do not use nip.io or similar services, you must add the appropriate DNS record to access the module’s WEB interface.

Create a DNS record to access a WEB interface of the documentation module:

  • Discover public IP address of the node where the Ingress controller is running.
  • If you have the DNS server and you can add a DNS records:
    • If your cluster DNS name template is a wildcard DNS (e.g., %s.kube.my), then add a corresponding wildcard A record containing the public IP, you've discovered previously.
    • If your cluster DNS name template is NOT a wildcard DNS (e.g., %s-kube.company.my), then add A or CNAME record containing the public IP, you've discovered previously, for the deckhouse.example.com service DNS name:
  • If you don't have a DNS server: on your PC add static entries (specify your public IP address in the PUBLIC_IPvariable) that match the deckhouse.example.com to the public IP to the /etc/hosts file for Linux (%SystemRoot%\system32\drivers\etc\hosts for Windows):

    export PUBLIC_IP="<PUBLIC_IP>"
    
    export PUBLIC_IP="<PUBLIC_IP>"

    Add an entry to the /etc/hosts file:

    sudo -E bash -c "cat <<EOF >> /etc/hosts
    $PUBLIC_IP deckhouse.example.com
    EOF
    "
    
    sudo -E bash -c "cat <<EOF >> /etc/hosts $PUBLIC_IP deckhouse.example.com EOF "