APIService resource is incorrectly generated with v1beta1 while Kubernetes cluster supports v1

[vegetablest]

What happened?:
When installing Prometheus Adapter using Helm, the APIService resource in the rendered template is generated with apiVersion: apiregistration.k8s.io/v1beta1. However, my Kubernetes cluster supports apiVersion: apiregistration.k8s.io/v1 (verified with kubectl api-versions).

What did you expect to happen?:
The Helm chart should generate the APIService resource with apiVersion: apiregistration.k8s.io/v1, as my Kubernetes cluster does not require v1beta1.

Anything else we need to know?:

1. Deploy Prometheus Adapter using Helm with the following command:

   helm install prometheus-adapter prometheus-community/prometheus-adapter --namespace monitoring

2. Inspect the rendered APIService resource:

   helm template prometheus-adapter prometheus-community/prometheus-adapter --namespace monitoring

3. Notice that the apiVersion is set to apiregistration.k8s.io/v1beta1 instead of apiregistration.k8s.io/v1.

Environment:

• prometheus-adapter version: v0.12.0
• Kubernetes version (use kubectl version): v1.31.2
• Helm version: v3.16.4

[k8s-ci-robot]

This issue is currently awaiting triage.

If prometheus-adapter contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.