kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add a few more handy commands to the commands page

This commit is contained in:
Ole Markus With 2020-04-10 20:14:01 +02:00
parent 1eac727390
commit 9ded114dcd
1 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/getting_started/commands.md
View File

@ -1,12 +1,18 @@
# Commands & Arguments
This page lists the most common kops commands.
Please refer to the kops [cli reference](../cli/kops.md) for full documentation.
## `kops create cluster`
## `kops create
`kops create cluster <clustername>` creates a cloud specification in the registry. It will not create the cloud resources unless
you specify `--yes`, so that you have the chance to `kops edit` them. (You will likely `kops update cluster` after
creating it).
`kops create` registers a cluster. There are two ways of registering a cluster: using a cluster spec file or using cli arguments.
### `kops create -f <cluser spec>`
`kops create -f <cluster spec>` will register a cluster using a kops spec yaml file. After the cluster has been registered you need to run `kops update cluster --yes` to create the cloud resources.
### `kops create cluster`
`kops create cluster <clustername>` creates a cloud specification in the registry using cli arguments. In most cases, you will need to edit the cluster spec using `kops edit` before actually creating the cloud resources. If you are sure you do not need to do any moditication, you can add the `--yes` flag to immediately create the cluster including cloud resource.
## `kops update cluster`
@ -34,6 +40,9 @@ cluster. It also removes the cluster from the registry.
It is recommended that you run it first in 'preview' mode with `kops delete cluster --name <name>`, and then
when you are happy that it is deleting the right things you run `kops delete cluster --name <name> --yes`.
## `kops toolbox template`
`kops toolbox template` lets you generate a kops spec using go templates. This is very handy if you want to consistently manage multiple clusters.
## `kops version`