eks.addons.deleteRemove an add-on
DELETE /eks/api/clusters/{cluster}/addons/{name}IAM eks:DeleteAddonChanges stateDestructive
Its workloads and EWS-made objects go; its CRDs and your resources of them (Certificates, IngressRoutes) stay.
Request syntax
DELETE /eks/api/clusters/{cluster}/addons/{name}Path parameters
clusterRequiredstring
Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/
nameRequiredstring
Response
200 with { name, status: "deleting" }, also when it was already being removed; the cluster removes it in the background. 404 for an unknown cluster or an add-on it does not have, 403 without the permission.
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:DeleteAddon 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 delete cluster namecurl -X DELETE "https://console.platform-development.deutschecloud.app/eks/api/clusters/cluster/addons/name" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_eks_addons_delete.