Pipelines
Pipelines (deprecated)
Pipelines from an aggregator (deprecated).
OK
DNS label format as of defined on RFC1123
"my-pipeline"
Pipeline configuration history entry.
Pipeline status history entry.
Resource profile model.
The deployment strategy to use when creating or updating changes to this pipeline.
"ghcr.io/calyptia/core/calyptia-fluent-bit:23.1.2"
the previous replica set counter
total number of checks associated with the pipeline.
total number of checks with ok status.
total number of checks with running status.
minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.
value contains the amount of change which is permitted by the policy.
ScaleUpPeriodSeconds specifies the window of time for which the policy should hold true.
value contains the amount of change which is permitted by the policy.
ScaleUpPeriodSeconds specifies the window of time for which the policy should hold true.
UtilizationCPUAverage defines the target value for average CPU utilization
UtilizationMemoryAverage defines the target value for average CPU utilization
The kind/type of the service associated to this port.
Create pipeline
Create pipeline within an aggregator. The pipeline name must be unique within the aggregator. The resource profile must exist already. If you don't provide one, it will default to "best-effort-low-resource". Use them to easily deploy configured agents to the aggregator.
DNS label format as of defined on RFC1123
"new-pipeline"
Kind of deployment used when deploying this pipeline
"ghcr.io/calyptia/core/calyptia-fluent-bit:23.1.2"
"my-resource-profile"
If true, no Pipeline checks will be auto-generated from the configuration.
If set to true:
If all checks associated with the pipeline run successfully, the status of the pipeline will be switched to CHECKS_OK and the deployment will be executed.
If any of the checks associated with the pipeline fails, the status of the pipeline will be switched to CHECKS_FAILED and the deployment of the pipeline will be blocked.
If set to false (default):
If all checks associated with the pipeline run successfully, the status of the pipeline will be switched to CHECKS_OK and the deployment will be executed.
If any of the checks associated with the pipeline fails, the status of the pipeline will be switched to CHECKS_FAILED and the deployment of the pipeline will be executed.
if true, no ports will be automatically generated from the configuration.
The kind/type of the service associated to this port.
Created
"my-pipeline"
Kind of deployment used when deploying this pipeline
Pipeline configuration history entry.
Pipeline status history entry.
Resource profile model.
Delete Pipelines
Delete pipelines from an aggregator.
Deleted