JobTrackingWithFinalizers: Orphan pods might not get the finalizer cleared #108645
Labels
area/batch
kind/bug
Categorizes issue or PR as related to a bug.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
What happened?
I run into a situation where a pod didn't loose the finalizer, then it blocked the deletion of a namespace.
We do have an integration test for orphan pods
kubernetes/test/integration/job/job_test.go
Line 537 in 425ff1c
But I fear that it might not cover all cases
What did you expect to happen?
Finalizer to always be removed
How can we reproduce it (as minimally and precisely as possible)?
This is a theory, rather than a concrete set of steps:
Anything else we need to know?
No response
Kubernetes version
1.23.4
Cloud provider
OS version
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: