Skip to content

Commit 6e3ced6

Browse files
authored
Merge pull request #78864 from ahardin-rh/node-resolver-syntax-typo
Fixing syntax typo
2 parents 1f32a47 + 29f8d90 commit 6e3ced6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/nw-controlling-dns-pod-placement.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
[id="nw-controlling-dns-pod-placement_{context}"]
77
= Controlling DNS pod placement
88

9-
The DNS Operator has two daemon sets: one for CoreDNS called `dns-default` and one for managing the `/etc/hosts` file `called node-resolver`.
9+
The DNS Operator has two daemon sets: one for CoreDNS called `dns-default` and one for managing the `/etc/hosts` file called `node-resolver`.
1010

1111
You might find a need to control which nodes have CoreDNS pods assigned and running, although this is not a common operation. For example, if the cluster administrator has configured security policies that can prohibit communication between pairs of nodes, that would necessitate restricting the set of nodes on which the daemonset for CoreDNS runs. If DNS pods are running on some nodes in the cluster and the nodes where DNS pods are not running have network connectivity to nodes where DNS pods are running, DNS service will be available to all pods.
1212

0 commit comments

Comments
 (0)