You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2021. It is now read-only.
$ 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.
The text was updated successfully, but these errors were encountered:
sandan
changed the title
Does this approach with Fargate only
Does this approach with Fargate only pods?
Dec 21, 2020
sandan
changed the title
Does this approach with Fargate only pods?
Does this approach work with Fargate only pods?
Dec 21, 2020
sandan
changed the title
Does this approach work with Fargate only pods?
Does this approach work with just EKS Fargate?
Dec 21, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a fargate only EKS cluster:
I deployed the metrics server since the README mentioned needing it:
Then I ran the the deploy step
But when I describe the deployment, I see:
The text was updated successfully, but these errors were encountered: