k9s delete behaves differently with kubectl

[dongho-jung]

I'm using k8s 1.26 on EKS.

I had a pod that have terminationGracePeriodSeconds as 60 seconds

• When I kubectl delete the pod, it turns into Terminating state for 60 seconds and gets deleted with SIGKILL signal as I expected.
• When I ctrl+d (delete) with propagation=whatever the pod, it disappears in display immediately and I can't see it with kubectl get pod anymore despite not even a minute having passed. Interestingly, If I already have kubectl logs -f or kubectl exec -it with it, I could interact with it for 60 seconds

I thought k9s delete behaves similarly with kubectl.. but it didn't. why does it so?

I checked with k9s -l debug but couldn't find any interesting yet.

[fbueno]

Doesn't it happen all the time? Is it the way to reproduce it?

Have you tried upgrading to the latest k9s version?

[dongho-jung]

I was using v0.26.3(0893f13, 2022-08-04T05:18:24Z)
and I tried again with v0.27.4(f4543e9, 2023-05-07T16:55:34Z).

now, it was shown as Terminating as I expected

thanks for reminding me of k9s version. I'll close this issue