Load test shouldn't delete configmaps and secrets for running pods

[mborsz]

From kubernetes/kubernetes#96038 (comment)

It looks like we do delete deployment, configmap and secret at roughly the same time. This is incorrect in general, as there can be large delay between deployment deletion and pod deletion (e.g. if we make our tests even faster and the kube-controller-manager has a O(minutes) backlog of pods to be deleted).

During that delay, the running pod should be able to restart for whatever reason (e.g. kernel panic, machine failure).

We should modify our test to delete configmaps and secrets after we waited for all pods to be deleted.

[wojtek-t]

I don't think that's really a bug per-se. Yes - technically we can delete secrets/configmaps before deleting a pod, but that's supported usecase in k8s.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[wojtek-t]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[wojtek-t]

/remove-lifecycle stale
/lifecycle frozen

[jkaniuk]

/assign @mborsz