traefik ingress: service not reacheable

Question

I've just deployed traefik:

$ helm install traefik traefik/traefik --set dashboard.ingressRoute=true

I'm using a k3d cluster with 2 workers.

Once installed traefik, I've realized there are several ingress-like resources:

$ kubectl api-resources | grep ingress
NAME               SHORTNAMES   APIGROUP               NAMESPACED   KIND
ingresses          ing          extensions             true         Ingress
ingresses          ing          networking.k8s.io      true         Ingress
ingressroutes                   traefik.containo.us    true         IngressRoute
ingressroutetcps                traefik.containo.us    true         IngressRouteTCP

First question is: Why are there so many ingress-like resources?

I'm able to get access to my just desployed traefik dashboard under localhost/dashboard.

Nevertheless, I'm installed a straightforward service I'm not able to figure out why it's not reacheable.

Here, graylog.localhost ingress description:

$ kubectl describe ingresses.networking.k8s.io graylog-web
Name:             graylog-web
Namespace:        graylog
Address:          
Default backend:  default-http-backend:80 (<none>)
Rules:
  Host               Path  Backends
  ----               ----  --------
  graylog.localhost  
                     /gelf   graylog-tcp:gelf (10.42.0.24:12201,10.42.1.33:12201)
                             graylog-web:graylog (10.42.0.24:9000,10.42.1.33:9000)
Annotations:
Events:  <none>

However, when I'm trying to get access to graylog.localhost:

$ curl graylog.localhost
404 page not found

This is the deployed traefik deployment:

$ kubectl describe deployments.apps traefik
Name:                   traefik
Namespace:              kube-system
CreationTimestamp:      Sun, 08 Mar 2020 20:51:09 +0100
Labels:                 app=traefik
                        chart=traefik-4.0.0
                        heritage=Helm
                        release=traefik
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               app=traefik,release=traefik
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  1 max unavailable, 1 max surge
Pod Template:
  Labels:           app=traefik
                    chart=traefik-4.0.0
                    heritage=Helm
                    release=traefik
  Service Account:  traefik
  Containers:
   traefik:
    Image:       traefik:2.1.3
    Ports:       9000/TCP, 8000/TCP, 8443/TCP
    Host Ports:  0/TCP, 0/TCP, 0/TCP
    Args:
      --global.checknewversion=true
      --global.sendanonymoususage=true
      --entryPoints.traefik.address=:9000
      --entryPoints.web.address=:8000
      --entryPoints.websecure.address=:8443
      --api.dashboard=true
      --ping=true
      --providers.kubernetescrd
      --log.level=WARN
    Liveness:     http-get http://:9000/ping delay=10s timeout=2s period=10s #success=1 #failure=3
    Readiness:    http-get http://:9000/ping delay=10s timeout=2s period=10s #success=1 #failure=1
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   traefik-6c6c896889 (1/1 replicas created)
Events:
  Type    Reason             Age    From                   Message
  ----    ------             ----   ----                   -------
  Normal  ScalingReplicaSet  4d11h  deployment-controller  Scaled up replica set traefik-6c6c896889 to 1

And here you have traefik service description:

$ kubectl describe services traefik
Name:                     traefik
Namespace:                kube-system
Labels:                   app=traefik
                          chart=traefik-4.0.0
                          heritage=Helm
                          release=traefik
Annotations:              <none>
Selector:                 app=traefik,release=traefik
Type:                     LoadBalancer
IP:                       10.43.215.222
LoadBalancer Ingress:     172.20.0.2
Port:                     web  80/TCP
TargetPort:               web/TCP
NodePort:                 web  31000/TCP
Endpoints:                10.42.1.12:8000
Port:                     websecure  443/TCP
TargetPort:               websecure/TCP
NodePort:                 websecure  31856/TCP
Endpoints:                10.42.1.12:8443
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

Any ideas?

neer neer · Accepted Answer · 2020-03-17T21:19:45

Don't know the complete answer, but k3s comes pre-installed with traefik, so that's probably why you get so many.

traefik ingress: service not reacheable

1 Answers