[CAP-3826] Improve Kubernetes Pods dashboard widgets

[AntoineEsteve]

What does this PR do?

This follow-up to #24590 fine-tunes the Kubernetes Pods Overview dashboard. It applies weighted pod-state queries, improves the weekly issue comparison, and adds a Disk I/O widget alongside the network widgets.

Fix pod count inflation with .weighted()

The Pods by Phase and Ready Pods widgets need .weighted() so short-lived pod states—for example, a pod briefly entering the Pending state—do not inflate counts across an entire time bucket.

Before — without .weighted()

Screen.Recording.2026-07-21.at.15.26.07.mov

After — with .weighted()

Screen.Recording.2026-07-21.at.15.30.46.mov

Motivation

Follow up on #24590 with clearer pod counts, a more precise weekly comparison, and visibility into storage activity. This work is tracked in CAP-3826.

Review checklist (to be filled by reviewers)

Try the updated dashboard with production data, and compare it with the previous version.

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run