Deckhouse Virtualization Platform for bare metal

Make sure the Kruise controller manager is Running. Run the following command on the master node:

sudo d8 k -n d8-ingress-nginx get po -l app=kruise

Set up the Ingress controller and DNS.

1. Setting up an Ingress controller

   Copy content

   sudo d8 k apply -f - <<EOF
   # The parameters of the NGINX Ingress controller.
   # https://deckhouse.io/products/virtualization-platform/reference/cr/ingressnginxcontroller.html
   apiVersion: deckhouse.io/v1
   kind: IngressNginxController
   metadata:
     name: nginx
   spec:
     ingressClass: nginx
     # The way traffic goes to cluster from the outer network.
     inlet: HostPort
     hostPort:
       httpPort: 80
       httpsPort: 443
     # Describes on which nodes the Ingress Controller will be located.
     # You might consider changing this.
     nodeSelector:
       node-role.kubernetes.io/control-plane: ""
     tolerations:
     - effect: NoSchedule
       key: node-role.kubernetes.io/control-plane
       operator: Exists
   EOF
   

   sudo d8 k apply -f - <<EOF # The parameters of the NGINX Ingress controller. # https://deckhouse.io/products/virtualization-platform/reference/cr/ingressnginxcontroller.html apiVersion: deckhouse.io/v1 kind: IngressNginxController metadata: name: nginx spec: ingressClass: nginx # The way traffic goes to cluster from the outer network. inlet: HostPort hostPort: httpPort: 80 httpsPort: 443 # Describes on which nodes the Ingress Controller will be located. # You might consider changing this. nodeSelector: node-role.kubernetes.io/control-plane: "" tolerations: - effect: NoSchedule key: node-role.kubernetes.io/control-plane operator: Exists EOF

   It may take some time to start the Ingress controller after installing Deckhouse. Make sure the Ingress controller has started before continuing (run on the master node):

   Copy content

   sudo d8 k -n d8-ingress-nginx get po -l app=controller
   

   sudo d8 k -n d8-ingress-nginx get po -l app=controller

   Wait for the Ingress controller pods to switch to Running state.

   Example of the output...

   $ sudo -i d8 k -n d8-ingress-nginx get po -l app=controller
   NAME                                       READY   STATUS    RESTARTS   AGE
   controller-nginx-r6hxc                     3/3     Running   0          5m
   

2. Create DNS records to organize access to the cluster web-interfaces:
   • 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 records containing the public IP, you've discovered previously, for the following Deckhouse service DNS names:

       api.example.com
       argocd.example.com
       dashboard.example.com
       documentation.example.com
       dex.example.com
       grafana.example.com
       hubble.example.com
       istio.example.com
       istio-api-proxy.example.com
       kubeconfig.example.com
       openvpn-admin.example.com
       prometheus.example.com
       status.example.com
       upmeter.example.com
       

     • Important: The domain used in the template should not match the domain specified in the clusterDomain parameter and the internal service network zone. For example, if clusterDomain is set to cluster.local (the default value) and the service network zone is ru-central1.internal, then publicDomainTemplate cannot be %s.cluster.local or %s.ru-central1.internal.

   • 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 names of specific services to the public IP to the /etc/hosts file for Linux (%SystemRoot%\system32\drivers\etc\hosts for Windows):

     Copy content

     export PUBLIC_IP="<PUT_PUBLIC_IP_HERE>"
     sudo -E bash -c "cat <<EOF >> /etc/hosts
     $PUBLIC_IP api.example.com
     $PUBLIC_IP argocd.example.com
     $PUBLIC_IP dashboard.example.com
     $PUBLIC_IP documentation.example.com
     $PUBLIC_IP dex.example.com
     $PUBLIC_IP grafana.example.com
     $PUBLIC_IP hubble.example.com
     $PUBLIC_IP istio.example.com
     $PUBLIC_IP istio-api-proxy.example.com
     $PUBLIC_IP kubeconfig.example.com
     $PUBLIC_IP openvpn-admin.example.com
     $PUBLIC_IP prometheus.example.com
     $PUBLIC_IP status.example.com
     $PUBLIC_IP upmeter.example.com
     EOF
     "
     

     export PUBLIC_IP="<PUT_PUBLIC_IP_HERE>" sudo -E bash -c "cat <<EOF >> /etc/hosts $PUBLIC_IP api.example.com $PUBLIC_IP argocd.example.com $PUBLIC_IP dashboard.example.com $PUBLIC_IP documentation.example.com $PUBLIC_IP dex.example.com $PUBLIC_IP grafana.example.com $PUBLIC_IP hubble.example.com $PUBLIC_IP istio.example.com $PUBLIC_IP istio-api-proxy.example.com $PUBLIC_IP kubeconfig.example.com $PUBLIC_IP openvpn-admin.example.com $PUBLIC_IP prometheus.example.com $PUBLIC_IP status.example.com $PUBLIC_IP upmeter.example.com EOF "