Question regarding gateway listener and port config

Traefik Traefik v3 (latest)
,
1

I’ve got a pretty basic traefik helm install which uses the following values:

logs:
  access:
    enabled: true
  level: DEBUG

nodeSelector:
  kubernetes.io/os: linux

providers:
  kubernetesIngressNginx:
    enabled: false
  kubernetesGateway:
    enabled: true
    experimentalChannel: true

experimental:
  kubernetesGateway:
    enabled: true

entryPoints:
  tcp5800:
    address: ":5800"

ports:
  tcp5800:
    port: 5800
    expose: {}
    exposedPort: 5800

and I’m attempting to create a simple gateway for this install to test traffic coming into an app on port 80. When I specify port 80 like so:

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: hj-amd5-gateway
  namespace: pw-hj-amd5-1001389117
spec:
  gatewayClassName: hj-amd5-gatewayclass
  listeners:
  - name: web
    protocol: HTTP
    port: 80
    hostname: "pw-hj-amd5.platdev2-cust-eastus.domain.com"
    allowedRoutes:
      namespaces:
        from: All

I get errors from my traefik pod:

2026-01-21T21:05:45Z ERR Gateway Not Accepted error="1 error occurred:\n\t* Cannot find entryPoint for Gateway: no matching entryPoint for port 80 and protocol "HTTP"\n\n" gateway=nginx-hj-amd5-gateway namespace=pw-hj-amd5-1001389117 providerName=kubernetesgateway

and if I change that port from 80 to 8000 then the errors go away and it looks like traffic is flowing in correctly but based on all the docs and examples I can find, it seems like this should be port 80?

Am I missing something in my helm values or gateway config?

2

It seems there is a need to configure “traefik entrypoints”.

ports:
  web:
    port: 80
    exposedPort: 80
    protocol: TCP
  websecure:
    port: 443
    exposedPort: 443
    protocol: TCP

After adding this, the Cannot find entryPoint for Gateway error went away on the gateway objects.

Perhaps I’m missing something and can be accomplished some other way that doesn’t break the gateway api abstration, but this method certainly does. I’m currently testing different implementations and this will pretty immediately eliminate traefik as an option. I’m surprised it’s listed as fully conformant if this additional configuration is required.

3

If I try to specify that in my helm chart I get errors about permission denied for traefik using those low numbered ports. I’m on Azure AKS if that matters.

4

can you share some log messages of your gateway and your newly defined entrypoints in your values.yaml?