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
When target-allocator is deployed with per-node allocation strategy and otel-collector pod deployed as a daemonset, for targets that don't belong to a node (e.g apiserver), fallback allocation strategy is suggested. However, I would like to explore if there is a means to enforce such targets to be scraped by pod in certain node (say: control-plane) to get more deterministic behavior.
The text was updated successfully, but these errors were encountered:
Component(s)
target allocator
Describe the issue you're reporting
When target-allocator is deployed with
per-node
allocation strategy and otel-collector pod deployed as a daemonset, for targets that don't belong to a node (e.g apiserver), fallback allocation strategy is suggested. However, I would like to explore if there is a means to enforce such targets to be scraped by pod in certain node (say: control-plane) to get more deterministic behavior.The text was updated successfully, but these errors were encountered: