FailedScheduling - 0/12 nodes are available: 12 Insufficient vpc.amazonaws.com/pod-eni.
saikumar21698 opened this issue · 2 comments
Containers:
amazon-mq-proxy:
Image: xxxxxxxxxxxx
Ports: 5673/TCP, 443/TCP
Host Ports: 0/TCP, 0/TCP
Limits:
cpu: 500m
memory: 40Mi
vpc.amazonaws.com/pod-eni: 1
Requests:
cpu: 5m
memory: 20Mi
vpc.amazonaws.com/pod-eni: 1
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5jz9r (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
kube-api-access-5jz9r:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
vpc.amazonaws.com/pod-eni:NoSchedule op=Exists
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal NotTriggerScaleUp 2m6s (x61 over 12m) cluster-autoscaler pod didn't trigger scale-up: 12 Insufficient vpc.amazonaws.com/pod-eni
Warning FailedScheduling 23s (x13 over 12m) default-scheduler 0/12 nodes are available: 12 Insufficient vpc.amazonaws.com/pod-eni.
Please help me with the fix
@saikumar21698 you are going to need to provide much more information to get help with something like. I cannot see the link to the Amazon VPC CNI, so I am going to close this and suggest that you open an EKS support ticket from your AWS console.
⚠️ COMMENT VISIBILITY WARNING⚠️
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.