unkin-agent
216b1d72ac
records.yaml had grown to ten DNSRecord documents across two zones, so finding or reviewing a single record meant scanning the whole file and every change touched it. - move each record to authoritative/<zone>/<type>/<record>.yaml - add a kustomization.yaml per zone and per type directory - keep the git.unkin.net cutover record commented out, alongside a commented kustomization entry - move the DNSRecord-namespace rationale onto the authoritative kustomization - delete records.yaml Rendered output is unchanged. Reviewed-on: #501 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>
16 lines
491 B
YAML
16 lines
491 B
YAML
---
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
# Individually-managed authoritative records live under <zone>/<type>/<record>.yaml.
|
|
# DNSRecords must live in the same namespace as their BindZone (the operator
|
|
# resolves zoneRef/clusterRef/updateKeyRef within the record's namespace), so
|
|
# these sit alongside the zone in bind-internal, not in the app namespace.
|
|
resources:
|
|
- cluster.yaml
|
|
- tsigkey.yaml
|
|
- zones.yaml
|
|
- unkin-net
|
|
- ceph-unkin-net
|
|
- acls.yaml
|