Delay before pausing

[SkYNewZ]

Would it be possible, now or in the near future, to specify a delay between the last request to the pod and its pause? This would be to avoid unnecessary successive pause/unpause in case of batch for example.

[psschwei]

It's definitely doable (and something we were planning), though I think it'll be handled in Knative Serving rather than here.
/assign

[SkYNewZ]

Thanks for this quick reply. Would you like me to create the issue at Knative serving?

[psschwei]

No, I think it's fine here.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[psschwei]

/reopen

[knative-prow]

@psschwei: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle-stale

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[psschwei]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[psschwei]

/lifecycle frozen

[kiemtcb]

/lifecycle frozen

hi, my container is an image processing application, it takes 30s to start up. However I see "queue-proxy" container launches immediately so it make pod goes to a frozen state while my container hasn't started up yet.
i used the readinessprobe for my container so that the pod is not ready 2/2 immediately, but the "queue-proxy" container runs up and pod goes to freeze while the pod is only ready 1/2

[psschwei]

@kiemtcb as all pods are initially frozen. you might unfortunately have found a scenario where the freezer's default behavior isn't ideal...

[psschwei]

Closing this as we're archiving this repo (as discussed in #217 )