dcloud eks clusters restore

Restore the control plane from one of the cluster’s etcd snapshots

IAM eks:RestoreClusterChanges stateAsks before it deletes (-y skips)

Every Kubernetes object returns to the snapshot; objects created since are gone. A pre-restore snapshot is taken first, so a restore can be undone. Then every control-plane machine is replaced: the API is down until the first new one has restored etcd (about 5–10 minutes), worker nodes keep running their pods and reconnect, kubeconfigs keep working (same CA and endpoint). Only verified snapshots; `confirm` must be the cluster’s name. 409 unless the cluster is active (one restore at a time, none during an upgrade or a deletion). A customer’s restore is excluded from the SLA for its first 30 minutes.

Synopsis

dcloud eks clusters restore cluster --snapshot-id snapshotId --confirm confirm

Arguments

  • <cluster>Required

    string

    Also accepted as --cluster. Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/

Flags

  • --snapshot-idRequired

    string

    A verified snapshot of this cluster (`dcloud eks snapshots list`)

    Constraints: /^etcds-[0-9a-f]{12}$/

  • --confirmRequired

    string

    The cluster’s name, to confirm: every object created after the snapshot is lost

    Constraints: 1-100 chars

Example

dcloud eks clusters restore cluster --snapshot-id example --confirm example

Generated from the API description, the same one the API checks requests against and the CLI is built from.