# Percona pg operator 2.7.0 problem with pmm3

**URL:** <https://forums.percona.com/t/percona-pg-operator-2-7-0-problem-with-pmm3/39396>\
**Category:** PostgreSQL\
**Tags:** pmm\
**Created:** [September 17, 2025, 7:17am UTC](https://forums.percona.com/t/percona-pg-operator-2-7-0-problem-with-pmm3/39396 "2025-09-17T07:17:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maveric](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/maveric/32/19788_2.png) [@Maveric](https://forums.percona.com/u/Maveric)\
**Post date:** [September 17, 2025, 7:17am UTC](https://forums.percona.com/t/percona-pg-operator-2-7-0-problem-with-pmm3/39396/1 "2025-09-17T07:17:03Z")

</div>

Hi, I upgraded my cluster to pg-operator 2.7.0 but still have a problem with pmm3.

Pmm-client wants to get configuration from:  
/usr/local/percona/pmm2/config/pmm-agent.yaml

but correct path should be:

/usr/local/percona/pmm/config/pmm-agent.yaml

```auto
time="2025-09-17T07:15:18.878+00:00" level=info msg="Updating PMM Server address from \"monitoring-service\" to \"monitoring-service:443\"." component=setup │
│ pmm-agent is not running. │
│ Config file /usr/local/percona/pmm2/config/pmm-agent.yaml is not writable: no such file or directory. │
│ time="2025-09-17T07:15:18.882+00:00" level=info msg="'pmm-agent setup' exited with 1" component=entrypoint 

```

```auto
  pmm-client: │
     Container ID: containerd://92715518d2002fbb7327f81cea2df8b9c4a567f4cc064e2193fa49de9438065f │
     Image: docker.io/percona/pmm-client:3.3.0 │
     Image ID: docker.io/percona/pmm-client@sha256:4fa5f53dff93cf102ad3262b4097a95f980dc1a5aefa4fb80790ca5f5eb8cd90 │ │
     State: Waiting │
       Reason: CrashLoopBackOff │
     Last State: Terminated │
       Reason: Error │
       Exit Code: 1 │ │
     Liveness: http-get http://:7777/local/Status delay=60s timeout=5s period=10s #success=1 #failure=3 │
     Environment: │
       POD_NAME: test-pg-db-test-5f75-0 (v1:metadata.name) │
       POD_NAMESPACE: percona-pg (v1:metadata.namespace) │
       PMM_USER: api_key │
       PMM_SERVER: monitoring-service │ │
       PMM_AGENT_SERVER_USERNAME: api_key │ │
       PMM_AGENT_LISTEN_PORT: 7777 │
       PMM_AGENT_PORTS_MIN: 30100 │
       PMM_AGENT_PORTS_MAX: 30105 │
       PMM_AGENT_CONFIG_FILE: /usr/local/percona/pmm2/config/pmm-agent.yaml │
       PMM_AGENT_LOG_LEVEL: info 

```

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [September 17, 2025, 4:51pm UTC](https://forums.percona.com/t/percona-pg-operator-2-7-0-problem-with-pmm3/39396/2 "2025-09-17T16:51:32Z")

</div>

Hello, our operators are currently not compatible with PMM3. We will be publishing updated operators within this quarter to make them PMMv3 compatible.

---

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [September 22, 2025, 1:37pm UTC](https://forums.percona.com/t/percona-pg-operator-2-7-0-problem-with-pmm3/39396/3 "2025-09-22T13:37:07Z")

</div>

@Maveric We have added support of PMM3 in PGO 2.7.0. It should work.

Did you check the documentation?

> **[Percona Operator for PostgreSQL - Percona Operator for PostgreSQL 2.7.0...](https://docs.percona.com/percona-operator-for-postgresql/2.0/ReleaseNotes/Kubernetes-Operator-for-PostgreSQL-RN2.7.0.html?h=pmm3#pmm3-support)**
>
> Get started with the Operator

> **[Percona Operator for PostgreSQL - 5 Monitor the database with PMM](https://docs.percona.com/percona-operator-for-postgresql/2.0/monitoring-tutorial.html#install-pmm-server)**
>
> Finally, when we are done with backup, it’s time for one more step.
> In this section you will learn how to monitor the health of Percona Distribution for PostgreSQL with Percona Monitoring and Management (PMM) .

As you can see you need to use PMM\_SERVER\_TOKEN in your secret with PMM3.

---

<div class="post-metadata">

**Author:** ![Maveric](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/maveric/32/19788_2.png) [@Maveric](https://forums.percona.com/u/Maveric)\
**Post date:** [September 25, 2025, 12:31pm UTC](https://forums.percona.com/t/percona-pg-operator-2-7-0-problem-with-pmm3/39396/4 "2025-09-25T12:31:05Z")

</div>

Yes, that was it !!! ;-). Thanks a lot.

So if you create secret with PMM\_SERVER\_KEY it means you want to use PMM2,  
and if with PMM\_SERVER\_TOKEN it means you want to use PMM3 ?

BR.

---

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [September 28, 2025, 1:40pm UTC](https://forums.percona.com/t/percona-pg-operator-2-7-0-problem-with-pmm3/39396/5 "2025-09-28T13:40:54Z")

</div>

@Maveric Yes, it is how operators automatically detects PMM version 🙂