You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: explicitly delete DNSRecordSets when Gateway is deleted
Owner reference-based garbage collection doesn't work for DNSRecordSets
because the dns-operator sets itself as the controller owner during
replication. Kubernetes GC only deletes resources when ALL owners are
deleted, so the Gateway's owner reference has no effect.
This adds explicit cleanup in the Gateway finalizer that deletes
DNSRecordSets matching our labels (dns.datumapis.com/source-name,
dns.datumapis.com/source-namespace) when the Gateway is being deleted.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
0 commit comments