You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug a clear and concise description of what the bug is.
In my values.yaml, i've set the value of prometheus.prometheusSpec.storageSpec.volumeClaimTemplate.spec.storageClassName to longhorn-static (which is an existing storage class in my cluster), but the generated PVC by the prometheus-kube-prometheus-stack StatefulSet has longhorn as its storage class.
Here are all the storage classes present on my cluster:
Describe the bug a clear and concise description of what the bug is.
In my
values.yaml
, i've set the value ofprometheus.prometheusSpec.storageSpec.volumeClaimTemplate.spec.storageClassName
tolonghorn-static
(which is an existing storage class in my cluster), but the generated PVC by theprometheus-kube-prometheus-stack
StatefulSet haslonghorn
as its storage class.Here are all the storage classes present on my cluster:
What's your helm version?
v3.16.3
What's your kubectl version?
Client Version: v1.31.2 Kustomize Version: v5.4.2 Server Version: v1.29.3+k3s1
Which chart?
kube-prometheus-stack
What's the chart version?
67.8.0
What happened?
No response
What you expected to happen?
I expect the generated PVC to have the
storageClassName
I provided in thevalues.yaml
How to reproduce it?
No response
Enter the changed values of values.yaml?
Enter the command that you execute and failing/misfunctioning.
N/A (deployed using ArgoCD)
Anything else we need to know?
I'm using
k3s
,ArgoCD
andLonghorn
in my clusterThe text was updated successfully, but these errors were encountered: