You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I make a PR hashicorp/go-discover#194 on go-discover who give this opportunity.
If you can validate this PR and update to the new go-discover inside nomad...
The text was updated successfully, but these errors were encountered:
obeyler
changed the title
Allow chand default endpoint for server join in case of aws
Allow change default endpoint for server join in case of aws
May 13, 2022
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Proposal
Nomad allows to join cluster by using tag on aws vm instance. (https://www.nomadproject.io/docs/configuration/server_join) In case of AWS cloud provider, unfortunately the default endpoint can not be set.
Use-cases
Sometime default aws endpoint have to be change (example in case of outscale cloud provider who share same api with aws but differs from endpoint: https://docs.outscale.com/en/userguide/Regions-Endpoints-and-Availability-Zones-Reference.html)
Attempted Solutions
I make a PR hashicorp/go-discover#194 on go-discover who give this opportunity.
If you can validate this PR and update to the new go-discover inside nomad...
The text was updated successfully, but these errors were encountered: