3 ms·
Can you elaborate a bit on your architecture? I'd love to understand what your use case is. In most architectures I've seen where containers are involved, the
by otterley 7y ago
Can you elaborate a bit on your architecture? I'd love to understand what your use case is.
In most architectures I've seen where containers are involved, the rendezvous point between external clients and containerized services is an external proxy (i.e., a load balancer), and the only DNS lookup required by such clients is of the proxy itself, so no DNS UDP traffic needs to be sent into the cluster. In K8S we call this proxy an "ingress."
Is the situation that you want to expose the cluster's internal DNS to the outside world to avoid having to configure ingress? Or is it something else?
- geggam 7y agoI could see an SRV record style of load balancing being done on containers optimizing that layer by reducing a hop
- mark242 7y agoContainers that require custom DNS queries about incoming connections from a non-HTTP service (we're using the NLB for this), using a caching DNS server that isn't publicly accessible.