- 最新
- 投票最多
- 评论最多
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
Actually I have very limited permission of EKS given by my organization but I can see one fargate profile and targeted the same in my Jaeger deployment.
apiVersion: apps/v1 kind: Deployment metadata: name: jaeger namespace: telemetry annotations: eks.amazonaws.com/fargate-profile: app-fargate-dev spec: replicas: 1 selector: matchLabels: app: jaeger template: metadata: labels: app: jaeger fargate: 'yes' spec: tolerations: - key: "eks.amazonaws.com/compute-type" operator: "Equal" value: "fargate" effect: "NoSchedule" containers: - name: jaeger image: jaegertracing/all-in-one:latest ports: - containerPort: 16686 resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m"
https://repost.aws/knowledge-center/eks-resolve-pending-fargate-pods Probably one of this would help you.
相关内容
- AWS 官方已更新 5 个月前
- AWS 官方已更新 8 个月前
- AWS 官方已更新 1 年前
top nodes gave below output.
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY% fargate-ip-10-98-246-134.ec2.internal 12m 0% 144Mi 7% fargate-ip-10-98-246-139.ec2.internal 13m 0% 158Mi 8% fargate-ip-10-98-246-142.ec2.internal 13m 0% 129Mi 7% fargate-ip-10-98-246-168.ec2.internal 16m 0% 131Mi 7% fargate-ip-10-98-246-178.ec2.internal 14m 0% 115Mi 6% fargate-ip-10-98-246-179.ec2.internal 14m 0% 136Mi 7% fargate-ip-10-98-246-181.ec2.internal 13m 0% 150Mi 8% fargate-ip-10-98-246-148.ec2.internal <unknown> <unknown> <unknown> <unknown>
It seems memory is there