# PMM Server deployed on k8s - failed to establish two-way communication channel

**URL:** <https://forums.percona.com/t/pmm-server-deployed-on-k8s-failed-to-establish-two-way-communication-channel/22708>\
**Category:** Database Monitoring and Management\
**Created:** [June 9, 2023, 5:44pm UTC](https://forums.percona.com/t/pmm-server-deployed-on-k8s-failed-to-establish-two-way-communication-channel/22708 "2023-06-09T17:44:38Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:07pm UTC](https://forums.percona.com/t/pmm-server-deployed-on-k8s-failed-to-establish-two-way-communication-channel/22708/5 "2023-09-29T17:07:24Z")

</div>

I had this same issue and was able to work-around it by adding annotations to the helm ingress values:

```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/pmm-server-deployed-on-k8s-failed-to-establish-two-way-communication-channel/22708)._