Percona pg operator 2.7.0 problem with pmm3

PostgreSQL
1

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

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 

  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
2

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

3

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

Did you check the documentation?

As you can see you need to use PMM_SERVER_TOKEN in your secret with PMM3.

4

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.

5

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