Robot Upgrade: kube-state-metrics chart upgrade from 4.22.* to 7.1.0

[weizhoublue]

I am robot, upgrade: project kube-state-metrics chart upgrade from 4.22.* to 7.1.0

[gemini-code-assist]

Summary of Changes

Hello @weizhoublue, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a significant upgrade of the kube-state-metrics Helm chart, moving to a newer major version. The update introduces several key features such as enhanced security through kube-rbac-proxy integration, flexible network policy definitions, and the ability to collect metrics from custom resources. It also modernizes the chart by removing deprecated Pod Security Policy components and improving deployment configuration options, ensuring better compatibility and control within Kubernetes environments.

Highlights

• Major Version Upgrade: The kube-state-metrics Helm chart has been upgraded from version 4.22.* to 7.1.0, bringing the underlying kube-state-metrics application version from 2.6.0 to 2.18.0.
• Pod Security Policy (PSP) Removal: Support for Pod Security Policies has been removed, aligning with Kubernetes' deprecation of PSPs. Corresponding PSP-related files and configurations have been deleted.
• kube-rbac-proxy Integration: New functionality to enable kube-rbac-proxy as a sidecar has been added, allowing for secure, authenticated access to metrics endpoints via HTTPS. This includes new configuration options and RBAC rules.
• Enhanced Network Policy Support: The chart now supports both Kubernetes NetworkPolicy and CiliumNetworkPolicy, providing more flexible options for controlling network access to kube-state-metrics.
• Custom Resource State Metrics: Added support for defining and collecting metrics from custom resources, configurable via a new customResourceState option and associated ConfigMap.
• Prometheus ScrapeConfig Resource: A new ScrapeConfig custom resource can now be generated for Prometheus Operator users, offering an alternative to the traditional ServiceMonitor for scraping metrics.
• Improved Probes and Deployment Controls: Introduced startupProbe configuration, refined livenessProbe and readinessProbe settings, and added options for updateStrategy, revisionHistoryLimit, initContainers, dnsConfig, and dnsPolicy for greater deployment control.
• Dual-Stack IP and Service Enhancements: The service configuration now includes support for ipDualStack and loadBalancerSourceRanges, along with named targetPort definitions for better service management.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request automates the upgrade of the kube-state-metrics Helm chart from version 4.22.* to 7.1.0. This is a significant major version upgrade that brings in numerous features, improvements, and necessary breaking changes from the upstream chart. Key changes include the removal of deprecated APIs like PodSecurityPolicy, updates to RBAC rules for newer Kubernetes resources like EndpointSlices, and the introduction of new features such as kube-rbac-proxy support, configurable network policies, and custom resource state metrics. The overall quality of the upgrade is high, and the changes align with modern Kubernetes and Helm best practices. I've identified a minor documentation issue in the README files that should be addressed.

[gemini-code-assist]

There is a malformed Markdown link in the documentation. The link to the helm repo documentation is nested, which will cause rendering issues. It should be corrected for clarity.

Suggested change

	The installation instructions use the OCI registry. Refer to the [`helm repo`]([`helm repo`](https://helm.sh/docs/helm/helm_repo/)) command documentation for information on installing charts via the traditional repository.
	The installation instructions use the OCI registry. Refer to the [`helm repo`](https://helm.sh/docs/helm/helm_repo/) command documentation for information on installing charts via the traditional repository.

[gemini-code-assist]

There is a malformed Markdown link in the documentation. The link to the helm repo documentation is nested, which will cause rendering issues. It should be corrected for clarity.

Suggested change

	The installation instructions use the OCI registry. Refer to the [`helm repo`]([`helm repo`](https://helm.sh/docs/helm/helm_repo/)) command documentation for information on installing charts via the traditional repository.
	The installation instructions use the OCI registry. Refer to the [`helm repo`](https://helm.sh/docs/helm/helm_repo/) command documentation for information on installing charts via the traditional repository.