external-dns

On a kubernetes cluster you can run external-dns, which always runs in the cluster and watches for new Ingress records routing traffic on a certain domain. And then external-dns will go manage Route53 DNS records (also works with the goog). https://github.com/kubernetes-incubator/external-dns A similar thing happens for ssl certs from LetsEncrypt https://github.com/jetstack/cert-manager So I just `kubecctl create ingress` with a new domain and after a minute or two, the cluster has set it all the certs/dns set up for me (and in the case of CI, the pipeline will continue and run e2e tests against it). It obv took investment to learn and set it all up, but on a team I could see how it could save people time who don't want to wrange dns records and such.

I didn't say anything about K8S across regions, it's fundamentally not designed for it anyway. GKE doesn't support federation because it's not a final feature either, it was beta at best and is now being revised and renamed to "multi-cluster": https://github.com/kubernetes/community/tree/master/sig-mult... If you need to reach services between clusters, that's completely different from ingress. Ingress is about external access to cluster services. You can still use an authentication layer and expose everything through an ingress, or use internal IPs for the services/containers which are already routable in GCP's network across regions. A headless service to get the IPs and a cron job to sync these to a public DNS system will give you the same thing federation does for cross-cluster service discovery. There are also apps like ExternalDNS t