[kube-prometheus-stack] ArgoCD reports of differences in multiple places which are set by the chart

[zefferno]

Describe the bug a clear and concise description of what the bug is.

I'm encountering a strange issue with the deployment of the kube-prometheus-stack using Argo CD application. I'm consistently seeing differences in the Argo CD application, which prompts for the removal of resources and caBundle entries from the cluster. This started happening after I upgraded to version 58.7.2 (screenshot attached). I’ve attempted both downgrading and upgrading, but it hasn’t resolved the problem. Any idea what could be reason for this discrepancy?

What's your helm version?

v3.16.2

What's your kubectl version?

v1.30.5

Which chart?

kube-prometheus-stack

What's the chart version?

58.7.2

What happened?

No response

What you expected to happen?

No response

How to reproduce it?

No response

Enter the changed values of values.yaml?

No response

Enter the command that you execute and failing/misfunctioning.

Deploying the helm chart using ArgoCD application: project: default destination: server: 'https://kubernetes.default.svc' namespace: monitoring syncPolicy: automated: {} syncOptions:

• CreateNamespace=true
• ServerSideApply=true sources:
  • repoURL: 'https://prometheus-community.github.io/helm-charts' targetRevision: 58.7.2 helm: valueFiles:
    • $x/prometheus-default-values.yaml
    • $y/grafana-overlay-values.yaml
    • $z/prometheus-additional-values.yaml releaseName: prometheus-operator values: | grafana: additionalDataSources:
      • ... prometheus: prometheusSpec: retention: "[REDUCTED]" storageSpec: volumeClaimTemplate: spec: accessModes:
        • ReadWriteOnce resources: requests: storage: "[REDUCTED]" chart: kube-prometheus-stack
  • repoURL: '....' targetRevision: ... ref: ...
  • repoURL: '....' targetRevision: ... ref: ..

Anything else we need to know?

No response