# Helm UPGRADE FAILED: no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"

**URL:** <https://discourse.jupyter.org/t/helm-upgrade-failed-no-matches-for-kind-ingress-in-version-networking-k8s-io-v1beta1/18069>\
**Category:** BinderHub\
**Created:** [February 21, 2023, 2:37am UTC](https://discourse.jupyter.org/t/helm-upgrade-failed-no-matches-for-kind-ingress-in-version-networking-k8s-io-v1beta1/18069 "2023-02-21T02:37:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ruslan\_Ivanov](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/ruslan_ivanov/32/8437_2.png) [@Ruslan\_Ivanov](https://discourse.jupyter.org/u/Ruslan_Ivanov)\
**Post date:** [February 21, 2023, 2:37am UTC](https://discourse.jupyter.org/t/helm-upgrade-failed-no-matches-for-kind-ingress-in-version-networking-k8s-io-v1beta1/18069/1 "2023-02-21T02:37:22Z")

</div>

Hi all!

I broke my head and can’t find a clue on what’s wrong with helm upgrade procedure.  
helm upgrade --cleanup-on-fail --install binder jupyterhub/binderhub --version=0.2.0-n966.h248f390 --namespace=binder -f ./secret.fifo -f config.yaml --dry-run --debug

**Returns error:**  
resource mapping not found for name: “binderhub” namespace: “” from “”: no matches for kind “Ingress” in version “[networking.k8s.io/v1beta1](http://networking.k8s.io/v1beta1)”

helm template --verify has no reference for “[networking.k8s.io/v1beta1](http://networking.k8s.io/v1beta1)” and produces no errors.

**K8s cluster** : Azure AKS version v1.24.9

**current helm chart** : binderhub-0.2.0-n611.he777436

Any ideas where helm picking up old API reference from or how to fix it?

Thanks

---

<div class="post-metadata">

**Author:** ![manics](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/manics/32/85_2.png) [@manics](https://discourse.jupyter.org/u/manics)\
**Post date:** [February 21, 2023, 10:12am UTC](https://discourse.jupyter.org/t/helm-upgrade-failed-no-matches-for-kind-ingress-in-version-networking-k8s-io-v1beta1/18069/2 "2023-02-21T10:12:44Z")

</div>

Do you also see this error with the [latest dev release (1.0.0-0.dev.git.3018.he00ec49)](https://hub.jupyter.org/helm-chart/#development-releases-binderhub)?

---

<div class="post-metadata">

**Author:** ![Ruslan\_Ivanov](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/ruslan_ivanov/32/8437_2.png) [@Ruslan\_Ivanov](https://discourse.jupyter.org/u/Ruslan_Ivanov)\
**Post date:** [February 21, 2023, 7:19pm UTC](https://discourse.jupyter.org/t/helm-upgrade-failed-no-matches-for-kind-ingress-in-version-networking-k8s-io-v1beta1/18069/3 "2023-02-21T19:19:41Z")

</div>

Thanks for getting back to me.

Yes, the latest version also produces same error. I’ve tried many different version and getting same issue.

---

<div class="post-metadata">

**Author:** ![manics](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/manics/32/85_2.png) [@manics](https://discourse.jupyter.org/u/manics)\
**Post date:** [February 24, 2023, 4:12pm UTC](https://discourse.jupyter.org/t/helm-upgrade-failed-no-matches-for-kind-ingress-in-version-networking-k8s-io-v1beta1/18069/4 "2023-02-24T16:12:36Z")

</div>

I can’t think of any potential causes. Does it also occur with a new deployment, or only with an upgrade?

---

<div class="post-metadata">

**Author:** ![Ruslan\_Ivanov](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/ruslan_ivanov/32/8437_2.png) [@Ruslan\_Ivanov](https://discourse.jupyter.org/u/Ruslan_Ivanov)\
**Post date:** [March 7, 2023, 11:00pm UTC](https://discourse.jupyter.org/t/helm-upgrade-failed-no-matches-for-kind-ingress-in-version-networking-k8s-io-v1beta1/18069/5 "2023-03-07T23:00:49Z")

</div>

Thanks for looking into the issue.  
New deployment is working fine. I couldn’t find the issue, so redeployed the jupyterhub.  
The only tricky part was migration of user’s data, but I figured it out.