Import managed cluster
import_managed_clusterAdopt a managed Kubernetes cluster that already runs at the provider (the twin of ankra cluster managed import): Ankra fetches its kubeconfig through the provider API and installs the agent itself, so unlike import_cluster there is no command for the operator to run. Take provider_cluster_id from discover_managed_clusters. Refused when the cluster is already imported or the name is taken. The cluster reads as offline until the agent checks in.
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": {
"provider": "<provider>",
"credential_id": "<credential_id>",
"provider_cluster_id": "<provider_cluster_id>"
},
"name": "import_managed_cluster"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Name the cluster gets in Ankra. Defaults to the provider's name. | |
| provider | Yes | Managed Kubernetes provider. | |
| description | No | Optional description. | |
| environment | No | What the cluster is for. Ankra's autonomy gates treat a cluster like production until a person confirms what it is for. A label named here is that confirmation only when a member confirms this call's card in Ankra chat; over MCP, or with no member's confirmation, it is recorded as set by automation and confirms nothing (a production label is still honoured). Omit it and the cluster is labelled development, recorded as a default nobody confirmed. | |
| credential_id | Yes | UUID of the provider credential the cluster is reachable through. | |
| provider_cluster_id | Yes | The provider's cluster id (from discover_managed_clusters). |