Skip to content
This repository was archived by the owner on Jan 8, 2024. It is now read-only.

Conversation

@hc-github-team-waypoint
Copy link
Collaborator

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 install into 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 the waypoint-server service needs to be given a public IP, to which the install procedure connects after job submission.

For example, using a meta.public_ip that I set manually in my Nomad client config:

$ ./waypoint install -accept-tos \
  -platform=nomad \
  -nomad-host-volume=waypoint \
  -nomad-runner-host-volume=waypoint \
  -nomad-service-provider=nomad \             
  -nomad-service-address='${meta.public_ip}' \
  -nomad-network-mode=bridge

✓ Waypoint server ready
...
✓ Runner "static" adopted successfully.
Waypoint server successfully installed and configured!
...
Advertise Address: 192.168.56.200:9701
Web UI Address: https://192.168.56.200:9702/

Of course -nomad-service-address=192.168.56.200 would 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:

$ nomad service info waypoint-server
Job ID           Address              Tags        Node ID   Alloc ID
waypoint-server  192.168.56.200:9701  [waypoint]  f8ffd891  57e5dcfd
$ nomad service info waypoint-ui
Job ID           Address              Tags        Node ID   Alloc ID
waypoint-server  192.168.56.200:9702  [waypoint]  f8ffd891  57e5dcfd

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

@hc-github-team-waypoint hc-github-team-waypoint force-pushed the backport/nomad-service-address/constantly-sweet-ostrich branch from 56fdc49 to 3c00be0 Compare April 28, 2023 14:44
@hc-github-team-waypoint hc-github-team-waypoint merged commit eab582b into release/0.11.x Apr 28, 2023
@hc-github-team-waypoint hc-github-team-waypoint deleted the backport/nomad-service-address/constantly-sweet-ostrich branch April 28, 2023 14:44
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants