Traefik v3.1 Dashboard + Gateway API + HTTPRoute setup?

Traefik Traefik v3 (latest)
1

Following up on the recent blog post on using the Gateway APi instead of Ingress Services.

Following the whoami deployment example it dosent show up in the HTTP Routers section in the dashboard?

I have set my rule path "/whoami" which is tested and accessible outside the cluster.
and I have already exposed and moved my other apps using the gateway api and HTTPRoute... but theyr'e not showing up.

Anyone currently using the new api with the dashboard?

kind: Deployment
apiVersion: apps/v1
metadata:
  name: whoami
  namespace: whoami
spec:
  replicas: 1
  selector:
    matchLabels:
      app: whoami
  template:
    metadata:
      labels:
        app: whoami
    spec:
      containers:
      - name: whoami
        image: traefik/whoami
---
apiVersion: v1
kind: Service
metadata:
  name: whoami
  namespace: whoami
  labels:
    app: whoami
spec:
  type: ClusterIP
  ports:
  - port: 80
    name: whoami
  selector:
    app: whoami
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: whoami-httproute
  namespace: whoami
spec:
  parentRefs:
  - name: traefik-gateway
    namespace: traefik
  hostnames:
  - whoami.example.com
  rules:
    - matches:
      - path:
          type: PathPrefix
          value: /whoami
      backendRefs:
        - name: whoami
          namespace: whoami
          port: 80

traefik.yml

kind: Deployment
apiVersion: apps/v1
metadata:
  name: traefik-deployment
  labels:
    app: traefik

spec:
  replicas: 1
  selector:
    matchLabels:
      app: traefik
  template:
    metadata:
      labels:
        app: traefik
    spec:
      serviceAccountName: traefik-account
      containers:
        - name: traefik
          image: traefik:v3.1.0
          args:
            - --api.insecure
            - --providers.kubernetesgateway
            - --providers.kubernetesingress=false
          ports:
            - name: web
              containerPort: 80
            - name: dashboard
              containerPort: 8080

@jakubhajek @bluepuma77 any thoughts?

2

I ran into this, and ended up having to set the namespacePolicy=All on the associated listener. See this value in the Helm chart for reference. Since my HTTPRoute was in a different namespace, I needed to set that to have the Gateway "see" it. Once I did that, not only did the route start working, but I also saw it in the dashboard. Hope this helps!