Repository navigation
[pipeline-manager] Add GET /pipelines/{name}/deployment - #7490
Conversation
|
What I ran
Gates
Uncovered cases (see the inline comments for the details)
Docs: the endpoint is behind an unstable flag and documented through OpenAPI. That is fine for now, but it needs a docs page before the flag is removed. |
c2f42ed to
06fef83
Compare
06fef83 to
ff54511
Compare
ff54511 to
5043342
Compare
|
Review: What I ran:
What looks good: the runner route sits behind the mTLS Test cases the PR does not cover:
Gates: no |
7ad60c0 to
8ced31e
Compare
|
Replies to the review summaries:
|
Desired and current CPU, memory, and storage per host, with kstatus states. The default executor returns the spec only.
8ced31e to
e91d147
Compare
Signed-off-by: feldera-bot <feldera-bot@feldera.com>
The docs site compiles OpenAPI descriptions as MDX, where <https://...> is a tag.
|
Verdict: infrastructure flake, not this PR. Confidence: high.
Opened #7961 to track this occurrence (new data point: longest recorded compile yet, 1133.8s, ending in a 503 rather than a timeout). Next step: re-queueing should pass — nothing to fix in this PR. |
Read-only endpoint that shows what the runner's platform has for a pipeline now: desired and current CPU, memory, and storage per host, with a state, reason, and message for each.
/logs. The default executor returns the spec only. The Kubernetes runner (feldera/cloud#2088) fills in the status.Endpoint
GET /v0/pipelines/{pipeline_name}/deploymentPipelineDeploymentErrorResponse/deploymentroute)ErrorResponseErrorResponseSchema
?marks a field that can be absent or null.DeploymentSpecResourcesCopied from the pipeline's
deployment_config.resources. Each*_minis a Kubernetes request and each*_maxa limit.cpu_cores_min1cpu_cores_max2memory_min"1G"memory_max"2G"storage_min"10G"storage_max"100G"Transition fields (flattened into
computeandstorage)stateDeploymentStatereasonPodResizePending,VolumeNotExpandedmessagelast_transition_timestate(KuberneteslastTransitionTime)ComputeResourcesandStorageResourcesNormalized units, so
desiredandcurrentcompare directly.ComputeResourcescpu_cores_min,cpu_cores_maxmemory_mb_min,memory_mb_maxStorageResourcesstorage_mbEnums
DeploymentStateCurrentInProgressFailedTerminatingNotFoundUnknownResourceManagerUserdesiredAutoscalerdesired, within the configured boundsTop-level
status.stateLike kstatus
AggregateStatus. Each object is compared with the state the pipeline lifecycle expects for it:ProvisionedCurrentStoppedNotFoundInUseCurrentClearingorClearedNotFoundstatus.statereason,messagefromFailedFailedUnknownUnknownInProgressNotFoundif nothing is expected to exist, elseCurrentExample
A running single-host pipeline during an in-place CPU scale-down (Kubernetes runner):
{ "spec": { "resources": { "cpu_cores_min": 1, "cpu_cores_max": 2, "memory_min": "4G", "memory_max": "8G", "storage_min": "10G", "storage_max": null } }, "status": { "state": "InProgress", "reason": "InProgress", "hosts": [ { "ordinal": 0, "compute": { "state": "InProgress", "reason": "InProgress", "last_transition_time": "2026-11-03T19:40:00Z", "manager": "User", "desired": {"cpu_cores_min": 1, "cpu_cores_max": 2, "memory_mb_min": 4000, "memory_mb_max": 8000}, "current": {"cpu_cores_min": 4, "cpu_cores_max": 8, "memory_mb_min": 4000, "memory_mb_max": 8000} }, "storage": { "state": "Current", "message": "PVC is Bound", "manager": "User", "desired": {"storage_mb": 10000}, "current": {"storage_mb": 10000} } } ] } }With the default executor the response is
{"spec": {...}}only.