Health Trait
The health trait is responsible for configuring the container probes on the Integration container.
this trait is enabled by default in plain-quarkus runtime, leveraging the camel-observability-services component. You can disable turning it off. |
The trait uses Camel health component in order to provide a readiness probe. You can also configure liveness and startup probes which are disabled by default. The default values (delay, timeout, etc…), whereas not specified are the default ones provided by Kubernetes.
You can also configure manually the trait parameters in order to provide a customized probes configuration.
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.yamlThe 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 dependency used). |
|
| The liveness port to use (default 8080). |
|
| 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 dependency used). |
|
| The readiness port to use (default 8080). |
|
| 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 (default 10 if not specified). |
|
| The startup probe path to use (default provided by the dependency used). |
|
| The startup port to use (default 8080). |
the variable names are "snake case" if you’re using in kamel CLI, for example trait.myParam has to be translated as -t trait.my-param |