Bump bind-operator to v0.2.2 (config-hash rolling restart) (#254)

## 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>

This commit was merged in pull request #254.

This commit is contained in:

Ben Vincent

2026-07-12 22:52:19 +10:00

committed by

BenVincent

parent 69788a967c

commit 1f22ec2aa7

3 changed files with 3 additions and 3 deletions

									
										apps/base/bind-system/deployment.yaml
									
		+1
		-1
	
												View File
												
				@@ -21,7 +21,7 @@ spec:

				        runAsNonRoot: true

				      containers:

				        - name: operator

				          image: git.unkin.net/unkin/bind-operator:v0.2.1

				          image: git.unkin.net/unkin/bind-operator:v0.2.2

				          args:

				            - --metrics-bind-address=:8080

				            - --health-probe-bind-address=:8081