Couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

1 개요

couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

$ kubectl get no
E0321 18:39:50.786082  151293 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0321 18:39:50.794701  151293 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0321 18:39:50.796391  151293 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0321 18:39:50.797897  151293 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
NAME       STATUS   ROLES           AGE    VERSION
minikube   Ready    control-plane   141m   v1.26.1

# kubectl get pods -A | grep metrics-server                                                                                                                      
E1117 13:54:58.971445   28669 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E1117 13:54:59.945282   28669 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E1117 13:55:00.801531   28669 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E1117 13:55:01.232673   28669 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
kube-system            metrics-server-v0.5.0-585cd678d7-5kmkn                                            2/2     Running                 0                112m

$ kubectl cluster-info
E0406 10:16:14.156000    1794 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0406 10:16:14.231443    1794 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0406 10:16:14.233014    1794 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0406 10:16:14.234844    1794 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
Kubernetes control plane is running at https://hkm.int.h.net:6443
CoreDNS is running at https://hkm.int.h.net:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://hkm.int.h.net:6443/api/v1/namespaces/kube-system/services/https:metrics-server:https/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

2 같이 보기

• MissingEndpoints
• kubectl cluster-info
• metrics.k8s.io/v1beta1: the server is currently unable to handle the request
• error: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request

3 참고

• https://github.com/rancher/rke/issues/3288
• https://platform9.com/kb/kubernetes/kubectl-commands-throwing--error-metrics-server-currently-unable
• https://forums.rancher.com/t/solved-k3s-only-master-gives-the-error-couldnt-get-resource-list-for-metrics-k8s-io-v1beta1-the-server-is-currently-unable-to-handle-the-request/40416/6