Force Deleting Kube Namespaces
18 May 2024 |
3 minutes to read
Sometimes there are finalizers blocking the deletion of a namespace through kubectl or k9s.
To force the deletion, we can update the resource through the kube api server directly.
kubectl proxy --help
```sh
kubectl proxy --help
Creates a proxy server or application-level gateway between localhost and the Kubernetes API server.
It also allows serving static content over specified HTTP path. All incoming data enters through one
port and gets forwarded to the remote Kubernetes API server port, except for the path matching the
static content path.
Examples:
# To proxy all of the Kubernetes API and nothing else
kubectl proxy --api-prefix=/
# To proxy only part of the Kubernetes API and also some static files
# You can get pods info with 'curl localhost:8001/api/v1/pods'
kubectl proxy --www=/my/files --www-prefix=/static/ --api-prefix=/api/
# To proxy the entire Kubernetes API at a different root
# You can get pods info with 'curl localhost:8001/custom/api/v1/pods'
kubectl proxy --api-prefix=/custom/
# Run a proxy to the Kubernetes API server on port 8011, serving static content from ./local/www/
kubectl proxy --port=8011 --www=./local/www/
# Run a proxy to the Kubernetes API server on an arbitrary local port
# The chosen port for the server will be output to stdout
kubectl proxy --port=0
# Run a proxy to the Kubernetes API server, changing the API prefix to k8s-api
# This makes e.g. the pods API available at localhost:8001/k8s-api/v1/pods/
kubectl proxy --api-prefix=/k8s-api
Options:
--accept-hosts='^localhost$,^127\.0\.0\.1$,^\[::1\]$':
Regular expression for hosts that the proxy should accept.
--accept-paths='^.*':
Regular expression for paths that the proxy should accept.
--address='127.0.0.1':
The IP address on which to serve on.
--api-prefix='/':
Prefix to serve the proxied API under.
--append-server-path=false:
If true, enables automatic path appending of the kube context server path to each request.
--disable-filter=false:
If true, disable request filtering in the proxy. This is dangerous, and can leave you
vulnerable to XSRF attacks, when used with an accessible port.
--keepalive=0s:
keepalive specifies the keep-alive period for an active network connection. Set to 0 to
disable keepalive.
-p, --port=8001:
The port on which to run the proxy. Set to 0 to pick a random port.
--reject-methods='^$':
Regular expression for HTTP methods that the proxy should reject (example
--reject-methods='POST,PUT,PATCH').
--reject-paths='^/api/.*/pods/.*/exec,^/api/.*/pods/.*/attach':
Regular expression for paths that the proxy should reject. Paths specified here will be
rejected even accepted by --accept-paths.
-u, --unix-socket='':
Unix socket on which to run the proxy.
-w, --www='':
Also serve static files from the given directory under the specified prefix.
-P, --www-prefix='/static/':
Prefix to serve static files under, if static file directory is specified.
Usage:
kubectl proxy [--port=PORT] [--www=static-dir] [--www-prefix=prefix] [--api-prefix=prefix]
[options]
Use "kubectl options" for a list of global command-line options (applies to all commands).
```
Start kubectl proxy in background:
kubectl proxy --port 8886 &
Fetch our resource, patch finalizers spec, and push to api server
NAMESPACE=NamespaceToDelete
kubectl get namespace $NAMESPACE -o json | jq '.spec = {"finalizers":[]}' > temp.json
# note the @ in front of temp.json
curl -k -H "Content-Type: application/json" -X PUT --data-binary @temp.json 127.0.0.1:8886/api/v1/namespaces/$NAMESPACE/finalize
