M’he trobat que en intentar eliminar un namespace s’ha quedat penjat
$ kubectl get ns
NAME STATUS AGE
default Active 2y86d
dev Active 2y82d
kube-node-lease Active 2y86d
kube-public Active 2y86d
kube-system Active 2y86d
kubernetes-dashboard Active 571d
prometheus Terminating 24d
logicmonitor Active 24d4Y2WA-D71EH-M84Z0-KV1N0-9YUJ2A vegades pot passar perquè es queden recursos pendents d’aturar o eliminar, i ho podem mirar així i després eliminar el que queda manualment. Però en aquest cas em mostrava el següent error
$ kubectl api-resources --verbs=list --namespaced -o name | xargs -n 1 kubectl get --show-kind --show-labels --ignore-not-found -n prometheus
error: unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, custom.metrics.k8s.io/v1beta2: the server is currently unable to handle the request, external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, metrics.k8s.io/v1beta1: the server is currently unable to handle the requestHe vist que es pot eliminar el “finalizer” que es el que esta impedin que un recurs s’elimini. generarem un json del namespace i editarem el fitxer
$ kubectl get ns prometheus -o json > tmp.json
$ vi tmp.json
{
"apiVersion": "v1",
"kind": "Namespace",
"metadata": {
"annotations": {
"kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"v1\",\"kind\":\"Namespace\",\"metadata\":{\"annotations\":{},\"labels\":{\"name\":\"prometheus\"},\"name\":\"prometheus\"}}\n"
},
"creationTimestamp": "2022-06-17T11:11:11Z",
"deletionTimestamp": "2022-07-08T11:13:21Z",
"labels": {
"kubernetes.io/metadata.name": "prometheus",
"name": "prometheus"
},
"name": "prometheus",
"resourceVersion": "103275125",
"uid": "04db44ff-0a69-4275-b84c-318e2417c801"
},
"spec": {
"finalizers": [
"kubernetes"
]
},
"status": {
"conditions": [
{
"lastTransitionTime": "2022-07-08T11:13:26Z",
"message": "Discovery failed for some groups, 4 failing: unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, custom.metrics.k8s.io/v1beta2: the server is currently unable to handle the request, external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, metrics.k8s.io/v1beta1: the server is currently unable to handle the request",
"reason": "DiscoveryFailed",
"status": "True",
"type": "NamespaceDeletionDiscoveryFailure"
},
{
"lastTransitionTime": "2022-07-08T11:13:29Z",
"message": "All legacy kube types successfully parsed",
"reason": "ParsedGroupVersions",
"status": "False",
"type": "NamespaceDeletionGroupVersionParsingFailure"
},
{
"lastTransitionTime": "2022-07-08T11:13:29Z",
"message": "All content successfully deleted, may be waiting on finalization",
"reason": "ContentDeleted",
"status": "False",
"type": "NamespaceDeletionContentFailure"
},
{
"lastTransitionTime": "2022-07-08T11:14:59Z",
"message": "All content successfully removed",
"reason": "ContentRemoved",
"status": "False",
"type": "NamespaceContentRemaining"
},
{
"lastTransitionTime": "2022-07-08T11:14:59Z",
"message": "All content-preserving finalizers finished",
"reason": "ContentHasNoFinalizers",
"status": "False",
"type": "NamespaceFinalizersRemaining"
}
],
"phase": "Terminating"
}
}i a continuació editem la secció finalizers perquè quedi així
"spec": {"finalizers": [] },
En una terminal apart obrirem un proxy
$ kubectl proxy
Starting to serve on 127.0.0.1:8001I en un altre terminal executem la seguent petició
$ curl -k -H "Content-Type: application/json" -X PUT --data-binary \
@tmp.json http://127.0.0.1:8001/api/v1/namespaces/prometheus/finalize
{
"kind": "Namespace",
"apiVersion": "v1",
"metadata": {
"name": "prometheus",
"spec": {},
"status": {
"phase": "Terminating",
"conditions": [
{
"type": "NamespaceDeletionDiscoveryFailure",
"status": "True",
"lastTransitionTime": "2020-07-19T12:53:50Z",
"reason": "DiscoveryFailed",
"message": "Discovery failed for some groups, 1 failing: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
},
{
"type": "NamespaceDeletionGroupVersionParsingFailure",
"status": "False",
"lastTransitionTime": "2020-07-19T12:53:54Z",
"reason": "ParsedGroupVersions",
"message": "All legacy kube types successfully parsed"
},
{
"type": "NamespaceDeletionContentFailure",
"status": "False",
"lastTransitionTime": "2020-07-19T12:53:54Z",
"reason": "ContentDeleted",
"message": "All content successfully deleted"
}
]
}
També podem executar aquest script i no ens cal obrir tanta finestra
$ python3 -c "namespace='prometheus';import atexit,subprocess,json,requests,sys;proxy_process = subprocess.Popen(['kubectl', 'proxy']);atexit.register(proxy_process.kill);p = subprocess.Popen(['kubectl', 'get', 'namespace', namespace, '-o', 'json'], stdout=subprocess.PIPE);p.wait();data = json.load(p.stdout);data['spec']['finalizers'] = [];requests.put('http://127.0.0.1:8001/api/v1/namespaces/{}/finalize'.format(namespace), json=data).raise_for_status()"
amb tot aixo el namespace ja no tindria d’apareixer
$ kubectl get ns
W0712 12:49:34.487129 108251 azure.go:92] WARNING: the azure auth plugin is deprecated in v1.22+, unavailable in v1.25+; use https://github.com/Azure/kubelogin instead.
To learn more, consult https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins
NAME STATUS AGE
default Active 2y86d
dev Active 2y82d
kube-node-lease Active 2y86d
kube-public Active 2y86d
kube-system Active 2y86d
kubernetes-dashboard Active 571d
logicmonitor Active 24d