I use a K3S Kubernetes Instance. I have installed Traefik 2.0.1 (similar to the Let's Encrypt example but without TLS support) with activated dashbord and insecure mode. I can access the dashbaord. I have installed als IngessRoute:
apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: name: simpleingressroute spec: entryPoints: - web routes: - match: Host(`debian10vm.fritz.box`) && Path(`/whoami`) kind: Rule services: - name: whoami port: 80
The Traefik Dashboard shows that the IngressRoute was successful installed.
But I can not call the service use the IngressRoute.
I have used http://debian10vm.fritz.box:8000/whoami but this does'nt work.
Another question is that I have not a fully understanding of the "Traefik - Ingress" way using the IngessRoute over the Kubernetes CRD (CustomResourceDefinition) mechanism.
Normally I would expect that a Ingress Instance would allocate a external IP so I can access a service which is running inside the kubernetes cluster.
For me it lokks like that is not the case with Traefik 2.0 in Kubernetes.
I think I'm missing a piece of information about Traefik 2.0 in Kubernetes.
It would be nice to get a hint.