Hacker News new | past | comments | ask | show | jobs | submit login

We wrote a similar guide a few months back at Datawire.io (https://www.datawire.io/guide/infrastructure/setting-kuberne...)

It's a little bit out of date now but we're working on an updated version that deals with managing upgrades, CI/CD for infrastructure and adding other pieces of cloud infrastructure in a way that the Kube cluster can access it seamlessly.




can you comment on why you suggest using a public route53 hosted zone? Using a public rather than a private zone always felt pretty dirty to me.


Reducing friction. At the time private zones in Kops were more of a PITA to setup and I would have had to explain a bunch more stuff in the article.

I might look at that again when I redo the guide. Also considering switching to the new Gossip based discovery mechanism so that Route 53 isn't even a requirement. I was recently setting up a cluster for a customer and they complained about having to use Route 53.


just learned about the gossip support, pretty interested in it too.




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: