Skip to content

Commit

Permalink
Improve startup probe hint about progress deadline
Browse files Browse the repository at this point in the history
  • Loading branch information
ReToCode authored and knative-prow-robot committed Aug 9, 2024
1 parent d930661 commit 74122e5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/serving/services/configure-probing.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ Supported probe types are:
## Progress Deadline and Startup Probes
It is important to know that Knative has a deadline until a Knative Service should initially start up (or rollout). This is called [progress deadline](../configuration/deployment.md#configuring-progress-deadlines). When using Startup probes, the progress deadline is set to a value that is higher than the maximal Startup probe timeout (e.g. `initialDelaySeconds + success/failureThreshold` * `periodSeconds` * `timeoutSeconds`). Otherwise, the Startup probe might never pass before the progress deadline is reached, and the Service will never successfully start up. The Knative Service will then mark this in the status of the Service object:
It is important to know that Knative has a deadline until a Knative Service should initially start up (or rollout). This is called [progress deadline](../configuration/deployment.md#configuring-progress-deadlines). When using Startup probes, the user has to ensure that the progress deadline is set to a value that is higher than the maximum time the Startup probe can take. Consider your configuration of `initialDelaySeconds`, `success/failureThreshold`, `periodSeconds` and `timeoutSeconds` for this. Otherwise, the Startup probe might never pass before the progress deadline is reached, and the Service will never successfully start up. The Knative Service will then mark this in the status of the Service object:

```json
[
Expand Down

0 comments on commit 74122e5

Please sign in to comment.