Merged
Conversation
becb885 to
f41995e
Compare
f41995e to
ebf8aed
Compare
|
|
|
|
d1aef3b to
ab4bc8e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.5.1→v0.6.0v0.18.0→v0.21.0v0.14.4→v0.19.1This PR updates the operator versions used for API documentation generation.
API reference documentation will be automatically regenerated by the GitHub Actions workflow.
Release Notes
datum-cloud/dns-operator (datum-cloud/dns-operator)
v0.6.0: - Activity TimelineCompare Source
This release introduces activity timelines for DNS zones and records — giving you clear, real-time visibility into what's happening with your DNS configurations.
Instead of digging through logs or status conditions to figure out if a DNS change actually went live, you can now see a friendly timeline of events: when a zone was created, when records became active, and — importantly — when something went wrong and why. Whether you're rolling out new records, debugging a failed update, or just keeping tabs on who changed what, the activity timeline has you covered.
What's Changed
New Contributors
Full Changelog: datum-cloud/dns-operator@v0.5.2...v0.6.0
v0.5.2Compare Source
What's Changed
Full Changelog: datum-cloud/dns-operator@v0.5.1...v0.5.2
datum-cloud/milo (datum-cloud/milo)
v0.21.0Compare Source
What's Changed
New Contributors
Full Changelog: datum-cloud/milo@v0.20.0...v0.21.0
v0.20.0Compare Source
What's Changed
Full Changelog: datum-cloud/milo@v0.19.1...v0.20.0
v0.19.1Compare Source
What's Changed
Full Changelog: datum-cloud/milo@v0.19.0...v0.19.1
v0.19.0Compare Source
What's Changed
Full Changelog: datum-cloud/milo@v0.18.0...v0.19.0
datum-cloud/network-services-operator (datum-cloud/network-services-operator)
v0.19.1Compare Source
What's Changed
Full Changelog: datum-cloud/network-services-operator@v0.19.0...v0.19.1
v0.19.0Compare Source
What's Changed
New Contributors
Full Changelog: datum-cloud/network-services-operator@v0.18.1...v0.19.0
v0.18.1Compare Source
What's Changed
Full Changelog: datum-cloud/network-services-operator@v0.18.0...v0.18.1
v0.18.0Compare Source
What's Changed
Full Changelog: datum-cloud/network-services-operator@v0.17.0...v0.18.0
v0.17.0Compare Source
🎉 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
CertificatesReadycondition that tells you the state of all your HTTPS hostnames at a glance. You'll also see per-hostnameCertificateReadyconditions 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.🔍 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
DNSAuthorityMissingwill 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.0Compare Source
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.hostnameStatuseswithVerified,DNSRecordProgrammed, andAvailableconditions, plus an aggregateDNSRecordsProgrammedcondition.See #111 for details.
Requirements
enableDNSIntegration: truein operator configBug Fixes
Full Changelog: datum-cloud/network-services-operator@v0.15.1...v0.16.0
v0.15.1Compare Source
What's Changed
Full Changelog: datum-cloud/network-services-operator@v0.15.0...v0.15.1
v0.15.0Compare Source
What's Changed
Full Changelog: datum-cloud/network-services-operator@v0.14.5...v0.15.0
v0.14.5Compare Source
What's Changed
Full Changelog: datum-cloud/network-services-operator@v0.14.4...v0.14.5
Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.