Adjusts gateway VM deployment to use static ip address. #1781
Conversation
This file contains 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
BedrockSquirrel
approved these changes
Feb 29, 2024
anixon604
temporarily deployed
to
dev-testnet
GitHub Actions
Inactive
anixon604
force-pushed
the
anthony/OG-static-ip
branch
from
d4afa0a to
e781f43
Compare
anixon604
temporarily deployed
to
dev-testnet
GitHub Actions
Inactive
|
Checked on dev-testnet, caught but where had to move the dns assignment from the vm flag, to attach to the pre-defined static-ip. This dns-name check/assignment is added as a prior step. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why this change is needed
We have intermittent issues with the Gateway not being accessible on redeploy from what is believed to be DNS delay from the dynamic IP. Static IPs on the VM will solve this.
Note: originally I had planned to introduce a LoadBalancer, but decided against as the backend pools will balance as well and the static IPs will be more cost effective. (however this will be deprecated when migration to terraform is in place as the below workflow doesn't accommodate multiple instances / horizontal scaled gateways.
What changes were made as part of this PR
PR checks pre-merging
N/A for workflow