Issue

I've created a Kubernetes cluster with AWS ec2 instances using kubeadm but when I try to create a service with type LoadBalancer I get an EXTERNAL-IP pending status

NAME         TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE
kubernetes   ClusterIP      10.96.0.1       <none>        443/TCP         123m
nginx        LoadBalancer   10.107.199.170  <pending>     8080:31579/TCP  45m52s

My create command is

kubectl expose deployment nginx --port 8080 --target-port 80 --type=LoadBalancer

I'm not sure what I'm doing wrong.

What I expect to see is an EXTERNAL-IP address given for the load balancer.

Has anyone had this and successfully solved it, please?

Thanks.

Solution

You need to setup the interface between k8s and AWS which is aws-cloud-provider-controller.

apiVersion: kubeadm.k8s.io/v1beta1
kind: InitConfiguration
nodeRegistration:
  kubeletExtraArgs:
    cloud-provider: aws

More details can be found:

Once you finish this setup, you will have the luxury to control not only the creation of AWS LB for each k8s service with type LoadBalancer.. But also , you will be able to control many things using annotations.

apiVersion: v1
kind: Service
metadata:
  name: example
  namespace: kube-system
  labels:
    run: example
  annotations:
     service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:xx-xxxx-x:xxxxxxxxx:xxxxxxx/xxxxx-xxxx-xxxx-xxxx-xxxxxxxxx #replace this value
     service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
spec:
  type: LoadBalancer
  ports:
  - port: 443
    targetPort: 5556
    protocol: TCP
  selector:
    app: example

Different settings can be applied to a load balancer service in AWS using annotations.

Answered By - Abdennour TOUMI

Answer Checked By - Gilberto Lyons (WPSolving Admin)

Wednesday, October 5, 2022

[SOLVED] K8s expose LoadBalancer service giving external-ip pending

Issue

Solution