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

Merge pull request #2981 from StevenACoffman/master 

Issue #2977: Improve Manifest documentation
This commit is contained in:
Chris Love 2017-07-17 15:54:41 -06:00 committed by GitHub
parent 5b7c1cfe2d ae1feadd0f
commit 7e1e5ba9cb
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/manifests_and_customizing_via_api.md
View File

@ -6,12 +6,14 @@ This document also applies to using the `kops` API to customize a Kubernetes clu
> We like to think of it as `kubectl` for Clusters.
Because of the above statement `kops` includes an API which provides a feature for users to utilize YAML or JSON manifests for managing their `kops` created Kubernetes installations. In the same way, you can use a YAML manifest to deploy a Job you can deploy and manage a `kops` Kuberenetes instance with a manifest. All of these values are also usable via the interactive editor with `kops edit`.
Because of the above statement `kops` includes an API which provides a feature for users to utilize YAML or JSON manifests for managing their `kops` created Kubernetes installations. In the same way that you can use a YAML manifest to deploy a Job, you can deploy and manage a `kops` Kuberenetes instance with a manifest. All of these values are also usable via the interactive editor with `kops edit`.
> You can see all the options that are currently supported in Kops [here](https://github.com/kubernetes/kops/blob/master/pkg/apis/kops/componentconfig.go) or [more prettily here](https://godoc.org/k8s.io/kops/pkg/apis/kops#ClusterSpec)
The following is a list of the benefits of using a file to manage instances.
- Capability to access API values that are not accessible via the command line such as setting the max price for spot instances.
- Create, update, and delete clusters without entering an interactive editor. This feature is helpful when automating cluster creation.
- Create, replace, update, and delete clusters without entering an interactive editor. This feature is helpful when automating cluster creation.
- Ability to check-in files to source control that represents an installation.
- Run commands such as `kops delete -f mycuster.yaml`.
@ -220,7 +222,7 @@ spec:
- us-east-2c
```
Next, delete the cluster from the state store.
Next, delete the cluster from the state store. (**Note:** An alternative to deleting and then creating again from the new manifest might be to replace with `kops replace -f $NAME.yaml`)
```console
kops delete -f $NAME.yaml