Pipelines from a core instance (deprecated).
Last pipelines.
Pipelines before the given cursor.
Name matching pipelines.
Tag query.
tagone AND tagtwo
Desired output config format.
Include all ports, secrets and files objects in the pipeline.
Exclude internal pipelines (health-check).
OK
Create pipeline within a core instance. The pipeline name must be unique within the core instance. 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 core instance.
Create pipeline request body.
DNS label format as of defined on RFC1123
new-pipeline
deployment
Possible values: classic
Example: yaml
Possible values: null
Example: 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.
false
If true, this will automatically create a set of Pipeline checks to validate that the configured output services are reachable.
false
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.
false
if true, no ports will be automatically generated from the configuration.
false
false
The kind/type of the service associated to this port.
LoadBalancer
Possible values: 0
0
Unknown
Possible values: 0
0
Unknown
Possible values: 0
0
0
0
Created