From 1e62803323eaa752aaa69ffebcacf6ac3effdcbd Mon Sep 17 00:00:00 2001 From: Chris O'Haver Date: Fri, 9 Nov 2018 09:00:04 -0500 Subject: [PATCH] Update scaling_coredns_in_k8s.md --- content/blog/scaling_coredns_in_k8s.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/scaling_coredns_in_k8s.md b/content/blog/scaling_coredns_in_k8s.md index f7a2223..1aff224 100644 --- a/content/blog/scaling_coredns_in_k8s.md +++ b/content/blog/scaling_coredns_in_k8s.md @@ -1,4 +1,4 @@ -+++ title = "Scaling CoreDNS in Kubernetes Clusters" description = "A guide for tuning CoreDNS resources/requirements in Kubernetes clusters" tags = ["Kubernetes", "Service", "Discovery", "DNS", "Documentation", "Deployment"] date = "2018-11-06T11:12:13-00:00" author = "chris" +++ ++++ title = "Scaling CoreDNS in Kubernetes Clusters" description = "A guide for tuning CoreDNS resources/requirements in Kubernetes clusters" tags = ["Kubernetes", "Service", "Discovery", "DNS", "Documentation", "Deployment"] date = "2018-11-15T00:00:00-00:00" author = "chris" +++ I'm sharing the results of some tests I ran with CoreDNS (1.2.5) in Kubernetes (1.12) to provide some reference points for tuning CoreDNS to your cluster. In addition to testing CoreDNS in its default configuration, I tested CoreDNS with the optional *autopath* plugin enabled.