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
* link:https://docs.openshift.com/container-platform/{ocp-version}/rest_api/storage_apis/volumesnapshot-snapshot-storage-k8s-io-v1.html[VolumeSnapshot API specification]
35
+
* link:https://docs.openshift.com/container-platform/{ocp-version}/rest_api/storage_apis/volumesnapshot-snapshot-storage-k8s-io-v1.html[VolumeSnapshot API specification] ({OCP} documentation)
* To create a thin pool on the host, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/{op-system-version-major}/html/configuring_and_managing_logical_volumes/creating-and-managing-thin-provisioned-volumes_configuring-and-managing-logical-volumes[Creating and managing thin provisioned volumes]
43
+
* To create a thin pool on the host, see link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_and_managing_logical_volumes/basic-logical-volume-management_configuring-and-managing-logical-volumes#creating-thin-logical-volume_creating-logical-volumes[Creating a thin logical volume] ({op-system-base} documentation)
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/storage/using-container-storage-interface-csi#persistent-storage-csi-snapshots-provision_persistent-storage-csi-snapshots[Restoring a volume snapshot]
81
+
* link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html/storage/using-container-storage-interface-csi#persistent-storage-csi-snapshots-restore_persistent-storage-csi-snapshots[Restoring a volume snapshot]
84
82
85
83
//this module is reused from OCP; take care in editing for MicroShift
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/storage/configuring-persistent-storage#lvms-creating-volume-clones-in-single-node-openshift_logical-volume-manager-storage[LVMS volume cloning for Single-Node OpenShift]
94
+
//* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/storage/configuring-persistent-storage#lvms-creating-volume-clones-in-single-node-openshift_logical-volume-manager-storage[LVMS volume cloning for Single-Node OpenShift]
95
+
//cannot find new link
97
96
98
97
* To configure the host to enable cloning, see xref:../microshift_storage/volume-snapshots-microshift.adoc#microshift-lvm-thin-volumes_volume-snapshots-microshift[About LVM thin volumes]
|Default value is null or an empty array. A null or empty array defaults to deploying `snapshot-controller` and `snapshot-webhook`. Expected values are `csi-snapshot-controller`, `csi-snapshot-webhook`, or `none`. An entry of `none` is mutually exclusive with all other values.
262
+
|Default value is null or an empty array. A null or empty array defaults to deploying `snapshot-controller`. Expected values are `csi-snapshot-controller`or `none`. A value of `none` is mutually exclusive with all other values.
Copy file name to clipboardExpand all lines: modules/microshift-disabling-lvms-csi-snapshot.adoc
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -32,11 +32,11 @@ This procedure is for users who are defining the configuration file before insta
32
32
<1> Accepted values are:
33
33
* Not defining `optionalCsiComponents`.
34
34
* Specifying `optionalCsiComponents` field with an empty value (`[]`) or a single empty string element (`[""]`).
35
-
* Specifying `optionalCsiComponents` with one of the accepted values which are `snapshot-controller`, `snapshot-webhook`, or `none`. `none` is mutually exclusive with all other values.
35
+
* Specifying `optionalCsiComponents` with one of the accepted values which are `snapshot-controller`, or `none`. A value of`none` is mutually exclusive with all other values.
36
36
+
37
37
[NOTE]
38
38
====
39
-
If the `optionalCsiComponents` value is empty or null, {microshift-short} defaults to deploying snapshot-controller and snapshot-webhook.
39
+
If the `optionalCsiComponents` value is empty or null, {microshift-short} defaults to deploying snapshot-controller.
40
40
====
41
41
42
42
. After the `optionalCsiComponents` field is specified with a supported value in the `config.yaml`, start {microshift-short} by running the following command:
Copy file name to clipboardExpand all lines: modules/microshift-disconnected-host-procedure.adoc
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ $ sudo systemctl reboot <1>
95
95
96
96
At this point, network access to the {microshift-short} host has been severed. If you have access to the host terminal, you can use the host CLI to verify that the cluster has started in a stable state.
97
97
98
-
. Verify that the {microshift-short} cluster is running by entering the following command:
98
+
. Verify that the {microshift-short} cluster is running by entering the following commands:
<1> Replace _<namespace>_ and _<snapshot_name>_ with the namespace and snapshot name you used.
26
27
27
28
. Get the unique identity of the volume created on the storage backend by using the following command and inserting the name retrieved in the previous step:
28
29
+
29
30
[source,terminal]
30
31
----
31
-
$ oc get volumesnapshotcontent snapcontent-<retrieved_volume_identity> -o 'jsonpath={.status.snapshotHandle}'
32
+
$ oc get volumesnapshotcontent snapcontent-<retrieved_volume_identity> -o 'jsonpath={.status.snapshotHandle}' # <1>
32
33
----
34
+
<1> Replace _<retrieved_volume_identity>_ with the volume identity.
33
35
34
36
. Display the snapshots by using the unique identity of the volume you retrieved in the previous step to determine which one you want to backup by running the following command:
0 commit comments