Custom Gateway API - Not programmed - cannot find entrypoint

Traefik Traefik v3 (latest)
1

Hi,

i'm trying to create a custom Gateway to route my OpenTelemetry traffic in my k8s cluster.

so i'm creating the following rule :

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: collector-gateway
  namespace: default
spec:
  gatewayClassName: traefik

  # Only Routes from the same namespace are allowed.
  listeners:
    - name: otlphttp
      protocol: HTTP
      port: 4318
      allowedRoutes:
        namespaces:
          from: All

    - name: grpc
      protocol: HTTP
      port: 4317
      allowedRoutes:
        namespaces:
          from: All
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: collectorhttp
  namespace: default
spec:
  parentRefs:
    - name: collector-gateway
      sectionName: otlphttp
  rules:
    - backendRefs:
        - name: otel-collector
          port: 4318
---
apiVersion: gateway.networking.k8s.io/v1
kind: GRPCRoute
metadata:
  name: collectorgrpc
  namespace: default
spec:
  parentRefs:
    - name: collector-gateway
      sectionName: grpc
  rules:
    - backendRefs:
        - name: otel-collector
          port: 4317

since i have the jubernetesgateway enabled :

     - --providers.kubernetesgateway
        - --providers.kubernetesgateway.experimentalchannel=true

When deploying this gateway , the status is not programmed,
and the reason is Cannot find entryPoint for Gateway: no matching entryPoint for port 4318 and protocol "HTTP"

i was expecting Traefik detecting new entrypoints and creating them dynamically.

How can i add those missing entrypoints using kubernetes CRDs?

What should i do to have this custom Gateway? is it possible?

Thanks,

2

To have the gateway api working , i have added the enpoints manully in the deployments of traefik:

        - --entryPoints.grpc.address=:4317/tcp
        - --entryPoints.otlphttp.address=:4318/tcp

Not sure it's the best way of doing it , but the gateway seems to work now.