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

add pod cidrs (#26)

Browse source
This commit is contained in:
Chris O'Haver 2017-11-15 16:36:12 -05:00 • committed by John Belamaric
parent 5e6be8673a
commit f40fd9b5b4
3 changed files with 9 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

8
kubernetes/README.md
View file

@ -15,21 +15,19 @@ to use the CoreDNS deployment. By re-using the existing service, there is no dis
servicing requests.
The script doesn't delete the kube-dns deployment or replication controller - you'll have to
do that manually.
do that manually, after deploying CoreDNS.
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:
In the best case scenario, all that's needed to replace Kube-DNS are these two commands (replacing the CIDRs with the service and pod CIDRs in your deployment respectively):
~~~
$ ./deploy.sh 10.3.0.0/24 | kubectl apply -f -
$ ./deploy.sh 10.3.0.0/12 172.17.0.0/16 | kubectl apply -f -
$ kubectl delete --namespace=kube-system deployment kube-dns
~~~
-Note that the CIDR's netmask needs to be a multiple of 8.
For non-RBAC deployments, you'll need to edit the resulting yaml before applying it:
1. Remove the line `serviceAccountName: coredns` from the `Deployment` section.
2. Remove the `ServiceAccount`, `ClusterRole`, and `ClusterRoleBinding` sections.