The virtualization module: configuration

This feature is actively developed. It might significantly change in the future.

The module is not enabled by default in any bundles.

Set the spec.enabled module parameter to true or false to explicitly enable or disable the module.

Example of enabling the virtualization module:

          apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: virtualization
spec:
  enabled: true

        

Example of disabling the virtualization module:

          apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: virtualization
spec:
  enabled: false

        

Note! Module depends on the cni-cilium module. Make sure your cluster is deployed with Cilium as the main CNI plugin.

If cilium works in tunnel mode, enabling this module will result in short downtime due to reconfiguration of overlay network to a non-standard VXLAN port.

You will also need to specify one or more desired subnets from which IP addresses will be allocated to virtual machines:

vmCIDRs:
- 10.10.10.0/24

The subnet for the VMs should not conflict with the subnet for the pods and the subnet for the services

The module is configured using the ModuleConfig custom resource named virtualization (learn more about setting up Deckhouse…).

Example of the ModuleConfig/virtualization resource for configuring the module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: virtualization
spec:
  version: 1
  enabled: true
  settings: # <-- Module parameters from the "Parameters" section below.

Parameters

Schema version: 1

highAvailabilityboolean
Manually enable the high availability mode.

By default, Deckhouse automatically decides whether to enable the HA mode. Click here to learn more about the HA mode for modules.

Examples:
```
highAvailability: true
```
```
highAvailability: false
```
vmCIDRsarray of strings
Required value
List of CIDRs used to allocate static IP addresses for Virtual Machines.

Example:
```
vmCIDRs:
- 10.10.10.0/24
- 10.10.20.0/24
```