Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dns-custom-namerserver: break down the page into mutliple sections #8900

Merged
merged 4 commits into from
Jun 12, 2018
Merged

dns-custom-namerserver: break down the page into mutliple sections #8900

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5ffcf12
dns-custom-namerserver: break down the page into mutliple sections
neolit123 May 31, 2018
82b3c75
Copyedits, fix headings for customizing DNS
Bradamant3 Jun 8, 2018
17c6289
Interim fix for talking about CoreDNS
Bradamant3 Jun 12, 2018
39c799f
Fix CoreDNS details
Bradamant3 Jun 12, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,16 @@ content_template: templates/task

{{% capture overview %}}
This page explains how to configure your DNS Pod and customize the
DNS resolution process.
DNS resolution process. In Kubernetes version 1.11 and later, CoreDNS is installed
by default. See [Configuring CoreDNS](#config-coredns) and
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of:
In Kubernetes version 1.11 and later, CoreDNS is installed by default.

we need to say something in the lines of:
In Kubernetes version 1.11, CoreDNS has reached the General Availability status and is installed by default from kubeadm.

so it is GA since 1.11, but only installed by default from kubeadm.

[Using CoreDNS for Service Discovery](/docs/tasks/administer-cluster/coredns/).
{{% /capture %}}

{{% capture prerequisites %}}
* {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
* Kubernetes version 1.6 and above.
* The cluster must be configured to use the `kube-dns` addon.
* Kubernetes version 1.6 or later. To work with CoreDNS, version 1.9 or later.
* The cluster must be configured to use the `kube-dns` add-on. Note that the add-on name
is the same whether you run kube-dns or CoreDNS.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of:

The cluster must be configured to use the kube-dns add-on. Note that the add-on name is the same whether you run kube-dns or CoreDNS.

i suggest we use:

To install CoreDNS as an addon with kubeadm, have a look at kubeadm alpha phase addon.

{{% /capture %}}

{{% capture steps %}}
Expand Down Expand Up @@ -186,7 +189,7 @@ data:

{{% /capture %}}

## Configuring CoreDNS
## Configuring CoreDNS {config-coredns}

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is possible to add here a link to the page Using CoreDNS for Service Discovery ?

You can configure [CoreDNS](https://coredns.io/) as a service discovery.

Expand Down