set iptables FORWARD rules ACCEPT for inside VPC traffic #535
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.