Skip to content

Commit e5c28fa

Browse files
committed
Changed intro to reflect that the coredns multicluster plugin is available vs. mandatory
Signed-off-by: Nicolas Pintaux <[email protected]>
1 parent dbcd58c commit e5c28fa

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

site-src/guides/coredns.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Configuring CoreDNS with the multicluster option
22

3-
The [CoreDNS multicluster plugin](https://coredns.io/explugins/multicluster/) is necessary to be able to reference multicluster services properly. By default, [CoreDNS](https://coredns.io/) does not include this plugin and it is therefore necessary to recompile CoreDNS to build a container image enabling this functionality.
3+
There is a ready made [CoreDNS multicluster plugin](https://coredns.io/explugins/multicluster/) you can use as the DNS component against MCS API implementations using EndpointSlices. By default, [CoreDNS](https://coredns.io/) does not include this plugin and it is therefore necessary to recompile CoreDNS to build a container image enabling this functionality.
44
The following paragraphs highlight how one can re-deploy CoreDNS with the [multicluster plugin](https://coredns.io/explugins/multicluster/). To illustrate the concepts, it has been chosen to use a Kind cluster with its default configuration.
55

66
## Step 1: Deploying a Kind cluster and checking its CoreDNS configuration

0 commit comments

Comments
 (0)