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
When a ResourceGroup is deleted, the dynamiccontroller's informer for that RG's corresponding GVR isn't properly shutting down. After calling UnregisterGVK, the informer appears to still be running despite cleanup attempts. This could be an upstream Kubernetes client-go bug or an implementation issue in our shutdown logic.
Current behavior in dynamiccontroller.UnregisterGVK:
Calls wrapper.shutdown() to cancel context
Calls wrapper.informer.Shutdown()
Removes informer from maps/caches
Informer still appears active
Investigation steps needed:
Check if client-go's DynamicSharedInformerFactory Shutdown is working correctly
Verify our context cancellation propagation
Which option describes the most your issue?
No response
The text was updated successfully, but these errors were encountered:
Description
When a ResourceGroup is deleted, the
dynamiccontroller's
informer for that RG's corresponding GVR isn't properly shutting down. After callingUnregisterGVK
, the informer appears to still be running despite cleanup attempts. This could be an upstream Kubernetesclient-go
bug or an implementation issue in our shutdown logic.Current behavior in
dynamiccontroller.UnregisterGVK
:wrapper.shutdown()
to cancel contextwrapper.informer.Shutdown()
Investigation steps needed:
DynamicSharedInformerFactory
Shutdown is working correctlyWhich option describes the most your issue?
No response
The text was updated successfully, but these errors were encountered: