Redeploy stack
redeploy_stackRedeploy a stack's resources that are stuck in a transitional state (creating, updating, stopping): re-runs their deployment jobs in dependency order. Resources already covered by an in-flight operation are skipped, and the call is a no-op when nothing is transitional. NOT reversible: the triggered deployment jobs run to completion.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"stack_name": "<stack_name>",
"cluster_id": "<cluster_id>"
},
"name": "redeploy_stack"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| force | No | Optional, default false. Set true only when a manifest's apply failed with an error reading conflict with "<manager>" and the person accepts the overwrite. The manifests among the resources this call re-runs then apply with server-side apply force-conflicts, for this redeploy only: nothing is stored on the stack. The result names them under forced_resource_ids: a manifest not listed there was not forced, so check that the one that failed is there before saying the conflict was taken back. Members this call does not re-run and add-ons are not forced, and an application member's apply forces conflicts either way. Force takes the conflicting fields back to the stack's values on the live objects and overwrites whatever they hold now, which Ankra cannot undo. before-first-apply is Kubernetes' name for fields written before Ankra's first server-side apply, not another controller, though the value may still be one a person set. Needs clusters.write on the cluster on top of stacks.deploy, and an approved plan does not cover it: it runs only as a call of its own. | |
| cluster_id | Yes | Ankra cluster id (UUID) the call targets. Discover ids with list_clusters. | |
| stack_name | Yes | Name of the stack to redeploy. |