Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
Kubespray
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Model registry
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Mirror
Kubespray
Commits
dd7e1469
Commit
dd7e1469
authored
5 years ago
by
Samina Fu
Committed by
Kubernetes Prow Robot
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Fix typo of docs/dns-stack (#5307)
parent
186ec135
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/dns-stack.md
+2
-2
2 additions, 2 deletions
docs/dns-stack.md
with
2 additions
and
2 deletions
docs/dns-stack.md
+
2
−
2
View file @
dd7e1469
...
...
@@ -25,7 +25,7 @@ values lead to poor performance of DNS stack, so please choose it wisely.
Custom search domains to be added in addition to the cluster search domains (
``default.svc.{{ dns_domain }}, svc.{{ dns_domain }}``
).
Most Linux systems limit the total number of search domains to 6 and the total length of all search domains
to 256 characters. Depending on the length of
``dns_domain``
, you're limited to less th
e
n the total limit.
to 256 characters. Depending on the length of
``dns_domain``
, you're limited to less th
a
n the total limit.
Please note that
``resolvconf_mode: docker_dns``
will automatically add your systems search domains as
additional search domains. Please take this into the accounts for the limits.
...
...
@@ -97,7 +97,7 @@ used as a backup nameserver. After cluster DNS is running, all queries will be a
servers, which in turn will forward queries to the system nameserver if required.
#### host_resolvconf
This activates the classic Kubespray behavio
u
r that modifies the hosts
``/etc/resolv.conf``
file and dhclient
This activates the classic Kubespray behavior that modifies the hosts
``/etc/resolv.conf``
file and dhclient
configuration to point to the cluster dns server (either coredns or coredns_dual, depending on dns_mode).
As cluster DNS is not available on early deployment stage, this mode is split into 2 stages. In the first
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment