eks.addons.get

One add-on: version, options, status, workloads ready, upgrade available

GET /eks/api/clusters/{cluster}/addons/{name}IAM eks:DescribeAddonRead

Request syntax

GET /eks/api/clusters/{cluster}/addons/{name}

Path parameters

  • clusterRequired

    string

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

  • nameRequired

    string

Response

200 with the add-on: name, version, system, status, statusMessage, config, health, namespace, latestVersion, upgradeAvailable, createdBy, createdAt, updatedAt. 404 for an unknown cluster or an add-on the cluster does not have (403 without eks:DescribeAddon on it, checked before the add-on is looked up). System components are only in `list`.

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:DescribeAddon 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 addons get cluster name

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