Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

please reopen, it's still an issue

Thank you @viceice for pointing out that the “component” label missing
As a temporary fix, in the values,
I added a component label to the matomo pod using:

podLabels:
  app.kubernetes.io/component: matomo

Disabled the provided podDisruptionBudget :

pdb:
  create: false

And then created a custom PDB matching the component using the extradeploy option available in Bitnami charts :

extraDeploy:
  - apiVersion: policy/v1
    kind: PodDisruptionBudget
    metadata:
      name: matomo-pdb
    spec:
      maxUnavailable: 1
      selector:
        matchLabels:
          app.kubernetes.io/component: matomo

Hope it can help.

fix on the road:

• [bitnami/matomo] Add missing app.kubernetes.io/component label to deployment and pdb #32774

Thank you for the PR! The team will take a look