chore(grafana-dashboards)!: Update dashboard Kubernetes / Views / Pods (40 ➔ 41) #2177
No reviewers
Labels
No labels
area/bootstrap
area/ci
area/kubernetes
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
renovate/container
renovate/github-action
renovate/github-release
renovate/grafana-dashboard
renovate/helm
renovate/terraform
type/digest
type/major
type/minor
type/patch
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
GiorgioAresu/home-ops!2177
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/15760-41.x"
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?
This PR contains the following updates:
40→41Configuration
📅 Schedule: (in timezone Europe/Rome)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
✅ Automated recommendation: APPROVE
Analysis engine: minimax/MiniMax-M2-7-anthropic@http://litellm.ai.svc.cluster.local:4000/v1 (anthropic)
Recommendation: Approve
Simple Grafana dashboard revision bump (40 → 41) for the "Kubernetes / Views / Pods" dashboard (ID 15760). The change updates only the revision number in the download URL, which is a routine dashboard sync operation.
Changed file:
kubernetes/apps/observability/kube-prometheus-stack/app/grafanadashboard.yaml— revision URL updated from/revisions/40/downloadto/revisions/41/downloadNon-blocking caveat: The PR body flags "Some dependencies could not be looked up" in the Renovate dependency dashboard, but this applies to other dependencies tracked by Renovate, not to the dashboard revision update itself which was successfully resolved.
No blockers, no findings from konflate, no repository conventions to violate.