-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor probes based on performance feedback #264
Changes from 16 commits
855e5fe
6101fb7
dd9ccfc
130d95e
2e28591
13857f7
a42237b
07d5498
9667779
f7ad587
86cacc2
dbb1915
4569224
f801f6b
e078d60
81889a5
4ea9eaf
43e4311
c7e8cc1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -393,17 +393,22 @@ tier: | |
disktype: ssd | ||
``` | ||
|
||
### Liveness and readiness probes | ||
|
||
[Probes are used by Kubernetes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) to determine application health. Configure a probe for *liveness* to determine if a Pod has entered a broken state; configure it for *readiness* to determine if the application is available to be exposed. You can configure probes independently for each tier. If not explicitly configured, default probes are used during the deployment. Set the following parameters as part of a `livenessProbe` or `readinessProbe` configuration. | ||
|
||
Parameter | Description | Default value | ||
--- | --- | --- | ||
`initialDelaySeconds` | Number of seconds after the container has started before liveness or readiness probes are initiated. | `300` | ||
`timeoutSeconds` | Number of seconds after which the probe times out. | `20` | ||
`periodSeconds` | How often (in seconds) to perform the probe. Some providers such as GCP require this value to be greater than the timeout value. | `30` | ||
`successThreshold` | Minimum consecutive successes for the probe to be considered successful after it determines a failure. | `1` | ||
`failureThreshold` | The number consecutive failures for the pod to be terminated by Kubernetes. | `3` | ||
### Liveness, readiness, and startup probes | ||
|
||
[Probes are used by Kubernetes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) to determine application health. Configure a probe for *liveness* to determine if a Pod has entered a broken state; configure it for *readiness* to determine if the application is available to be exposed; configure it for *startup* to determine if a pod is ready to be checked for liveness. You can configure probes independently for each tier. If not explicitly configured, default probes are used during the deployment. Set the following parameters as part of a `livenessProbe`, `readinessProbe`, or `startupProbe` configuration. | ||
|
||
Notes: | ||
* `startupProbe` is only supported as of Kubernetes 1.18. If running a version older than 1.18, `startupProbe` will be ignored and different default values will be used for `livenessProbe` and `readinessProbe`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Kubernetes 1.18 and later supports There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done (with minor modifications) |
||
* `timeoutSeconds` cannot be greater than `periodSeconds` in some GCP environments. See [this API library from Google](https://developers.google.com/resources/api-libraries/documentation/compute/v1/csharp/latest/classGoogle_1_1Apis_1_1Compute_1_1v1_1_1Data_1_1HttpHealthCheck.html#a027a3932f0681df5f198613701a83145). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For details, see [this API library from Google] There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done |
||
* Default values are listed below in order of liveness, readiness, and startup. | ||
|
||
Parameter | Description | Default - 1.18+ | Default - pre 1.18 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Default - pre-1.18 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done |
||
--- | --- | --- | --- | ||
`initialDelaySeconds` | Number of seconds after the container has started before probes are initiated. | `0`, `0`, `10` | `200`, `30` | ||
`timeoutSeconds` | Number of seconds after which the probe times out. | `20`, `20`, `10` | `20`, `10` | ||
`periodSeconds` | How often (in seconds) to perform the probe. | `30`, `30`, `10` | `30`, `10` | ||
`successThreshold` | Minimum consecutive successes for the probe to be considered successful after it determines a failure. | `1`, `1`, `1` | `1`, `2` | ||
`failureThreshold` | The number consecutive failures for the pod to be terminated by Kubernetes. | `3`, `3`, `20` | `3`, `6` | ||
|
||
Example: | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pega supports using liveness, readiness, and startup probes to determine application health in your deployments. For an overview of these probes, see Configure Liveness, Readiness and Startup Probes .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done (with minor modifications)