Service stuck in "pending" on EKS with Fargate

0

Hi!
I created a simple cluster and a simple deployment with service (see below).

eksctl create cluster --name artem-cluster --region eu-west-1 --fargate --profile mfa

apiVersion: apps/v1
kind: Deployment
metadata:
name: sample-app
spec:
replicas: 2
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: public.ecr.aws/nginx/nginx:1.19.6
ports:
- name: http
containerPort: 80

apiVersion: v1
kind: Service
metadata:
name: sample-service
annotations:
service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip
spec:
ports:
- port: 80
targetPort: 80
protocol: TCP
type: LoadBalancer
selector:
app: nginx

But service is stuck in <pending> state -
sample-service LoadBalancer 10.100.5.193 <pending> 80:31505/TCP 5h57m

In "describe" I see the only string:

Type Reason Age From Message


Normal EnsuringLoadBalancer 29m service-controller Ensuring load balancer

By the way, if I create service without "service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip", it created successfully, but
curl <external_ip>:80 returns empty response, so I found in docs that I should use "nlb-ip" and now stuck with it.

asked 4 years ago1.3K views
2 Answers
1
Accepted Answer

Ah in my case I didn't read through the prereqs closely enough and hadn't set up the AWS Load Balancer Controller. This is need to create an ALB or NLB targetting IP (like in Fargates case). I followed the steps here: https://aws.amazon.com/premiumsupport/knowledge-center/eks-alb-ingress-controller-fargate/

answered 4 years ago
0

Following thread. I've also run into the same issue.

answered 4 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions