Skip to main content
Version: 1.41

Configure DNS

For optimal performance, we recommend running Deeploy Core on a dedicated domain such as example.com or a subdomain like deeploy.example.com. All Deeploy services will be associated with the base domain you choose. To do this, you will need the ability to add and edit DNS records for the domain.

After installing Deeploy Core, a new load balancer will be created in your Azure account. This load balancer routes incoming traffic to our Istio ingress controller. To view the CNAME of your load balancer, which is located under the EXTERNAL-IP column for the istio-ingressgateway service, simply run the command kubectl get svc -n istio-system.

$ kubectl get svc -n istio-system

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
cluster-local-gateway ClusterIP 10.100.225.156 <none> 80/TCP,443/TCP,31400/TCP,15011/TCP,8060/TCP,15029/TCP,15030/TCP,15031/TCP,15032/TCP 1m36s
istio-ingressgateway LoadBalancer 10.100.165.135 example.eu-central-1.elb.amazonaws.com 15020:31406/TCP,80:31380/TCP,443:31390/TCP,31400:31400/TCP,15029:30820/TCP,15030:32590/TCP,15031:32501/TCP,15032:32700/TCP,15443:31344/TCP 1m36s
istio-pilot ClusterIP 10.100.7.204 <none>

To allow users to access the Deeploy web application, you need to add specific CNAME records via your DNS provider using the external IP address mentioned above. This is necessary, especially if you're using a subdomain like deeploy.example.com.

CNAME  deeploy.example.com        example.eu-central-1.elb.amazonaws.com
CNAME api.deeploy.example.com example.eu-central-1.elb.amazonaws.com