-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Allow to restrict servers that can join a given Serf Consul cluster. #7628
Allow to restrict servers that can join a given Serf Consul cluster. #7628
Conversation
a7749c2
to
58715e9
Compare
This PR looks good. Could you rebase so that I can review? |
58715e9
to
1139a46
Compare
@i0rek DONE: had to revamp doc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Could you add a test in runtime_test.go
for the hcl and json conversion?
@i0rek Done, added the new Unit test for HCL/JSON serialization |
Based on work done in hashicorp/memberlist#196 this allows to restrict the IP ranges that can join a given Serf cluster and be a member of the cluster. Restrictions on IPs can be done separatly using 2 new differents flags and config options to restrict IPs for LAN and WAN Serf.
This test does check that blocking IPs works on LAN
e6e62e6
to
d19e8c4
Compare
@i0rek The test failing is |
d19e8c4
to
14ad95c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your work!
…7628) Based on work done in hashicorp/memberlist#196 this allows to restrict the IP ranges that can join a given Serf cluster and be a member of the cluster. Restrictions on IPs can be done separatly using 2 new differents flags and config options to restrict IPs for LAN and WAN Serf.
Based on work done in hashicorp/memberlist#196
This allows restricting the IP ranges that can join a given Serf cluster and be a member of the cluster.
Restrictions on IPs can be done separately using 2 new differents flags and config options to restrict IPs for both LAN and WAN Serf.
This will allow to secure a bit more clusters as well as protecting non-encrypted clusters from an agent in dev mode to join clusters and thus fixing #5916