Senthil Kumaran

`sudo bash /opt/cni/bin/aws-cni-support.sh` should be run from the node where you are observing the crash loop. Can you also see what the ipamd.log and plugin.log say in the same node....

> [INFO] plugin/kubernetes: pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:231: failed to list *v1.EndpointSlice: Get "https://10.96.0.1:443/apis/discovery.k8s.io/v1/endpointslices?limit=500&resourceVersion=0": dial tcp 10.96.0.1:443: i/o timeout This seems like the coredns pod go the ip-ddress, but it wasn't able to communicate...

@terryjix - This is question on setting up VPC CNI on a non EKS cluster. How did you go about with this?

Closing this due to lack of more information.

> fairly ubiquitous issue when attempting to use the amazon-vpc-cni in a non-EKS environment. We will need to reproduce this and investigate. Re-opened.

Hello @wtvamp , I can use vpc-cni on kops cluster following the instructions from https://kops.sigs.k8s.io/networking/aws-vpc/ ``` kops validate cluster --wait 10m Using cluster from kubectl context: cluster3.k8s.local Validating cluster cluster3.k8s.local...

Cluster Create Instructions for Non EKS Cluster. ``` export NAME= export KOPS_STATE_STORE= export AWS_REGION= kops create cluster \ --name=${NAME} \ --cloud=aws \ --zones=${AWS_REGION}a,${AWS_REGION}b \ --networking=amazonvpc \ --control-plane-size=t3.medium \ --node-size=t3.medium \...

Closing this as we have provided the instructions for using vpc-cni on a non eks cluster - https://github.com/aws/amazon-vpc-cni-k8s/issues/2839#issuecomment-2483686084 If there are any other specific issues, please share a step by...

I thought, it will have context of the introduction and github of the course and it will give the URL. I will keep asking specific question. I wanted the model...

The original issue here was > {"level":"error","ts":"2024-07-05T04:31:02.334Z","caller":"datastore/data_store.go:652","msg":"DataStore has no available IP/Prefix addresses"} It means, the not enough IP was available the node. - `ENABLE_PREFIX_DELEGATION=true` is a way to resolve this....