Kubernetes persistent terminating status after deleting namespace

After deleting the configuration files for Isti and Foo, namespace continues to terminating state, and no Istio-system namespace can be created at this time

namespace "Istio-system"Edited[email protected]:~/istio-0.8.0/install/kubernetes# KubectlGetnsname STATUS Agechoerodon-devops-prod Active 21ddefaultActive 30dfoo terminating 11distio-system terminating 19djack-Demo Active 29dkube- PublicActive 30dkube-system Active 30dsock-shop Active 22d

Deleting istio-system can not be deleted at this time

[Email protected]:~/istio-0.8.0/install/kubernetes# kubectl Delete ns Istio-system
Error from Server (Conflict): operation cannot being fulfilled on namespaces ' Istio-system ': The system is ensuring all Conte NT is removed from this namespace. Upon completion, this namespace would automatically is purged by the system.

It's like a dead loop.

Now look at the pod and discover that the Istio series pod that should have been deleted still appears in the system, and is in unknowed state, lost?

 [Email protected]:~/istio-0.8 . 0 /install/kubernetes# kubectl get  pod-n Istio-system NAME ready S Tatus restarts Ageistio -ingressgateway-6bc7c7c4bc-zwqmn 1 /1  Unknown 0   19 Distio -statsd-prom-bridge-6dbb7dcc7f-44gzv 1 /          1  Unknown 0   19distio -telemetry-54b5bf4847-rn9qj 2 /2  Unknown 0  19d 

[email protected]:~/istio-0.8. 0 get Pods-n fooname                       ready     STATUS    restarts   agehttpbin-68fbcdcfc7-xbf2c    2/2       Unknown   0          11d

Guess the problem might be here.

At this time with Kubetl delete-f Normal deletion does not respond, so the next use forced to delete

[Email protected]:~/istio-0.8.0/install/kubernetes# kubectl Delete pod-n istio-system istio-ingressgateway-6bc7c7c4bc-zwqmn--grace-period=0--forcewarning:immediate deletion does not wait forConfirmation that the running resource have been terminated. The resource MayContinueTo run on the cluster indefinitely.pod"istio-ingressgateway-6bc7c7c4bc-zwqmn"Deleted[email protected]:~/istio-0.8.0/install/kubernetes# kubectl Delete pod-n istio-system istio-statsd-prom-bridge-6dbb7dcc7f-44gzv--grace-period=0--Force warning:immediate Deletion does not wait forConfirmation that the running resource have been terminated. The resource MayContinueTo run on the cluster indefinitely.pod"Istio-statsd-prom-bridge-6dbb7dcc7f-44gzv"Deleted[email protected]:~/istio-0.8.0/install/kubernetes# kubectl Delete pod-n istio-system istio-telemetry-54b5bf4847-rn9qj--grace-period=0--Force warning:immediate Deletion does not wait forConfirmation that the running resource have been terminated. The resource MayContinueTo run on the cluster indefinitely.pod"ISTIO-TELEMETRY-54B5BF4847-RN9QJ"Deleted[email protected]:~/istio-0.8.0/install/kubernetes# kubectl Delete pod-n foo httpbin-68fbcdcfc7-xbf2c--grace-period=0--forcewarning:immediate deletion does not wait forConfirmation that the running resource have been terminated. The resource MayContinueTo run on the cluster indefinitely.pod"httpbin-68fbcdcfc7-xbf2c"Deleted

At first, the state of terminating, waiting for a while, will find that the system is back to normal

get ns-o widename                    STATUS    agechoerodon-devops-prod   Active    21d  Default                 Active    30djack-demo               active    29dkube- Public             Active    30dkube-system             active    30dsock-shop               active    22d

Kubernetes persistent terminating status after deleting namespace