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: modules/virt-single-node-cluster.adoc
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,7 @@
5
5
[id="virt-single-node-cluster_{context}"]
6
6
= Changes in {VirtProductName} behavior on a single node cluster
7
7
8
-
You can use {VirtProductName} with single node clusters, also known as Single Node OpenShift (SNO). These clusters are not configured for high-availability operation, which results in significant changes to {VirtProductName} behavior.
8
+
You can use {VirtProductName} with single node clusters, also known as single-node OpenShift. These clusters are not configured for high-availability operation, which results in significant changes to {VirtProductName} behavior.
9
9
10
10
* {VirtProductName} components have only one replica, and pod disruption budgets do not apply.
11
11
* Live migration is not supported.
12
-
* Due to differences in storage behavior, some virtual machine templates are incompatible with SNO. To ensure compatibility, do not set the `evictionStrategy` field for any templates or virtual machines that use data volumes or storage profiles.
0 commit comments