eks.clusters.kubeconfig

The endpoint and CA a kubeconfig entry needs

GET /eks/api/clusters/{cluster}/kubeconfigIAM eks:DescribeClusterRead

`dcloud eks update-kubeconfig` writes the entry from this, with `dcloud eks get-token` as its exec plugin.

Request syntax

GET /eks/api/clusters/{cluster}/kubeconfig

Path parameters

  • clusterRequired

    string

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

Response

200 with { clusterId, name, server (https://…:6443; the private VPC address when the public endpoint is off), certificateAuthorityData (base64 PEM) }. Nothing secret. 409 while the cluster is still being created. 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 kubeconfig cluster

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