kubernetes.deployment.get

Read a single Deployment's metadata, spec, and status

Reads a single Deployment from the cluster as a Kubernetes object.

If it exists, the sanitized object (apiVersion, kind, metadata, spec, status) is merged onto the workflow envelope alongside exists=True. If it is not found (404), returns exists=False and no object keys.

Inputs:

• connection_uuid: UUID of the cloud connection (required)
• namespace: Namespace the Deployment lives in (required)
• name: Deployment name (required)

Outputs:

• exists: bool
• apiVersion, kind, metadata, spec, status: the Deployment itself

Overview

Property	Value
Workflow type	Atomic
Library	App-kubernetes
Version	1.0

Input Schema

Field	Type	Required	Default	Description
connection_uuid	uuid	Yes	—	—
namespace	string	Yes	—	—
name	string	Yes	—	—
organization_uuid	uuid	No	—	—

Output Schema

Field	Type	Required	Default	Description
connection_uuid	uuid	No	—	—
organization_uuid	uuid	No	—	—
namespace	string	No	—	—
name	string	No	—	—
exists	boolean	No	—	—
apiVersion	string	No	—	—
kind	string	No	—	—
metadata	json	No	—	—
spec	json	No	—	—
status	json	No	—	—
data	json	No	—	—
binaryData	json	No	—	—
stringData	json	No	—	—
immutable	boolean	No	—	—
type	string	No	—	—
rules	json	No	—	—
aggregationRule	json	No	—	—
roleRef	json	No	—	—
subjects	json	No	—	—
failure_reason	string	No	—	—
failure_type	string	No	—	—
failed_action	string	No	—	—
failed_at_state	string	No	—	—
failed_step	string	No	—	—
failed_layer	string	No	—	—
error	string	No	—	—
error_type	string	No	—	—

States

State	Initial	Terminal	Success	Auto-advance	Description
pending	Yes	No	—	execute	—
completed	No	Yes	Yes	—	—
failed	No	Yes	No	—	—

State Diagram

Transitions

From	Action	To	Description
pending	execute	completed	—
* (any state)	fail	failed	—

API Usage

POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "kubernetes.deployment.get",
  "initial_data": {
    "connection_uuid": "value",
    "namespace": "value",
    "name": "value"
  }
}