fix(dns): recover from broken operator chart 0.0.10 #95

Merged

morten-olsen merged 1 commit from fix/HOMEIT-510-dns-operator-recovery into main

2026-11-01 21:03:10 +01:00

morten-olsen commented

2026-11-01 21:02:30 +01:00

Owner

Summary

The published DNS operator chart 0.0.10 renders /:0.0.10, leaving its new pod in InvalidImageName and the Application Degraded. Restore the previously running chart 0.0.8 and exclude only 0.0.10 from Renovate so it cannot be offered again.

-dns-operator chart: 0.0.10 → image /:0.0.10
+dns-operator chart: 0.0.8 → ghcr.io/morten-olsen/homelab-dns-operator:0.0.8

Evidence

Before: desired image /:0.0.10, new pod InvalidImageName, Deployment ProgressDeadlineExceeded, ArgoCD Synced/Degraded. Existing 0.0.8 pod is ready.
Rendering the published artifacts reproduces the malformed 0.0.10 image; 0.0.8 renders the known working image. Chart 0.0.9 also has a full image reference but is not the recovery target.
helm lint charts/core, helm template core charts/core, existing charts/core/tests/render.sh, and server dry-run of the published 0.0.8 Deployment pass.
CI must be green before merge. Main workflows validate charts and perform advisory scanning; they publish no release.

Merge danger

Door: two-way. Version rollback and exact-version exclusion, with no changes to records, namespace, credentials, RBAC or CRDs.

Blast radius: app. The previous ready operator remains available during the recovery rollout.

Rollback and verification

Roll back: retain 0.0.8 if recovery fails; reverting to 0.0.10 restores the known invalid-image failure and is not a recovery action.
Verify after rollout: Forgejo mirror without error, core at the merged revision, DNS Application Synced/Healthy at 0.0.8, Deployment 1/1 ready with the existing image digest, no invalid-image pod, retained DNSRecords and healthy DNSClass/resolution.
Reviewers: owner review; this restores a known state and does not widen security permissions or exposure.

## Summary The published DNS operator chart `0.0.10` renders `/:0.0.10`, leaving its new pod in `InvalidImageName` and the Application Degraded. Restore the previously running chart `0.0.8` and exclude only `0.0.10` from Renovate so it cannot be offered again. ```diff -dns-operator chart: 0.0.10 → image /:0.0.10 +dns-operator chart: 0.0.8 → ghcr.io/morten-olsen/homelab-dns-operator:0.0.8 ``` ## Evidence - Before: desired image `/:0.0.10`, new pod `InvalidImageName`, Deployment `ProgressDeadlineExceeded`, ArgoCD Synced/Degraded. Existing 0.0.8 pod is ready. - Rendering the published artifacts reproduces the malformed 0.0.10 image; 0.0.8 renders the known working image. Chart 0.0.9 also has a full image reference but is not the recovery target. - `helm lint charts/core`, `helm template core charts/core`, existing `charts/core/tests/render.sh`, and server dry-run of the published 0.0.8 Deployment pass. - CI must be green before merge. Main workflows validate charts and perform advisory scanning; they publish no release. ## Merge danger **Door:** two-way. Version rollback and exact-version exclusion, with no changes to records, namespace, credentials, RBAC or CRDs. **Blast radius:** app. The previous ready operator remains available during the recovery rollout. ## Rollback and verification - **Roll back:** retain 0.0.8 if recovery fails; reverting to 0.0.10 restores the known invalid-image failure and is not a recovery action. - **Verify after rollout:** Forgejo mirror without error, core at the merged revision, DNS Application Synced/Healthy at 0.0.8, Deployment 1/1 ready with the existing image digest, no invalid-image pod, retained DNSRecords and healthy DNSClass/resolution. - **Reviewers:** owner review; this restores a known state and does not widen security permissions or exposure.

morten-olsen added 1 commit

2026-11-01 21:02:30 +01:00