PMM client 3.0.0 can't be used
Report
PMM client 3.0.0 can't be used with 2.5.1 pg-operator (helm chart). In logs show missing permissions for .../pmm2/config/pmm-agent.yaml
But the real case is that pmm2 path doesn't exist in pmm 3.0.0. It's just pmm. So path would be .../pmm/config/pmm-agent.yaml
More about the problem
In logs show missing permissions for .../pmm2/config/pmm-agent.yaml
if pmm version configured to 2.44.0 then it can't register to pmm server 3.0.0
Steps to reproduce
- deploy pmm server 3.0.0
- deploy pg-operator 2.5.1 chart and pg-db 2.5.1 chart and set pmm enabled with tag 3.0.0
- check logs for pmm client
Versions
- Kubernetes
- Operator
- Database
Anything else?
No response
Hi @GenLN !
We have a ticket open for PMM v3 support for each operator, so for PG operator I would suggest to watch this ticket: https://perconadev.atlassian.net/browse/K8SPG-719
Regards, Tomislav
Hi @GenLN, PR https://github.com/percona/percona-postgresql-operator/pull/1084 is under review now. We will add it soon.
We have released PGO v2.7.0 with PMM3 support.