“Let’s use Kubernetes.” Now you have eight problems

Re:“Let’s use Kubernetes.” Now you have eight problems by totony on Friday March 06, 2020 @12:25AM (#22501191)

>Compare this to have a service that edits (let say an HAProxy) configuration and populates it with IP addresses.

Just edit the hosts file? If you have access to machines that run your code and can edit configuration, and also don't want the downsides of resolvers (pull-based instead of push-based updates, TTLs), DNS still seems like a better idea than some new stacks, plus you can push hosts files easily via ssh/ansible/basically any configuration management software

EDIT: The only issue I see with DNS as service discovery is that you can't specify ports. But usually software should use standard ports for their uses and that's never been a problem in my experience.

[ Parent | on HN ]

Re:“Let’s use Kubernetes.” Now you have eight problems by drybjed on Friday March 06, 2020 @02:08AM (#22501563)

You can specify ports using SRV resource records.

[ Parent | on HN ]

Re:“Let’s use Kubernetes.” Now you have eight problems by totony on Friday March 06, 2020 @04:22AM (#22502153)

You could but there's no integration for that that i know of so it'd be a bit of work to get working, which is why i didnt include it

[ Parent | on HN ]

Re:“Let’s use Kubernetes.” Now you have eight problems by imtringued on Friday March 06, 2020 @10:01AM (#22504057)

https://www.haproxy.com/documentation/aloha/9-5/traffic-mana...

[ Parent | on HN ]

Re:“Let’s use Kubernetes.” Now you have eight problems by nitrogen on Friday March 06, 2020 @05:21AM (#22502439)

It's how mdns works with Avahi/Bonjour/Zeroconf

[ Parent | on HN ]