Help! Stuck in a Helm Upgrade Loop with HPA Issues

0
0
Asked By TechWiz99 On

Hey everyone, I'm facing a frustrating problem while trying to upgrade the `ingress-nginx` Helm chart on my Kubernetes cluster (version v1.30). I got this error: 'resource mapping not found for name: "ingress-nginx-controller" namespace: "ingress-nginx" from "": no matches for kind "HorizontalPodAutoscaler" in version "autoscaling/v2beta2"'. I tried running the **helm mapkubeapis** command, but it didn't resolve the issue. Rollback and upgrade attempts haven't worked either because my Helm release has "autoscaling/v2beta2" on the HPA, and I really don't want to uninstall my resources. Has anyone else experienced something similar? Can I edit Helm's release history (the Secret) to remove the problematic manifest? Any help would be greatly appreciated!

1 Answer

Answered By HelmMaster42 On

It sounds like the API version might have changed, which is causing the error. Try running `kubectl explain hpa` to get the correct version. You either need to upgrade the chart to the version that matches the output of that command or manually change the API version to match. Make sure you've updated it properly before upgrading again.

KubeGuru88 -

In my case, the hpa file's apiVersion was set to autoscaling/v2beta2. I manually changed it, but the error persisted. Even after recreating the HPA, I'm still getting the same issue with v2beta2. Seems like it's tricky to get around this.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.