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
This fix addresses the root cause of test flakiness by ensuring traffic
doesn't route through the activator during the graceful shutdown test.
The flakiness occurred when requests routed through the activator
(particularly with Kourier): deleting the Configuration triggered
Revision deletion, causing the activator's revision lookup to fail for
in-flight requests with 'revision not found' errors.
The fix sets minScale=1 and target-burst-capacity=0 to:
1. Keep the revision active (prevents scale-to-zero)
2. Route traffic directly to the pod (bypasses the activator)
This ensures the test properly validates graceful shutdown behavior
regardless of resource deletion order, which was the original intent.
0 commit comments