Skip to content
Proud to collaborate with Microsoft for Startups

kubernetes.deployment.restart ​

Trigger a rollout restart of a Deployment (kubectl rollout restart equivalent)

Triggers a rollout restart of a Deployment by patching the pod-template annotation kubectl.kubernetes.io/restartedAt with an ISO 8601 UTC timestamp. This is equivalent to kubectl rollout restart and honours the Deployment's existing RollingUpdate strategy.

Inputs:

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

Outputs:

  • connection_uuid, namespace, name
  • restarted_at: ISO 8601 UTC timestamp written to the annotation
  • generation: New Deployment generation reported by the API server

Plugin required: context.get_plugin("connection").kubernetes_runner_clients(connection_uuid, organization_uuid) must expose apps_v1 with patch_namespaced_deployment.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-kubernetes
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
connection_uuidstringYes——
namespacestringYes——
namestringYes——
organization_uuiduuidNo——

Output Schema ​

FieldTypeRequiredDefaultDescription
connection_uuidstringNo——
organization_uuiduuidNo——
namespacestringNo——
namestringNo——
restarted_atstringNo——
generationintegerNo——
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

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

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