whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add a chapter to existing blog for filling survey "CoreDNS adoption" (#9731)

Browse Source 
* - add a chapter for filling survey "CoreDNS adoption"
- fix typo.

* - address review comments
This commit is contained in:
Francois Tur
2018-08-22 15:00:42 -04:00
committed by k8s-ci-robot
parent cf8f500891
commit ab7a57815c
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/blog/_posts/2018-07-10-coredns-ga.md
+8 -1
View File
@@ -18,7 +18,14 @@ CoreDNS is a general-purpose, authoritative DNS server that provides a backwards
In this article, you will learn about the differences in the implementations of kube-dns and CoreDNS, and some of the helpful extensions offered by CoreDNS.
## Implemenation differences
## We appreciate your feedback
We are conducting a survey to evaluate the adoption of CoreDNS as the DNS for Kubernetes's cluster.
If you are currently using CoreDNS inside a Kubernetes cluster, please, [take 5 minutes to provide us some feedback by filling this survey](https://www.surveymonkey.com/r/SKZQSLK).
Thank you, we appreciate your collaboration here.
## Implementation differences
In kube-dns, several containers are used within a single pod: `kubedns`, `dnsmasq`, and `sidecar`. The `kubedns`
container watches the Kubernetes API and serves DNS records based on the [Kubernetes DNS specification](https://github.com/kubernetes/dns/blob/master/docs/specification.md), `dnsmasq` provides caching and stub domain support, and `sidecar` provides metrics and health checks.