Elastic readiness probe faliure

Elastic Stack Elasticsearch
1

hello , i am trying to helm install using the official elastic repo:
helm repo add elastic https://helm.elastic.co

this is my values.yaml:

clusterName: "elasticsearch"

nodeGroup: "master"

# Elasticsearch roles that will be applied to this nodeGroup

# These will be set as environment variables. E.g. node.master=true

roles:

  master: "true"

  ingest: "true"

  data: "true"

#Kubernetes replica count for the StatefulSet

replicas: 1

minimumMasterNodes: 1

clusterHealthCheckParams: 'wait_for_status=yellow&timeout=1s'

# Allows you to add any config files in /usr/share/elasticsearch/config/

# such as elasticsearch.yml

esConfig:

 elasticsearch.yml: |

   xpack.security.enabled: false

image: "docker.elastic.co/elasticsearch/elasticsearch"

imageTag: "7.12.0"

imagePullPolicy: "IfNotPresent"

esJavaOpts: "-Xms1024m -Xmx2048m"

resources:

  requests:

    cpu: "1000m"

    memory: "4Gi"

  limits:

    cpu: "1000m"

    memory: "4Gi"

networkHost: "0.0.0.0"

volumeClaimTemplate:

  accessModes:

    - ReadWriteMany

  storageClassName: elk-azurefile-sc

  resources:

    requests:

      storage: 10Gi    

persistence:

  enabled: true

  labels:

    # Add default labels for the volumeClaimTemplate of the StatefulSet

    enabled: false

  annotations: {}

protocol: http

httpPort: 9200

transportPort: 9300

sysctlVmMaxMapCount: 262144

this Is the messages i get from kubectl describe pod:

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  73s                default-scheduler  Successfully assigned elk-stack/elasticsearch-master-0 to aks-large-26770588-vmss000000
  Normal   Pulled     72s                kubelet            Container image "docker.elastic.co/elasticsearch/elasticsearch:7.12.0" already present on machine
  Normal   Created    72s                kubelet            Created container configure-sysctl
  Normal   Started    72s                kubelet            Started container configure-sysctl
  Normal   Pulled     24s (x3 over 72s)  kubelet            Container image "docker.elastic.co/elasticsearch/elasticsearch:7.12.0" already present on machine
  Normal   Created    24s (x3 over 72s)  kubelet            Created container elasticsearch
  Normal   Started    24s (x3 over 72s)  kubelet            Started container elasticsearch
  Warning  Unhealthy  13s (x2 over 43s)  kubelet            Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=yellow&timeout=1s" )
Cluster is not yet ready (request params: "wait_for_status=yellow&timeout=1s" )
  Warning  BackOff  6s (x2 over 38s)  kubelet  Back-off restarting failed container

any help on this issue would be highly appreciated :slight_smile:

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.