[mihirduvedi]

Replace the legacy tier, component, release, chart, and heritage labels for chart 2.0 with the Kubernetes-recommended application labels requested in #34048. Update resource and pod labels together with workload, Service, policy, and autoscaling selectors. Centralize label generation and normalization, preserve user-label precedence, and update the existing Helm tests, executor pod template, examples, and documentation.

The review follow-up removes the separate label test module and news fragment, reverts unrelated resource-list changes, and includes the recommended name, instance, and version labels. This refresh rebases onto current main and reads the expected application version from Chart.yaml so version bumps do not leave hardcoded assertions behind.

closes: #34048

Validation for this refresh:

• Regular and manual prek checks passed; the final commit's hooks passed, including kubeconform, mypy, Ruff, and formatting.
• Helm lint passed. A rendered audit passed for 67 resources, 14 pod templates, 10 workload selectors, and 8 Service selectors with optional components enabled.
• Full Helm tests passed: 2,280 tests across all nine groups with Kubernetes 1.31.12. Helm release checks, CI static checks, the Helm documentation build, and documentation publication/version validation also passed.
• All normal database/non-database core jobs and the special core matrix passed. The broader fork run finished with 112 successful jobs, but is not fully green: Kubernetes/Kustomize integration jobs stop before exercising the chart because the expected base PROD image is missing locally; additional PROD e2e jobs fail during image-pull setup. These integration tests are not counted as passing.
• Upstream Tests (AMD) and CodeQL require maintainer approval before they can run.

---

Was generative AI tooling used to co-author this PR?

• Yes — Codex (GPT-5) for the original contribution; Codex (GPT-6) for this refresh.

Generated-by: Codex (GPT-6) following the guidelines

---

Drafted-by: Codex (GPT-6) (no human review before posting)

[Miretpl]

With using recommended k8s labels, we could delete old once (we are on chart 2.0 on main) and leave only necessery onces. We don't need to have all of these labels with duplicated values when there is Kubernetes standard for them.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[mihirduvedi]

Refreshed this PR against current main and addressed the four review threads: removed the separate label test module and news fragment, reverted the unrelated test changes, and included the recommended name, instance, and version labels. The version assertions now read Chart.yaml rather than hardcoding the application version.

The fork CI run passed all 2,280 Helm tests across nine groups with Kubernetes 1.31.12, Helm release checks, static checks, the Helm documentation build, and the normal and special core test matrices.

The overall fork run is still red because of integration setup failures: Kubernetes tests cannot find the expected base PROD image before exercising the chart, and PROD e2e tests fail during image-pull setup. These are not reported as passing integration tests.

This is ready for another review. Could a maintainer approve the upstream Tests (AMD) and CodeQL runs so project CI can complete validation?

---

Drafted-by: Codex (GPT-6) (no human review before posting)