fix(monitoring): enable kube-state-metrics to populate Kubernetes Cluster dashboard

[Copilot]

• Explore repository structure and monitoring configuration
• Enable kube-state-metrics in prometheus-helmrelease.yaml (primary source for dashboard 7249)
• Enable kubeStateMetrics defaultRules
• Add kube-state-metrics resource constraints appropriate for Pi
• Run validation to confirm changes are correct (all 10 checks pass)
• Resolve merge conflict by aligning our file with main branch version

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Kubernetes Cluster (Prometheus) dashboard shows N/A for all metrics</issue_title>
<issue_description>The Prometheus-focused Kubernetes dashboard shows no data despite long-running deployment.

Scope
• Check Prometheus self-metrics
• Validate label selectors and job names
• Confirm RBAC is not blocking metric access

Acceptance Criteria
• Dashboard is populated or issue is conclusively explained
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Kubernetes Cluster (Prometheus) dashboard shows N/A for all metrics #3

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[philbudden]

@copilot there is a merge conflict that needs to be resolved

[Copilot]

@copilot there is a merge conflict that needs to be resolved

Resolved in 68dfa41 — the main branch had an independently committed version of the same fix with slightly different comments and a 20m CPU request (vs 10m). I've aligned our branch to match main exactly, which eliminates the conflict.