Release notes (Kubernetes)
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,
vdbRepositoryName
andvdbStageMountpath
are now deprecated.-
vdbRepositoryName
is no longer required for provisioning as the repository is autoselected based on thesourceDBName
. -
vdbStageMountpath
is 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
ownershipSpec
parameter sets the file permissions of Delphix mounted files to match with theuserid
of 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
engineName
annotation 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
tags
annotation 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
scheme
andtlsInsecureSkipVerify
parameters. -
Added default value of
WaitforFirstConsumer
for the StorageClass'svolumeBindingMode
. -
Removed
list
capabilities 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