K3S-HOME/observability
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

FIX(otel): use per-node strategy for DaemonSet mode

Browse Source 
- Change allocationStrategy to per-node (required for DaemonSet)
- Operator rejects consistent-hashing with DaemonSet mode
This commit is contained in:
Mayne0213
2026-01-09 23:32:56 +09:00
parent 1fdbb5e1dd
commit 254687225c
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
opentelemetry-collector/manifests/collector.yaml
View File

@@ -18,12 +18,12 @@ spec:
serviceAccount: otel-collector serviceAccount: otel-collector
# Target Allocator - distributes Prometheus scrape targets across collectors # Target Allocator - distributes Prometheus scrape targets across collectors
# Using consistent-hashing strategy (not per-node due to collector-node mapping bug) # per-node strategy: each collector scrapes targets on its own node
targetAllocator: targetAllocator:
enabled: true enabled: true
serviceAccount: otel-collector-targetallocator serviceAccount: otel-collector-targetallocator
image: ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:0.113.0 image: ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:0.113.0
allocationStrategy: consistent-hashing allocationStrategy: per-node
filterStrategy: relabel-config filterStrategy: relabel-config
prometheusCR: prometheusCR:
enabled: true enabled: true