Change outbound nodeport rule to accept RELATED and ESTABLISHED traffic #695
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
|
@RaveNoX thanks for the PR and detailed bug report #692 I don't recall why (but very likely due docker changing default FORWRD policy as described in kubernetes/kubernetes#39823) that rule was added as part of #120. Current rule is a bad solution. So it must be changed. I need to test it to understand better. But here are the questions that are going through my mind
Let me try the fix and revert back |
|
Hello! |
|
@RaveNoX, thanks for the fix! @murali-reddy I wonder if there are any updates from your side? It looks like we are hitting the same problem at the end. |
|
@murali-reddy any news on this? |
|
Should no longer be needed as of kube-router 1.2.X. |
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.
This pull request fixes issue #692