Pod stuck in terminating about knsk

[thyarles]

Hi @GregoryVds,

Thanks for reporting. Late last week we made a huge change on the script, now it try to delete the pod by kubectl force mode and, if it not work, by patching the finalizer of stuck resource. We can add more tries to avoid orphan resources.

Please, could you give us the output of kubectl get pod -n dataplane -o json?

[GregoryVds]

Hi @thyarles,

Thanks for the quick answer! Good to know, I will update to the latest version of knsk in my CI build to get the latest improvements.

When it happened I was actually running commit 257a664 of knsk, which is 3 weeks old, so I certainly doesn't have those latest improvements.

I then tried to run by hand the master version on the cluster and it didn't clean the Pod. But maybe that is just because the 257a664 version had already wiped the Namespace itself, and thus Master version couldn't track resources in that Namespace that was already gone?

Anyway, I am emailing you the JSON dump.

[thyarles]

@GregoryVds ,

Looking into your JSON I saw:

[...]
"deletionTimestamp": "2020-01-21T00:30:22Z",
[...]
"blockOwnerDeletion": true,
[...]

I think there is something blocking the deletion. What do you think?

[thyarles]

Please, take a look at https://github.com/thyarles/knsk/tree/%238-terminating-resources. Don't use the option --delete-orphans yet, it is not intensive tested.

[GregoryVds]

@thyarles Thanks for the help.

I think there is something blocking the deletion. What do you think?

=> To be honest I have no idea :-) I didn't have time to investigate much more...

I updated my CI script with the latest Master version of knsk.
I will close for now and make sure to reopen this issue in case I see the problem again.

Thanks again for knsk, that's very helpful :-)