generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 237
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
How to use it?
- kwok
- kwokctl --runtime=docker (default runtime)
- kwokctl --runtime=binary
- kwokctl --runtime=nerdctl
- kwokctl --runtime=kind
What happened?
Currently we're using kwok 0.5.1, wondering if upgrading would fix this issue.
So we have a pod that is in Failed state that should have terminated via the pod-remove-finalizer stage. Its underlying node is gone (which maybe affects things). But the pod still hangs around and kwok is unable to cleanup these pods.
What did you expect to happen?
The failed pod should be cleaned up after the test finishes. But the pod still exists with a kwok finalizer.
How can we reproduce it (as minimally and precisely as possible)?
unclear how to repro.
Anything else we need to know?
No response
Kwok version
Details
$ kwok --version
# paste output here
$ kwokctl --version
# paste output hereOS version
Details
```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output hereOn Darwin:
$ uname -a
paste output here
On Windows:
C:> wmic os get Caption, Version, BuildNumber, OSArchitecture
paste output here
</details>
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.