K
Q

Docker Kubernetes (Mac) - Autoscaler unable to find metrics

1/9/2019

I have installed a local instance of Kubernetes via Docker on my Mac.

Following the walkthrough on how to activate autoscaling on a deployment I have experienced an issue. The autoscaler can't read the metrics.

When I am running kubectl describe hpa the current cpu usage comes back as unknown / 50% with the warnings:

Warning FailedGetResourceMetric: 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 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)

I have installed the metrics-server via git clone https://github.com/kubernetes-incubator/metrics-server.gitand installed it with kubectl create -f deploy/1.8+

-- Mr.Turtle
docker
kubernetes

Similar Questions

How to get to the end of the Kubernates containers log
Kubernetes services are not accessible through nodeport
set limit CPU Horizontal Pod Autoscaling in pourcent
Put every configs in a single repo or each repo shoud have their own configs
What are the differences between k8s service 's external IP and Ingress
CouchbaseCluster resource in kubernetes disappears after a few days

3 Answers

1/9/2019

I finally got it working.. Here are the full steps I took to get things working:

  1. Have Kubernetes running within Docker

  2. Delete any previous instance of metrics-server from your Kubernetes instance with kubectl delete -n kube-system deployments.apps metrics-server

  3. Clone metrics-server with git clone https://github.com/kubernetes-incubator/metrics-server.git

  4. Edit the file deploy/1.8+/metrics-server-deployment.yaml to override the default command by adding a command section that didn't exist before. The new section will instruct metrics-server to allow for an insecure communications session (don't verify the certs involved). Do this only for Docker, and not for production deployments of metrics-server:

    containers:
- name: metrics-server
    image: k8s.gcr.io/metrics-server-amd64:v0.3.1
    command:
      - /metrics-server
      - --kubelet-insecure-tls

  5. Add metrics-server to your Kubernetes instance with kubectl create -f deploy/1.8+ (if errors with the .yaml, write this instead: kubectl apply -f deploy/1.8+)

  6. Remove and add the autoscaler to your deployment again. It should now show the current cpu usage.

-- Mr.Turtle
Source: StackOverflow
6/12/2019

For who are use Internal-IP here may work for you. Follow @Mr.Turtle above at step 4. add more one command.

  containers:
  - name: metrics-server
    image: k8s.gcr.io/metrics-server-amd64:v0.3.3
    command:
      - /metrics-server
      - --kubelet-insecure-tls
      - --kubelet-preferred-address-types=InternalIP
-- 6LYTH3
Source: StackOverflow
7/22/2019

We upgraded to AWS EKS version 1.13.7 and that's when we started having problems with HPA, It turns out on my deployment I had to specified a value for resources.requests.cpu=200m and the HPA started working for me.

-- david garcia
Source: StackOverflow