Hello k3d team. I got started with k3d a couple of years ago with this image

rancher/k3s:v1.25.4-k3s1

configured in my cluster-config.yaml file. With this version the Traefik dashboard (and API) were fully enabled so I was able to define an IngressRoute to enable access to the Traefik dashboard, which worked great. I just recently upgraded to image:

rancher/k3s:v1.28.8-k3s1

. I left the rest of the cluster-config.yaml and all other config files the same, including the above

IngressRoute

and attempted to access the Traefik dashboard, but I now get a

404 page not found

from Traefik. I've double-checked the in-cluster Traefik Deployment and Service in the

kube-system

namespace and they appear to be installed and running healthy. In fact, I can do a local port-forward to the

traefik

pod to port 9000 and I'm able to bring up the dashboard at

<http://localhost:9000/dashboard/>

. So I know the dashboard is up and running, but for some reason the

IngressRoute

I'd originally defined to route traffic to

name: api@internal

and

kind: TraefikService

is no longer working. Before posting here I did a bunch of digging into Traefik's docs and they seem to suggest that Traefik's API needs to be enabled, which apparently isn't by default. Does anyone know if this is a change from the previous K3S config? Would this be something I'd have to consult with folks on the k3s channel? Has anyone else ran into this? Sorry if this has already been brought up and answered. I did a search of this channel, but it looks like Slack community version is being used so there's not much of a retained history. Thanks in advance if you have any advice.