unkinben
1f22ec2aa7
## Why v0.2.2 (bind-operator #10) stamps a `bind.unkin.net/config-hash` on the pod template, so a ConfigMap or `keys.conf` change flips the hash and triggers an operator-driven rolling restart. This fixes the class of bug where config edits (ACLs, forwarders, `validate-except`, primary address, TSIG rotation) never reached running pods — they held a startup snapshot and needed manual pod deletes. ## Changes - Bump the operator image (`bind-system/deployment.yaml`) and the pulled CRD bundle URL (`bind-system/kustomization.yaml`) to `v0.2.2`. - Bump the `bind-tsig-api` image (`bind-internal/tsig-api/tsig-api.yaml`) to `v0.2.2`. CRDs are unchanged from v0.2.1 (controller-only change), so the generated kubeconform schemas need no update. ## Validation - `bind-system` renders with the v0.2.2 CRD bundle; pre-commit clean. ## Deploy note When the v0.2.2 operator first reconciles it stamps the config-hash annotation, triggering **one rolling restart per bind StatefulSet** — expected, and it also pulls in any already-pending config. From then on, config changes roll pods automatically. Reviewed-on: #254 Co-authored-by: Ben Vincent <ben@unkin.net> Co-committed-by: Ben Vincent <ben@unkin.net>
12 lines
356 B
YAML
12 lines
356 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.2/config/crd/install.yaml
|
|
- rbac.yaml
|
|
- deployment.yaml
|