Traefik 3.x + Knative Serving (v1.19): kservice Returns "IngressNotConfigured"

Traefik Traefik v3 (latest)
, ,
1

Hello everyone,

I am setting up a Knative Serving environment using Traefik as the Ingress Controller, following the official Traefik documentation for the Knative provider.

  • Environment: k3s default traefik disabled

  • Knative Serving: Version v1.19

  • Traefik: Version v3.6.2 (Installed via Helm)

Problem:

The Traefik installation completes without errors, and the Traefik pods are successfully Running.

However, when I create a Knative Service, the resource consistently returns the status IngressNotConfigured. This indicates that Traefik is not processing or creating the necessary Ingress/Route for the service.

Example kservice Status:

YAML


status:
  conditions:
  - type: IngressNotConfigured
    status: "True"
    reason: "Failed to configure the networking layer."

Steps and Configurations Attempted

  1. Traefik Configuration (Based on Docs):

    • I have enabled the relevant provider flags. The arguments in my Traefik deployment are:

      --experimental.knative=true
--providers.knative=true
--providers.kubernetesingress=true
--providers.kubernetescrd=true

  2. Knative Configuration:

    • I configured Knative's config-network to explicitly use Traefik.

      YAML

      apiVersion: v1
kind: ConfigMap
metadata:
  name: config-network
  namespace: knative-serving
data:
  ingress.class: "traefik"

Additional Info

  • I have already attempted to use curl against the Traefik Load Balancer (LB), setting the Host header correctly, but I receive a 404 error. Direct access to the Knative revision works, but the general service route (kservice) does not.

Thank you!