metrics-server: unable to fetch metrics from API: the server could not find the requested resource (get pods.metrics.k8s.io)
Hello, I have installed locally with minikube the metric server and it worked like a charm!
But when I try to install it on my servers it doesn’t seem to work. It’s like my hpa doesn’t see it at all.
What I did:
1- Init My cluster
2- Use Weave as my CNI
3- Join a node
4- Install the metric server by cloning and kubectl create -f deploy/1.8+
5- Create a deployment for nginx
6- Create a hpa
I get this error with kubectl describe hpa
Warning FailedComputeMetricsReplicas 23m (x13 over 29m) horizontal-pod-autoscaler failed to get cpu utilization: unable to get metrics for resource cpu: unable to fetch metrics from API: the server could not find the requested resource (get pods.metrics.k8s.io)
Warning FailedGetResourceMetric 19m (x21 over 29m) horizontal-pod-autoscaler unable to get metrics for resource cpu: unable to fetch metrics from API: the server could not find the requested resource (get pods.metrics.k8s.io)
Warning FailedComputeMetricsReplicas 7m (x13 over 13m) horizontal-pod-autoscaler failed to get cpu utilization: unable to get metrics for resource cpu: unable to fetch metrics from API: the server could not find the requested resource (get pods.metrics.k8s.io)
Warning FailedGetResourceMetric 3m (x21 over 13m) horizontal-pod-autoscaler unable to get metrics for resource cpu: unable to fetch metrics from API: the server could not find the requested resource (get pods.metrics.k8s.io)
I am using Kubernetes 1.9.3
The Metric Server Seems to be running okay:
I0228 21:26:58.367749 1 heapster.go:72] Metrics Server version v0.2.1
I0228 21:26:58.368133 1 configs.go:61] Using Kubernetes client with master "https://10.96.0.1:443" and version
I0228 21:26:58.368155 1 configs.go:62] Using kubelet port 10255
I0228 21:26:58.369592 1 heapster.go:128] Starting with Metric Sink
I0228 21:26:58.900975 1 serving.go:308] Generated self-signed cert (apiserver.local.config/certificates/apiserver.crt, apiserver.local.config/certificates/apiserver.key)
I0228 21:26:59.394026 1 heapster.go:101] Starting Heapster API server...
[restful] 2018/02/28 21:26:59 log.go:33: [restful/swagger] listing is available at https:///swaggerapi
[restful] 2018/02/28 21:26:59 log.go:33: [restful/swagger] https:///swaggerui/ is mapped to folder /swagger-ui/
I0228 21:26:59.395431 1 serve.go:85] Serving securely on 0.0.0.0:443
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 3
- Comments: 19 (3 by maintainers)
现在解决了吗？
Your metric-server add on is disabled by default. Check it using $ minikube addons list If its disabled, you will see something like metrics-server: disabled Enable it using $minikube addons enable metrics-server
After that delete and recreate your HPA.
@cthakar you can refer to the image below for adding the flag --horizontal-pod-autoscaler-use-rest-clients=false in /etc/kubernetes/manifests/kube-controller-manager.yaml file
You can also use metric server instead of setting this flag in kube-controller-manager.yaml. The correct method is using the metrics server.
Clone the repo and run
After that delete your hpa and again autoscale it
I had the same issue. This solved my problem: https://stackoverflow.com/q/54106725/2291510
This method worked for me. I was using minikube which did not have metrics-server enabled. I enabled it, waited a few minutes for the pod to start up then re-created my HPA. It is now showing proper CPU and scaling!
I had the same issue with Minikube on macOS, using the default Docker driver. I got it to work by using @yadavkkumar’s tip. But in the case of Minikube, you just need to start it like this:
$ minikube start --extra-config=controller-manager.horizontal-pod-autoscaler-use-rest-clients=falseIf you are using kops, edit the cluster using kops edit cluster and add below line
update the cluster using kops and check the file /etc/kubernetes/manifests/kube-controller-manager.manifest from master node if it got reflected or not, then redeploy your hpa
Fixed by removing all the proxy env variable from kube-apiserver manifest