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
| status ||[HyperConvergedStatus](#hyperconvergedstatus)|| false |
126
126
127
127
[Back to TOC](#table-of-contents)
@@ -201,7 +201,7 @@ HyperConvergedSpec defines the desired state of HyperConverged
201
201
| infra | infra HyperConvergedConfig influences the pod configuration (currently only placement) for all the infra components needed on the virtualization enabled cluster but not necessarily directly on each node running VMs/VMIs. |[HyperConvergedConfig](#hyperconvergedconfig)|| false |
202
202
| workloads | workloads HyperConvergedConfig influences the pod configuration (currently only placement) of components which need to be running on a node where virtualization workloads should be able to run. Changes to Workloads HyperConvergedConfig can be applied only without existing workload. |[HyperConvergedConfig](#hyperconvergedconfig)|| false |
203
203
| featureGates | featureGates is a map of feature gate flags. Setting a flag to `true` will enable the feature. Setting `false` or removing the feature gate, disables the feature. |[HyperConvergedFeatureGates](#hyperconvergedfeaturegates)| {"downwardMetrics": false, "enableCommonBootImageImport": true, "deployVmConsoleProxy": false, "deployKubeSecondaryDNS": false, "disableMDevConfiguration": false, "persistentReservation": false, "autoResourceLimits": false, "enableApplicationAwareQuota": false, "primaryUserDefinedNetworkBinding": false} | false |
204
-
| liveMigrationConfig | Live migration limits and timeouts are applied so that migration processes do not overwhelm the cluster. |[LiveMigrationConfigurations](#livemigrationconfigurations)| {"completionTimeoutPerGiB": 800, "parallelMigrationsPerCluster": 5, "parallelOutboundMigrationsPerNode": 2, "progressTimeout": 150, "allowAutoConverge": false, "allowPostCopy": false} | false |
204
+
| liveMigrationConfig | Live migration limits and timeouts are applied so that migration processes do not overwhelm the cluster. |[LiveMigrationConfigurations](#livemigrationconfigurations)| {"completionTimeoutPerGiB": 150, "parallelMigrationsPerCluster": 5, "parallelOutboundMigrationsPerNode": 2, "progressTimeout": 150, "allowAutoConverge": false, "allowPostCopy": false} | false |
205
205
| permittedHostDevices | PermittedHostDevices holds information about devices allowed for passthrough |*[PermittedHostDevices](#permittedhostdevices)|| false |
206
206
| mediatedDevicesConfiguration | MediatedDevicesConfiguration holds information about MDEV types to be defined on nodes, if available |*[MediatedDevicesConfiguration](#mediateddevicesconfiguration)|| false |
@@ -271,7 +271,7 @@ LiveMigrationConfigurations - Live migration limits and timeouts are applied so
271
271
| parallelMigrationsPerCluster | Number of migrations running in parallel in the cluster. |*uint32 | 5 | false |
272
272
| parallelOutboundMigrationsPerNode | Maximum number of outbound migrations per node. |*uint32 | 2 | false |
273
273
| bandwidthPerMigration | Bandwidth limit of each migration, the value is quantity of bytes per second (e.g. 2048Mi = 2048MiB/sec) |*string || false |
274
-
| completionTimeoutPerGiB | If a migrating VM is big and busy, while the connection to the destination node is slow, migration may never converge. The completion timeout is calculated based on completionTimeoutPerGiB times the size of the guest (both RAM and migrated disks, if any). For example, with completionTimeoutPerGiB set to 800, a virtual machine instance with 6GiB memory will timeout if it has not completed migration in 1h20m. Use a lower completionTimeoutPerGiB to induce quicker failure, so that another destination or post-copy is attempted. Use a higher completionTimeoutPerGiB to let workload with spikes in its memory dirty rate to converge. The format is a number. |*int64 |800| false |
274
+
| completionTimeoutPerGiB | If a migrating VM is big and busy, while the connection to the destination node is slow, migration may never converge. The completion timeout is calculated based on completionTimeoutPerGiB times the size of the guest (both RAM and migrated disks, if any). For example, with completionTimeoutPerGiB set to 800, a virtual machine instance with 6GiB memory will timeout if it has not completed migration in 1h20m. Use a lower completionTimeoutPerGiB to induce quicker failure, so that another destination or post-copy is attempted. Use a higher completionTimeoutPerGiB to let workload with spikes in its memory dirty rate to converge. The format is a number. |*int64 |150| false |
275
275
| progressTimeout | The migration will be canceled if memory copy fails to make progress in this time, in seconds. |*int64 | 150 | false |
276
276
| network | The migrations will be performed over a dedicated multus network to minimize disruption to tenant workloads due to network saturation when VM live migrations are triggered. |*string || false |
277
277
| allowAutoConverge | AllowAutoConverge allows the platform to compromise performance/availability of VMIs to guarantee successful VMI live migrations. Defaults to false |*bool | false | false |
0 commit comments