4 ms·
thanks for the details, and sorry for the perhaps distracting question: how do you handle DNS for the servers on your foo.com? Did you have to provide nameserve
by marmaduke 8y ago
thanks for the details, and sorry for the perhaps distracting question: how do you handle DNS for the servers on your foo.com? Did you have to provide nameservers to your registrar so K8s manages the DNS? This is something I don't see addressed so often in k8s tutorials which usually assume minikube or GCK.
- Rotareti 8y ago> thanks for the details, and sorry for the perhaps distracting question: how do you handle DNS for the servers on your foo.com? No worries :) I use digitalocean for the nodes, storage volumes, etc. and namecheap to register the domains. At namecheap I simply use the "Custom DNS" option for each domain to apply the digitalocean nameservers. I only have to do this once for every domain. After that is done, I can use the digitalocean API, the "doctl" tool or the web-interface to handle domain records, subdomains, etc. In order to connect a domain/subdomain to a k8s cluster, I point the domain/subdomain to the master node of a cluster. In each k8s cluster I use an "ingress" (nginx) [0] to handle the incoming traffic (directing each request to the right service/pod. You can think of it as a loadbalancer that runs within your cluster). This strategy would work on other cloud providers (Azure, gcloud, etc) as well, I guess. 0: https://github.com/kubernetes/ingress-nginx https://github.com/kubernetes/ingress-nginx
- marmaduke 8y agoThat was really helpful, thanks!