unkin/argocd-apps
2
0
Fork 0
Code Issues 2 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

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

Merged
benvin merged 1 commits from benvin/bind-operator-0.2.2 into main 2026-07-12 22:52:20 +10:00
Conversation 0 Commits 1 Files Changed 3
+3 -3
unkinben commented 2026-07-12 22:49:20 +10:00
Owner
Copy Link
Copy Source

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.

## 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.
unkinben added 1 commit 2026-07-12 22:49:21 +10:00
Bump bind-operator to v0.2.2 (config-hash rolling restart)
ci/woodpecker/pr/pre-commit Pipeline was successful
Details
ci/woodpecker/pr/kubeconform Pipeline was successful
Details
2875649270 
v0.2.2 stamps a config hash on the pod template so ConfigMap / keys
changes roll the StatefulSet automatically, instead of pods holding a
stale startup snapshot until manually deleted.

- Bump the operator image and the pulled CRD bundle to v0.2.2.
- Bump the bind-tsig-api image to v0.2.2.

CRDs are unchanged from v0.2.1, so the generated schemas need no update.
benvin merged commit 1f22ec2aa7 into main 2026-07-12 22:52:20 +10:00
benvin deleted branch benvin/bind-operator-0.2.2 2026-07-12 22:52:20 +10:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
benvin (BenVincent) unkinben (Ben Vincent)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#254
Delete Branch "benvin/bind-operator-0.2.2"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?