Roll bind-operator to v0.2.7 (journal-aware zone seeding) (#480)

Deploy bind-operator v0.2.7. The operator seeded a fresh skeleton zone file at serial 1 over zones whose BIND journal was still on disk at a higher serial; BIND rejected the inconsistent pair (`addzone failed: out of range`) and, with a PVC per replica, the stale journal outlived restarts while every reconcile rewrote the skeleton, so it never converged. That SERVFAILed roughly 1 in 3 authoritative answers for k8s.syd1.au.unkin.net and resolvers cached the failures.

- Bumps the operator image to v0.2.7
- Bumps the CRD install pin to the v0.2.7 tag, which changes the CRDs

Expect one rolling restart of the operator Deployment as the new image lands.

Reviewed-on: #480
Co-authored-by: unkin-agent <unkin-agent@unkin.net>
Co-committed-by: unkin-agent <unkin-agent@unkin.net>
This commit was merged in pull request #480.
This commit is contained in:
2026-09-20 00:53:47 +10:00
committed by BenVincent
parent f14bcc4d2a
commit 5a74b2cec6
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -21,7 +21,7 @@ spec:
runAsNonRoot: true
containers:
- name: operator
image: artifactapi.k8s.syd1.au.unkin.net/docker-internal/bind-operator:v0.2.6
image: artifactapi.k8s.syd1.au.unkin.net/docker-internal/bind-operator:v0.2.7
args:
- --metrics-bind-address=:8080
- --health-probe-bind-address=:8081