Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gcp pvc never binds #14

Open
vdamianchicon opened this issue Jan 24, 2019 · 2 comments
Open

gcp pvc never binds #14

vdamianchicon opened this issue Jan 24, 2019 · 2 comments

Comments

@vdamianchicon
Copy link

vdamianchicon commented Jan 24, 2019

Thanks for the elasticsearch operator and cluster
Pod has unbound PersistentVolumeClaims never resolves. Any suggestions?

here is my manifest

elasticsearch:
image:
repository: quay.io/pires/docker-elasticsearch-kubernetes
tag: "6.4.2"
name: efk-cluster
clientReplicas: 2
masterReplicas: 3
dataReplicas: 3
dataVolumeSize: 10Gi
javaOpts: "-Xms1024m -Xmx1024m"
zones:
- us-central1-f
- us-central1-b
- us-central1-a
resources:
requests:
memory: 1024Mi
cpu: 200m
limits:
memory: 2048Mi
cpu: '1'
storage:
storage-class-provisioner: kubernetes.io/gce-pd

@komljen
Copy link
Owner

komljen commented Jan 25, 2019

So, PVCs are created, just not bounded? Try to describe PVC and ES pods, there should be more info.

@vdamianchicon
Copy link
Author

looks like in gcp when using a multi-zone cluster, all of the node pools are replicated to those zones automatically. SO I just use a multi-zone cluster and omit the zone definition in the manifest. The reason I get a Pod has unbound PersistentVolumeClaims when declaring the zone definition in the manifest and using a multi-zone cluster, may be because of a naming convention conflict. I'm not certain : (

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants