Downgrade Flannel in Canal deployment to v0.9.0 #4047
Merged
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.
Flannel v0.9.1 introduces a single change to add 2 iptables rules to the
FORWARD
chain, permitting traffic in/out of the pod network (introduced to improve compatibility with newer versions of Docker). This change is unnecessary for Canal deployments for the following reasons:DefaultEndpointToHostAction
is set toACCEPT
in the manifest deployed by kops, allowing traffic by default once all other Calico rules are processed.ChainInsertMode
is set toAPPEND
, the flannel rules will be processed before the Calico rules, accepting traffic by default, and so Kubernetes network policies will not take effectThis change is temporary until a more permanent resolution is available with Flannel, such as providing a configurable option to disable the addition of these rules when deployed with Calico.
Related to #4037