Add cluster custom DNS zone
add_cluster_custom_dns_zoneDeclare that a cluster also serves a DNS zone with one of the organisation's DNS credentials (the twin of ankra cluster custom-dns-zones add), so the hosts of its Ingresses in that zone are published by Ankra. With provider 'cloudflare' the credential must be an organisation Cloudflare credential (ankra org cloudflare connect); Ankra checks with Cloudflare that its token reaches the zone with DNS edit before storing anything, and the zone's external-dns runs upsert-only: it creates and updates only the records it owns and never changes or deletes a record someone else made. Refused for a zone the cluster's generated zone already covers. Requires credentials.write.
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": {
"zone": "<zone>",
"credential_name": "<credential_name>"
},
"name": "add_cluster_custom_dns_zone"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| zone | Yes | Zone to serve, e.g. ankra.cloud or apps.example.com. | |
| provider | No | Which kind of credential credential_name must be. Omit to accept whichever kind the name resolves to; name it to have a mismatch refused. | |
| cluster_id | No | UUID of the target cluster. Optional when a cluster is selected. | |
| cluster_name | No | Exact name of the target cluster. Optional when a cluster is selected. | |
| credential_name | Yes | Name of the organisation credential that publishes into the zone: a Cloudflare credential, a DNS webhook credential, or the Avura connection. |