v0.21.0

What's Changed

• feat: split work based on clusters with sharding by @zachsmith1 in #128
• chore: convert prometheus config to kustomize component by @scotwells in #130
• chore: add metrics service to prometheus component by @scotwells in #131

Full Changelog: v0.20.0...v0.21.0

v0.20.0

What's Changed

• feat: add quota resource registrations and claim policies by @zachsmith1 in #129

Full Changelog: v0.19.1...v0.20.0

v0.19.1

What's Changed

• fix: respect existing hostname by @zachsmith1 in #127

Full Changelog: v0.19.0...v0.19.1

v0.19.0

What's Changed

• feat: make hostnames more human-friendly by @drewr in #121

New Contributors

• @drewr made their first contribution in #121

Full Changelog: v0.18.1...v0.19.0

v0.18.1

What's Changed

• fix: custom hostname cert issuance by @zachsmith1 in #122
• fix: move ownerRef for existing cert fixes by @zachsmith1 in #123

Full Changelog: v0.18.0...v0.18.1

v0.18.0

What's Changed

• feat: add leader election config by @zachsmith1 in #113
• feat: add config for gateway concurrent reconciles by @zachsmith1 in #119
• fix: resolve gateway annotation phantom-blocking and httpproxy reconciliation storm by @zachsmith1 in #120
• feat: shared tls secret for default https listener by @zachsmith1 in #118

Full Changelog: v0.17.0...v0.18.0

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 🎊

v0.16.0

Automatic DNS Record Management for Gateway Hostnames

Configure custom hostnames on an HTTPProxy or Gateway and DNS records are created automatically when Datum DNS manages your domain. The operator creates CNAME records pointing to the gateway's canonical hostname (or ALIAS records for apex domains).

New status fields surface DNS programming status per-hostname via status.hostnameStatuses with Verified, DNSRecordProgrammed, and Available conditions, plus an aggregate DNSRecordsProgrammed condition.

See #111 for details.

Requirements

• Domain verified via Datum DNS zone
• Feature flag enableDNSIntegration: true in operator config
• dns-operator CRDs installed

Bug Fixes

• preserve VerifiedDNSZone condition after DNSZone verification (#111)
• use non-controller ownerReference for DNSRecordSets (#111)

---

Full Changelog: v0.15.1...v0.16.0

v0.15.1

What's Changed

• fix: wait for https listener before applying envoypatchpolicy by @zachsmith1 in #112

Full Changelog: v0.15.0...v0.15.1

v0.15.0

What's Changed

• feat: Add connector EnvoyPatchPolicy for HTTPProxy backends by @zachsmith1 in #93

Full Changelog: v0.14.5...v0.15.0