search

amazon-archives / k8s-cloudwatch-adapter

An implementation of Kubernetes Custom Metrics API for Amazon CloudWatch
Apache License 2.0
158 stars 98 forks source link

Does this approach work with just EKS Fargate? #73

Open sandan opened 3 years ago

sandan commented 3 years ago

I have a fargate only EKS cluster: 

$ eksctl create cluster --fargate

I deployed the metrics server since the README mentioned needing it:

$ kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.3.7/components.yaml

Then I ran the the deploy step

$ kubectl get pods --all-namespaces
NAMESPACE        NAME                                     READY   STATUS    RESTARTS   AGE
custom-metrics   k8s-cloudwatch-adapter-554dd66bc-vm4xp   0/1     Pending   0          61s
kube-system      coredns-69dfb8f894-cwrf7                 1/1     Running   0          40m
kube-system      coredns-69dfb8f894-mx6rh                 1/1     Running   0          40m
kube-system      metrics-server-7949d47784-q8d6m          1/1     Running   1          2m12s

But when I describe the deployment, I see:

Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  18s (x2 over 18s)  default-scheduler  0/3 nodes are available: 3 Too many pods.