fix(vpc): use elastic IP for tunnel connection when available #6306
+5
−2
Conversation
This file contains hidden or 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
When elastic IPs are configured, use the first elastic IP address for the tunnel connection instead of the bastion instance's public IP. This ensures the tunnel uses the stable NAT instance IP (which gets replaced by the EIP after creation) rather than a potentially changing public IP address. Addresses anomalyco#6305.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When elastic IPs are configured, use the first elastic IP address for the tunnel connection instead of the bastion instance's public IP. This ensures the tunnel uses the stable NAT instance IP (which gets replaced by the EIP after creation) rather than a potentially changing public IP address.
Addresses #6305.