We recommend running Deeploy Core on a dedicated domain
example.com or a subdomain
deeploy.example.com. All Deeploy services will be tied to a base domain of your choice, under which you will need the ability to add and edit DNS records.
Now that you've successfully installed Deeploy Core, a new load balancer will have spun up in your Azure account. This load balancer routes incoming traffic to our Isitio ingress controller. Run
kubectl get svc -n istio-system to view your Load Balancer's CNAME, located under the
EXTERNAL-IP column for the
$ 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> 15010/TCP,15011/TCP,8080/TCP,15014/TCP 1m36s
In order for users to access the Deeploy web application, you will need to add the following CNAME records through your DNS provider using the external IP address listed above (assuming you use a subdomain like
CNAME deeploy.example.com example.eu-central-1.elb.amazonaws.com
CNAME api.deeploy.example.com example.eu-central-1.elb.amazonaws.com
Please sign in to leave a comment.