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 bug occurs in our custom StatusReader for Config Connector (CC) resources. When a CC resource is deleted, the status reader returns an unknown error instead of a NotFound message, resulting in an endless reconcile loop.
Expected behavior
destroy returns successful
Actual behavior
destroy seems to hang although resource is no longer present in cluster (and in GCP)
Information
Steps to reproduce the behavior
At this point kpt seems to hang. I checked via kubectl to confirm it was deleted
When I exited and retried again it seemed to exit with 0
The text was updated successfully, but these errors were encountered: