Version 1.7.0 - October 23, 2026
This release adds the following feature:
Added support for the default.nfsVersion Helm value, which enables administrators to specify the NFS version (3 or 4) used for all VDB mounts. When this value is set, the driver uses the specified version instead of automatic fallback. When the value is not set (the default), the driver continues to use automatic fallback.
This release includes the following fixes:
-
Restored automatic NFS mount version fallback. The driver now attempts an NFSv4 mount first and falls back to NFSv3 only if the NFSv4 mount fails. Previously, the driver used the NFS version declared by the Delphix Engine for the VDB. The Engine's declared version can be based on how the VDB's source host was originally configured and might not reflect what a Kubernetes node supports, which could cause mount failures.
-
Improved error handling for several internal lookups performed during provisioning, including lookups for a VDB's environment, engine, source dataset, dataset group, and Oracle default template. Transient lookup failures are now reported as clear provisioning errors rather than allowing provisioning to continue as though no changes were required.
-
Fixed an issue where failures to update a VDB's NFS access whitelist on the Delphix Engine were silently ignored rather than causing the mount attempt to fail with a clear error.
Version 1.6.0 - October 05, 2026
This release adds the following features:
-
A new
nodePoolCIDRHelm value enables the driver to whitelist an entire node-pool subnet, or multiple comma-separated subnets, for a VDB's environment in a single entry instead of adding each covered node's IP address individually as pods are scheduled. This keeps the Delphix Engine's NFS access list from growing without bound on large or long-running clusters. -
When
nodePoolCIDRis set, the driver removes individual node IP addresses already on the list that the configured CIDR covers. -
nodePoolCIDRis optional and defaults to empty. If you do not set it, the driver continues to use per-node IP whitelisting.
This release includes the following fixes:
-
Improved recovery when the Delphix Engine temporarily rejects a mount while its NFS export access list is still updating after a provisioning or refresh operation.
-
Improved recovery from a stale NFS file handle on a pod's mount, so the affected pod is automatically rescheduled instead of requiring manual intervention.
Version 1.5.2 - September 24, 2026
This release includes the following fixes:
-
Improved handling of NFS storage failures to reduce pod startup and recovery issues.
-
Improved pod recovery after storage connection failures.
-
Improved error handling during volume expansion to support reliable retries.
-
Improved NFS mount handling when the server is unavailable or unresponsive.
-
Updated container images to include the latest security fixes.
Version 1.5.1 - July 30, 2026
This release includes the following fixes:
-
Improved processing of Kubernetes volume lifecycle operations, including mount, unmount, enable/disable, and PVC deletion workflows.
-
Improved processing of long-running engine operations and timeout conditions.
-
Improved detection of VDB refresh and rewind operations.
-
Fixed an issue that could affect file system export availability following a VDB refresh or rewind.
-
Fixed an issue that could result in incorrect file ownership on mounted volumes after a refresh.
Version 1.5.0 - July 15, 2026
This release adds the following features:
GKE (Google Kubernetes Engine) support
Added support for GKE with the following Helm chart enhancements:
-
Added an optional privileged init container that loads NFS kernel modules on Container-Optimized OS (COS) nodes.
-
Added an option to disable installation of the bundled snapshot-controller to avoid conflicts with the snapshot-controller managed by GKE.
This release includes the following fixes:
-
Fixed an issue that could cause unnecessary disable and enable operations after a VDB refresh, resulting in repeated mount activity.
-
Fixed export path comparison logic to prevent unchanged export paths from being incorrectly identified as refreshed.
-
Fixed an issue that could prevent refresh operations from completing successfully for non-Oracle (AppData) VDBs.
-
Fixed an issue where stale VDB state information could be used during mount operations following a refresh.
-
Corrected export path generation to use the format IP:/exported/data/directory.
-
Updated post-refresh disable log messages for improved clarity.
To learn more, see Kubernetes driver Helm chart parameters
Version 1.4.0 - May 02, 2025
To access the new features introduced in this 1.4.0 release, ensure that you are running the following minimum versions:
-
Delphix Continuous Data Engine version 2025.2.0+
-
DCT version 2025.2.0+
This release adds the following new features:
-
Support provisioning of Oracle VDBs (Single Tenant only). Additional Oracle-specific parameters and requirements have been added. See Helm chart parameters for further information.
-
Two PVC annotations,
vdbRepositoryNameandvdbStageMountpathare now deprecated.-
vdbRepositoryNameis no longer required for provisioning as the repository is autoselected based on thesourceDBName. -
vdbStageMountpathis now created by the driver as/mnt/<pvcname_namespace>/from the values provided in the PVC manifest.
-
-
This release has also introduced a new optional PVC parameter:
ownershipSpec.-
The
ownershipSpecparameter sets the file permissions of Delphix mounted files to match with theuseridof the mount path owner on the container image.
-
For further information, refer to the following pages that were updated as part of this release: Kubernetes, Installation and upgrade, Helm chart parameters, Ingestion architecture.
Version 1.3.1 - February 20, 2025
This release adds the following new features:
-
Support provisioning of masked VDBs
-
isMasked:The new (optional) isMasked annotation adds support to provision masked VDBs during the Kubernetes provisioning workflow
-
The isMasked parameter checks the “Mask this VDB” flag during provisioning without selecting masking jobs or specifying “Configure clone hooks”. Note, the hooks can be added later to the provisioned VDB.
-
The isMasked parameter only accepts string values “true”, “True”, “false”, and “False”.
-
Default value is “false”
-
-
-
Enhanced replication compatibility
-
The Kubernetes driver now accepts ID values for ‘sourceDBName’ and ‘envName’ in addition to the name. If a replica already exists, select a specific dataset or environment. This will eliminate conflict
-
This release fixes the following bugs:
-
Resolved a Replication issue that caused VDB Provisioning to fail due to duplicate Environment names.
Version 1.3.0 - June 20, 2024
This release adds the following new features:
-
Provision Kubernetes VDB from PostgreSQL dSource: A PostgreSQL dSource can be used as a source to provision a Kubernetes VDB. Upgrading to the PostgreSQL v4.3.0 connector is required to take advantage of this new feature.
-
Volume clone: Added support for copying an existing PVC via the volume clone functionality. This operation will provision a child VDB from an existing VDB.
-
New Default Annotations
-
Engine name: (Required) The new
engineNameannotation will provision the VDB to the specified engine. This value is the hostname (FQDN) or IP of the target engine and helps avoid VDB name collisions in replication scenarios. -
Tags: (Optional) The new
tagsannotation will create key-value pairs on VDBs that support better organization and access control within DCT.
-
This release fixes the following bugs:
-
Resolved the "Invalid memory address" or "nil pointer dereference" errors encountered while provisioning a VDB caused by differing internal API response codes.
-
Fixed an issue where the controller pod would not recover automatically and enter a ‘CrashloopBackOff’ statie if invalid annotation parameters were specified. Internal error codes have been standardized so that the controller will remain operational.
-
Resolved VDB naming collisions that would occur when provisioning from a replicated source. The Kubernetes driver will now identify the correct dataset group and avoid the collision. Users can work around this issue in prior driver releases by specifying a different dataset group (vdbGroupName).
-
Addressed a 400 error response during the VDB search step in failover scenarios with normal replication. Leverage the new Engine Name annotation to specify the target engine in replication scenarios.
Version 1.2.0 - March 15, 2024
This release adds the following new features:
-
Volume Snapshots: It introduces the ability to create volume snapshots and provision from these volume snapshots. Volume Snapshots are equivalent to Data Control Tower Bookmarks.
The feature set includes:
-
Create Volume Snapshot
-
Delete Volume Snapshot
-
Add Tags to the Volume Snapshot's Bookmark
-
Provision a dataset from a Volume Snapshot
-
-
Helm Driver Upgrades: Going forward, the Helm Upgrade command can be used to bring the K8s Driver to later versions.
Version 1.1.0 - December 21, 2023
This release adds the following new features:
-
Added support for Data Control Tower’s 'API Usage Report'. Users can now reference the following key-value pairs when generating the report to understand their usage patterns:
-
User-agent: Kubernetes-driver-v<driver-version>
-
Client-name: Kubernetes-driver
-
This Client Telemetry information is included in all shared support bundles to improve our user experience. For more details, refer to the DCT documentation.
-
Added support for AWS Elastic Kubernetes Service (EKS) v1.27+.
This release resolves the following issues:
-
Added default values for the driver’s
schemeandtlsInsecureSkipVerifyparameters. -
Added default value of
WaitforFirstConsumerfor the StorageClass'svolumeBindingMode. -
Removed
listcapabilities for Secrets. -
Each ClusterRoleBinding now has its own ServiceAccount rather than one that is shared.
Version 1.0.0 - November 17, 2023
This is the initial release for the Delphix Kubernetes (K8s) Driver. It introduces the ability to provision and manage virtualized datasets for Kubernetes applications and containerized databases. It supports the following features:
-
Provision a virtualized dataset
-
Destroy a virtualized dataset
-
Enable a virtualized dataset
-
Disable a virtualized dataset