kubernetes.horizontalpodautoscaler.delete

Delete a namespaced Kubernetes HorizontalPodAutoscaler

Deletes a HorizontalPodAutoscaler in the given namespace. Swallows 404 so the workflow is idempotent.

Deleting an HPA does not scale the workload back down. The Deployment keeps whatever replica count the autoscaler last set, and it stays there until something writes a new one — so a teardown that removes the HPA and stops should not assume the tenant returned to its baseline size.

Inputs:

• connection_uuid: Cloud connection UUID (required)
• namespace: Target namespace (required)
• name: HorizontalPodAutoscaler name (required)

Outputs:

• namespace, name, existed: bool

Plugin required: autoscaling_v2 with delete_namespaced_horizontal_pod_autoscaler.

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	—	—
workflow_run_id	string	No	—	Engine workflow run id for DAG step execution
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	—	—
existed	boolean	No	—	—
workflow_run_id	string	No	—	Engine workflow run id for DAG step execution
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.horizontalpodautoscaler.delete",
  "initial_data": {
    "connection_uuid": "value",
    "namespace": "value",
    "name": "value"
  }
}