Import cluster
import_clusterImport an EXISTING Kubernetes cluster into Ankra - any distribution, any provider, anywhere (EKS, GKE, AKS, k3s, kind, on-premises). This is how a cluster that already runs is brought under Ankra management, and it is NOT the same as the create_*_cluster / create_managed_cluster tools, which provision brand-new billable cloud infrastructure. Use this one whenever the user says import, onboard, connect, add, or bring in a cluster they already have. Two steps by design: this call registers the cluster and returns import_command, the command that installs the Ankra Agent; the operator then runs it against that cluster's kubeconfig, because Ankra has no route into a cluster it has not met. The cluster reports 'offline' until the agent checks in. Only onboards NEW clusters - a name that already exists is refused rather than reconfigured. It does not connect a GitOps repository; use connect_gitops_repository afterwards for that.
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": {
"name": "<name>"
},
"name": "import_cluster"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name the cluster gets in Ankra. Alphanumeric with dashes and underscores, and unique in the organisation - an existing name is refused, not overwritten. | |
| description | No | Optional free-text description of what this cluster is for. | |
| 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 label stays empty, which every gate reads as production. |