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
I am using java / junit / testcontainers with Kubedock to spin up a bunch of containers for a test.
After the test has finished, the containers are not removed immediately, but they are eventually cleaned up after an hour or so.
Is this expected behaviour?
To get around this I have added an afterAll hook that explicitly removes the pods, which works fine, but I wonder whether something is misconfigured as from the docs it sounds like pod removal should happen automatically after the test has finished.
The text was updated successfully, but these errors were encountered:
Closing this as I think I had misunderstood kubedock's role in cleaning up old pods. Kubedock does indeed reap old pods after 60 minutes if a test doesn't end gracefully. I think it's the responsibility of the user to ensure that pods are removed at the end of the test run.
I am using java / junit / testcontainers with Kubedock to spin up a bunch of containers for a test.
After the test has finished, the containers are not removed immediately, but they are eventually cleaned up after an hour or so.
Is this expected behaviour?
To get around this I have added an
afterAll
hook that explicitly removes the pods, which works fine, but I wonder whether something is misconfigured as from the docs it sounds like pod removal should happen automatically after the test has finished.The text was updated successfully, but these errors were encountered: