[ISSUE] Pod has unbound immediate...

[KarenKawaii]

OS: Centos7
Config for .yaml files:

Hi

I was reading and recreating the installation in your blog for ELK and when I execute:

The following error is showed:

I have checked my volume and it is in pending state.

Why is this happening?
How can I know the reason why the volume claim is pending?

I would appreciate any comments about it to guide me in finding the solution.

Regards.

[Jesse Swidler]

I see you are using the ssd class - this is used with either GKE or AWS. If you are using something else, you need to figure out how to configure the storage class a different way, or you can switch back to the default every cluster has called standard.

[N F]

To follow up on this, it seems the pod cannot be scheduled due to the persistent volume claim never leaving the Pending status:

Configuration:

Enter a kubernetes namespace for the elasticsearch cluster (default='default'): elk
Enter a name for the elasticsearch cluster (default='my-es-cluster'): charge-es-cluster
Select the node size: 
1: minikube
2: 4cpu X N
3: 8cpu X N
4: 16cpu X N
[1-4]:  (default='2'): 2
Enter the number of nodes (2-9) (default='2'): 2
Enter the data volume size in GB [10-9999] (default='250'): 250

Any ideas?

UPDATE:

This issue was caused by not specifying the volume type to SSD instead of standard during cluster creation.