eks.clusters.eventsThe cluster’s activity: provisioning steps, changes, control-plane reports
Request syntax
GET /eks/api/clusters/{cluster}/eventsPath parameters
clusterRequiredstring
Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/
Query parameters
sinceOptionalstring
Only events strictly after this ISO time (for polling). Default: from the first
limitOptionalnumber
At most this many events, oldest first, 1–500; default 200
Constraints: integer, 1-500
Response
200 with the cluster’s events, oldest first: id, source (control_plane | machine), level (info | warn | error), phase, message, createdAt. Without `since` that is the first 200 (or `limit`) events since the cluster was created; poll with `since` set to the last createdAt. 404 when no cluster has that id or name, 403 without the permission on it (eks:DescribeCluster).
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:DescribeCluster 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 events clustercurl -X GET "https://console.platform-development.deutschecloud.app/eks/api/clusters/cluster/events" \
-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_clusters_events.