unkin-agent
7581578df1
A single records.yaml holding every DNSRecord means any record change touches a shared file, and deleting one record is a hunk edit rather than a file removal. One file per record under <zone>/<type>/<record>.yaml makes each record independently editable and removable. - move acme-apex-ns to acme-unkin-net/ns/apex.yaml and acme-ns1-a to acme-unkin-net/a/ns1.yaml - add kustomization.yaml per zone and type directory, referencing directories from the parent - carry the delegation rationale onto the zone kustomization - drop records.yaml and reference the zone directory from the app kustomization Rendered output is unchanged. Reviewed-on: #500 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>
17 lines
398 B
YAML
17 lines
398 B
YAML
---
|
|
apiVersion: bind.unkin.net/v1alpha1
|
|
kind: DNSRecord
|
|
metadata:
|
|
name: acme-ns1-a
|
|
namespace: bind-external
|
|
spec:
|
|
zoneRef: acme-unkin-net
|
|
name: ns1
|
|
type: A
|
|
ttl: 3600
|
|
values:
|
|
# Public address of this cluster's external BIND, same target as
|
|
# acme-ns1.unkin.net. Resolvers that cached the seeded ns1.acme.unkin.net
|
|
# NS name must still reach the zone.
|
|
- 103.216.191.185
|