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 we trigger a cpu/mem hog scenario, one pod is scheduled in the default namespace. After the scenario is completed, this pods keeps lying there and isn't removed.
In my view, this pod should be removed/cleaned once the scenario test is completed.
To verify, after the scenario is completed run $ oc get pods -n default
The text was updated successfully, but these errors were encountered:
When we trigger a cpu/mem hog scenario, one pod is scheduled in the default namespace. After the scenario is completed, this pods keeps lying there and isn't removed.
In my view, this pod should be removed/cleaned once the scenario test is completed.
To verify, after the scenario is completed run $ oc get pods -n default
The text was updated successfully, but these errors were encountered: