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
Currently finalizers on ResourceGroup Instances use the parent ResourceGroup's UUID to build the finalizer string (only me to blame for this call). This causes issues when a ResourceGroup is deleted and recreated, as the new ResourceGroup gets a new UUID. The controller can't properly clean up instances from the previous ResourceGroup because it doesn't recognize the old finalizer string.
@a-hilaly - hi , i was looking into this , i see that "getInstanceFinalizerName()" helper function accept UID of "types.uid" , instead of it can we try using "types.Namespace" and create string as rgName + Namespace.kro.run//finalizer . Let me know do you think if this will work ? i haven't tested this yet , but let me know your thoughts on it
Description
Currently finalizers on ResourceGroup Instances use the parent ResourceGroup's UUID to build the finalizer string (only me to blame for this call). This causes issues when a ResourceGroup is deleted and recreated, as the new ResourceGroup gets a new UUID. The controller can't properly clean up instances from the previous ResourceGroup because it doesn't recognize the old finalizer string.
Example buggy behavior:
Fix: Use a deterministic string for finalizers based on the ResourceGroup name or kind instead of its UUID.
Which option describes the most your issue?
No response
The text was updated successfully, but these errors were encountered: