AWS EKS - cannot access apache httpd behind a LoadBalancer

9/19/2018

I've deployed an apache httpd server in a container and am attempting to expose it externally via a LoadBalancer. Although I can log on to the local host and get the expected response (curl -X GET localhost) when I try and access the external URL exposed by the load balancer I get an Empty reply from server:

curl -X GET ad8d14ea0ba9611e8b2360afc35626a3-553331517.us-east-1.elb.amazonaws.com:5000
curl: (52) Empty reply from server

Any idea what I am missing - is there some kind of additional redirection going on that I'm unaware of?

The yaml is here:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: apache
labels:
  app: apache
spec:
  replicas: 1
selector:
  matchLabels:
    pod: apache
template:
  metadata:
    name: apachehost
    labels:
      pod: apache
    spec:
      containers:
      - name: apache
        image: myrepo/apache2
      ports:
      - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: apache
labels:
  app: apache
spec:
  type: LoadBalancer
  selector:
    pod: apache
  ports:
    - name: port1
      port: 5000
      targetPort: 80
-- revhpstinkerpinker
amazon-web-services
apache
kubernetes

2 Answers

9/20/2018

1.Check your pod running.

2.Check aws IAM and security group also may be 5000 port not open for public.Use curl command in kubernet master and check port.

3.Share a pod logs

-- raka
Source: StackOverflow

2/11/2019

check on your aws load balancer for open port of 5000 in security group for LB. as in bound rule.

check for inbound rule of load balancer.

-- Harsh Manvar
Source: StackOverflow