Backport of add HOST_IP to mesh-gateway into release/1.0.x #2128
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.
Backport
This PR is auto-generated from #1808 to be assessed for backporting due to the inclusion of the label backport/1.0.x.
🚨
The person who merged in the original PR is:
@DanStough
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
Changes proposed in this PR:
HOST_IP
environment variable back to mesh-gateway deploymentExpansion of this var is supported according to the docs, but requires the var to actually be set: https://developer.hashicorp.com/consul/docs/connect/proxies/envoy#envoy_statsd_url
How I've tested this PR:
How I expect reviewers to test this PR:
Note too sure the best way to add a test for this. Suggestions would be greatly appreciated.
Checklist:
Overview of commits