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
Enabling workloadUpdates strategies by default
can expose unexpected behaviours.
Temporary disable it until we properly
covered all the corner cases.
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=2017394
This is a manual cherry pick of #1577
Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
Copy file name to clipboardexpand all lines: docs/api.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,7 @@ HyperConvergedSpec defines the desired state of HyperConverged
132
132
| obsoleteCPUs | ObsoleteCPUs allows avoiding scheduling of VMs for obsolete CPU models |*[HyperConvergedObsoleteCPUs](#hyperconvergedobsoletecpus)|| false |
133
133
| commonTemplatesNamespace | CommonTemplatesNamespace defines namespace in which common templates will be deployed. It overrides the default openshift namespace. |*string || false |
134
134
| storageImport | StorageImport contains configuration for importing containerized data |*[StorageImportConfig](#storageimportconfig)|| false |
135
-
| workloadUpdateStrategy | WorkloadUpdateStrategy defines at the cluster level how to handle automated workload updates |*[HyperConvergedWorkloadUpdateStrategy](#hyperconvergedworkloadupdatestrategy)|{"workloadUpdateMethods": {"LiveMigrate"}, "batchEvictionSize": 10, "batchEvictionInterval": "1m0s"}| false |
135
+
| workloadUpdateStrategy | WorkloadUpdateStrategy defines at the cluster level how to handle automated workload updates |*[HyperConvergedWorkloadUpdateStrategy](#hyperconvergedworkloadupdatestrategy)|| false |
136
136
137
137
[Back to TOC](#table-of-contents)
138
138
@@ -155,9 +155,9 @@ HyperConvergedWorkloadUpdateStrategy defines options related to updating a KubeV
| workloadUpdateMethods | WorkloadUpdateMethods defines the methods that can be used to disrupt workloads during automated workload updates. When multiple methods are present, the least disruptive method takes precedence over more disruptive methods. For example if both LiveMigrate and Shutdown methods are listed, only VMs which are not live migratable will be restarted/shutdown. An empty list defaults to no automated workload updating. |[]string |{"LiveMigrate"}| false |
159
-
| batchEvictionSize | BatchEvictionSize Represents the number of VMIs that can be forced updated per the BatchShutdownInteral interval |*int |10| false |
160
-
| batchEvictionInterval | BatchEvictionInterval Represents the interval to wait before issuing the next batch of shutdowns |*metav1.Duration |"1m0s"| false |
158
+
| workloadUpdateMethods | WorkloadUpdateMethods defines the methods that can be used to disrupt workloads during automated workload updates. When multiple methods are present, the least disruptive method takes precedence over more disruptive methods. For example if both LiveMigrate and Evict methods are listed, only VMs which are not live migratable will be restarted/shutdown. An empty list defaults to no automated workload updating. |[]string || false |
159
+
| batchEvictionSize | BatchEvictionSize Represents the number of VMIs that can be forced updated per the BatchShutdownInteral interval |*int || false |
160
+
| batchEvictionInterval | BatchEvictionInterval Represents the interval to wait before issuing the next batch of shutdowns |*metav1.Duration || false |
0 commit comments