-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support multiple host_network names for the same interface #10106
Comments
Hi @AndrewChubatiuk!
I'm not sure I understand... can you explain the behavior you're seeing here a bit more? |
@tgross
Hetzner region Nomad Agent config example
AWS region Nomad Agent config example
Job Example
Hetzner region Nomad Agent config example
AWS region Nomad Agent config example
Job Example
|
I'm also running into this issue, but in a slightly different way. On several of my test nodes I have a large amount of host networks. To properly identify them they are all configured as However that default range is different between some of the nodes. As a result I have no way to schedule a job in the "default" network, as that is no longer known to Nomad. Using the For my use case there would be another solution besides those mentioned by Andrew; And that is to let Nomad also define the "default" host network, even if a Losing the "default" range when making all host networks explicit also results in jobs being unable to schedule if no explicit |
Closed by #10104, which will ship in Nomad 1.1.0 |
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. |
Nomad version
nomad v1.0.4
Issue
Having issue with multi-region infrastructure setup. One region is in AWS VPC and another is in Hetzner + Nebula for private networks setup. Host networks configuration in Hetzner is:
To be able to use the same job for both regions (cause there's no
host_network
variable interpolation) had to use the same interface for both public and private agent networks configuration in AWS for compatibilityBut nomad doesn't create allocations in AWS a job, which uses both public and private interfaces, cause nomad agent is registred with
private
network only. Is there any option to either addhost_network
interpolation support or use multiple network names for the same interface?The text was updated successfully, but these errors were encountered: