Jsonnet good first issues

This enhancement request proposes integrating Pressure Stall Information (PSI) metrics into existing dashboards and alert systems. The goal is to provide users with more granular insights into resource contention, similar to how CPU throttling is currently displayed. The request also seeks input on potential implementation approaches.

This enhancement request proposes publishing a list of required metrics with each release of the project. This would help users who are integrating the project's dashboards and alerts with different Kubernetes monitoring stacks, ensuring compatibility and enabling them to identify and include any missing metrics.

The user is requesting updated guidance on Kubernetes version compatibility for the project's releases, as the previous compatibility matrix appears to be outdated. They are currently running an older version of the project with a newer Kubernetes version and are seeking information to ensure proper compatibility.

The KubeCPUOvercommit alert in the kubernetes-mixin project currently does not consider node pools or tolerations. This could lead to inaccurate alerts, as it doesn't account for specific node configurations or scheduling constraints. The issue seeks community input on how to address this limitation.

The current KubeCPUQuotaOvercommit and KubeMemoryQuotaOvercommit alerts use the current number of nodes to calculate total capacity, which can lead to excessive noise in clusters with autoscalers. The enhancement proposes modifying these alerts to consider the maximum available nodes instead of the current count, potentially by leveraging metrics from the Kubernetes autoscaler.

This issue requests updating documentation examples that currently use Nginx Ingress. Since Nginx Ingress is deprecated, these examples should be migrated to use either an alternative ingress controller or, preferably, the Gateway API for better long-term support.

This issue proposes enabling native histograms in kube-prometheus, which are more efficient and accurate than legacy histograms. It requires modifications to Prometheus scraping, ingestion, and potentially conversion of existing histograms, with a phased rollout to allow users to transition at their own pace.