Helm 3 Release Manifest — Error unable to recognize “”: no matches for kind “xxxxx” in version “xxxxx”

Recently I came across a scenario to upgrade AKS cluster version from 1.21.x to 1.22. While doing so, we upgraded all our microservices ingress API versions from “extensions/v1beta1” to “networking.k8s.io/v1” as beta versions are no longer supported.

Upgrade of AKS cluster went smooth. However when we started deployment of our microservice apis, we encountered following error:

We revalidated AKS version, ingress controller versions but everything looked fine.

To troubleshoot, I picked a new api which was not previously deployed to cluster and it got deployed successfully. This helped us to ensure that the AKS cluster configuration is correct and there is something wrong with deployment.

I focused on the error again and noticed the words “current release manifest”. This striked me that there might be a problem with HELM chart — may be caching or something else.

On further analysis, I found that in Helm 3 release data is stored as Kubernetes “Secret” in application namespace. You can list down all the secrets in application namespace by:

kubectl -n [your namespace] get secrets

This will list down all the release data secrets starting with sh.helm.release.*

Here `xxxx` is the release name of your Helm deployment. And v1, v2& v3 are the release version of your Helm…