Understanding & Removing Terminating Namespace in Kubernetes

Understanding & Removing Terminating Namespace in Kubernetes

At IT & Automation our intention is to share knowledge and learn from community.

In this video we will look into:

A Kubernetes namespace may be stuck in the terminating state for various reasons. Some of these reasons include slow resources likes of policy may take some time.

Grace Period could come into rescue for such scenario.

In other case, it could be hanging resources for other reason.

One time finalizer update could come into rescue for such scenario.

And 3rd one most importantly; it could be api extension which is causing the real issue.

If a Kubernetes API extension is not available, the resources that are managed by the extension cannot be deleted. Failure to delete the API extension causes namespace deletion to fail.

Other cause: Residual resources exist in the namespace that you want to delete from the cluster.

0:00 Precap
0:31 Intro
0:50 Grace Period
1:25 What is Finalizer?
2:58 Update Finalizer
5:00 Missing APIService