Skip to content
This repository was archived by the owner on Sep 24, 2025. It is now read-only.

Add flexibility into the allowable network ranges that can access the loadbalancer#25

Open
grimesjm wants to merge 2 commits into
hashicorp-modules:masterfrom
grimesjm:master
Open

Add flexibility into the allowable network ranges that can access the loadbalancer#25
grimesjm wants to merge 2 commits into
hashicorp-modules:masterfrom
grimesjm:master

Conversation

@grimesjm
Copy link
Copy Markdown

@grimesjm grimesjm commented May 6, 2019

I ran into a limitation with using a non-public LB setup with consul and also vault which I can also submit a PR for if we are OK with this change for consul. We have our network extended into AWS and want to limit the CIDR ranges that exist on that internal network that have access to the loadbalancer. This gives us an optional list we can pass into the module to add that access to that range.

I ran this against my own TF I have for provisioning a consul cluster and it updates the SG rules as I would expect.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant