Closed MarkusGeigerDev closed 3 years ago
Figured it out myself: The ingress route above is for the "traefik" endpoint, which is not exposed by the service.
After starting kubectl port-forward pods/<name of traefik pod> 9000:9000
I was able to access the traefik dashboard locally.
But since this is a developement machine and I wanted to access the dashboard over the network, I added the following new ingress route:
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
labels:
app.kubernetes.io/instance: traefik
app.kubernetes.io/name: traefik
name: traefik-dashboard-public
namespace: kube-system
spec:
entryPoints:
- web
- websecure
routes:
- kind: Rule
match: PathPrefix(`/dashboard`) || PathPrefix(`/api`)
services:
- kind: TraefikService
name: api@internal
I have sucessfully installed v0.21.1-k3s1r0 on a Raspi 3B+ and I can see that the traefik service and its pod are doing fine.
k3s kubectl get ingressroutes --all-namespaces
reveals that there is already an ingress route for the traefik dashboard:Looking at the ingress route with
k3s kubectl describe ingressroute traefik-dashboard -n kube-system
yields:Still, if I enter
http://[external node address]/dashboard/
in the browser of another PC, I get traefik's404 page not found
message. I know that the browser is talking to the ingress controller, because I recognoze the error message as comming from traefik.What am I missing? Thanks in advance for any hints!