You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/tasks/administer-cluster/cluster-management.md
-12Lines changed: 0 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,18 +197,6 @@ See [Node](/docs/concepts/architecture/nodes/) for more details.
197
197
198
198
## Advanced Topics
199
199
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
-
212
200
### Turn on or off an API version for your cluster
213
201
214
202
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