eks.clusters.retry-upgrade

Ask again, now, for the pre-upgrade snapshot a held upgrade waits for

POST /eks/api/clusters/{cluster}/upgrade/retryIAM eks:UpdateClusterVersionChanges stateDestructive

An upgrade replaces no machine until its own pre-upgrade etcd snapshot is verified; when that snapshot fails the upgrade is held (`upgrade.held` on the cluster) and Deutsche Cloud retries every 15 minutes. This asks now: at most once per 5 minutes, 409 while one is being taken or when nothing is held.

Request syntax

POST /eks/api/clusters/{cluster}/upgrade/retry

Path parameters

  • clusterRequired

    string

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

Response

202 with the requested pre-upgrade snapshot (status `pending`): id, kind, status, requestedBy, requestedAt, takenAt, revision, totalKeys, sizeBytes, sha256, verifiedAt, error, expiresAt. 409 when the upgrade is not held, a pre-upgrade snapshot is being taken, or the last was asked for less than 5 minutes ago. 404 when no cluster has that id or name, 403 without the permission on it.

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:UpdateClusterVersion 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 clusters retry-upgrade cluster

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_eks_clusters_retry-upgrade.