This was resolved by creating a fargate profile in EKS Cluster under the namespace telemetry with label app=jaeger.
So if you want to run a pod in fragate then you need to create a fargate profile and mention the same key value pair label which you mentioned in your deployment.
Below lines from AWS documentation link https://docs.aws.amazon.com/eks/latest/userguide/fargate.html#fargate-considerations
Pods must match a Fargate profile at the time that they're scheduled to run on Fargate. Pods that don't match a Fargate profile might be stuck as Pending. If a matching Fargate profile exists, you can delete pending Pods that you have created to reschedule them onto Fargate.
Check the resource utilization on your nodes. It's possible that the nodes are running out of resources such as CPU or memory. Use tools like
kubectl top nodes to view resource usage.
How did you configure your Fargate Profile ? seems your deployment is not targeting Fargate but Your EC2 nodes which are out of capacity.
You can look at this section of eksworkshop that explain how enabling and targeting Fargate to schedule EKS Pods : https://www.eksworkshop.com/docs/fundamentals/fargate/enabling
https://repost.aws/knowledge-center/eks-resolve-pending-fargate-pods Probably one of this would help you.
- asked 9 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 7 days ago
- Why is my Amazon EKS pod stuck in the ContainerCreating state with the error "failed to create pod sandbox"?AWS OFFICIALUpdated 17 days ago
- EXPERTpublished 6 months ago
- EXPERTpublished 2 months ago