Deploy application
deploy_applicationDeploy an Application's built chart onto a cluster: creates or updates the installation in the given namespace. Requires a published build. Check the application's existing installations first (list_application_installations). Name the target by cluster_id or by environment (id, cluster name or role) - exactly one of the two. A redeploy re-applies the same manifests, so to recover a pod stuck on a missing Secret or ConfigMap propose it only when an earlier apply failed for a cause that has since cleared (such as an admission webhook that was still starting), and say so in the proposal.
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": {
"application_id": "<application_id>"
},
"name": "deploy_application"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| inputs | No | Optional deploy input values (non-secret). | |
| namespace | No | Target namespace (defaults to the application's name). | |
| cluster_id | No | UUID of the target cluster. Pass this or environment, never both. | |
| deploy_mode | No | Optional deploy mode passed through to the deploy lane. | |
| environment | No | The target environment named the way a person names it: its id, its cluster name, or its role (staging, production). Pass this or cluster_id, never both. | |
| application_id | Yes | The Application's id. | |
| prepare_database | No | Set the application's database up for this deploy: when it declares PostgreSQL and the target cluster has no CloudNativePG operator, install Ankra's operator stack there first. Same as Set up the database on the deploy form and ankra ship --set-up-database. Needs stacks.write on the cluster. Pass it after a deploy was refused for the missing operator, or when the user asked for the database to be set up. |