|
9 | 9 | == New installations of {product-title} |
10 | 10 | For new installations of {product-title} 4.13, or later, automatic migration is enabled by default. |
11 | 11 |
|
12 | | -[id="upgrading-openshift_{context}"] |
13 | | -== Upgrading {product-title} |
14 | | -When upgrading from {product-title} 4.12, or earlier, to 4.13, automatic CSI migration for vSphere only occurs if you opt in. |
| 12 | +[id="updating-openshift_from_4.13_{context}"] |
| 13 | +== Updating from {product-title} 4.13 to 4.14 |
| 14 | +If you are using vSphere in-tree persistent volumes (PVs) and want to update from {product-title} 4.13 to 4.14, update vSphere vCenter and ESXI host to 7.0 Update 3L or 8.0 Update 2, otherwise the {product-title} update is blocked. After updating vSphere, your {product-title} update can occur and automatic migration is enabled by default. |
15 | 15 |
|
16 | | -[IMPORTANT] |
17 | | -==== |
18 | | -Carefully review the following consequences before opting in to migration: |
19 | | -
|
20 | | -* link:https://access.redhat.com/node/7011683[There are known issues that can occur that can cause the migration to fail]. |
21 | | -
|
22 | | -* Enabling migration cannot be undone. |
| 16 | +Alternatively, if you do not want to update vSphere, you can proceed with an {product-title} update by performing an administrator acknowledgment: |
23 | 17 |
|
24 | | -* Migration can take awhile to complete depending on how many nodes are on the cluster. |
| 18 | +[source, cli] |
| 19 | +---- |
| 20 | +oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.13-kube-127-vsphere-migration-in-4.14":"true"}}' --type=merge |
| 21 | +---- |
25 | 22 |
|
26 | | -* Migration is a disruptive process. The Machine Config Operator (MCO) has to update kubelet, which means degrading each node as it rolls out the new MachineConfig to each machine. |
| 23 | +[IMPORTANT] |
| 24 | +==== |
| 25 | +If you do *not* update to vSphere 7.0 Update 3L or 8.0 Update 2 and use an administrator acknowledgment to update to {product-title} 4.14, known issues can occur due to CSI migration being enabled by default in {product-title} 4.14. link:https://access.redhat.com/node/7011683[Before proceeding with the administrator acknowledgement, carefully read this knowledge base article]. |
27 | 26 | ==== |
28 | 27 |
|
29 | | -=== Using the web console to opt in to automatic CSI migration |
30 | | - |
31 | | -==== Prerequisites |
32 | | - |
33 | | -* Access to the {product-title} web console. |
34 | | - |
35 | | -* Access to the cluster with cluster-admin privileges. |
36 | | - |
37 | | -===== Procedure |
38 | | - |
39 | | -To opt in to automatic CSI migration for vSphere: |
40 | | - |
41 | | -. Log in to the web console. |
42 | | - |
43 | | -. Click *Administration* -> *CustomResourceDefinitions*. |
44 | | - |
45 | | -. On the *CustomResourceDefinitions* page, type "Storage" to find the `Storage` custom resource (CR). |
46 | | - |
47 | | -. Click the *Storage* CR. |
48 | | - |
49 | | -. On the *storages.operator.openshift.io* page, click the *Instances* tab. |
| 28 | +[id="updating-openshift_from_4.12_{context}"] |
| 29 | +== Updating from {product-title} 4.12 to 4.14 |
| 30 | +If you are using vSphere in-tree persistent volumes (PVs) and want to update from {product-title} 4.12 to 4.14, update vSphere vCenter and ESXI host to 7.0 Update 3L or 8.0 Update 2, otherwise the {product-title} update is blocked. After updating vSphere, your {product-title} update can occur and automatic migration is enabled by default. |
50 | 31 |
|
51 | | -. Click the name of the desired instance, and then click the *YAML* tab. |
| 32 | +Alternatively, if you do not want to update vSphere, you can proceed with an {product-title} update by performing an administrator acknowledgment by running *both* of the following commands: |
52 | 33 |
|
53 | | -. Set the `spec.vsphereStorageDriver` parameter to `CSIWithMigrationDriver`, as shown in the following example: |
54 | | -+ |
55 | | -[source, yaml] |
| 34 | +[source, terminal] |
56 | 35 | ---- |
57 | | -.... |
58 | | -spec: |
59 | | - logLevel: Normal |
60 | | - managementState: Managed |
61 | | - operatorLogLevel: Normal |
62 | | - vsphereStorageDriver: CSIWithMigrationDriver <1> |
63 | | -... |
| 36 | +oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.12-kube-126-vsphere-migration-in-4.14":"true"}}' --type=merge |
64 | 37 | ---- |
65 | | -<1> `spec.vsphereStorageDriver` parameter set to `CSIWithMigrationDriver` |
66 | | - |
67 | | -. Click *Save*. |
68 | | - |
69 | | -=== Using the CLI to opt in to automatic CSI migration |
70 | 38 |
|
71 | | -==== Prerequisites |
72 | | - |
73 | | -* Access to the cluster with cluster-admin privileges. |
74 | | - |
75 | | -==== Procedure |
76 | | - |
77 | | -To opt in to automatic CSI migration for vSphere, run the following command: |
78 | | - |
79 | | -[source, cli] |
| 39 | +[source, terminal] |
80 | 40 | ---- |
81 | | -oc patch storage cluster --type=merge -p '{"spec":{"vsphereStorageDriver":"CSIWithMigrationDriver"}}' |
| 41 | +oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.13-kube-127-vsphere-migration-in-4.14":"true"}}' --type=merge |
82 | 42 | ---- |
83 | 43 |
|
84 | | -[NOTE] |
| 44 | +[IMPORTANT] |
85 | 45 | ==== |
86 | | -You can determine when migration is complete by verifying that the `VSphereMigrationControllerAvailable` condition is set to "true" in the `Storage` object. |
| 46 | +If you do *not* update to vSphere 7.0 Update 3L or 8.0 Update 2 and use an administrator acknowledgment to update to {product-title} 4.14, known issues can occur due to CSI migration being enabled by default in {product-title} 4.14. link:https://access.redhat.com/node/7011683[Before proceeding with the administrator acknowledgement, carefully read this knowledge base article]. |
87 | 47 | ==== |
| 48 | + |
| 49 | +Updating from {product-title} 4.12 to 4.14 is an Extended Update Support (EUS)-to-EUS update. To understand the ramifications for this type of update and how to perform it, see the _EUS-to-EUS update_ link in the _Additional resources_ section below. |
0 commit comments