Disco doesn't update/delete records when k8s resources are updated/removed
kayrus opened this issue · 3 comments
If a k8s resource with a disco label is removed or updated, the DNS record is kept untouched.
That's the expected behavior as described in the readme
Description covers only deletion (and I doubt that this limitation statement is a reason to close an issue). What about the update? If resource's disco zone/cname/record is updated, disco won't update it.
I closed the issue since I don't see one here.
If the DISCO created the recordset, updates and deletions are done during reconciliation on change of the k8s resource and periodically.
As stated in the readme, there are limitations to the DISCO such as not managing DNS zones as they are done manually in our case, and not all records are deleted if the creator is in question e.g. records created by the disco are cleaned up, records created manually then taken over by disco (ingress/svc/.. created later) are not deleted as they are identified via record description, etc.
Though it would be technically possible to implement these, it's currently out of scope.