Forum archive › Kubernetes & Helm Charts

Cannot bind to requested volume \"\": storageClassName does not match

Read-only archive. These discussions are from Tracston's earlier technical forum and are kept online because the answers are still useful. New replies are closed. Need help with something like this? Talk to us.

Question 18 Apr 2023

Problem

User tries to deploy an helm chart and gets the following error:

Cannot bind to requested volume "core-services-kafka-moshe-sharon": storageClassName does not match

Solution

Add Storage classname name to your pvc

apiVersion: v1

kind: PersistentVolumeClaim

metadata:

annotations:

pv.kubernetes.io/bind-completed: "yes"

pv.kubernetes.io/bound-by-controller: "yes"

volume.beta.kubernetes.io/storage-provisioner: openebs.io/local

volume.kubernetes.io/storage-provisioner: openebs.io/local

name: {{ .Release.Name }}-kafka-{{ .Release.Namespace }}

namespace: {{ .Release.Namespace}}

spec:

accessModes:

- ReadWriteOnce

resources:

requests:

storage: {{ .Values.kafka.storage.size }}

volumeMode: Filesystem

volumeName: {{ .Release.Name }}-kafka-{{ .Release.Namespace }}

storageClassName: standard

Attachment: commands.txt

Need this fixed properly?

We do this for a living.

Kubernetes, DevOps and platform engineering, delivered in days — not another weekend lost to a stack trace.

Start a project →