Notes

I am trying to deploy a service and ingress for a demo service (from 'Kubernetes in Action') to an AWS EKS cluster in which the traefik ingress controller has been Helm installed.

I am able to access the traefik dashboard from the traefik.example.com hostname after manually adding the IP address of the AWS ELB provisioned by traefik to that hostname in my local /etc/hosts file.

If I describe the service and ingress of the traefik-dashboard:

$ kubectl describe svc -n kube-system traefik-dashboard

Name:              traefik-dashboard

Namespace:         kube-system

Labels:            app=traefik

                   chart=traefik-1.52.6

                   heritage=Tiller

                   release=traefik

Annotations:       <none>

Selector:          app=traefik,release=traefik

Type:              ClusterIP

IP:                10.100.164.81

Port:              <unset>  80/TCP

TargetPort:        8080/TCP

Endpoints:         172.31.27.70:8080

Session Affinity:  None

Events:            <none>



$ kubectl describe ing -n kube-system traefik-dashboard

Name:             traefik-dashboard

Namespace:        kube-system

Address:

Default backend:  default-http-backend:80 (<none>)

Rules:

Host                 Path  Backends

----                 ----  --------

traefik.example.com

                        traefik-dashboard:80 (172.31.27.70:8080)

Annotations:

Events:  <none>

The service and ingress controller seem to be using the running traefik-575cc584fb-v4mfn pod in the kube-system namespace.

Given this info and looking at the traefik docs, I try to expose a demo service through its ingress with the following YAML:

apiVersion: apps/v1beta2

kind: ReplicaSet

metadata:

name: kubia

spec:

replicas: 3

selector:

    matchLabels:

    app: kubia

template:

    metadata:

    labels:

        app: kubia

    spec:

    containers:

    - name: kubia

        image: luksa/kubia



---



apiVersion: v1

kind: Service

metadata:

name: kubia

namespace: default

spec:

selector:

    app: traefik

    release: traefik

ports:

- name: web

    port: 80

    targetPort: 8080



---



apiVersion: extensions/v1beta1

kind: Ingress

metadata:

name: kubia

namespace: default

spec:

rules:

- host: kubia.int

    http:

    paths:

    - path: /

        backend:

        serviceName: kubia

        servicePort: web

After applying this, I am unable to access the kubia service from the kubia.int hostname after manually adding the IP address of the AWS ELB provisioned by traefik to that hostname in my local /etc/hosts file. Instead, I get a Service Unavailable in the response. Describing the created resources shows some differing info.

$ kubectl describe svc kubia

Name:              kubia

Namespace:         default

Labels:            <none>

Annotations:       kubectl.kubernetes.io/last-applied-configuration:

                    {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"kubia","namespace":"default"},"spec":{"ports":[{"name":"web","por...

Selector:          app=traefik,release=traefik

Type:              ClusterIP

IP:                10.100.142.243

Port:              web  80/TCP

TargetPort:        8080/TCP

Endpoints:         <none>

Session Affinity:  None

Events:            <none>



$ kubectl describe ing kubia

Name:             kubia

Namespace:        default

Address:

Default backend:  default-http-backend:80 (<none>)

Rules:

Host       Path  Backends

----       ----  --------

kubia.int

            /   kubia:web (<none>)

Annotations:

kubectl.kubernetes.io/last-applied-configuration:  {"apiVersion":"extensions/v1beta1","kind":"Ingress","metadata":{"annotations":{},"name":"kubia","namespace":"default"},"spec":{"rules":[{"host":"kubia.int","http":{"paths":[{"backend":{"serviceName":"kubia","servicePort":"web"},"path":"/"}]}}]}}



Events:  <none>

I also notice that the demo kubia service has no endpoints, and the corresponding ingress shows no available backends.

Another thing I notice is that the demo kubia service and ingress is in the default namespace, while the traefik-dashboard service and ingress are in the kube-system namespace.

Does anything jump out to anyone? Any suggestions on the best way to diagnose it?

Many thanks in advance!

It would seem that you are missing the kubernetes.io/ingress.class: traefik that tells your Traefik ingress controller to serve for that Ingress definition.

apiVersion: extensions/v1beta1

kind: Ingress

metadata:

  name: kubia

  namespace: default

  annotations:

    kubernetes.io/ingress.class: traefik

spec:

rules:

- host: kubia.int

    http:

    paths:

    - path: /

        backend:

        serviceName: kubia

        servicePort: web

If you look at the examples in the docs you can see that the only Ingress that doesn't have annotation is traefik-web-ui that points to the Traefik Web UI.