# Kubernetes ingress regression in PMM helm chart 1.2.0

**URL:** <https://forums.percona.com/t/kubernetes-ingress-regression-in-pmm-helm-chart-1-2-0/20438>\
**Category:** PMM 2.x\
**Created:** [March 6, 2023, 1:14pm UTC](https://forums.percona.com/t/kubernetes-ingress-regression-in-pmm-helm-chart-1-2-0/20438 "2023-03-06T13:14:29Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jeff.plewes](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jeff.plewes](https://forums.percona.com/u/jeff.plewes)\
**Post date:** [September 29, 2023, 5:10pm UTC](https://forums.percona.com/t/kubernetes-ingress-regression-in-pmm-helm-chart-1-2-0/20438/6 "2023-09-29T17:10:14Z")

</div>

A work-around i provided to [PMM Server deployed on k8s - failed to establish two-way communication channel - #5 by jeff.plewes](https://forums.percona.com/t/pmm-server-deployed-on-k8s-failed-to-establish-two-way-communication-channel/22708/5)

Add this to your helm values for ingress:

```auto
  community:
    annotations:
      nginx.ingress.kubernetes.io/use-regex: "true"

```

The [nginx.ingress.kubernetes.io/use-regex:](http://nginx.ingress.kubernetes.io/use-regex:) “true” was needed to have the ingress controller use regex location blocks for ‘/agent., /inventory.’ etc… without this config, such calls to these urls would not match the location blocks in the ingress controller and instead hit the default location / and its non-grpc upstream.

---

_[View the full topic](https://forums.percona.com/t/kubernetes-ingress-regression-in-pmm-helm-chart-1-2-0/20438)._