Skip to content

set iptables FORWARD rules ACCEPT for inside VPC traffic#535

Closed
Komey wants to merge 2 commits intoaws:masterfrom
Komey:master
Closed

set iptables FORWARD rules ACCEPT for inside VPC traffic#535
Komey wants to merge 2 commits intoaws:masterfrom
Komey:master

Conversation

@Komey
Copy link
Copy Markdown

@Komey Komey commented Jul 21, 2019

Description of changes:
For some AMI doesn't ACCEPT FORWARD traffic by default, this will enable those traffic FORWARD in VPC CIDR

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mogren mogren self-requested a review July 24, 2019 22:21
@mogren
Copy link
Copy Markdown
Contributor

mogren commented Jul 31, 2019

Hi @Komey,

Could you explain the use case for this? It seems like a configuration that should belong in the AMI and not the CNI?

@Komey
Copy link
Copy Markdown
Author

Komey commented Aug 2, 2019

Hi @Komey,

Could you explain the use case for this? It seems like a configuration that should belong in the AMI and not the CNI?

Hi @mogren

I was testing a self-hosted k8s cluster with AMI --> ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20190212.1 (ami-0c55b159cbfafe1f0) , which is not accept forward traffic in any cidr.
In my opinion, It will be better that CNI take care of the traffic which has been configured within the VPC cird

@mogren
Copy link
Copy Markdown
Contributor

mogren commented Apr 29, 2020

The reason we do it outside the CNI is that this applies outside of Kubernetes as well, for example if you have Docker containers running on an EC2 instance.

@mogren mogren closed this Apr 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants