[18.09] prometheus-node-exporter: remove go 1.9 pinning #54910
Merged
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.
Motivation for this change
Since Go1.9 has been marked as insecure (5a3e195) all setups relying on the prometheus-node-exporter would fail to build a new generation.
With Go1.11 the daemon seems to work just fine. I was unable to observe
any crashes (due to the wifi module being loaded).
cc @WilliButz, can you verify that it also runs for you?
Things done
sandbox
innix.conf
on non-NixOS)varnish
exporter test failed but the others succeded. It did not look like this change could have potentially introduced the varnish error so I ignored it.nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)