packages/coredns-deployment
1
0
Fork 0
mirror of https://github.com/notherealmarco/coredns-deployment.git synced 2025-05-05 20:42:33 +02:00
Code Issues Projects Releases Packages 1 Wiki Activity Actions

[issue/7] fix minor typos in Kubernetes README.md (#8)

Browse source 
Fixes: issue 7

Files changed:  kubernetes/README.md
This commit is contained in:
Mark Petrovic 2017-05-01 14:07:14 -07:00 • committed by John Belamaric
parent 8a21a7ac52
commit 901fba81cb
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
kubernetes/README.md
View file

@ -1,7 +1,7 @@
# kubernetes # Kubernetes
CoreDNS can run in place of the standard Kube-DNS in Kubernetes. Using the *kubernetes* CoreDNS can run in place of the standard Kube-DNS in Kubernetes. Using the *kubernetes*
middleware, CoreDNS will reading zone data from a Kubernetes cluster. It implements the middleware, CoreDNS will read zone data from a Kubernetes cluster. It implements the
spec defined for Kubernetes DNS-Based service discovery: spec defined for Kubernetes DNS-Based service discovery:
https://github.com/kubernetes/dns/blob/master/docs/specification.md https://github.com/kubernetes/dns/blob/master/docs/specification.md
@ -9,7 +9,7 @@ spec defined for Kubernetes DNS-Based service discovery:
## deploy.sh and coredns.yaml.sed ## deploy.sh and coredns.yaml.sed
`deploy.sh` is a convenience script to generate a manifest for running CoreDNS on a cluster `deploy.sh` is a convenience script to generate a manifest for running CoreDNS on a cluster
that is currently running standard kube-dns. Using the `coredns.yaml.sed` as a template, that is currently running standard kube-dns. Using the `coredns.yaml.sed` file as a template,
it creates a ConfigMap and a CoreDNS deployment, then updates the Kube-DNS service selector it creates a ConfigMap and a CoreDNS deployment, then updates the Kube-DNS service selector
to use the CoreDNS deployment. By re-using the existing service, there is no disruption in to use the CoreDNS deployment. By re-using the existing service, there is no disruption in
servicing requests. servicing requests.
@ -28,9 +28,9 @@ $ ./deploy.sh 10.3.0.0/24 | kubectl apply -f -
$ kubectl delete --namespace=kube-system deployment kube-dns $ kubectl delete --namespace=kube-system deployment kube-dns
~~~ ~~~
Kubernetes 1.6 uses Role Based Access Control (RBAC). The following example uses the 1.6 yaml tamplate to replace Kube-DNS and add the RBAC needed for coredns to access the API. Kubernetes 1.6 uses Role Based Access Control (RBAC). The following example uses the 1.6 yaml tamplate to replace Kube-DNS and add the RBAC needed for CoreDNS to access the API.
~~~ ~~~
$ ./deploy.sh 10.3.0.0/24 cluster.local coredns.1.6.yaml.sed | kubectl apply -f - $ ./deploy.sh 10.3.0.0/24 cluster.local coredns-1.6.yaml.sed | kubectl apply -f -
$ kubectl delete --namespace=kube-system deployment kube-dns $ kubectl delete --namespace=kube-system deployment kube-dns
~~~ ~~~