Kubernetes namespace is undeletable after 3rd party resources are created

[istio]

Kubernetes namespace is undeletable after 3rd party resources are created

[GregHanson]

@kyessenov I see they have closed that issue and if I read it right, the suggested workaround is to delete all the resources before deleting the namespace. Though apparently this solution is "not a silver bullet . . . use at your own discretion"

[kyessenov]

My understanding is that TPRs are shared across namespaces. So we cannot delete TPRs per namespace. The only workaround is to go under kube API and manipulate them directly in etcd.

[kyessenov]

Quick clarification - I mean TPR declarations, not TPRs themselves.

[GregHanson]

@zcahana @elevran: I think one or both of you have some experience working with third party resources in Kubernetes. Any thoughts on this issue?

[ayj]

This seems to be fixed in 1.5.2.

$ kubectl create namespace mynamespace
namespace "mynamespace" created

$ kubectl create -f resource.yaml
thirdpartyresource "cron-tab.stable.example.com" created

$ kubectl delete namespace mynamespace
namespace "mynamespace" deleted

$ kubectl get namespace
NAME          STATUS        AGE
default       Active        3m
kube-system   Active        3m
mynamespace   Terminating   31s           # <=== 1.5.1 gets stuck here

[15:26:00] jasonyoung@ayj0:~
$ kubectl get namespace
NAME          STATUS    AGE
default       Active    3m
kube-system   Active    3m

[kyessenov]

Thanks for the heads up!