Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

per-node allocation strategy #3530

Open
sfc-gh-akrishnan opened this issue Dec 10, 2024 · 1 comment
Open

per-node allocation strategy #3530

sfc-gh-akrishnan opened this issue Dec 10, 2024 · 1 comment

Comments

@sfc-gh-akrishnan
Copy link

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.

@swiatekm
Copy link
Contributor

If that's what you want, I think it's simpler to start a separate collector for this purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants