Exercise 6.6 loadBalancer external IP in pending
suser
Posts: 49
Hello
During exercise 6.6 I am doing something wrong with my load balancer config; While the load balancer appears working correctly (I am able to access the nginx server from outside the node by web and by curl locally using both service and pod IPs), the service is listed as having a pending external IP and I dont know if this is normal (I don't see necesarly to specify the node IP as external IP in the yaml). Any help?
Yaml:
apiVersion: v1
kind: Service
metadata:
name: lb
spec:
selector:
type: nserver
ports:
- port: 80
targetPort: 80
protocol: TCP
nodePort: 31000
type: LoadBalancer
kubectl get svc:
lb LoadBalancer 10.111.157.39 <pending> 80:31000/TCP 9m18s
kubectl describe service lb
Name: lb
Namespace: default
Labels:
Annotations: kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"lb","namespace":"default"},"spec":{"ports":[{"nodePort":31000,"po...
Selector: type=nserver
Type: LoadBalancer
IP: 10.111.157.39
Port: 80/TCP
TargetPort: 80/TCP
NodePort: 31000/TCP
Endpoints: 192.168.159.113:80
Session Affinity: None
External Traffic Policy: Cluster
Events:
Thanks in advance!
Stefan
Best Answer
-
chrispokorni
Posts: 509
Hi Stefan,
Unless your Kubernetes release is configured to talk to the underlying infrastructure, such as a manager Kubernetes service, you may not have an external service listening for API requests for an external Load Balancer.
You can read more about it here:
https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer
Regards,
-Chris5