Fix Grafana CrashLoopBackOff — disable loki-stack sidecar datasource #20
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-platform!20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "18-fix-grafana-duplicate-default-datasource-v2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Grafana has been in CrashLoopBackOff for ~8 days because two datasources are marked
isDefault: true. The loki-stack Helm chart auto-generates a ConfigMap that conflicts with the kube-prometheus-stack default Prometheus datasource. This PR disables the loki-stack sidecar datasource provisioning, leaving the existing custom Terraform-managed ConfigMap as the sole Loki datasource.Changes
terraform/main.tf: Expanded the loki-stackgrafanaHelm values block to includesidecar = { datasources = { enabled = false } }, preventing the chart from auto-generating a competing default datasource ConfigMap.Test Plan
tofu fmt -checkpasses — no formatting issuestofu validatepasses — valid configurationtofu plan— should show only the loki-stack Helm release updating (requires cluster access)tofu apply, verify Grafana pod exits CrashLoopBackOff and starts successfullyReview Checklist
Related Notes
todo-fix-grafana-duplicate-default-datasource— the bug this PR fixesClosing — agent branched from stale
origin/main(GitHub, now removed). Redoing withforgejoas sole remote.Pull request closed