The module lifecycle stage: Generally available version

The module has requirements for installation

v1.0.2

Release date: November 16, 2026.

Highlights

v1.0.1

Release date: November 12, 2026.

Highlights

  • Fixed a data-loss risk caused by reformatting a volume with an existing filesystem when mounting it again.
  • During migration from DVPClusterConfiguration to ModuleConfig, active provider and node settings are no longer replaced with values for the same parameters from ModuleConfig.
  • Updated libraries and base images to address known vulnerabilities.

Fixes

  • Fixed reformatting a volume with an existing filesystem during mounting in the DVP Container Storage Interface (CSI) driver. The csi.dvp.deckhouse.io driver checks the filesystem before mounting the volume for a workload and uses it without reformatting. If the check fails, the CSI driver stops the mount operation and reports an error.
  • During migration from DVPClusterConfiguration to ModuleConfig, shared parameters are no longer overridden by values from ModuleConfig. Until all migration resources are applied, they are taken only from DVPClusterConfiguration.
  • Fixed the default network policy applied during migration. If provider.networkPolicy is not specified in DVPClusterConfiguration, the module uses the Isolated value.

Security

  • Updated Go libraries and base images in provider components to address known vulnerabilities.

v1.0.0

Release date: October 30, 2026.

Highlights

  • The cloud provider now has its own release cycle and release channels.
  • Added support for creating nodes with graphics processing units (GPUs).
  • The parent cluster autoscaler can now select the CPU share for node virtual machines automatically.
  • Load balancers now receive the network policies needed to reach nodes in Isolated mode.
  • When a workload moves to another node, its disk is fully detached from the previous node before it can be attached again.

New features

  • The cloud-provider-dvp module is installed from a module source and updated through the selected release channel. Provider updates can be delivered separately from Deckhouse Platform updates.
  • Added support for attaching graphics processing units (GPUs) to node virtual machines (VMs). Devices are selected through GPUClass, and attachments are configured in virtualMachine.gpus in DVPClusterConfiguration and DVPInstanceClass.
  • Added the Auto value for coreFraction. Instead of specifying a fixed CPU share, you can delegate its selection to the parent cluster Vertical VirtualMachine Autoscaler.
  • Added additionalVMLabels and ingressPorts to configure access to node VMs. You can select TCP ports that accept traffic from any source and apply custom NetworkPolicy resources using VM labels, for example to allow access through a bastion host in the parent cluster.
  • The storage.parameters.excludedStorageClasses parameter lets you hide parent cluster storage classes that child cluster workloads should not use. Classes can be selected by name or regular expression.
  • With networkPolicy: Isolated, the module creates a network policy for each load balancer. The policy allows traffic to the required node ports, so access through the load balancer does not require disabling network isolation.

Upgrade notes

  • Before updating Deckhouse Platform to a version that replaces the built-in provider with the external module, make sure cloud-provider-dvp is available from the configured module source. The update deploys provider components from this module.
  • If the cluster is configured through DVPClusterConfiguration, migrate its configuration to ModuleConfig using the migration guide (in Russian).
  • Before attaching graphics processing units (GPUs), prepare the parent cluster according to the DVPInstanceClass requirements. Enable the required modules and feature gates, and create GPUClass resources for the devices.
  • Changing virtualMachine.gpus recreates CloudEphemeral nodes and restarts the virtual machines of master and CloudPermanent nodes during dhctl converge. Plan for interruptions on these nodes and maintain control plane quorum.
  • Before using coreFraction: Auto, make sure the parent cluster runs the Vertical VirtualMachine Autoscaler and has the HotplugCPUAndMemoryWithInPlaceResize feature gate enabled in the virtualization module.

Fixes

  • Nodes managed by other cloud providers are no longer treated as missing or shut down during cloud-provider-dvp checks. This prevents the cloud node lifecycle controller from deleting them incorrectly.
  • Eliminated repeated GetCapacity not implemented errors caused by storage capacity queries. The DVP Container Storage Interface (CSI) driver no longer advertises support for queries it does not implement.
  • The D8CloudProviderDVPMigrationPending alert no longer reports a pending configuration migration after all required resources have been applied. The module correctly recognizes a completed migration.
  • Fixed cluster bootstrap stalling while the network plugin is not ready. Provider components can reach the API server and resolve names through the node network before the cluster network starts.
  • Fixed cloud-provider-dvp interfering with load balancers managed by another controller. When backend addresses change, the module skips Service objects with an explicit loadBalancerClass.
  • Fixed health checks for UDP services. Backend readiness no longer depends on a TCP check of a UDP port, which could incorrectly exclude available addresses from load balancing.
  • When a workload moves to another node, the DVP CSI driver waits until its disk is fully detached from the previous node virtual machine. This prevents attempts to attach the disk to the new node while the previous node is still using it.
  • The DVP CSI driver reports the node disk attachment limit to the scheduler. The scheduler takes this limit into account when placing workloads that require disks.
  • System annotations added by the parent cluster to the secret containing node bootstrap data no longer cause repeated infrastructure changes during drift checks and converge runs.
  • Migration from DVPClusterConfiguration to ModuleConfig preserves networkPolicy: None. Network isolation that was explicitly disabled is no longer enabled automatically, so existing network access rules remain in effect.
  • Fixed load balancer deletion failing when its associated Service in the parent cluster is protected from direct deletion.
  • Fixed prolonged waits during node creation when bootstrap data becomes available later. The provider resumes node creation once the data is available.

Security

  • Updated Go libraries to address known vulnerabilities in provider components.

Limitations

Documentation