> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/cli/release/clusters/kubeconfig.md).

# release clusters kubeconfig

Command reference doc for the Release CLI

Downloads the Kubernetes config file for one or more clusters

```
release clusters kubeconfig [OUT_DIR] [flags]
```

## Examples

```

Download kubeconfig file for the default cluster to the given directory:
> release clusters kubeconfig ~/.kube

Download kubeconfig file for a specific cluster to the given directory:
> release clusters kubeconfig --cluster my-cluster-context ~/.kube

Download kubeconfig file for a all clusters to the given directory:
> release clusters kubeconfig --all-clusters ~/.kube

Download kubeconfig file for a all clusters to the given directory,
overwriting existing files if present:
> release clusters kubeconfig --overwrite --all-clusters ~/.kube
```

## Options

| `--account <string>` | Account name or ID (default: $RELEASE\_ACCOUNT or "account" in config file) |
| -------------------- | --------------------------------------------------------------------------- |
| `--all-clusters`     | Download kubeconfig for all clusters                                        |
| `--cluster <string>` | Cluster context or ID                                                       |
| `--overwrite`        | Overwrite existing files                                                    |

## Options inherited from parent commands

| `--config <string>` | config file (default is $HOME/.release.yaml) |
| ------------------- | -------------------------------------------- |
| `--debug`           | enable debug logging                         |

## Related

* [release clusters](/cli/release/clusters.md) - Manage clusters


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.release.com/cli/release/clusters/kubeconfig.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.