title: Readiness and Liveness probes for elasticsearch 6.3.0 on Kubernetes failing
body: <p>I am trying to setup EFK stack on Kubernetes . The Elasticsearch version being used is 6.3.2. Everything works fine until I place the probes configuration in the deployment YAML file. I am getting error as below. This is causing the pod to be declared unhealthy and eventually gets restarted which appears to be a false restart.</p>
  
  <p>Warning Unhealthy 15s kubelet, aks-agentpool-23337112-0 Liveness probe failed: Get <a href="http://10.XXX.Y.ZZZ:9200/_cluster/health" rel="nofollow noreferrer">http://10.XXX.Y.ZZZ:9200/_cluster/health</a>: dial tcp 10.XXX.Y.ZZZ:9200: connect: connection refused</p>
  
  <p>I did try using telnet from a different container to the elasticsearch pod with IP and port and I was successful but only kubelet on the node is unable to resolve the IP of the pod causing the probes to fail.</p>
  
  <p>Below is the snippet from the pod spec of the Kubernetes Statefulset YAML. Any assistance on the resolution would be really helpful. Spent quite a lot of time on this without any clue :(</p>
  
  <p>PS: The stack is being setup on AKS cluster</p>
  
  <pre><code>      - name: es-data
          image: quay.io/pires/docker-elasticsearch-kubernetes:6.3.2
          env:
          - name: NAMESPACE
            valueFrom:
              fieldRef:
                fieldPath: metadata.namespace
          - name: NODE_NAME
            valueFrom:
              fieldRef:
                fieldPath: metadata.name
          - name: CLUSTER_NAME
            value: myesdb
          - name: NODE_MASTER
            value: "false"
          - name: NODE_INGEST
            value: "false"
          - name: HTTP_ENABLE
            value: "true"
          - name: NODE_DATA
            value: "true"
          - name: DISCOVERY_SERVICE
            value: "elasticsearch-discovery"
          - name: NETWORK_HOST
            value: "_eth0:ipv4_"          
          - name: ES_JAVA_OPTS
            value: -Xms512m -Xmx512m
          - name: PROCESSORS
            valueFrom:
              resourceFieldRef:
                resource: limits.cpu
          resources:
            requests:
              cpu: 0.25
            limits:
              cpu: 1
          ports:
          - containerPort: 9200
            name: http
          - containerPort: 9300
            name: transport
          livenessProbe:
            httpGet:
              port: http
              path: /_cluster/health
            initialDelaySeconds: 40
            periodSeconds: 10
         readinessProbe:
           httpGet:
             path: /_cluster/health
             port: http
           initialDelaySeconds: 30
           timeoutSeconds: 10 
  </code></pre>
  
  <p>The pods/containers runs just fine without the probes in place . Expectation is that the probes should work fine when set on the deployment YAMLs and the POD should not get restarted.</p>