[kube-prometheus-stack] Shards PVC has too long name so that it cannot be provisioned

[kworkbee]

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

I'm deploying Prometheus via kube-prometheus-stack helm chart on AWS EKS environment, but operator is giving too long PVC name even though fullnameOverride value is short. Therefore, there's an issue that PVC cannot be provisioned.

What's your helm version?

3.14.3

What's your kubectl version?

1.28.2

Which chart?

kube-prometheus-stack

What's the chart version?

55.8.1

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.

Sync through ArgoCD

Anything else we need to know?

No response

[zeritti]

Setting volumeClaimTemplate.metadata.name may help: #3392 (comment)

[kworkbee]

@zeritti It works! Thanks for your help 😄

[kworkbee]

Some of them still have long names...

[kworkbee]

AWS EFS access points have a limit of 100 characters for the full path, as described here
https://docs.aws.amazon.com/efs/latest/ug/efs-access-points.html#enforce-root-directory-access-point

But already unique id occupies 36 characters, so we have to track this issue

[kworkbee]

Aside from such issues, it certainly seems problematic that Prometheus is repeated in the currently generated PVC naming.

[jkroepke]

This to set the value

helm-charts/charts/kube-prometheus-stack/values.yaml

Line 4695 in e0c3624

cleanPrometheusOperatorObjectNames: false

to true.

Other note: Please mention that it expected that the TSDB (prometheus database) may get corrupt on NFS based volumes, since it not an supported file storage.

[kworkbee]

@jkroepke It solved clearly. Thank you for your help.