v0.17.0

🎉 v0.17.0 Release Notes

Your proxies just got a whole lot chattier (in a good way!)

This release is all about visibility. We've taught your HTTPProxy resources to tell you exactly what's happening with your TLS certificates and DNS setup—no more wondering why things aren't working.

✨ Certificate Health Tracking

Ever deployed an HTTPProxy and wondered if your TLS certificate actually got issued? Wonder no more! HTTPProxy now sports a shiny new CertificatesReady condition that tells you the state of all your HTTPS hostnames at a glance. You'll also see per-hostname CertificateReady conditions with helpful messages like "We're provisioning and applying a certificate to this hostname - it may take a few minutes" instead of cryptic error codes.

kubectl get httpproxy
NAME       HOSTNAME            PROGRAMMED   CERTIFICATES   AGE
my-proxy   app.example.com     True         True           5m

🔍 Smarter DNS Authority Checks

We've made the DNS integration smarter about figuring out whether Datum DNS actually has authority over your domain. Instead of just checking if a domain was "verified via DNSZone," we now verify the full chain: domain ownership + DNSZone readiness + nameserver delegation. This means better compatibility with domains that were verified before recent fixes, and clearer error messages when something's off.

New status reasons like DNSAuthorityMissing will tell you exactly what to fix—whether it's updating your registrar's NS records or waiting for the DNSZone to become ready.

🧹 Proper DNS Cleanup

Fixed a sneaky bug where DNSRecordSets weren't being cleaned up when you deleted a Gateway. Turns out Kubernetes garbage collection wasn't doing its job here (long story involving controller owner references), so we added explicit cleanup in the Gateway finalizer. Your DNS records will now properly disappear when the Gateway does.

---

Full details: PR #115 — @mattdjenkinson's first contribution 🎊