KIngress stuck on Uninitialized and Unknown state with Istio

[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]

Describing the KIngress, shows the following in the status

Status:
  Conditions:
    Last Transition Time:  2025-10-19T02:01:55Z
    Message:               Waiting for load balancer to be ready
    Reason:                Uninitialized
    Status:                Unknown
    Type:                  LoadBalancerReady
    Last Transition Time:  2025-07-03T01:38:59Z
    Status:                True
    Type:                  NetworkConfigured
    Last Transition Time:  2025-10-19T02:01:55Z
    Message:               Waiting for load balancer to be ready
    Reason:                Uninitialized
    Status:                Unknown
    Type:                  Ready
  Observed Generation:     1

[BobyMCbobs]

Both HTTPRoutes (internal and external) are valid.

Status for external

Status:
  Parents:
    Conditions:
      Last Transition Time:  2025-07-03T01:38:58Z
      Message:               Route was valid, bound to 3 parents
      Observed Generation:   1
      Reason:                Accepted
      Status:                True
      Type:                  Accepted
      Last Transition Time:  2025-07-03T01:38:58Z
      Message:               All references resolved
      Observed Generation:   1
      Reason:                ResolvedRefs
      Status:                True
      Type:                  ResolvedRefs
      Last Transition Time:  2025-07-03T01:38:58Z
      Message:               All waypoints resolved
      Observed Generation:   1
      Reason:                ResolvedWaypoints
      Status:                True
      Type:                  ResolvedWaypoints
    Controller Name:         istio.io/gateway-controller
    Parent Ref:
      Group:      gateway.networking.k8s.io
      Kind:       Gateway
      Name:       gateway
      Namespace:  istio-ingress

Status for internal

Status:
  Parents:
    Conditions:
      Last Transition Time:  2025-07-03T01:38:58Z
      Message:               Route was valid
      Observed Generation:   1
      Reason:                Accepted
      Status:                True
      Type:                  Accepted
      Last Transition Time:  2025-07-03T01:38:58Z
      Message:               All references resolved
      Observed Generation:   1
      Reason:                ResolvedRefs
      Status:                True
      Type:                  ResolvedRefs
      Last Transition Time:  2025-07-03T01:38:58Z
      Message:               All waypoints resolved
      Observed Generation:   1
      Reason:                ResolvedWaypoints
      Status:                True
      Type:                  ResolvedWaypoints
    Controller Name:         istio.io/gateway-controller
    Parent Ref:
      Group:      gateway.networking.k8s.io
      Kind:       Gateway
      Name:       knative-local-gateway
      Namespace:  istio-ingress

[BobyMCbobs]

With bringing up a local environment, I've realised a thing that may be related to this issue.
I'm using proxy protocol with Istio and the Load Balancer.
When I delete the EnvoyFilter enabling proxy protocol on Istio and disable the functionality on the Load Balancer, the issue doesn't occur.

nginx being a ksvc created without proxy protocol and nginx1 being one created with it enabled:

🐚 kubectl get king
NAME     READY     REASON
nginx    True
nginx1   Unknown   Uninitialized