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

Add a flag for iptables supporting --random-fully #48

Merged
merged 3 commits into from Jul 4, 2018
Merged

Add a flag for iptables supporting --random-fully #48

merged 3 commits into from Jul 4, 2018

Conversation

ghost
Copy link

@ghost ghost commented May 31, 2018

This is important for Flannel on Kubernetes, see https://tech.xing.com/a-reason-for-unexplained-connection-timeouts-on-kubernetes-docker-abd041cf7e02 and kubernetes/kubernetes#56903 for some background information.

This is important for Flannel on Kubernetes.
Copy link
Collaborator

@squeed squeed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need a public function to expose this too.

The other hasFoo properties are only used internally so the library can select the optimal locking strategy; they're not exposed to the user.

So, can you also add a getter function HasRandomFully()? That way users of the library can construct the best SNAT line.

While you're in there, can you add a getter for the iptables version? We might as well expose it directly.

@ghost
Copy link
Author

ghost commented Jun 18, 2018

@squeed Added the getter, and also started storing the extracted iptables version and added a getter for that as well.

@squeed squeed merged commit 25d087f into coreos:master Jul 4, 2018
@ghost ghost deleted the add_random_fully_flag branch July 5, 2018 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants