pmm 3.0 helm - wrong permissions for postgresql directory

[pvstekunov]

Description

25-02-27 20:47:23.433 UTC [1218] LOG:  could not receive data from client: Connection reset by peer
2025-02-27 20:47:27.049 UTC [46] LOG:  received fast shutdown request
2025-02-27 20:47:27.053 UTC [46] LOG:  aborting any active transactions
2025-02-27 20:47:27.055 UTC [46] LOG:  background worker "logical replication launcher" (PID 81) exited with exit code 1
2025-02-27 20:47:27.057 UTC [76] LOG:  shutting down
2025-02-27 20:47:27.212 UTC [46] LOG:  database system is shut down
2025-02-27 20:48:19.296 UTC [13] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-02-27 20:48:19.296 UTC [13] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2025-02-27 20:48:20.361 UTC [361] FATAL:  data directory "/srv/postgres14" has invalid permissions
2025-02-27 20:48:20.361 UTC [361] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).

Expected Results

Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).

Actual Results

.

Version

PMM 3.0.0 helm

Steps to reproduce

helmfile.yaml

repositories:

• name: percona
  url: https://percona.github.io/percona-helm-charts/
  releases:
• name: pmm
  namespace: monitoring
  chart: percona/pmm
  installed: true

Relevant logs

Code of Conduct

• I agree to follow Percona Community Code of Conduct

[azharprabudi]

Hi @pvstekunov I also facing the same issue

The way I can fix the issue, and make the PMM server run by adding the podSecurityContext

Before

  securityContext:
    fsGroup: 1000
    runAsGroup: 1000
    runAsUser: 1000

After

securityContext:
    fsGroup: 1000
    fsGroupChangePolicy: OnRootMismatch
    runAsGroup: 1000
    runAsUser: 1000

I hope this also fixes your issue

[andrius-u]

securityContext doesn't work in my case, but works under podSecurityContext

podSecurityContext:
    fsGroup: 1000
    fsGroupChangePolicy: OnRootMismatch
    runAsGroup: 1000
    runAsUser: 1000

[azharprabudi]

yes sorry for missing out the information, I also configured it under podSecurityContext

[BupycHuk]

Thanks, created PR to helm charts percona/percona-helm-charts#499

[BupycHuk]

Fix is merged, please check