pddp11

6 ms·

1. 1.▲
   by pddp11 6y ago

   Done https://github.com/kubernetes-sigs/external-dns/pull/1765
2. 2.▲
   by pddp11 6y ago

   I've added some discussion/clarification of these issues in the post and addressed the issues in more detail in another comment: https://news.ycombinator.com/item?id=24224189 .
3. 3.▲
   by pddp11 6y ago

   While certain aspects of the article are GCP specific, part of the motivation of using ingress-nginx and cert-manager is to make the solution more generically applicable to _any_ Kubernetes cluster. The specific commands used to spin up the
4. 4.▲
   by pddp11 6y ago

   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 p
5. 5.▲
   by pddp11 6y 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
6. 6.▲
   by pddp11 6y ago

   I've added a Discussion section that provides information on cost and how to tear things down.