eks.clusters.tokenA 10-minute Kubernetes API token for the cluster, as an ExecCredential
Needs eks:AccessKubernetesApi AND an access entry on the cluster (403 otherwise). The token carries your Deutsche Cloud identity as `ews:<username>` and your access entries as groups; `aud` is the cluster id.
Request syntax
POST /eks/api/clusters/{cluster}/tokenPath parameters
clusterRequiredstring
Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/
Response
200 with an ExecCredential: { apiVersion: "client.authentication.k8s.io/v1", kind: "ExecCredential", status: { token, expirationTimestamp } }, the shape kubectl’s exec plugin prints. 403 without eks:AccessKubernetesApi, or when the caller (or a group or role it acts through) has no access entry on the cluster; 404 for an unknown cluster.
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:AccessKubernetesApi 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 token clustercurl -X POST "https://console.platform-development.deutschecloud.app/eks/api/clusters/cluster/token" \
-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_token.