deleting a daemonset removes the daemonset but keeps the pods

[ghost]

Describe the bug
deleting a daemonset removes the daemonset but keeps the pods

To Reproduce
Steps to reproduce the behavior:

1. navigate to daemonset view
2. delete daemonset (ctrl-d)

Expected behavior
daemonset and pods should be removed

Versions (please complete the following information):

• OS: OSX
• K9s 0.7.1
• K8s 1.13.6

[derailed]

@devkws Thank you for the report! That's definitely surprising. K9s is not doing anything to prevent that behavior. Will need to research if feature or bug?? As my current understanding is upon ds delete all associated pods should be deleted unless cascade is set to false which is not the case here in k9s??

[ghost]

@derailed that’s my understanding as well and in fact kubectl and the GKE dashboard does just that. I’m wondering now if it was because the pods were in a crashloop. But again, kubectl and GKE removed the underlying pods. Weird.

[thllxb]

@devkws kubectl has the cascade option set to true by default when deleting. This is why when you delete a DS or RC, all the underlying pods are deleted as well. Apparently k9s doesn't have this option, or it has it hardcoded to false.
@derailed It needs to be a config item in the config file, or on the UI, to match the default behavior of kubectl. https://github.com/kubernetes/apimachinery/blob/master/pkg/apis/meta/v1/types.go#L506 should be useful.

[derailed]

@thllxb Thank you so much for your input and research! I've looked into it and agree with your assessment. I'll fix the behavior in the next drop.

[derailed]

@devkws @thllxb Fixed 0.7.6