[bitnami/matomo] Failed to calculate the number of expected pods: jobs.batch does not implement the scale subresource

[viceice]

Name and Version

bitnami/matomo 8.0.13

What architecture are you using?

amd64

What steps will reproduce the bug?

1. Deploy chart with archive job enabled
2. See Failed to calculate the number of expected pods: jobs.batch does not implement the scale subresource warning

Are you using any custom parameters or values?

cronjobs:
  taskScheduler:
    enabled: false
  archive:
    schedule: 15 * * * *

What is the expected behavior?

Don't see that warning

What do you see instead?

Seeing the Failed to calculate the number of expected pods: jobs.batch does not implement the scale subresource warning for the PodDisruptionBudget

Additional information

It looks like the pdb is also matching the archive job because the selector label are matching all matomo pods.

I think the matomo deployment should also get the app.kubernetes.io/component label and the pdb selector should also get that added.

[carrodher]

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.

[github-actions[bot]]

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.

[github-actions[bot]]

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.

[viceice]

please reopen, it's still an issue

[no-fy]

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.

[viceice]

fix on the road:

• #32774

[javsalgar]

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