June 18, 2022, 6:37am
I'm using below spec and as per documenation, the
standard storageClassName should be available as standard. But getting error:
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
- name: default
June 19, 2022, 6:08pm
Just to be sure: What
s in your kubectl get storageclass`?
kubectl describe pvc elasticsearch-data-quickstart-es-default-0 might be interesting.
June 19, 2022, 6:37pm
was expecting the storageclass/pv would be automatically generated by the operator?
Or should a pv be generated separately?
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
June 19, 2022, 11:28pm
storageClassName depends on your Kubernetes distribution / provider, see the
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 is probably a good starting point.
June 20, 2022, 7:17am
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
June 20, 2022, 7:43am
If you leave out the storage class in your manifest and if your cluster admin has set up a
default storage class (which is not identified by the name
standard but by an
annotation on the 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 could indeed be improved as it does not explain where the
standard storage class comes from. I will open an
issue to get this updated.
July 18, 2022, 7:58am
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.