Knative Service Trait
The Knative Service trait allows to configure options when running the integration as Knative service instead of a standard Kubernetes Deployment.
Running integrations as Knative Services adds auto-scaling (and scaling-to-zero) features, but those features are only meaningful when the routes use a HTTP endpoint consumer.
This trait is available in the following profiles: Knative.
Configuration
Trait properties can be specified when running any integration with the CLI:
kamel run --trait knative-service.[key]=[value] --trait knative-service.[key2]=[value2] integration.groovyThe following configuration options are available:
| Property | Type | Description |
|---|---|---|
knative-service.enabled |
bool |
Can be used to enable or disable a trait. All traits share this common property. |
knative-service.autoscaling-class |
string |
Configures the Knative autoscaling class property (e.g. to set Refer to the Knative documentation for more information. |
knative-service.autoscaling-metric |
string |
Configures the Knative autoscaling metric property (e.g. to set Refer to the Knative documentation for more information. |
knative-service.autoscaling-target |
int |
Sets the allowed concurrency level or CPU percentage (depending on the autoscaling metric) for each Pod. Refer to the Knative documentation for more information. |
knative-service.min-scale |
int |
The minimum number of Pods that should be running at any time for the integration. It’s zero by default, meaning that the integration is scaled down to zero when not used for a configured amount of time. Refer to the Knative documentation for more information. |
knative-service.max-scale |
int |
An upper bound for the number of Pods that can be running in parallel for the integration. Knative has its own cap value that depends on the installation. Refer to the Knative documentation for more information. |
knative-service.auto |
bool |
Automatically deploy the integration as Knative service when all conditions hold:
|