Kubernetes · Arazzo Workflow
Kubernetes Restart a Pod by Deleting It
Version 1.0.0
Confirm a pod is controller-owned, delete it gracefully, and watch the replacement appear.
View Spec
View on GitHub
AutomationCloud-NativeCNCFContainersDeploymentOpen-SourceOrchestrationScalingArazzoWorkflows
Provider
Workflows
restart-pod
Delete a controller-owned pod so its controller recreates it.
Reads the target pod and captures its ownerReferences, deletes it with a graceful termination period, and lists the namespace's matching pods so the freshly scheduled replacement can be observed.
1
readPod
Read the pod and capture its ownerReferences. A pod with no owner will not be recreated after deletion, so this read is the safety check.
2
deletePod
Delete the pod. The kubelet sends SIGTERM and waits the grace period before forcing termination; the owning controller schedules a replacement.
3
observeReplacement
List the pods matching the same label selector to observe the replacement pod. A new uid distinguishes the replacement from the deleted pod.
Source API Descriptions
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.