Kube State Metrics unable to find v2beta2.HorizontalPodAutoscaler

[MattCosturos]

What happened:
Kube State Metrics logs an error every second about not being able to find v2beta2.HorizontalPodAutoscaler.

I1003 18:35:19.188423       1 builder.go:232] Active resources: certificatesigningrequests,configmaps,cronjobs,daemonsets,deployments,endpoints,horizontalpodautoscalers,ingresses,jobs,limitranges,mutatingwebhookconfigurations,namespaces,networkpolicies,nodes,persistentvolumeclaims,persistentvolumes,poddisruptionbudgets,pods,replicasets,replicationcontrollers,resourcequotas,secrets,services,statefulsets,storageclasses,volumeattachments
W1003 18:35:19.214974       1 reflector.go:324] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: failed to list *v2beta2.HorizontalPodAutoscaler: the server could not find the requested resource
E1003 18:35:19.215215       1 reflector.go:138] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: Failed to watch *v2beta2.HorizontalPodAutoscaler: failed to list *v2beta2.HorizontalPodAutoscaler: the server could not find the requested resource
W1003 18:35:20.685757       1 reflector.go:324] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: failed to list *v2beta2.HorizontalPodAutoscaler: the server could not find the requested resource
E1003 18:35:20.685798       1 reflector.go:138] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: Failed to watch *v2beta2.HorizontalPodAutoscaler: failed to list *v2beta2.HorizontalPodAutoscaler: the server could not find the requested resource

What you expected to happen:
I expect Kube State Metrics to not try and list a depreciated api version.

We are currently not even using any HPA

kubectl describe hpa -A
No resources found

kubectl api-versions | grep autoscaling
autoscaling/v1
autoscaling/v2

How to reproduce it (as minimally and precisely as possible):
Not really feasible to repo but this is how we got here.
Have kube running in azure with a version before 1.27.
Add HPA annotation to a pod.
later on remove HPA annotation from pods since we didn't really need it.
Update to version 1.27.9

Anything else we need to know?:

Environment:

• kube-state-metrics version:

  • Image tag docker.io/bitnami/kube-state-metrics:2.5.0-debian-11-r3

• Kubernetes version (use kubectl version):

Client Version: v1.27.9
Kustomize Version: v5.0.1
Server Version: v1.27.9

• Cloud provider or hardware configuration: Azure, 1.27.9
• Other info:

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics 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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[t3hmrman]

Hey @MattCosturos just a (very late) note -- this is solved in v2.15.0 that is out now.

[MattCosturos]

Thanks!