Openshift oc Project deletion struck in Terminating

-

You can try to delete the namespace with a curl command to Openshift API:

1. Get namespace status into json file:

oc get namespace $NS_TO_DELETE -o json > tmp_ns.json

2. Remove the line with "kubernetes" (under "finalizers"):

vi tmp_ns.json

3. Open proxy connection to your cluster (as a background process)

oc proxy &

4. Push the json content to your cluster with curl:

curl -k -H "Content-Type: application/json" -X PUT --data-binary @tmp_ns.json http://127.0.0.1:8001/api/v1/namespaces/$NS_TO_DELETE/finalize

5. your-namespace should be gone now:

oc get namespace $NS_TO_DELETE # namespaces not found

6. Switch to the background process (fg) of the Proxy and stop it (Ctrl+c), or directly with:

kill -9 %%

Note: If you have jq installed, you can run steps 1 & 2 by: oc get namespace $NS_TO_DELETE -o json | jq '.spec = {"finalizers":[]}' > tmp_ns.json

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more