-
Bug
-
Resolution: Unresolved
-
Critical
-
1.37.0, 1.38.0
-
None
-
None
Following https://101668--ocpdocs-pr.netlify.app/openshift-serverless/latest/integrations/serverless-integrating-service-mesh/serverless-integrating-ossm-3-x-setup.html#serverless-ossm-installing-and-configuring-openshift-service-mesh-3-x_serverless-integrating-ossm-3-x-setup (from https://github.com/openshift/openshift-docs/pull/101668 )
the net istio controller doesn't seem to probe knative services, so may become Ready before the gateway has configured the route, which may cause 404 responses from the gateway.
{"severity":"INFO","timestamp":"2025-12-08T16:11:07.217207478Z","logger":"net-istio-controller.istio-ingress-controller.probe-lister","caller":"ingress/lister.go:128","message":"Skipping Gateway knative-serving/knative-ingress-gateway because it has no corresponding Service","commit":"fd41148-dirty","knative.dev/controller":"istio-ingress-controller"}
{"severity":"INFO","timestamp":"2025-12-08T16:11:07.217247414Z","logger":"net-istio-controller.istio-ingress-controller.probe-lister","caller":"ingress/lister.go:128","message":"Skipping Gateway knative-serving/knative-local-gateway because it has no corresponding Service","commit":"fd41148-dirty","knative.dev/controller":"istio-ingress-controller"}
The problem looks like the namespaces for gateways and their k8s services is inconsistent (some has "knative-serving" and other "knative-serving-ingress"
