Skip to content

fix(unraid): schedule Alloy collectors #113

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.

Sign up for GitHub

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

Merged
syscod3 merged 1 commit into from
Sep 13, 2026
Merged

fix(unraid): schedule Alloy collectors #113

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion values/clusters/unraid-lab/grafana-k8s-monitoring.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,17 @@ annotationAutodiscovery:
# Every usable Unraid node is a tainted control-plane node. The Alloy Operator
# must tolerate that taint before it can create the metrics collector.
alloy-operator:
tolerations:
tolerations: &control_plane_tolerations
- key: node-role.kubernetes.io/control-plane
operator: Exists
effect: NoSchedule

# The stateful metrics collector and singleton event collector also run as Pods,
# so they require the same explicit scheduling permission.
collectors:
alloy-metrics:
controller:
tolerations: *control_plane_tolerations
alloy-singleton:
controller:
tolerations: *control_plane_tolerations
Loading