Re:Kubernetes Networking: Behind the Scenes
by atombender on Wednesday October 16, 2019 @03:32PM
(#21274495)
Ah, I see. That's presumably possible because Go has its own DNS resolver, and it (net.DefaultResolver) can be overridden by libraries; no LD_PRELOAD needed.
[ Parent
| on HN ]
Re:Kubernetes Networking: Behind the Scenes
by justinsaccount on Wednesday October 16, 2019 @04:06PM
(#21274887)
it's because connect.NewService is the consul client, not something like net.DialTCP
Re:Kubernetes Networking: Behind the Scenes
by atombender on Wednesday October 16, 2019 @04:25PM
(#21275128)
Oh, they require all TCP connections to go through that. That's a bit heavy-handed — requires rewriting all client code to adapt to that pattern. The nice thing about KubeDNS is that you don't have to. Same with Istio.
Re:Kubernetes Networking: Behind the Scenes
by justinsaccount on Wednesday October 16, 2019 @05:29PM
(#21275997)
I brought up the native client because you mentioned "they should have defined a new API".
Re:Kubernetes Networking: Behind the Scenes
by atombender on Wednesday October 16, 2019 @05:33PM
(#21276036)
That wasn't me. I'd argue the opposite. Though I'd also maybe argue that SRV records is what we should have standardized on for this stuff a long time ago.
Re:Kubernetes Networking: Behind the Scenes
by peterwwillis on Wednesday October 16, 2019 @05:29PM
(#21275989)
Integrating with app code is optional. The default is to use a sidecar.