# ECK Operator - unbound immediate PersistentVolumeClaims error
**URL:** https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558
**Category:** Elastic Cloud on Kubernetes (ECK)
**Created:** [June 18, 2022, 6:37am UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558 "2022-06-18T06:37:01Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@kelk](https://discuss.elastic.co/u/kelk)
#### Post date: [June 18, 2022, 6:37am UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558/1 "2022-06-18T06:37:01Z")
I'm using below spec and as per documenation, the `standard` storageClassName should be available as standard. But getting error:
```auto
Warning FailedScheduling 18s default-scheduler 0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.
```
I've installed the ECK 2.2.0 operator and below is the Elastic yaml
```auto
---
apiVersion: v1
kind: Namespace
metadata:
name: "elk"
---
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
name: quickstart
namespace: elk
spec:
version: 8.2.3
nodeSets:
- name: default
count: 2
volumeClaimTemplates:
- metadata:
name: elasticsearch-data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 2Gi
storageClassName: standard
---
```
---
### Author:  [@xeraa](https://discuss.elastic.co/u/xeraa)
#### Post date: [June 19, 2022, 6:08pm UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558/2 "2022-06-19T18:08:21Z")
Just to be sure: What`s in your `kubectl get storageclass`?
Also `kubectl describe pvc elasticsearch-data-quickstart-es-default-0` might be interesting.
---
### Author:  [@kelk](https://discuss.elastic.co/u/kelk)
#### Post date: [June 19, 2022, 6:37pm UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558/3 "2022-06-19T18:37:30Z")
was expecting the storageclass/pv would be automatically generated by the operator?
Or should a pv be generated separately?
```auto
kubectl -n elk get storageclass
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 59d
```
NO pvc was generated
As mentioned, I was just following the documenation & examples in the Elastic [Quickstart](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-quickstart.html)
---
### Author:  [@xeraa](https://discuss.elastic.co/u/xeraa)
#### Post date: [June 19, 2022, 11:28pm UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558/4 "2022-06-19T23:28:34Z")
IMO the `storageClassName` depends on your Kubernetes distribution / provider, see the [Kubernetes docs](https://kubernetes.io/docs/concepts/storage/storage-classes/).
And if I remember correctly, you need to either pick an existing storage class or create the one you want to use (and it should also be an optional setting). [Volume claim templates | Elastic Cloud on Kubernetes [2.2] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-volume-claim-templates.html) is probably a good starting point.
---
### Author:  [@kelk](https://discuss.elastic.co/u/kelk)
#### Post date: [June 20, 2022, 7:17am UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558/5 "2022-06-20T07:17:19Z")
Agree in case of pure k8s implementation, but we are speaking about Elastic/ECK operator. If you look into similar operator providers like Splunk all of the pv is built-in
My feedback/request was, this is NOT the case in ECK operator and warning is not provided in the documentation. I could have created a PV and attached, but as mentioned would expect the docs to reflect similar
---
### Author:  [@pebrc](https://discuss.elastic.co/u/pebrc)
#### Post date: [June 20, 2022, 7:43am UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558/6 "2022-06-20T07:43:31Z")
If you leave out the storage class in your manifest and if your cluster admin has set up a [default storage class](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1) (which is not identified by the name `standard` but by an [annotation on the storage class](https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/) ) it will work without any explicit storage class setup.
Our Quickstart example does not have an explicit `volumeClaimTemplate` but the documentation you linked to [Volume claim templates | Elastic Cloud on Kubernetes [2.2] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-volume-claim-templates.html) could indeed be improved as it does not explain where the `standard` storage class comes from. I will open an [issue](https://github.com/elastic/cloud-on-k8s/issues/5800) to get this updated.
---
### Author:  [@kelk](https://discuss.elastic.co/u/kelk)
#### Post date: [June 20, 2022, 7:57am UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558/7 "2022-06-20T07:57:53Z")
thanks for that.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 18, 2022, 7:58am UTC](https://discuss.elastic.co/t/eck-operator-unbound-immediate-persistentvolumeclaims-error/307558/8 "2022-07-18T07:58:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.