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

Investigate utilizing discovery.kubelet to handle super-large clusters #1090

Open
petewall opened this issue Jan 9, 2025 · 0 comments
Open
Assignees

Comments

@petewall
Copy link
Collaborator

petewall commented Jan 9, 2025

On very large clusters, using pod discovery:

discovery.kubernetes "pods" {
  role = "pods"
}

Can sometimes flood the amount of memory required for discovery and the amount of requests to the API server.

An interesting approach would be to set alloy-metrics to be a daemonset and utilize:

discovery.kubelet "pods" {
  ...
}

This limits Alloy's pod discovery to its local node only.

Doc: https://grafana.com/docs/alloy/latest/reference/components/discovery/discovery.kubelet/

@petewall petewall self-assigned this Jan 9, 2025
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

1 participant