|
|
@ -24,7 +24,7 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<section>
|
|
|
|
<section>
|
|
|
|
<header>Who Would This Be Useful For?</header>
|
|
|
|
<header>Who Might This Be Useful For?</header>
|
|
|
|
<section>
|
|
|
|
<section>
|
|
|
|
<header>The Lone Selfhoster</header>
|
|
|
|
<header>The Lone Selfhoster</header>
|
|
|
|
<p>
|
|
|
|
<p>
|
|
|
@ -37,12 +37,12 @@
|
|
|
|
<header>The Cloud-Native Company</header>
|
|
|
|
<header>The Cloud-Native Company</header>
|
|
|
|
<p>
|
|
|
|
<p>
|
|
|
|
While it hasn't been tested in large deployments, I think that this DNS YAML
|
|
|
|
While it hasn't been tested in large deployments, I think that this DNS YAML
|
|
|
|
could theoretically be a great addition for large bodies of people who work
|
|
|
|
could be a great addition for large bodies of people who work on applications
|
|
|
|
on applications within the same infrastructure. Traditionally, DNS records
|
|
|
|
within the same infrastructure. Traditionally, DNS records are managed by
|
|
|
|
are something that is managed by sysadmins who edit zone files by hand, or
|
|
|
|
sysadmins who edit zone files by hand, or through self-service UIs that some
|
|
|
|
through self-service UIs that some employees are allowed to acces. If one
|
|
|
|
employees are allowed to acces. If one were to, in stead, use version
|
|
|
|
were to, in stead, use version controlled DNS YAML documents in combination
|
|
|
|
controlled DNS YAML documents in combination with CI/CD, the following things
|
|
|
|
with CI/CD, the following things would be achieved:
|
|
|
|
would be achieved:
|
|
|
|
</p>
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
|
|
<ol>
|
|
|
|
<ol>
|
|
|
|