You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: stabilize InferencePool parent status reconciliation
Fixes#1331.
Inference Extension conformance can create multiple HTTPRoutes for the same InferencePool in quick succession. A reconcile can observe only one referenced Gateway through the controller cache and write a partial Parents status, then receive no later event to recompute the complete parent set.
Return a short requeue only when the InferencePool status actually changes. Status equality ignores LastTransitionTime so the follow-up reconcile converges and stops instead of looping forever.
Constraint: controller-runtime cache-backed route and gateway lists can lag related object events.
Rejected: Increasing conformance timeouts, because stale status can persist indefinitely without another reconcile.
Confidence: high
Scope-risk: moderate; changes InferencePool reconcile scheduling after status updates.
Tested: go test ./internal/controller -run TestInferencePoolController
Tested: go test ./internal/controller
Tested: make lint
Signed-off-by: liuhy <liuhongyu@apache.org>
0 commit comments