Commit Graph

11 Commits

Author SHA1 Message Date
Davanum Srinivas
50bea1dad8 Move from k8s.gcr.io to registry.k8s.io
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
2022-05-31 10:16:53 -04:00
pacoxu
58114e293f update node local dns readme for ipv6 and 1.18 GA 2021-04-23 17:04:55 +08:00
Benjamin Elder
83c56a0373 remove hack/e2e.go 2019-11-03 19:36:59 -05:00
prameshj
328f8dfe12 Use DNS_SERVER_IP as --cluster-dns in all cases.
NodeLocalDNS addon listens on both DNS_SERVER_IP as well as LOCAL_DNS_IP. So cluster-dns flag can continue to be DNS_SERVER_IP in all cases.
Documented the various variables in the yaml.
2019-10-29 12:38:46 -07:00
Pavithra Ramesh
e1748407a5 Doc changes for nodelocaldns graduating to beta 2019-05-14 14:01:33 -07:00
Xiang Dai
36065c6dd7 delete all duplicate empty blanks
Signed-off-by: Xiang Dai <764524258@qq.com>
2019-02-23 10:28:04 +08:00
Kubernetes Prow Robot
042f9ed3af Merge pull request #74093 from blakebarnett/lower-neg-cache-ttl
Lowers the default nodelocaldns denial cache TTL
2019-02-21 17:47:16 -08:00
Ben Moss
34ac4d9ee9 Update deprecated links 2019-02-15 09:13:07 -05:00
Blake
e51c9025ac Lowers the default nodelocaldns denial cache TTL
Similar to `--no-negcache` on dnsmasq, this prevents issues which poll DNS for orchestration such as operators with StatefulSets. It can also be very confusing for users when negative caching results in a change they just made seeming to be broken until the cache expires. This assumes that 5 seconds is reasonable and will still catch repeated AAAA negative responses. We could also set the denial cache size to zero which should effectively fully disable it like dnsmasq in kube-dns but testing shows this approach seems to work well in our (albeit small) test clusters.
2019-02-13 13:23:53 -08:00
prameshj
501eba8745 Update README.md 2018-12-11 17:20:57 -08:00
Pavithra Ramesh
d73466fe55 Add README for nodelocaldns 2018-11-14 15:45:14 -08:00