K3s: 80 port is not used, but lb stay pending

Created on 20 Nov 2019  路  5Comments  路  Source: k3s-io/k3s

Version:
k3s version v1.0.0-rc5 (99b8222e)

Describe the bug
the port 80 is not used, but lb is stay pending.
image
image
image

To Reproduce
https://github.com/dapr/samples/tree/master/2.hello-kubernetes

kind: Service
apiVersion: v1
metadata:
  name: nodeapp
  labels:
    app: node
spec:
  selector:
    app: node
  ports:
  - protocol: TCP
    port: 80
    targetPort: 3000
  type: LoadBalancer
Unscheduled kinquestion

Most helpful comment

I'm seeing the same behaviour as @Jamlee here, where the Traefik service uses random NodePorts:

kubectl get svc -n kube-system
NAME             TYPE           CLUSTER-IP    EXTERNAL-IP     PORT(S)                                     AGE
kube-dns         ClusterIP      10.43.0.10    <none>          53/UDP,53/TCP,9153/TCP                      6m18s
metrics-server   ClusterIP      10.43.83.74   <none>          443/TCP                                     6m17s
traefik          LoadBalancer   10.43.76.67   x.y.z.0         80:31916/TCP,443:31361/TCP,8080:30431/TCP   5m30s

All 5 comments

both ports 80, 443 and 8080 are used by traefik controller by default, you can check via kubectl get svc -n kube-system.

it look like that traefik not use 80 and 443 port too.
image

I'm seeing the same behaviour as @Jamlee here, where the Traefik service uses random NodePorts:

kubectl get svc -n kube-system
NAME             TYPE           CLUSTER-IP    EXTERNAL-IP     PORT(S)                                     AGE
kube-dns         ClusterIP      10.43.0.10    <none>          53/UDP,53/TCP,9153/TCP                      6m18s
metrics-server   ClusterIP      10.43.83.74   <none>          443/TCP                                     6m17s
traefik          LoadBalancer   10.43.76.67   x.y.z.0         80:31916/TCP,443:31361/TCP,8080:30431/TCP   5m30s

I have the same issue

Hello guys. I have the same issue here:

NAMESPACE     NAME                                TYPE           CLUSTER-IP     EXTERNAL-IP                                        PORT(S)                                     AGE
default       service/kubernetes                  ClusterIP      10.43.0.1      <none>                                             443/TCP                                     18h
kube-system   service/kube-dns                    ClusterIP      10.43.0.10     <none>                                             53/UDP,53/TCP,9153/TCP                      18h
kube-system   service/metrics-server              ClusterIP      10.43.47.78    <none>                                             443/TCP                                     18h
kube-system   service/traefik-prometheus          ClusterIP      10.43.13.19    <none>                                             9100/TCP                                    18h
kube-system   service/traefik                     LoadBalancer   10.43.139.50   192.168.8.22                                       80:31955/TCP,443:31719/TCP                  18h
default       service/influxdb-service-internal   ClusterIP      10.43.249.73   <none>                                             8086/TCP                                    18h
default       service/traefik-service-external    LoadBalancer   10.43.14.69    <pending>                                          80:30123/TCP,443:31403/TCP,8080:30641/TCP   15m

Service already have attributed ports, but no IP assign.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

weber-software picture weber-software  路  3Comments

Moep90 picture Moep90  路  3Comments

ubergeek801 picture ubergeek801  路  3Comments

gilkotton picture gilkotton  路  3Comments

seanmalloy picture seanmalloy  路  3Comments