Description
Component(s)
target allocator
What happened?
Description
When Collector is deployed as daemonset and prometheusreceiver is used alongside TA,TA is ignoring static_config targets
Steps to Reproduce
Deploy Collector as daemonset , and set strategy as "per-node"
Have some static_config in Target-allocator config section
port-forward TA pod
curl localhost:8080/jobs/<job_name>/targets | jq
The collectors have empty list of targets
However if collector is deployed as statefulset and strategy is kept as "consistent-hashing"
then I can see the targets and scraping happens as usually
Expected Result
Scraping should happen in daemonset also as the static targets reside in the same node of collector
or a documentation stating that this use-case is not supported/appropriate
Actual Result
No scraping
Kubernetes Version
1.23.0
Operator version
0.127.0
Collector version
0.127.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
Log output
Additional context
- job_name: abc-job
scrape_interval: 15s
scrape_timeout: 10s
static_configs:
- targets:
- 192.168.154.171:8082
- 192.168.40.214:8082
- 192.168.9.156:8082
- 192.168.213.20:8082
- 192.168.77.133:8082
- 192.168.189.140:8082
- 192.168.200.169:8082
- 192.168.70.3:8082
- 192.168.246.233:8082
- 192.168.150.139:8082
Similar kind of static targets are added