
Now if we run `airshipctl cluster get-kubeconfig` without args it will return kubeconfig for the entire site, which will have contexts for every cluster defined in cluster map. Relates-To: #460 Closes: #460 Change-Id: Icf1f09724a5c60ac520b1dbcbda69c3280ac4c7e
46 lines
1.1 KiB
Markdown
46 lines
1.1 KiB
Markdown
## airshipctl cluster get-kubeconfig
|
|
|
|
Retrieve kubeconfig for a desired cluster
|
|
|
|
### Synopsis
|
|
|
|
Retrieve cluster kubeconfig and print it to stdout
|
|
If you specify clusterName, kubeconfig will have a CurrentContext set to clusterName and
|
|
will have this context defined
|
|
If you don't specify clusterName, kubeconfig will have multiple contexts for every cluster
|
|
in the airship site. Context names will correspond to cluster names. CurrentContext will be empty
|
|
|
|
|
|
```
|
|
airshipctl cluster get-kubeconfig [clusterName] [flags]
|
|
```
|
|
|
|
### Examples
|
|
|
|
```
|
|
# Retrieve target-cluster kubeconfig
|
|
airshipctl cluster get-kubeconfig target-cluster
|
|
|
|
# Retrieve kubeconfig for the entire site; the kubeconfig will have context for every cluster
|
|
airshipctl cluster get-kubeconfig
|
|
|
|
```
|
|
|
|
### Options
|
|
|
|
```
|
|
-h, --help help for get-kubeconfig
|
|
```
|
|
|
|
### Options inherited from parent commands
|
|
|
|
```
|
|
--airshipconf string Path to file for airshipctl configuration. (default "$HOME/.airship/config")
|
|
--debug enable verbose output
|
|
```
|
|
|
|
### SEE ALSO
|
|
|
|
* [airshipctl cluster](airshipctl_cluster.md) - Manage Kubernetes clusters
|
|
|