Skip to content

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

Open
@mborsz

Description

@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.

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions