eks.versions.listList Kubernetes versions, control-plane tiers and node server types
GET /eks/api/versionsIAM eks:ListClustersRead
Request syntax
GET /eks/api/versionsResponse
200 with { defaultVersion, versions (version, kubernetes, endOfSupport, default), tiers (tier, controlPlaneNodes), nodeTypes (id, vcpu, memoryGib, diskGib, priceEuroCentsHourly, inStock, unsuitable: why it cannot run a node, or null) }. defaultVersion is what a create without `version` gets.
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:ListClusters 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 versions listcurl -X GET "https://console.platform-development.deutschecloud.app/eks/api/versions" \
-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_versions_list.