KIngress fails to reconcile with Cilium Gateway

[divanikus]

Since Cilium supports Gateway API up to 1.2.1 as of now, I'm trying to use it as Gateway for Knative.

Even though it does work, I can curl my service and it does respond, the KIngress state in Uninitialized state forever. Seems like this is because of Cilium Gateways report dummy IP:Port for it's endpoint, which is 192.192.192.192:9999

"logger":"net-gateway-api-controller","caller":"status/status.go:463","message":"Probing of http://hello.default.svc.cluster.local/ failed, IP: 192.192.192.192:9999, ready: false, error: error roundtripping http://hello.default.svc.cluster.local/: context deadline exceeded (depth: 0)"

Completely disabling this part of the code does help though: https://github.com/knative-extensions/net-gateway-api/blob/main/pkg/reconciler/ingress/lister.go#L64-L107

Probably you should reconsider your method of getting IP:Port for a gateway. At least for Cilium.

Cilium version: 1.17.0
Knative version: 1.17.0

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[BobyMCbobs]

Having the same issue on Knative Serving v1.19.6 + net-gateway-api v1.19.5 + gateway-api v1.3.0 + Istio v1.27.2.

Seeing

{"severity":"INFO","timestamp":"2025-10-20T21:51:26.339781205Z","logger":"net-gateway-api-controller","caller":"status/status.go:417","message":"Processing probe for http://nginx-apps-public.svc.bobymcbobs-infra.islive.xyz/, IP: 10.244.2.177:80 (depth: 0)","commit":"2fe8547-dirty","knative.dev/pod":"net-gateway-api-controller-58dbc6fb5d-z5rxv","knative.dev/controller":"knative.dev.net-gateway-api.pkg.reconciler.ingress.Reconciler","knative.dev/kind":"networking.internal.knative.dev.Ingress","knative.dev/traceid":"91454958-5e04-4de7-8d4f-bc44c5aa7431","knative.dev/key":"apps-public/nginx"}
{"severity":"ERROR","timestamp":"2025-10-20T21:51:26.341046517Z","logger":"net-gateway-api-controller","caller":"status/status.go:463","message":"Probing of http://nginx-apps-public.svc.bobymcbobs-infra.islive.xyz/ failed, IP: 10.244.2.177:80, ready: false, error: error roundtripping http://nginx-apps-public.svc.bobymcbobs-infra.islive.xyz/: read tcp 10.244.1.17:52280->10.244.2.177:80: read: connection reset by peer (depth: 0)","commit":"2fe8547-dirty","knative.dev/pod":"net-gateway-api-controller-58dbc6fb5d-z5rxv","knative.dev/controller":"knative.dev.net-gateway-api.pkg.reconciler.ingress.Reconciler","knative.dev/kind":"networking.internal.knative.dev.Ingress","knative.dev/traceid":"91454958-5e04-4de7-8d4f-bc44c5aa7431","knative.dev/key":"apps-public/nginx","stacktrace":"knative.dev/net-gateway-api/pkg/status.(*Prober).processWorkItem\n\tknative.dev/net-gateway-api/pkg/status/status.go:463\nknative.dev/net-gateway-api/pkg/status.(*Prober).Start.func1\n\tknative.dev/net-gateway-api/pkg/status/status.go:343"}

And

🐚 kubectl get king -A
NAMESPACE     NAME                          READY     REASON
apps-public   nginx                         Unknown   Uninitialized

My environment

• Knative Serving
• Istio Ingress
• Gateway

[BobyMCbobs]

/reopen
/remove-lifecycle stale

[knative-prow]

@BobyMCbobs: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle stale

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.