porter-archive
porter-archive copied to clipboard
node Local DNS cache
Location
- [ ] Browser
- [ ] CLI
- [ ] API
- [x] Infrastructure
Requirements
In the event of severe request spikes or heavy loads on node.js, dns resolution through coredns fails/is too slow because node.js does not have a caching layer. The onus of dns cache falls on the infrastructure, and coredns does not implement this. A caching layer is necessary in each node to prevent downtimes and slowdown. Problem better detailed here: https://tech.findmypast.com/k8s-dns-lookup/
Users should have the option to use local dns cache that's deployed as a Daemonset
(esp in the case of node servers) per https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/. Ideally should be default or an option during cluster provisioning process.
Additional Details
requires slightly different config between EKS and GKE