Open steinybot opened 5 years ago
This is because of a somewhat cyclic dependency of the APIService
pointing at the in your situation already deleted prometheus-adapter. If you delete the APIService
called metrics.k8s.io/v1beta1
then this should be able to complete.
This could be solved by installing APIServices into a different namespace. I like kube-system
for this because that's not going to be deleted until the cluster is going away - but some people might not have permission for that so making it configurable is nice.
kubectl delete APIServices v1beta1.metrics.k8s.io
tks, ti work well!
What happened?
Delete the namespace after deploying kube-state-metrics gets stuck with the message:
Did you expect to see some different?
Delete should succeed.
How to reproduce it (as minimally and precisely as possible):
jsonnetfile.json
:monitoring.jsonnet
:Make sure to first disable the metrics-server:
Then the usual convert to
gojsontoyaml
andkubectl apply
...Once deployed try and delete the namespace:
It will get stuck and never finish deleting. Terminating the process and then running:
Environment
N/A
minikube
From Jsonnet library.
N/A
N/A
Anything else we need to know?: