aws / aws/containers-roadmap

[EKS] Fargate capacity is unavailable at this time.

Open
#2,034 4 comments 2 reactions 0 assignees View on GitHub
EKS Fargate
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

We have been running Fargate EKS for quite some months. Recently, We've been encountering with the errors "Fargate capacity is unavailable at this time.", and pods remains in the pending state. And, this is on everyday basis and very frustrating. Any idea why this is happening (other than no nodes available in that az).

The cluster is in eu-central-1 ( Frankfurt). The EKS Fargate profile is associated with one subnet (eu-central-1a). We are running like 20-40 pods in that profile. Acc. to amazon fargate quota it is capable of running 1000 tasks (max 4000 vCPUs). But with us Fargate even cannot handle this 20 pods at a time. If we would have known this issue, I'd have thought of migrating to the Fargate and Serverless.

![image](https://github.com/aws/containers-roadmap/assets/6351392/1b94b151-93b5-4bf6-9ab8-4c44dee3095e)

Contributor guide

Open the contributing guide

Research direction

No repository file, test, or entry point is mentioned. Start by reviewing the reported EKS Fargate behavior in eu-central-1a, including the pending pods, 20–40 pod workload, and stated Fargate quota. Done means establishing and documenting the cause or a supported resolution for the recurring capacity errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.