Health Trait
The health trait is responsible for configuring the health probes on the integration container.
It’s disabled by default.
This trait is available in the following profiles: Kubernetes, Knative, OpenShift.
Configuration
Trait properties can be specified when running any integration with the CLI:
$ kamel run --trait health.[key]=[value] --trait health.[key2]=[value2] integration.groovy
The following configuration options are available:
Property | Type | Description |
---|---|---|
|
| Can be used to enable or disable a trait. All traits share this common property. |
|
| Configures the liveness probe for the integration container (default |
|
| Scheme to use when connecting to the liveness probe (default |
|
| Number of seconds after the container has started before the liveness probe is initiated. |
|
| Number of seconds after which the liveness probe times out. |
|
| How often to perform the liveness probe. |
|
| Minimum consecutive successes for the liveness probe to be considered successful after having failed. |
|
| Minimum consecutive failures for the liveness probe to be considered failed after having succeeded. |
|
| The liveness probe path to use (default provided by the Catalog runtime used). |
|
| Configures the readiness probe for the integration container (default |
|
| Scheme to use when connecting to the readiness probe (default |
|
| Number of seconds after the container has started before the readiness probe is initiated. |
|
| Number of seconds after which the readiness probe times out. |
|
| How often to perform the readiness probe. |
|
| Minimum consecutive successes for the readiness probe to be considered successful after having failed. |
|
| Minimum consecutive failures for the readiness probe to be considered failed after having succeeded. |
|
| The readiness probe path to use (default provided by the Catalog runtime used). |
|
| Configures the startup probe for the integration container (default |
|
| Scheme to use when connecting to the startup probe (default |
|
| Number of seconds after the container has started before the startup probe is initiated. |
|
| Number of seconds after which the startup probe times out. |
|
| How often to perform the startup probe. |
|
| Minimum consecutive successes for the startup probe to be considered successful after having failed. |
|
| Minimum consecutive failures for the startup probe to be considered failed after having succeeded. |
|
| The startup probe path to use (default provided by the Catalog runtime used). |