Mustache good first issues

The current security contact email in the SECURITY.md file is bouncing, preventing external security researchers from reporting vulnerabilities. The issue proposes directing reporters to GitHub's private vulnerability reporting feature and suggests fixing or replacing the email address, along with documenting expected response times.

This issue describes a problem with Minecraft server connectivity, specifically related to the "transport" option and the mc-monitor defaulting to RakNet. The Nethernet ports are also missing, preventing Minecraft clients from fully connecting. The reporter is seeking help to resolve these configuration issues.

This issue requests the expansion of kube-rclone's functionality beyond its current Plex media playback support. The goal is to enable compatibility with other services such as Sonarr and Radarr, indicating a need for broader integration capabilities.

This issue requests the addition of support for installing Argo CD Core using the existing Helm chart. The user wants to leverage the chart for Argo CD Core installations, similar to how it's done for the full Argo CD, and prefers this over manual or Kustomize installations.

This issue proposes to enable the Prometheus target allocator within the `otel-deployment` in the k8s-infra environment. This is intended to improve Prometheus target allocation for non-trivial workloads, suggesting a need for more robust monitoring infrastructure.

This issue proposes to replace a large, unnecessary UniFi Helm chart fixture in a test spec with a minimal Kubernetes Deployment using a small image like busybox. This change aims to significantly reduce test execution time and resource consumption by eliminating the need to pull and start a heavy application when only the `hostPort` configuration is being tested. The proposal also suggests removing the `--skip-wait-for-install` flag as the new fixture will start quickly.

This issue addresses a gap in testing for the Helm deployment manager. Currently, there are no tests that specifically cover the scenario where a valid configuration file points to a Helm chart that does not exist in the repository. The proposed solution is to add a new spec that simulates this failure, ensuring the system correctly reports the error and cleans up properly.

The issue proposes updating the documentation for 'pod_memory_hog' to clarify that it represents a general Kubernetes application best practice, not just a specific test. The goal is to better communicate Kubernetes-native best practices regarding memory resource management and behavior with resource limits.

This issue proposes migrating the ClickHouse Helm chart to use ClickHouse Keeper instead of Apache ZooKeeper. The primary motivation is to reduce memory consumption, especially in development environments where ZooKeeper's JVM overhead can be significant.

This issue requests an update to the README files of various SDKs to comprehensively document all possible use cases for the 'Read' operation. Specifically, it highlights a missing example for reading tuples related to a specific relation and object across all users, providing a code snippet for illustration.

This feature request aims to enable users to specify the `--defaultdb` flag when running the Temporal schema job, particularly when deploying via Helm. Currently, there's no direct way to pass this flag, unlike other configuration options. The proposed solutions involve either adding an environment variable for `--defaultdb` or allowing arbitrary flag passing to the schema job command.

This feature request aims to enable the deployment of the Argo CD MCP server within Kubernetes using a Helm chart. The user proposes either integrating it as an addon to the existing Argo CD Helm chart or creating a separate Helm chart for the MCP server, similar to the Grafana MCP chart.

The generated changelog links in the Argo Helm releases are incorrect, pointing to the wrong comparison tags. The expected behavior is for the link to show the diff between the current and previous versions of the specific chart, not a mix of different chart versions.

This issue requests the implementation of a gRPC DNS fix within the Argo CD Helm chart. The goal is to address a problem related to DNS resolution for gRPC services, likely improving connectivity and reliability.

This issue proposes adding `values.schema.json` files to various Argo Helm charts to enforce strict validation of `values.yaml` entries. The goal is to prevent silent failures when chart dependencies are updated by disallowing unknown properties.

When KEDA is installed as a dependency of another Helm chart, the installation fails because the dependent chart attempts to use KEDA's CRDs before they are installed. The proposed solution is to move KEDA's CRD definitions into a 'crds' folder within the KEDA chart, which Helm automatically installs first.

This feature request proposes enhancing the Argo Workflows Helm chart to automatically trigger deployment restarts when configuration changes occur. This is achieved by adding a specific Helm annotation to the deployment, ensuring that Argo CD picks up and applies these changes, thus avoiding manual intervention or reliance on the potentially problematic Argo Workflows config watcher.

This issue requests the implementation of changes from kube-state-metrics version v2.20.0 into the Prometheus community Helm charts. These changes include updates to RBAC configurations, which are necessary to keep the chart aligned with the latest upstream release.