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

V2 - Pod logs, Alloy is not getting scheduled #1176

Open
naveenkumarsp opened this issue Jan 28, 2025 · 1 comment
Open

V2 - Pod logs, Alloy is not getting scheduled #1176

naveenkumarsp opened this issue Jan 28, 2025 · 1 comment

Comments

@naveenkumarsp
Copy link

Daemonset of Alloy pod logs is not getting scheduled on AKS node where it has taint. In V1, the agents were getting scheduled on tainted node. Also there is no option in value file to add tolleration to the any agents.

taint - kubernetes.azure.com/scalesetpriority: spot:NoSchedule

What happend : Daemon set of alloy-log is not schduled on the nodes where taint is applied.

@petewall
Copy link
Collaborator

We just added an example that shows how to set tolerations in Alloy and other components:
https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/examples/tolerations

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