ExternalDNS on K8s with Exoscale

Transcript

1. ExternalDNS on K8s
   How to sync Services and Ingresses with external DNS Providers
   (on Exoscale Cloud)
   

   View Slide

2. Deployment Service LB/Ingress
   When we run apps on Kubernetes, we usually do this
   .. but when do we DNS?
   

   View Slide

3. On simple setups we just use wildcards…
   like *.dev.whizus.net
   Which just points to an IP (like 1.2.3.4)
   But…
   If we use serviceType: LoadBalancer we get “random” IPs…
   

   View Slide

4. and even multiple DNS providers
   (exoscale, rcode0, cloudflare…)
   If we use different levels
   (like *.dev..., *.staging…, *.erik…, *.dimis.special… a.s.o)…
   we have to manage them…
   and if we have backup clusters
   (AZ-BCK-B…a.s.o, or federations)…
   … we have FUN J
   

   View Slide

5. Let’s talk about ExternalDNS
   Deployment Service LB/Ingress ExternalDNS
   to manage all the DNS related stuff, we simply add
   a “small” extrastep
   

   View Slide

6. DEMO on
   

   View Slide

7. Demo: https://asciinema.org/a/65PPSNwHKH8BtrLF2nwvn5D5Y
   Speakerdeck: https://speakerdeck.com/dklesev
   GitHub: https://github.com/whizus
   Exoscale: https://exoscale.com
   WhizUs: https://whizus.com
   

   View Slide

8. We’re hiring!
   

   View Slide

9. Thank You!
   

   View Slide