AIServiceBackend status is not correct when updating to an invalid BSP ref name #1119
Description
Description:
AIServiceBackend status is not reliable when updating to an invalid BSP ref name, also we have a loop for all the gateway routes in the gateway reconciler and when one of the AIGatewayRoute fails to reconcile it blocks other routes to reconcile.
Repro steps:
- Initially the
gcp-us-east5-gcpanthropicAIServiceBackend was reconciled successfully and has the correct bsp ref namegcp-us-east5 - update the BackendSecurityPolicy ref to a non-existing policy ref name
gcp-us-east5-gcpanthropic - the AIServiceBackend status does not change to
NotAccepted
Environment:
0.3.0
Logs:
2025-08-24T13:37:45Z ERROR Reconciler error {"controller": "gateway", "controllerGroup": "gateway.networking.k8s.io", "controllerKind": "Gateway", "Gateway": {"name":"ai-nexus","namespace":"gateway"}, "namespace": "gateway", "name": "ai-nexus", "reconcileID": "cacfcf61-8656-4c5e-a444-93cebe6fcb33", "error": "failed to get AIServiceBackend gateway/gcp-us-east5-gcpanthropic/route/gcp.claude-opus-4/rule/0/ref/0: failed to get BackendSecurityPolicy gcp-us-east5-gcpanthropic: BackendSecurityPolicy.aigateway.envoyproxy.io \"gcp-us-east5-gcpanthropic\" not found"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler
/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:353
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem
/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:300
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.1
/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:202