whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove cluster/update-storage-objects.sh reference

Browse Source 
Seems like this https://github.com/kubernetes/kubernetes/pull/83969/files makes it obsolete
This commit is contained in:
Ricardo Rosales
2020-07-13 10:22:29 -05:00
committed by GitHub
parent 332cba8bf3
commit abfff67725
1 changed files with 0 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/administer-cluster/cluster-management.md
-12
View File
@@ -189,18 +189,6 @@ node discovery; currently this is only Google Compute Engine, not including Core
## Advanced Topics
### Upgrading to a different API version
When a new API version is released, you may need to upgrade a cluster to support the new API version (e.g. switching from 'v1' to 'v2' when 'v2' is launched).
This is an infrequent event, but it requires careful management. There is a sequence of steps to upgrade to a new API version.
1. Turn on the new API version.
1. Upgrade the cluster's storage to use the new version.
1. Upgrade all config files. Identify users of the old API version endpoints.
1. Update existing objects in the storage to new version by running `cluster/update-storage-objects.sh`.
1. Turn off the old API version.
### Turn on or off an API version for your cluster
Specific API versions can be turned on or off by passing `--runtime-config=api/<version>` flag while bringing up the API server. For example: to turn off v1 API, pass `--runtime-config=api/v1=false`.