Ensuring DNS chart integrity via Harbor‑verified Helm deployment
I updated the DNS pipeline to require that only Helm charts that have been reviewed and verified in Harbor are rendered and deployed, preventing un‑reviewed or stale packages from entering the cluster.
Integrity‑first validation gates
I modified validation-gates.md and the associated runbooks so that the static gate now renders the reviewed upstream release package after verifying its SHA‑256 against the Harbor chart catalog. The protected Helm chart publisher pulls the same package with an authenticated Harbor reader and confirms the hash before any deployment occurs. The static gate also checks the resource contract and withholds raw Helm errors, ensuring that only validated charts pass through.
Automated hash‑check test suite
I added tailnet-dns-chart-test.py which loads the contract module and asserts that a mismatched package hash or a catalog‑hash change raises a clear ValueError before rendering. The static‑check script was updated to invoke this new test instead of the deprecated retry test, and the runtime fixture now renders the chart using the contract verification step. These automated checks make it impossible for an un‑reviewed or altered chart to be rendered in CI.
Platform‑wide adoption of reviewed Helm publishing
The pattern of Harbor‑verified Helm publication, SHA‑256 hash checks, and Argo CD self‑management can be reused for any Helm‑based workload. Teams can add a static gate that validates the resource contract, require the protected publisher to confirm the reviewed package, and gate merges on the outcome of the hash‑check test suite. This ensures reproducible, auditable deployments across the homelab and any downstream projects.