AWS EKS Fargate with Kong ingress controllar External IP

1

Hi Everyone

I deployed kong ingress controller on aws eks cluster with fargate option.
I am unable to access out application over the internet over http port.
I am keep getting -ERR_CONNECTION_TIMED_OUT in browser.

I did the Kong deployment as per steps given in -

Kong-proxy service is created wihtout issue.
kong-proxy service is created yet its “EXTERNAL-IP” is still showing pending.

Screenshot 2020-03-26 at 4.42.22 PM
Screenshot 2020-03-26 at 4.42.22 PM1574×144 16.5 KB

We are able to access our local application in internal network (by logging on to running pod) via Kong-proxy CLUSTER-IP without any problem using curl.

A nlb load balancer is also created automatically in aws console when we created kong-proxy service. Its DNS name we are using to try to connect from internet.

Kindly help me understand what could be the problem.

my kong-proxy yaml is-

apiVersion: v1
kind: Service
metadata:
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
    service.beta.kubernetes.io/aws-load-balancer-type: nlb
  name: kong-proxy
  namespace: kong
spec:
  externalTrafficPolicy: Local
  ports:
  - name: proxy
    port: 80
    protocol: TCP
    targetPort: 80
  - name: proxy-ssl
    port: 443
    protocol: TCP
    targetPort: 443
  selector:
    app: ingress-kong
  type: LoadBalancer
2

I’m not sure why this is happening, please check with AWS on why a LoadBalancer is not being attached to the service.

Also, please try to remove the AWS specific annotations from the Service resource.