# ECK on AWS EKS: Readiness probe failed when using ingress and nodeport for es

**URL:** <https://discuss.elastic.co/t/eck-on-aws-eks-readiness-probe-failed-when-using-ingress-and-nodeport-for-es/264354>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [February 15, 2021, 7:51pm UTC](https://discuss.elastic.co/t/eck-on-aws-eks-readiness-probe-failed-when-using-ingress-and-nodeport-for-es/264354 "2021-02-15T19:51:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vinnar](https://avatars.discourse-cdn.com/v4/letter/v/bb73d2/32.png) [@vinnar](https://discuss.elastic.co/u/vinnar)\
**Post date:** [February 15, 2021, 7:51pm UTC](https://discuss.elastic.co/t/eck-on-aws-eks-readiness-probe-failed-when-using-ingress-and-nodeport-for-es/264354/1 "2021-02-15T19:51:58Z")

</div>

Hi Guys,  
I am trying to setup an elastic-kibana stack on EKS, starting with the quickstart template and then making changes incrementally to make it more suitable for the environment.  
For the es, I started with the ClusterIP type (default) and then with loadbalancer type - able to access the endpoint URLs in both cases as expected.  
However, when I try to use the NodePort service type, I am getting 'Readiness probe failed' error on the pod and a 503 Service Temporarily available in the browser.  
I have the AWS ingress controller installed in the cluster  
Can anyone please share pointers on what I might be missing in the specs that could be causing this?

Below are my specs:  
Created ECK using  
`kubectl apply -f https://download.elastic.co/downloads/eck/1.3.1/all-in-one.yaml`  
Created elastic stack using  
`kubectl apply -f elastic.yml`  
elastic.yml file:

```
# Elastic Deployment
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: elastic
spec:
  version: 7.10.2
  nodeSets:
  - name: masters
    count: 1
    config:
      node.roles: ["master"]
    podTemplate:
      spec:
        containers:
        - name: elasticsearch
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 6Gi
        storageClassName: gms-cluster-storage-01
---
# Elastic Service
apiVersion: v1
kind: Service
metadata:
  name: elastic-service
spec:
  selector:
    app: elastic
  ports:
    - protocol: TCP
      port: 80
      targetPort: 9200
  type: NodePort
---
# Elastic Ingress
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  namespace: default
  name: elastic
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/target-type: ip
spec:
  rules:
    - http:
        paths:
          - path: /*
            backend:
              serviceName: elastic-service
              servicePort: 80
```

---

<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:** [March 15, 2021, 7:52pm UTC](https://discuss.elastic.co/t/eck-on-aws-eks-readiness-probe-failed-when-using-ingress-and-nodeport-for-es/264354/2 "2021-03-15T19:52:32Z")

</div>

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