Add a Zone File to Kubernetes CoreDNS: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
The zone file is added as a ConfigMap entry which will be [[Kubernetes_Cluster_Configuration_Concepts#As_Files|projected in CoreDNS pods as a file]]. The Corefile should be also modified to refer the new zone file with the "file" directive. | The zone file is added as a ConfigMap entry which will be [[Kubernetes_Cluster_Configuration_Concepts#As_Files|projected in CoreDNS pods as a file]], under the zone file name. The Corefile projected as part of the same ConfigMap should be also modified to refer the new zone file with the "file" directive. | ||
The CoreDNS deployment is then scaled down, the new configuration file is added as an "item" in configMap volume mount, and the deployment is then scaled up. | The CoreDNS deployment is then scaled down, the new configuration file is added as an "item" in configMap volume mount, and the deployment is then scaled up. | ||
=Procedure= | =Procedure= | ||
Revision as of 20:46, 24 October 2019
Internal
Overview
The zone file is added as a ConfigMap entry which will be projected in CoreDNS pods as a file, under the zone file name. The Corefile projected as part of the same ConfigMap should be also modified to refer the new zone file with the "file" directive.
The CoreDNS deployment is then scaled down, the new configuration file is added as an "item" in configMap volume mount, and the deployment is then scaled up.