Skip to content

EKS pods are stuck on `ContainerCreating` state

0

after we deployed a new version of a pod on EKS pods are stuck on ContainerCreating state running kubectl describe pod <pod> on a problematic pod we see

Warning  FailedCreatePodSandBox  17m  kubelet            (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "container": plugin type="aws-cni" name="aws-cni" failed (add): add cmd: failed to assign an IP address to container

looking at the subnetes of the cluster we plenty of ips available

cdr of /16 to the cluster

we don use a cni-plugin

please help

1 Answer
0

Hello,

The VPC CNI add-on is necessary for creating and attaching the IPs to the EC2 nodes and then the add-on also assigns a private IPv4 or IPv6 address from your VPC to each Pod and service.

To install Amazon VPC CNI plugin refer this documentation: https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html

EXPERT
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.