Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pod to pod communication issue #619

Closed
evan-lin opened this issue Sep 18, 2019 · 3 comments
Closed

pod to pod communication issue #619

evan-lin opened this issue Sep 18, 2019 · 3 comments

Comments

@evan-lin
Copy link

We are building the K8S with CNI, and we are not using the EKS node AMI, it is build from centOS AMI.
After everything is setup, pod is allocated with the IP associate with the ENI, however, pod is not able to ping another pod.
Take a long time for investigation, and it turns out it is caused by FORWARD policy is DROP by default in iptables, after update it as ACCEPT, everything goes well. In EKS AMI, the policy is update to ACCEPT already.
Screen Shot 2019-09-18 at 12 52 33 PM

I think everyone try to setup the CNI without EKS AMI may meet the issue, and it is not easy for the trouble shooting, would be helpful if add issues like this to the trouble shooting documents.
https://github.com/aws/amazon-vpc-cni-k8s/blob/master/docs/troubleshooting.md

@mogren
Copy link
Contributor

mogren commented Sep 27, 2019

Related to #535 and awslabs/amazon-eks-ami#332

@jayanthvn
Copy link
Contributor

Sorry for the delay. Will update the troubleshooting guide.

@jayanthvn
Copy link
Contributor

Merged #1565

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants