You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to use a field supported by TA and bumped into an issue of these values not being synchronized, so I cannot use a fallbackStrategy to query a couple of targets that are not bound to a "node" object (i.e. kube apiserver serviceMonitor)
i.e. here are the settings for opentelemetry-kube-stack where I create a target-allocator daemonset to collect metrics from various services.
It gets passed as is to the operator
Component(s)
No response
What happened?
Description
I tried to use a field supported by TA and bumped into an issue of these values not being synchronized, so I cannot use a fallbackStrategy to query a couple of targets that are not bound to a "node" object (i.e. kube apiserver serviceMonitor)
i.e. here are the settings for opentelemetry-kube-stack where I create a target-allocator daemonset to collect metrics from various services.
It gets passed as is to the operator
The flag, while it can be assumed to be valid, is not passed through the layers of helm -> operator -> collector
Steps to Reproduce
set allocationFallbackStrategy (or any TA config option from the config.go schema converting it snake_case -> camelCase)
Expected Result
a correspondingly configured Collector object is created
Actual Result
the field is dropped
Kubernetes Version
1.31
Operator version
0.120
Collector version
0.123.0
Environment information
Environment
Ubuntu 24.04
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: