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 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