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
333 B
YAML
16 lines
333 B
YAML
---
|
|
apiVersion: bind.unkin.net/v1alpha1
|
|
kind: DNSRecord
|
|
metadata:
|
|
name: s3-ceph-cname
|
|
namespace: bind-internal
|
|
spec:
|
|
zoneRef: ceph-unkin-net
|
|
name: s3
|
|
type: CNAME
|
|
ttl: 600
|
|
values:
|
|
# radosgw S3 endpoint. Points at the Consul service for now; the real
|
|
# target will be changed later.
|
|
- radosgw.service.consul.
|