Skip to content

Commit 06a9e0f

Browse files
authored
Merge pull request #22490 from missingcharacter/patch-1
Remove `cluster/update-storage-objects.sh` reference
2 parents 390a4d8 + abfff67 commit 06a9e0f

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
@@ -197,18 +197,6 @@ See [Node](/docs/concepts/architecture/nodes/) for more details.
197197

198198
## Advanced Topics
199199

200-
### Upgrading to a different API version
201-
202-
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).
203-
204-
This is an infrequent event, but it requires careful management. There is a sequence of steps to upgrade to a new API version.
205-
206-
1. Turn on the new API version.
207-
1. Upgrade the cluster's storage to use the new version.
208-
1. Upgrade all config files. Identify users of the old API version endpoints.
209-
1. Update existing objects in the storage to new version by running `cluster/update-storage-objects.sh`.
210-
1. Turn off the old API version.
211-
212200
### Turn on or off an API version for your cluster
213201

214202
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)