Skip to content

Commit

Permalink
Add cluster management doc
Browse files Browse the repository at this point in the history
  • Loading branch information
lavalamp committed Mar 4, 2015
1 parent f205c98 commit 7a68a5a
Show file tree
Hide file tree
Showing 2 changed files with 35 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,8 @@ Frequently asked questions are answered on this project's [wiki](https://github.

* **Glossary** ([glossary.md](glossary.md)): Terms and concepts.

* **Cluster Management** ([cluster_management.md](cluster_management.md)): Starting and upgrading clusters.


## Further reading

Expand Down
33 changes: 33 additions & 0 deletions docs/cluster_management.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# Cluster Management

This doc is in progress.

## Upgrading a cluster

The `cluster/kube-push.sh` script will do a rudimentary update; it is a 1.0 roadmap item to have a robust live cluster update system.

## Updgrading to a different API version

There is a sequence of steps to upgrade to a new API version.

1. Turn on the new version.
2. Upgrade the cluster's storage to use the new version.
3. Upgrade all config files. Identify users of the old api version endpoints.
3. Turn off the old version.

### Turn on or off an API version for your cluster

TODO: There's an apiserver flag for this.

### Switching your cluster's storage API version

TODO: This functionality hasn't been written yet.

### Switching your config files to a new API version

You can use the kube-version-change utility to convert config files between different API versions.

```
$ hack/build-go.sh cmd/kube-version-change
$ _output/go/bin/kube-version-change -i myPod.v1beta1.yaml -o myPod.v1beta3.yaml
```

0 comments on commit 7a68a5a

Please sign in to comment.