4 ms·
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
by gobengo 8y ago
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 https://github.com/kubernetes-incubator/external-dns
A similar thing happens for ssl certs from LetsEncrypt
https://github.com/jetstack/cert-manager 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.