Issue with the Service web-dash on Chapter 12

fmiranda

Hello,

Quick question, I followed the video on Chapter 12, and all goes well, except when trying to create a deployment via the minikube dashboard, the service keeps always on the pending state.

Any ideas what I could have done wrong ? I tried to recreate it several times using that video as a guide and it always shows the service pending. Only happens when I create via the dashboard, if I created via kubectl, all works.

`$ kubectl get all -l k8s-app=web-dash
NAME READY STATUS RESTARTS AGE
pod/web-dash-5d65954d69-m5fw9 1/1 Running 0 54s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/web-dash LoadBalancer 10.99.88.254 8080:32478/TCP 54s

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/web-dash 1/1 1 1 54s

NAME DESIRED CURRENT READY AGE
replicaset.apps/web-dash-5d65954d69 1 1 1 54s`

and

$ kubectl describe svc web-dash Name: web-dash Namespace: default Labels: k8s-app=web-dash Annotations: <none> Selector: k8s-app=web-dash Type: LoadBalancer IP Family Policy: SingleStack IP Families: IPv4 IP: 10.99.88.254 IPs: 10.99.88.254 Port: tcp-8080-80-z7d7t 8080/TCP TargetPort: 80/TCP NodePort: tcp-8080-80-z7d7t 32478/TCP Endpoints: 10.244.205.197:80 Session Affinity: None External Traffic Policy: Cluster Internal Traffic Policy: Cluster Events: <none>

fmiranda

Apparently my edits to this post did not take effect!
I will try to re-post it again, so it will be better to understand the issue

fmiranda

Okay let's try again:

I followed the video on Chapter 12, and all goes well, except when trying to create a deployment via the minikube dashboard, the service keeps always on the pending state.

Any ideas what I could have done wrong ? I tried to recreate it several times using that video as a guide and it always shows the service pending. Only happens when I create via the dashboard, if I created via kubectl, all works.

When I run the command kubectl get all - l k8s-app=web-dash I can see all the "resources" part of this deployment, including the services, and the services keeps showing me a pending state for the EXTERNAL-IP:

`NAME READY STATUS RESTARTS AGE
pod/web-dash-5d65954d69-m5fw9 1/1 Running 2 15h

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/web-dash LoadBalancer 10.99.88.254 8080:32478/TCP 15h

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/web-dash 1/1 1 1 15h

NAME DESIRED CURRENT READY AGE
replicaset.apps/web-dash-5d65954d69 1 1 1 15h
`

fmiranda

It looks like even when creating it from the command line I get this issue as well:

$ kubectl expose deployment web-dash --type=LoadBalancer --port=8080
service/web-dash exposed

$ kubectl get all -l k8s-app=web-dash
NAME READY STATUS RESTARTS AGE
pod/web-dash-5d65954d69-m5fw9 1/1 Running 2 16h

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/web-dash LoadBalancer 10.99.209.94 8080:31271/TCP 70s

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/web-dash 1/1 1 1 16h

NAME DESIRED CURRENT READY AGE
replicaset.apps/web-dash-5d65954d69 1 1 1 16h

Maybe this is an issue when using Minikube using the driver=docker ?

fmiranda

aha! I re-read everything !and I ended up fixing the issue!!!

Here is the deal:

For Minikube clusters on the Docker driver, the NodePort cannot be accessed from the host workstation due to limitations of the Docker networking model. In those scenarios, another application access option is via the minikube tunnel. This option allows the Service ClusterIP to be directly exposed on the host as an External IP. First expose the webserver application through a LoadBalancer Service, and then enable the tunnel:

$ kubectl expose deployment webserver --name=web-lb --type=LoadBalancer --port=8080

$ minikube tunnel

That last command did the magic !