scheduler: enable upgrade path for bridge network finger print #9356
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.
This PR enables users of Nomad < 0.12 and bridge networks to
upgrade to Nomad 0.12 and beyond. Nomad 0.12 introduced a
network fingerprinter for bridge networks, which is a constraint checked
for if bridge network is being used. If users upgrade servers first (as
recommended), suddenly no clients running older versions of Nomad
will satisfy the bridge network resource constraint. This change insetad
only enforces the constraint if the Nomad client version is also >= 0.12.
Closes #8423