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
for context, I was planning on using kuttl as a driver for end-to-end test in an operator. The operator talks to an API to create/update/delete objects according to some CRDs.
configuration i noticed that the manager gets killed after the tests have finished and before the namespace was successfully deleted. That way it is not be able to clean up any remotely created objects anymore and resources are leaking. The manager did not get a chance to delete the finalizers.
What you expected to happen:
I was expecting the test suite to attempt to wait until the temporary namespace has been deleted.
How to reproduce it (as minimally and precisely as possible):
Hey everyone,
for context, I was planning on using
kuttl
as a driver for end-to-end test in an operator. The operator talks to an API to create/update/delete objects according to some CRDs.What happened:
When running tests using the
configuration i noticed that the manager gets killed after the tests have finished and before the namespace was successfully deleted. That way it is not be able to clean up any remotely created objects anymore and resources are leaking. The manager did not get a chance to delete the finalizers.
What you expected to happen:
I was expecting the test suite to attempt to wait until the temporary namespace has been deleted.
How to reproduce it (as minimally and precisely as possible):
N/A
Environment:
kubectl version
):kubectl kuttl version
):uname -a
):The text was updated successfully, but these errors were encountered: