drop port-collision checks against swarm.otel.telemetryPort
nothing at runtime: eval no longer asserts against a port the swarm collector no longer binds in the host netns.
This commit is contained in:
parent
6b1fc4b040
commit
ec562ca503
7 changed files with 9 additions and 21 deletions
|
|
@ -136,12 +136,10 @@ in
|
|||
failures. How you find out that telemetry is being lost, so it is
|
||||
worth keeping rather than switching off.
|
||||
|
||||
⚠️ **Deliberately neither 8888 nor 8889.** 8888 is the collector
|
||||
⚠️ **Deliberately not 8888.** 8888 is the collector
|
||||
binary's built-in default, which the hive tier
|
||||
({option}`services.hyperhive.otel.telemetryPort`) already binds, and
|
||||
8889 is the swarm tier's
|
||||
({option}`services.hyperhive.swarm.otel.telemetryPort`). This
|
||||
container runs with `privateNetwork = false`, so all three share the
|
||||
({option}`services.hyperhive.otel.telemetryPort`) already binds. This
|
||||
container runs with `privateNetwork = false`, so both share the
|
||||
host's network namespace whenever they are co-located — and unlike
|
||||
the OTLP ports this one appears nowhere in either config when it is
|
||||
left undeclared, so nothing that compares configured ports can see
|
||||
|
|
|
|||
Loading…
Reference in a new issue