eks.deleted-clusters.restoreRestore a deleted cluster from its final etcd snapshot
The cluster comes back under the same id and name with its settings, node groups, access entries, add-ons and pod identity associations. Deutsche Cloud builds the control plane again from the final snapshot (same CA and keys, the same endpoint name, behind a new load balancer whose address may change; kubeconfigs keep working), then the node groups’ nodes; the kept volumes attach again when their pods run; Service load balancers get new addresses. Billed and counted in the quota from the restore on. 409 when the name is taken by another cluster, the quota is full, the VPC is gone or the 7 days are over. `confirm` must be the cluster’s name.
Request syntax
POST /eks/api/deleted-clusters/{cluster}/restore
{
"confirm": "string"
}Path parameters
clusterRequiredstring
Constraints: 1-100 chars, /^[a-z0-9][a-z0-9-]*$/
Request body
confirmRequiredstring
The deleted cluster’s name, to confirm
Constraints: 1-100 chars
Response
202 with the cluster again, status `restoring`: id, name, regionId, tier, version, kubernetesVersion, availableVersion, latestPatch, status, reconcileError, endpoint, endpointIpv4, allowedCidrs, endpointPublicAccess, endpointPrivateAccess, endpointPrivateIpv4, serviceAccountIssuer, vpcId, podCidr, serviceCidr, controlPlaneNodes, deletionProtection, autoscaler, logging, support, forcedUpgrade, slaPercent, createdAt, …. 400 when `confirm` is not its name; 404 for no deleted cluster by that id or name, 403 without eks:RestoreCluster on it; 409 when several deleted clusters have the name (use the id), the retention ended, the final snapshot is gone, the name is taken, its Kubernetes minor is no longer offered, the network is gone or the quota is full.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow eks:RestoreCluster on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud eks deleted-clusters restore cluster --confirm examplecurl -X POST "https://console.platform-development.deutschecloud.app/eks/api/deleted-clusters/cluster/restore" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"confirm":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_eks_deleted-clusters_restore.