# Elastic readiness probe faliure

**URL:** <https://discuss.elastic.co/t/elastic-readiness-probe-faliure/304725>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [May 14, 2022, 10:51am UTC](https://discuss.elastic.co/t/elastic-readiness-probe-faliure/304725 "2022-05-14T10:51:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![arieltar](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@arieltar](https://discuss.elastic.co/u/arieltar)\
**Post date:** [May 14, 2022, 10:51am UTC](https://discuss.elastic.co/t/elastic-readiness-probe-faliure/304725/1 "2022-05-14T10:51:36Z")

</div>

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:

```auto
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:

```auto
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 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 11, 2022, 10:52am UTC](https://discuss.elastic.co/t/elastic-readiness-probe-faliure/304725/2 "2022-06-11T10:52:16Z")

</div>

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