5a74b2cec6
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>
14 lines
393 B
YAML
14 lines
393 B
YAML
---
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
resources:
|
|
- namespace.yaml
|
|
# CRDs are pulled from the bind-operator repo at the matching tag rather than
|
|
# vendored here, so they never drift from the operator.
|
|
- https://git.unkin.net/unkin/bind-operator/raw/tag/v0.2.7/config/crd/install.yaml
|
|
- rbac.yaml
|
|
- agent-dns-rbac.yaml
|
|
- deployment.yaml
|
|
- vpa.yaml
|