fix: Add all VPC CIDRs to VPCe config #697
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.
What does this PR do?
Adds the public subnet CIDR blocks to the security group on the VPC endpoints and adds the S3 gateway endpoint to the Public route table.
Motivation
I launched an instance in the Spark operator VPC to use as a bastion instance and selected the Public subnets but the SSM agent on the instance never connected. I think when the vpc endpoints are enabled, the SSM endpoint overrides the DNS for the service, but the Security group blocks traffic from the public subnet.
This shouldn't cause a problem for our examples/eks nodes as we don't really leverage the Public subnet but was annoying to debug.
More
website/docs
orwebsite/blog
section for this featurepre-commit run -a
with this PR. Link for installing pre-commit locallyFor Moderators