"Couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"의 두 판 사이의 차이

 
11번째 줄: 11번째 줄:
NAME      STATUS  ROLES          AGE    VERSION
NAME      STATUS  ROLES          AGE    VERSION
minikube  Ready    control-plane  141m  v1.26.1
minikube  Ready    control-plane  141m  v1.26.1
</syntaxhighlight>
<syntaxhighlight lang='console'>
# 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
</syntaxhighlight>
</syntaxhighlight>
<syntaxhighlight lang='console'>
<syntaxhighlight lang='console'>
33번째 줄: 41번째 줄:
==참고==
==참고==
* https://github.com/rancher/rke/issues/3288
* 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
* 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


[[분류: metrics-server]]
[[분류: metrics-server]]

2024년 6월 28일 (금) 15:54 기준 최신판

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 같이 보기[ | ]

3 참고[ | ]

문서 댓글 ({{ doc_comments.length }})
{{ comment.name }} {{ comment.created | snstime }}