You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 : (
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
The text was updated successfully, but these errors were encountered: