<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>multicluster on CoreDNS: DNS and Service Discovery</title><link>https://coredns.website.cncfstack.com/tags/multicluster/</link><description>Recent content in multicluster on CoreDNS: DNS and Service Discovery</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>CoreDNS - All Rights Reserved</copyright><lastBuildDate>Fri, 03 Mar 2023 03:51:43 +0000</lastBuildDate><atom:link href="https://coredns.website.cncfstack.com/tags/multicluster/index.xml" rel="self" type="application/rss+xml"/><item><title>multicluster</title><link>https://coredns.website.cncfstack.com/explugins/multicluster/</link><pubDate>Fri, 03 Mar 2023 03:51:43 +0000</pubDate><guid>https://coredns.website.cncfstack.com/explugins/multicluster/</guid><description>Description The multicluster plugin implements the Kubernetes DNS-Based Multicluster Service Discovery Specification.
Syntax multicluster [ZONES...] { kubeconfig KUBECONFIG [CONTEXT] noendpoints fallthrough [ZONES...] } kubeconfig KUBECONFIG [CONTEXT] authenticates the connection to a remote k8s cluster using a kubeconfig file. [CONTEXT] is optional, if not set, then the current context specified in kubeconfig will be used. It supports TLS, username and password, or token-based authentication. This option is ignored if connecting in-cluster (i.</description></item></channel></rss>