mirror of
https://github.com/notherealmarco/coredns-deployment.git
synced 2025-05-05 12:32:34 +02:00
Add k8s deployment script and README
This commit is contained in:
parent
2d63439b3e
commit
3c8dc1cbc7
3 changed files with 141 additions and 0 deletions
29
kubernetes/README.md
Normal file
29
kubernetes/README.md
Normal file
|
@ -0,0 +1,29 @@
|
|||
# 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
|
||||
spec defined for Kubernetes DNS-Based service discovery:
|
||||
|
||||
https://github.com/kubernetes/dns/blob/master/docs/specification.md
|
||||
|
||||
## deploy.sh and coredns.yaml.sed
|
||||
|
||||
`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,
|
||||
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
|
||||
servicing requests.
|
||||
|
||||
The script doesn't delete the kube-dns deployment or replication controller - you'll have to
|
||||
do that manually.
|
||||
|
||||
You should examine the manifest carefully and make sure it is correct for your particular
|
||||
cluster. Depending on how you have built your cluster and the version you are running,
|
||||
some modifications to the manifest may be needed.
|
||||
|
||||
In the best case scenario, all that's needed to replace Kube-DNS are these two commands:
|
||||
|
||||
~~~
|
||||
$ ./deploy.sh 10.3.0.0/24 | kubectl apply -f -
|
||||
$ kubectl delete --namespace=kube-system deployment kube-dns
|
||||
~~~
|
Loading…
Add table
Add a link
Reference in a new issue