Skip to content

Kubernetes

Manage your Kubernetes clusters directly from the terminal.

Terminal window
enumctl kubernetes list

Shows all clusters available in your enum account.

┌──────────────────────────────────┬──────────────┬──────────────┐
│ ID │ Name │ Project │
├──────────────────────────────────┼──────────────┼──────────────┤
│ eke-01h85x0aa0b2cm8k4fqe6jnwd1 │ production │ my-project │
│ eke-01kp2qy8nyfqb42vmyr6h8y717 │ staging │ my-project │
└──────────────────────────────────┴──────────────┴──────────────┘
Terminal window
enumctl kubernetes describe <cluster-name>

Returns details about a specific cluster.

ID eke-01kp2qy8nyfqb42vmyr6h8y717
Name production
Project my-project
Terminal window
enumctl kubernetes kubeconfig <cluster-name>

Merges the cluster’s kubeconfig into your local config (typically ~/.kube/config). You’ll be prompted before any changes are written.

After this, you can use kubectl as normal:

Terminal window
kubectl get nodes
kubectl get pods -A

If the context already exists in your kubeconfig, the operation is skipped.

Terminal window
enumctl kubernetes get-token

Outputs the current access token in Kubernetes ExecCredential format. This is called automatically by kubectl after you’ve configured access with kubeconfig — you typically don’t need to run this directly.