fix(#3125): the swarm collector writes its own resolver, like its siblings
All four sibling swarm containers import swarm-container-resolver.nix; this one did not. It matters more here than most: otel.endpoint is an operator-configured external hostname, and reaching it is the entire reason this container holds a credential. Also aligns two details with those siblings - the enable default is asserted from swarm-required-services.nix with the metrics pair it feeds, so that file remains the one place a service host is declared, and machine is readOnly since its description already calls it a fact rather than a knob.
This commit is contained in:
parent
98ab0ad59f
commit
28623e5eff
2 changed files with 25 additions and 5 deletions
|
|
@ -70,6 +70,12 @@ in
|
|||
# exactly one still sets it directly, which `mkDefault` allows.
|
||||
victoriametrics.enable = lib.mkDefault swarmCfg.enableRequiredServices;
|
||||
grafana.enable = lib.mkDefault swarmCfg.enableRequiredServices;
|
||||
|
||||
# The collector that feeds the pair above, and the only tier holding
|
||||
# the upstream credential. Same rule as the rest: once per swarm,
|
||||
# optional, and a hive that is not the service host is a *client* of
|
||||
# it (`swarm.otel.url`) rather than a second one.
|
||||
otel.enable = lib.mkDefault swarmCfg.enableRequiredServices;
|
||||
};
|
||||
|
||||
# The collector that feeds the pair above (note: no `swarm.` prefix,
|
||||
|
|
|
|||
Loading…
Reference in a new issue