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
This has been discussed before, and the current approach is to put it on the user to make sure all DNSRecords referencing a dns provider secret are deleted first. This isn't a great experience, especially during testing.
This ticket is to look into alternative options, if there are any, to allow the secret to remain in place while still being referenced by any existing DNSRecord.
The main issue I see is if the secret is referenced by more than one policy / record. Do we need a refernce count. IE how many records reference this secret and then if the ref count hits 0 remove the finalizer?
This has been discussed before, and the current approach is to put it on the user to make sure all DNSRecords referencing a dns provider secret are deleted first. This isn't a great experience, especially during testing.
This ticket is to look into alternative options, if there are any, to allow the secret to remain in place while still being referenced by any existing DNSRecord.
Related:
The text was updated successfully, but these errors were encountered: