21–25 of 25 posts
You should post a link to your article in the community blog post section of the external-dns GitHub readme https://github.com/kubernetes-sigs/external-dns
Question to those that use GCP/AWS and cert-manager....why not use a managed certificates service that both now offer? I found cert-manager to be the biggest pain point in my cluster (albeit this was 18 months ago)
I've added some information on why we made the choices we did in the Discussion section. Briefly, the GCP managed certs are only available with the native GKE load balancer solution. For costs reasons, we use nginx-ingress rather than the native solution.
Earlier quoted context omitted.
> The notion that you need an 'ingress' pod AND an external load-balancer, just to be able to respond to internet traffic - and not even all internet traffic (only HTTPS) - is truly staggering. If you are on a cloud provider, the load balancer abstraction is handled for you by AWS load balancer or Google Compute load balancer so really a non-factor. I own and run a DevOps consulting company[1], and clients of course…
> so really a non-factor. As long as money is a non-factor, sure. If the idea is "just pay the cloudy tax" then I'd rather be on something like Heroku that actually makes my life easier, not harder.
Okay I get it doesn’t work for all use cases. But it is such a gold standard for simplicity.
I moved an entire company from a falling infrastructure to heroku in a month. No downtime. Multiple environments and pipelines.
Now a company is a year into Kubernetes with no end in sight. Developers can barely function
Earlier quoted context omitted.
There's a lot of stuff in this thread. I've addressed some of them briefly by adding a Discussion section to the post. I'll go into a bit more depth here. It is important to identity where the complexity is coming from. The post describes how to spin up various resources in a common IaaS provider. Does it appear complicated? Well, everything is relative. Is what is described in the post more or less complicated than…
For a contrary perspective: https://www.youtube.com/watch?v=GkmyNBUugg8 "I don't like non-essential complexity, and as far as I can tell, Kubernetes is deliberate complexity."
You should post a link to your article in the community blog post section of the external-dns GitHub readme https://github.com/kubernetes-sigs/external-dns