This repository was archived by the owner on Jan 8, 2024. It is now read-only.
Backport of Additional install flags for Nomad service address and network mode into release/0.11.x #4641
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 #4619 to be assessed for backporting due to the inclusion of the label backport/0.11.x.
The below text is copied from the body of the original PR.
The overall goal here is to
waypoint installinto a Nomad node from the outside. In my case, a Vagrant machine from my laptop, but also should work with other cases like cloud vendors where thewaypoint-serverservice needs to be given a public IP, to which the install procedure connects after job submission.For example, using a
meta.public_ipthat I set manually in my Nomad client config:Of course
-nomad-service-address=192.168.56.200would have worked just as well, but the meta is for demonstration, as I imagine that on AWS one might use'${attr.unique.platform.aws.public-ipv4}'to set the service address dynamically.The ~publicly-routable IP at the bottom of the install output (and used during install) comes from the Nomad services:
I do wonder though if perhaps separate service(s) could/should be made for this connection during install, vs internal waypoint->waypoint communication? Do the runner(s) connect to waypoint-server using this service? I didn't look that far into this part.
Overview of commits