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
HI,
We are using KNative serving 1.11.1 with Istio Ingress gateway. We have service running for more than 7 mins without sending any status back to client. I have configured revision timeoutseconds as 1000 seconds, but i still get stream time out error on the client side after 5 minutes. We have set max revision timeout as 2400. How do i check, why my queue-proxy is not using revision timeout seconds.
Here is my service yaml:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
HI,
We are using KNative serving 1.11.1 with Istio Ingress gateway. We have service running for more than 7 mins without sending any status back to client. I have configured revision timeoutseconds as 1000 seconds, but i still get stream time out error on the client side after 5 minutes. We have set max revision timeout as 2400. How do i check, why my queue-proxy is not using revision timeout seconds.
Here is my service yaml:
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
name: test-service
namespace: testsvc
spec:
template:
metadata:
name: test-service-latest
annotations:
autoscaling.knative.dev/class: kpa.autoscaling.knative.dev
autoscaling.knative.dev/targetUtilizationPercentage: "100"
autoscaling.knative.dev/minScale: "1"
autoscaling.knative.dev/maxScale: "80"
autoscaling.knative.dev/scaleDownDelay: "30m"
Beta Was this translation helpful? Give feedback.
All reactions