public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify availability of DNS provider options

Browse Source
This commit is contained in:
Sebastiaan van Steenis
2019-03-22 10:07:37 -07:00
committed by Denise Schannon
parent c824e66ea7
commit 239f446bde
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/v0.1.x/en/config-options/add-ons/dns/_index.md
+7 -1
View File
@@ -11,6 +11,8 @@ The images used for kube-dns are under the [`system_images` directive]({{< baseu
## Scheduling kube-dns
_Available as of v0.2.0_
If you only wanted ingress controllers to be deployed on specific nodes, you can set a `node_selector` for the ingress. The label in the `node_selector` would need to match the label on the nodes for the ingress controller to be deployed.
```yaml
@@ -29,6 +31,8 @@ dns:
## Disabling kube-dns
_Available as of v0.2.0_
You can disable the default DNS provider by specifying `none` to the dns `provider` directive in the cluster configuration. Be aware that this will prevent your pods from doing name resolution in your cluster.
```yaml
@@ -39,6 +43,8 @@ dns:
### Upstream nameservers
_Available as of v0.2.0_
By default, kube-dns will use the host configured nameservers (usually residing at `/etc/resolv.conf`) to resolve external queries. If you want to configure specific upstream nameservers to be used by kube-dns, you can use the `upstreamnameservers` directive.
```yaml
@@ -51,7 +57,7 @@ dns:
## CoreDNS (experimental)
<p>Experimental support for CoreDNS is available in RKE v0.2.0 and later.</p>
_Available as of v0.2.0_
If you want to use CoreDNS, you can set the `provider` directive to `coredns`. Both the `node_selector` and `upstreamnameservers` directive is also supported for CoreDNS.