Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LoadBalancer Service has pending IP address #4113

Closed
Industrial opened this issue Apr 18, 2019 · 8 comments
Closed

LoadBalancer Service has pending IP address #4113

Industrial opened this issue Apr 18, 2019 · 8 comments
Labels
area/tunnel Support for the tunnel command co/service issues related to the service feature

Comments

@Industrial
Copy link

Hi!

I have read #2834 but that does not solve my issue:

When I run kubectl expose deployment test-deployment-nginx --type=LoadBalancer --name=nginx-example

and then look at the services with kubectl get svc then:

NAME            TYPE           CLUSTER-IP    EXTERNAL-IP   PORT(S)        AGE
kubernetes      ClusterIP      10.96.0.1     <none>        443/TCP        23h
nginx-example   LoadBalancer   10.96.11.32   <pending>     80:31378/TCP   3h10m

You can see it does not get an external IP.

For this reason the minikube service nginx-example does not work. I get a connection error.

@dvdmuckle
Copy link
Contributor

minikube does not come with anything that can spin up a service type of LoadBalancer. You can install something like metallb to enable this. https://metallb.universe.tf/tutorial/minikube/

@afbjorklund
Copy link
Collaborator

@dvdmuckle : minikube tunnel does provide a LoadBalancer, but for some reason it's not working here

@tstromberg
Copy link
Contributor

@Industrial - What happens when you run minikube tunnel?

@tstromberg
Copy link
Contributor

Also, do you mind providing the full output of minikube service nginx-example - you mentioned it returns a connection error.

@tstromberg tstromberg added area/tunnel Support for the tunnel command co/service issues related to the service feature labels Apr 22, 2019
@tstromberg
Copy link
Contributor

@balopat - Mind chiming in here? Is the normal state for a service until the tunnel is started?

@Industrial
Copy link
Author

The solution is to use minikube tunnel. This was not apparent for me following guide, docs, etc, up to the point of making the ticket.

@BenedictAdamson
Copy link

minikube does not come with anything that can spin up a service type of LoadBalancer.

And I guess even doing minikube addons enable ingress does not spin up that service, either (?)

amdickow added a commit to amdickow/accountservice that referenced this issue Nov 16, 2019
Prerequisites:
Requires a local registry for the docker image.
Minikube and kubectl installed.

How to deploy:
$ make release-docker-image
$ make deploy-k8s

Since minikube does not automatically know how to bring a LoadBalancer service up.
Use minikube tunnel to fix that - in a separate terminal run the following command to tunnel the deployment:
$ minikube tunnel

Good blog post on kubernetes deployments:
https://medium.com/google-cloud/kubernetes-101-pods-nodes-containers-and-clusters-c1509e409e16
https://medium.com/google-cloud/kubernetes-110-your-first-deployment-bf123c1d3f8
https://medium.com/google-cloud/kubernetes-120-networking-basics-3b903f13093a

Fix for LoadBalancer Service has <pending> IP address - 'minikube tunnel':
kubernetes/minikube#4113
@abdabughazaleh
Copy link

First of all, make sure from the listening port in your application and what port are you set when writing the command after that execute the minikube tunnel command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tunnel Support for the tunnel command co/service issues related to the service feature
Projects
None yet
Development

No branches or pull requests

6 participants