We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
discovery.kubelet
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:
alloy-metrics
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/
The text was updated successfully, but these errors were encountered:
petewall
No branches or pull requests
On very large clusters, using pod discovery:
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:This limits Alloy's pod discovery to its local node only.
Doc: https://grafana.com/docs/alloy/latest/reference/components/discovery/discovery.kubelet/
The text was updated successfully, but these errors were encountered: