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
7dde23e6
Commit
7dde23e6
authored
8 years ago
by
Bogdan Dobrelya
Browse files
Options
Downloads
Patches
Plain Diff
Add more DNS docs
Signed-off-by:
Bogdan Dobrelya
<
bdobrelia@mirantis.com
>
parent
429b08a4
No related branches found
Branches containing commit
No related tags found
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
+32
-0
32 additions, 0 deletions
docs/dns-stack.md
with
32 additions
and
0 deletions
docs/dns-stack.md
+
32
−
0
View file @
7dde23e6
K8s DNS stack by Kargo
======================
Kargo configures a
[
Kubernetes DNS
](
http://kubernetes.io/docs/admin/dns/
)
[
cluster add-on
](
http://releases.k8s.io/master/cluster/addons/README.md
)
to serve as an authoritative DNS server for a given
``dns_domain``
and its
``svc, default.svc``
default subdomains (a total of
``ndots: 5``
max levels).
Note, additional search (sub)domains may be defined in the
``searchdomains``
var. And additional recursive DNS resolvers in the
`` upstream_dns_servers``
,
``nameservers``
vars. Intranet DNS resolvers should be specified in the first
place, followed by external resolvers, for example:
```
skip_dnsmasq: true
nameservers: [8.8.8.8]
upstream_dns_servers: [172.18.32.6]
```
or
```
skip_dnsmasq: false
upstream_dns_servers: [172.18.32.6, 172.18.32.7, 8.8.8.8, 8.8.8.4]
```
Remember the limitations (the vars are explained below):
*
the
``searchdomains``
have a limitation of a 6 names and 256 chars
length. Due to default
``svc, default.svc``
subdomains, the actual
limits are a 4 names and 239 chars respectively.
*
the
``nameservers``
have a limitation of a 3 servers, although there
is a way to mitigate that with the
``upstream_dns_servers``
,
see below. Anyway, the
``nameservers``
can take no more than a two
custom DNS servers because of one slot is reserved for a Kubernetes
cluster needs.
Here is an approximate picture of how DNS things working and
being configured by Kargo ansible playbooks:
...
...
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