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

Jump to bottom

Describe setting coredns server in nameserver resolv chain #3997

Merged
merged 1 commit into from
Jun 21, 2017
Merged

Describe setting coredns server in nameserver resolv chain #3997

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 6 additions & 3 deletions docs/tasks/federation/set-up-coredns-provider-federation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,16 +97,22 @@ coredns-provider.conf has below format:
[Global]
etcd-endpoints = http://etcd-cluster.my-namespace:2379
zones = example.com.
coredns-endpoints = <coredns-server-ip>:<port>

- `etcd-endpoints` is the endpoint to access etcd.
- `zones` is the federation domain for which CoreDNS is authoritative and is same as --dns-zone-name flag of `kubefed init`.
- `coredns-endpoints` is the endpoint to access coredns server. This is an optional parameter introduced from v1.7 onwards.

*Note: middleware.etcd.zones in CoreDNS configuration and --dns-zone-name
flag to kubefed init should match.*


## Setup CoreDNS server in nameserver resolv.conf chain

*Note: Following section applies only to versions prior to v1.7 and
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested edit (add "the", "of", and closing * to end italics):

Note: The following section applies only to versions prior to v1.7 and will be automatically taken care of if the coredns-endpoints parameter is configured in coredns-provider.conf as described in section above.

Copy link
Contributor

Choose a reason for hiding this comment

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

@chenopis addressed this in a follow up PR - #4157. Can you please merge this and the follow up?

will be automatically taken care if the `coredns-endpoints` parameter
is configured in `coredns-provider.conf` as described in section above.

Once the federation control plane is deployed and federated clusters
are joined to the federation, you need to add the CoreDNS server to the
pod's nameserver resolv.conf chain in all the federated clusters as this
Expand All @@ -118,9 +124,6 @@ achieved by adding the below line to `dnsmasq` container's arg in

Replace `example.com` above with federation domain.

*Note: Adding CoreDNS server to the pod's nameserver resolv.conf chain will be
automated in subsequent releases.*


Now the federated cluster is ready for cross-cluster service discovery!

Expand Down