1

When I try to install metrics server on EKS Fargate cluster, it is throwing error:

0/4 nodes are available: 4 Insufficient pods.

Following instructions from here to install metrics server: http://arun-gupta.github.io/hpa-app-metrics/

Can someone tell me why this error is throwing up?

update: when i make additional deployment, it is allocating new pods and working fine. but it is showing this error when metrics are installed by following instructions in the above link

Rajeev
  • 4,762
  • 8
  • 41
  • 63
  • The same issue to me ! Is the problem solved? – bgwan Sep 04 '20 at 11:16
  • not resolved. seems people didn't get my question clearly – Rajeev Sep 05 '20 at 02:07
  • What kind of node type are you using in your EKS cluster? m5.2xlarge as suggested in the guide? – jccampanero Sep 07 '20 at 14:15
  • i didn't configure nodes explicitly. eks fargate assigning pods config as per requested pod configuration – Rajeev Sep 07 '20 at 14:20
  • Ok Rajeev, I asked you because the node type could limit the number of pods you can launch because of the available ENIs and IPs addresses. – jccampanero Sep 07 '20 at 14:51
  • @Rajeev Then, how do you create your Fargate stuff? How do your Fargate profile looks like? Please, can you expand your question and provide more information that maybe help in understand the problem? – jccampanero Sep 07 '20 at 17:09
  • pls see this link: https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html – Rajeev Sep 08 '20 at 04:14
  • Last time I ran into this it was because of volumes. The helm chart is trying to create a disk-backed volume on the Fargate node here https://github.com/helm/charts/blob/9a737ef3d42d4cb286edb120c7a499ee8fbfa7d4/stable/metrics-server/templates/metrics-server-deployment.yaml#L71 Fargate does not support mounting the local file system. If you edit the deployment and remove the lines referencing volumes, does it work? – Sam Myers Sep 08 '20 at 22:46

1 Answers1

2

From the AWS Fargate docs here

Fargate profiles support specifying subnets from VPC secondary CIDR blocks. You may want to specify a secondary CIDR block because there are a limited number of IP addresses available in a subnet. As a result, there are a limited number of pods that can be created in the cluster. Using different subnets for pods allows you to increase the number of available IP addresses. For more information, see Adding IPv4 CIDR blocks to a VPC.

Arghya Sadhu
  • 41,002
  • 9
  • 78
  • 107
  • how to increase size of the node in fargate? i never configured nodes explicitly in the cluster – Rajeev Aug 13 '20 at 08:05
  • The same isscue to me. I think the number of IP is enough, 8K*3 – bgwan Sep 04 '20 at 11:20
  • 1
    This is not the correct answer, this could be one of the reason for the issue faced. I checked the number of available IPs and subnet has around 400 IPs available still the pods are in pending state with error - "insufficient pods" – anurag Aug 16 '21 at 14:26