unkinben
4cdf9cef37
Writes (RFC2136/nsupdate) must hit pod-0; the round-robin read Service would land them on a secondary. Add a dedicated write endpoint per cluster (operator v0.1.5 primaryService field). - bind-authoritative: LoadBalancer write endpoint on 198.18.200.9 - bind-externaldns: ClusterIP write endpoint (in-cluster writers) - regenerate bindcluster kubeconform schema (primaryService + externalTrafficPolicy) external-dns is NOT yet repointed at bind-externaldns-primary: it authenticates with the existing key, which the operator-generated key doesn't match until the planned Vault-sync / secret-reflection features land.