Skip to content

Commit abfff67

Browse files
Remove cluster/update-storage-objects.sh reference
Seems like this https://github.com/kubernetes/kubernetes/pull/83969/files makes it obsolete
1 parent 332cba8 commit abfff67

File tree

1 file changed

+0
-12
lines changed

1 file changed

+0
-12
lines changed

content/en/docs/tasks/administer-cluster/cluster-management.md

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -189,18 +189,6 @@ node discovery; currently this is only Google Compute Engine, not including Core
189189

190190
## Advanced Topics
191191

192-
### Upgrading to a different API version
193-
194-
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).
195-
196-
This is an infrequent event, but it requires careful management. There is a sequence of steps to upgrade to a new API version.
197-
198-
1. Turn on the new API version.
199-
1. Upgrade the cluster's storage to use the new version.
200-
1. Upgrade all config files. Identify users of the old API version endpoints.
201-
1. Update existing objects in the storage to new version by running `cluster/update-storage-objects.sh`.
202-
1. Turn off the old API version.
203-
204192
### Turn on or off an API version for your cluster
205193

206194
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`.

0 commit comments

Comments
 (0)