Skip to main content

Release 123.3; Build 1088

May 08, 2024

New Feature

PGVECTOR extension for PostgreSQL

PDS now supports the PGVECTOR extension to PostgreSQL. This extension is designed to enhance database functionality by enabling efficient vector operations directly within your PostgreSQL environment.


The PGVECTOR extension does not require configuration via the shared_preload_libraries. This means, you can use it directly without any additional setup in the PostgreSQL configuration file. This simplifies the process of integrating and utilizing the PGVECTOR capabilities in your existing database systems.

For more information about using the shared_preload_libraries parameter, refer to the updated list of supported configuration parameters for PostgreSQL.

Release 123.2; Build 1087

April 25, 2024


New configuration parameter for PostgreSQL

PDS now supports the USE_SLOTS configuration parameter in the PostgreSQL data service. This new parameter provides administrators with enhanced control over replication slots. Setting this parameter enables more efficient management of replication processes by allowing users to specify whether a particular slot should be used for replication tasks.

For more information, refer to the updated list of supported configuration parameters for PostgreSQL.

Release 123.1; Build 1085

April 18, 2024


New configuration parameters for PostgreSQL

  • TRACK_COMMIT_TIMESTAMP: allows you to record the commit timestamp of transactions. It is particularly useful for applications that require tracking of transaction times for auditing or synchronization purposes.
  • PGLOGICAL_CONFLICT_RESOLUTION: introduces options for handling conflicts during logical replication. It offers flexibility in managing how data inconsistencies are resolved, which is crucial for maintaining data integrity across distributed systems.

For more information, refer to the updated list of supported configuration parameters for PostgreSQL.


The PostgreSQL version 12.x is now deprecated.

Release 123; Build 1084

December 19, 2023

New data service versions

PDS supports the following new data service versions in this release:

  • Cassandra: 4.0.11, 4.1.3
  • Consul: 1.14.10, 1.15.6, 1.16.2
  • Couchbase: 7.2.2
  • Kafka: 3.5.1, 3.6.0
  • MongoDB Enterprise: 6.0.11, 7.0.3
  • MySQL: 8.0.34
  • PostgreSQL: 12.17, 13.13, 14.10, 15.5, 16.1
  • RabbitMQ: 3.11.23, 3.12.6
  • Redis: 7.0.14
  • ZooKeeper: 3.8.3, 3.9.1

TLS support for MongoDB Enterprise

PDS now supports Transport Layer Security (TLS) for MongoDB Enterprise. This enhancement ensures secure communication for MongoDB instances within the PDS environment.

The implementation involves changes to the cert-manager Helm chart to generate combined PEM files, which MongoDB uses for TLS. Run the following command to upgrade or install cert-manager with version v1.11.0 and to enable the feature gate AdditionalCertificateOutputFormats, which results in cert-manager generating combined PEM files for MongoDB TLS:

helm upgrade --install \
cert-manager jetstack/cert-manager \
--namespace cert-manager \
--create-namespace \
--version v1.11.0 \
--set installCRDs=true \
--set featureGates="AdditionalCertificateOutputFormats=true" --set webhook.extraArgs={--feature-gates="AdditionalCertificateOutputFormats=true"}


  • helm upgrade --install: Helm command to upgrade or install a chart. It ensures that the specified release is created if it doesn't exist or upgraded if it already does.
  • cert-manager: Name of the Helm release, which is a named instance of a chart.
  • jetstack/cert-manager: Specifies the Helm chart repository and the chart name to be installed or upgraded. In this case, it's using the cert-manager chart from the Jetstack repository.
  • --namespace cert-manager: Sets the Kubernetes namespace for the cert-manager installation to cert-manager.
  • --create-namespace: Instructs Helm to create the specified namespace if it doesn't already exist.
  • --version v1.11.0: Specifies the version of the cert-manager chart to be installed or upgraded. In this case, it's version 1.11.0.
  • --set installCRDs=true: Sets a Helm value to true, indicating that custom resource definitions (CRDs) should be installed. cert-manager uses CRDs to define its custom resources.
  • --set featureGates="AdditionalCertificateOutputFormats=true": Sets a Helm value related to feature gates. It enables the AdditionalCertificateOutputFormats feature gate, which is a feature in cert-manager for generating combined PEM files.
  • --set webhook.extraArgs={--feature-gates="AdditionalCertificateOutputFormats=true"}: Sets additional extra arguments for the cert-manager webhook, specifically enabling the AdditionalCertificateOutputFormats feature gate.

Known Issue

Issue NumberIssue Description
DS-7438Issue: If there is an increase in memory consumption by Prometheus server and kube-state-metrics, there is a probability of hitting Out-of-Memory (OOM) events for pds-tc-prometheus-server and pds-tc-kube-state-metrics.
User Impact: Due to increased memory consumption, users may experience disruptions in monitoring capabilities as a result of OOM events, impacting the stability and performance of the pds-tc-prometheus-server and pds-tc-kube-state-metrics components.
Workaround: To mitigate the issue and prevent OOM events, manually adjust resource limits for pds-tc-prometheus-server and pds-tc-kube-state-metrics using the Helm upgrade command. Allocate additional resources based on specific cluster requirements. Ensure to replace <desired-value>, <your-tenant-id>, <your-bearer-token>, and <your-api-endpoint> with appropriate values for your environment.
To increase memory limits for pds-tc-prometheus-server:
helm upgrade --create-namespace --namespace=pds-system pds pds-target --repo= --set tenantId=<your-tenant-id> --set bearerToken=<your-bearer-token> --set apiEndpoint=<your-api-endpoint> --set prometheus.server.resources.limits.memory=<desired-value>
To increase CPU limits for pds-tc-prometheus-server:
helm upgrade --create-namespace --namespace=pds-system pds pds-target --repo= --set tenantId=<your-tenant-id> --set bearerToken=<your-bearer-token> --set apiEndpoint=<your-api-endpoint> --set prometheus.server.resources.limits.cpu=<desired-value>
Similarly, adjust memory and CPU limits for pds-tc-kube-state-metrics:
helm upgrade --create-namespace --namespace=pds-system pds pds-target --repo= --set tenantId=<your-tenant-id> --set bearerToken=<your-bearer-token> --set apiEndpoint=<your-api-endpoint> --set prometheus.kubeStateMetrics.resources.limits.memory=<desired-value> --set prometheus.kubeStateMetrics.resources.limits cpu=<desired-value>
DS-7468Issue: Discrepancy about the deployment version update status.
User Impact: You may encounter confusion when the deployment version appears to be the latest, but the deployment dashboard indicates that an update is available in the deployment details view. This inconsistency could lead to uncertainty about the actual status of the deployment's version.
Workaround: If you observe such a mismatch, it is recommended to manually refresh or reload the page. This action should synchronize the information and accurately reflect whether an update is indeed available.

Release 122; Build 1081

November 15, 2023

New Features

Enhanced storage size management

You can now increase storage size for your deployed data services by following this procedure in the PDS UI. This enhancement provides greater flexibility and control over your data service resources. However, you cannot reduce the storage size once initially set during deployment is not supported.

Additionally, for users who have deployed data services with Helm chart versions prior to 1.22.0, updating to the latest Helm chart version is necessary to take advantage of this feature. PDS does not offer support for expanding storage size for these older versions.

Deployment health statuses update

The deployment health statuses, accessible through the deployment status API end point, have undergone the following modifications:

Previous PDS releasesPDS 122 release
DegradedPartially Available

See deployment health states in the PDS documentation for more information.

New data service version

PDS now supports the Elasticsearch data service version 8.10.2. See the Elasticsearch data service supported versions.

Release 121; Build 1075

September 29, 2023

New Features

Proxy server support for target clusters

PDS now provides proxy server support for target clusters. This capability elevates security, optimizes performance, and grants precise control over outbound communication traffic, ensuring a more robust and efficient network environment for your clusters.

Learn more about setting up different types of proxies here.

Custom registry support

PDS now provides the ability to specify and utilize custom image registries for storing and deploying PDS custom images. This feature offers flexibility in scenarios where private image registries are preferred or when custom image repositories are needed, providing greater control over your PDS deployments.

Learn more about obtaining custom images and configuring PDS components to utilize the custom image registry here.

Secure PostgreSQL provisioning with PDS

This update details a streamlined procedure for provisioning PostgreSQL databases with Transport Security Layer (TLS) in Kubernetes clusters using PDS. It also highlights the importance of Role-Based Access Control (RBAC) for secure management of ServiceIdentities within isolated namespaces.

Learn more about integrating ServiceIdentities with namespaces, configuring RBAC at a namespace level, and how to provision PostgreSQL with PDS here.

Known issue

Issue NumberIssue Description
DS-6669Deployments may enter a failed state when you update restored PostgreSQL data services configured with TLS. This known issue may cause problems when you attempt to perform updates on services, including scaling up nodes or adjusting resource allocations.

Release 120; Build 1070

August 28, 2023

New Features

One-click restore 

From this release, PDS enables you to easily restore your data and system configuration from a previously saved backup. See the Restore a backup section to learn how to restore the state of your database to a specific point in time, minimizing data loss and reducing downtime.


Copilot, in PDS, is an AI-powered tool that helps you to interact with databases using natural language queries instead of writing complex SQL queries. Copilot understands and interprets natural language inputs and translates them into appropriate database queries. This simplifies the process of querying databases and eliminates the need for you to have in-depth knowledge of database systems.

See the Copilot section to learn how you can interact with it.

New data service version

PDS now supports the Couchbase data service version 7.2.0. See the Couchbase data service supported versions.

Known issues

Issue NumberIssue Description
DS-6064Copilot queries may not be scoped to the deployment where the chat occurs. For example, you can access any MySQL data service deployment and inquire about PostgreSQL or non-MySQL questions, and Copilot will still answer to such queries.
DS-6079Scaling out the deployed data services failed while a backup and minimal workload were running.

Workaround: Wait until the backup job completes, and then try scaling out the deployment.
DS-6109In situations where a deployment involves a disconnected target cluster, the process of deleting backup jobs via the UI results in the removal of these jobs only from the source location. To delete the backup jobs completely, you should establish access to the target cluster and delete them manually.

Release 119; Build 1057

July 12, 2023


PDS has improved the way it handles real-time deployment events, which are retained for a week instead of 60 minutes. This will help with analysis and troubleshooting of data service deployment issues. See View deployment health for more information.

Known issues

Issue NumberIssue Description
DS-5771DNS records may take time to propagate. If you attempt to connect to the service before the DNS records are resolvable, your system may cache the empty value.

Workaround: If this happens, clear your DNS cache or wait for the cache to expire (typically a few minutes).
DS-5777If any FailedScheduling or FailedMount events occur more than eight minutes after the deployment begins, then the deployment is marked as Failed.

The system will attempt to auto-heal and the status may return to Normal once all pods are deployed.
DS-5785When all Redis master nodes are simultaneously shutdown, the cluster can fail to come back up, with pods crashlooping.

To fix this issue, manually delete the crashlooping pods.

Release 118; Build 1052

June 08, 2023

New Feature

The Deployment details page now includes the Last seen information, which helps you determine when PDS was last able to successfully retrieve the status of the data service. This information can assist you in troubleshooting the issue and restoring the disconnected data service. For more information, see Deployment dashboard.


PDS has improved the way it manages default users. For most data services, PDS now creates additional users beyond the default pds user. For more information about the users created by PDS for each data service and their corresponding permissions, see PDS users and permissions.

Known issues

Issue NumberIssue Description
DS-5570By clicking Enable advanced settings in the Edit Deployment window, you are able to select any version or build for a data service.

Downgrading to an older version or build is not supported and may lead to failure and/or data loss.
DS-5410MS SQL Server version 2019-CU18-rhel-8.5 has been shortened to 2019-CU18.

You must install the PDS chart version 1.17.1 or newer to deploy MS SQL Server version 2019-CU18.

Release 117; Build 1048

May 16, 2023

New Features

Data services dashboard

PDS now provides the new data services dashboard, which helps to:

  • view the list of deployed data services
  • filter by data services, deployment states and deployment targets
  • get an overview of each data service
  • perform operations such as backup, delete, and update each data service

For more information, see Data services dashboard.

Availability of new data service

This release includes the MS SQL Server version 2019-CU18-rhel-8.5 data service. See here for the available MS SQL Server data service versions.

Release 116; Build 1041

April 13, 2023

New Features

Pod Security Admission

The Pod Security Admission (PSA) feature is a critical security enhancement introduced in the Kubernetes platform, which helps to enforce security policies by controlling the creation and deployment of pods. PSA allows cluster administrators to define security policies that are applied at the time of pod creation, ensuring that only trusted pods are deployed in the cluster.

For more information about the security levels currently implemented in PDS, see Pod Security Admission.

New Kubernetes versions and platforms support

PDS now supports the:

  • Kubernetes versions 1.25 and 1.26
  • OCP version 4.12

See Prerequisites and Supported versions for all the supported platforms and versions.

Known issue

Issue NumberIssue Description
DS-5263If the deployment target is disconnected, then the data services (that are in the Available state) deployed in such deployment target will still display the status as Available in the deployment details page.

When performing operations such as Update and Edit on such deployments, PDS displays the Deployment target is not available error.

Release 115; Build 1036

March 28, 2023

Latest Portworx version compatibility

PDS is now compatible with the Portworx 2.13.x versions.

You can find a list of supported target clusters and the corresponding Portworx versions in the Prerequisites topic.

Known issues

Issue NumberIssue Description
DS-5105Some PDS functionality is dependent on database access. Examples include monitoring and backups. If you change the password for the pds user, you need to also update the corresponding Kubernetes secret for the deployment. The secret can be found in the namespace with the name <_DEPLOYMENT-NAME_>-creds.

For more information, see Update Kubernetes secret after changing the pds password.
DS-5105Cassandra backups require database access. If you change the password for the pds user, you need to also update the cqlshrc file located on each pod. The file is located under ~/.cassandra/cqlshrc.

For more information, see Update the pds password in the cqlshrc file for Cassandra pods.

Fixed issues

This release fixes the following issues:

Issue NumberReported in ReleaseFix Description
DS-4612114It is now possible to select menu items by scrolling through the dropdown menus in the Deploy <data-service> window.
DS-4700114After rebooting any of the Couchbase pods, error messages will not appear in the pod logs.

Release 114; Build 1028

February 24, 2023

New Features

Static IP support

PDS now supports static IPs, which you can whitelist in your firewall rules. For more information, see Static IPs support.


The Portworx CSI provisioner is used as a default provisioner for Prometheus volumes in new PDS installations. The Portworx in-tree provisioner is deprecated and its support may be discontinued in future PDS releases.

Known issues

Issue NumberIssue Description
DS-4579When you deploy Couchbase on RKE2 and upgrade from previous image, the Failed to pull and unpack image error message appears. This issue occurs, because the containerd versions older than 1.6.10 had issues deflating images with extended attributes.

Workaround: Couchbase on RKE2 requires the containerd version 1.6.10 or newer.
DS-4612When you click a dropdown menu (Backup, Target, and so on) in the Deploy <data-service> and Edit Deployment windows, you cannot pull the scroll bar down to select the menu items.

Workaround: Use the down arrow on the keyboard, the wheel button on mouse, or any peripheral devices to scroll down and select the dropdown menu items.
DS-4700When you reboot any of the Couchbase pods, the nodes are restored. However, you will see unhealthy error messages in the pod logs. These messages are harmless and would not affect the actual data traffic.
DS-4727In a multi-node target cluster, if the node that is hosting the pds-operator-target-controller-manager pod goes down, then there will be an expected downtime of 5 minutes between PDS control plane and target cluster. During this time, the target cluster would become disconnected from the PDS control plane and all the data services on this target cluster will be inaccessible from PDS UI.

Workaround: Wait for five minutes until the target cluster is reconnected. Once it is connected, you can access all the relevant data services from PDS UI.

Release 113; Build - 1025

January 26, 2023

New Features

Availability of new data services

This release includes the following new data services:

  • Consul
  • Couchbase
  • Elasticsearch
  • MongoDB Enterprise

Before deploying Elasticsearch, you must configure the virtual memory limit of Elasticsearch to 262144 or higher on each Kubernetes node of the target cluster. For more information, see Configure Elasticsearch memory.


For MongoDB Enterprise and Elasticsearch, the automatically created PDS user does not have general Administrator privileges. It only has permission to create other users.

See the supported versions for MongoDB Enterprise and Elasticsearch data services..

Ability to add any users

The PDS administrator can now add users without a valid Portworx account to an existing PDS account. For more information about adding users, see Add users.

Deprecation announcement

From this release, support for the following legacy Portworx installations is deprecated:

  • Portworx with CSI driver disabled: By default, the CSI driver will be enabled on new Portworx installations. On the older Portworx installations, you can enable the CSI driver.
  • DaemonSet installation: PDS is compatible with the Portworx Operator installation. You can migrate the existing Portworx installed from a DaemonSet to the Operator.

Currently, Portworx provides technical support for the above mentioned legacy Portworx installations. This support may not be available in the future PDS releases.

Known issues

Issue NumberIssue Description
DS-2371If you deploy a single-node Redis cluster, then you cannot modify the node count in the Edit Redis Deployment -> Number of nodes dropdown.
DS-3265When you backup a Redis cluster, the backup job runs just on one container. So, PDS backs up only a part of the data. To perform a full backup, you can update the backup operator or use a new version to run backup jobs on each Redis container. However, updating the backup operator is not backward compatible since the operator runs backup script on each Redis container and it causes race condition on old containers that makes backup to fail.

Workaround: To backup Redis data service without issues, use the new Redis image.
DS-4014In most of the MySQL cluster deployments, the DNS host is taking more than 30 minutes to become available.

Workaround: Sometimes, this issue occurs due to the slow propagation of DNS records from AWS Route 53 to clients. You must wait for the public DNS caches to clear.
DS-4236PDS UI does not properly report the long running MySQL backups.

Workaround: To get up-to-date report, check the and resources in your Kubernetes target cluster.
DS-4356Existing backup targets go out of sync after some time, after being successfully synchronized to some EKS target clusters.

Workaround: Create a new backup target and check if the sync is successful.

Release 112; Build - 1022

December 15, 2022

This release provides a seamless experience with many UI improvements reported in the earlier versions.

Known issues

Issue NumberIssue Description
DS-3935Sometimes, even for a successfully deployed data service, intermittent error messages may appear in the data service Deployment dashboard after idling in the same screen for a long time.

Workaround: Refresh the dashboard and re-login to get rid of the error messages.

Release 111; Build - 1020

December 08, 2022

New Features

New data service versions

This release includes the following new data service versions:

  • MySQL: 8.0.31

  • Redis: 7.0.5

Known issues

Issue NumberIssue Description
DS-3792When all nodes in your MySQL cluster crash with OutOfMemory error due to high load, the MySQL cluster could fail to restart due to diverged GTIDs.

Workaround: To learn more about this issue and for troubleshooting instructions, see the Advanced data recovery topic.
DS-3803Data service endpoints are not reachable in the OCP 4.11 cluster. This issue occurs, if the external-dns change request is longer than 32000 characters.

Workaround: In the external-dns deployment spec, reduce the batch size for external-dns (for example, 100) by updating the aws-batch-change-size flag.
DS-3818You cannot backup a data service, while workload is in progress. This issue occurs when there are no available resources for backup process. For example, if a database is serving heavy workload consuming all available resources, the backup attempt may fail.

Workaround: You can restrict the workload inside a database to run with limited resources to provide the background processes (for example, backup) enough resources to run. Alternatively, you can retry backup when the database is slightly less busy in consuming resorces.
DS-3825Sometimes, even though the data service backup is completed successfully, the backup job indicator displays red.

Workaround: Delete the data service backup, and perform the backup job again.
DS-3838PDS allows new database deployments to namespaces that are in the terminating state, even though such deployments always fail.

Workaround: Run the following command to check if the deployment's database is in the terminating state:
kubectl get namespaces
If the database is in the terminating state, then:
  1. Create a new namespace with the "”: “true” label.
  2. Delete the failing deployment in the PDS UI.
  3. Deploy again using the new namespace.


Do not deploy into a namespace that is in the terminating state.
DS-3874If you create a Kubernetes cluster without installing Portworx, and register the created cluster to control plane, then the cluster gets added as Unhealthy. When you remove the Unhealthy cluster from the UI, it is removed successfully. However, a new entry for the same cluster is populated, which gets stuck in the Initializing phase.

Workaround: Before removing the Unhealthy cluster from the UI, you must uninstall the PDS Helm chart:
helm uninstall -n pds-system pds

Release 110; Build - 1016

November 15, 2022

New Features

Portworx CSI support

PDS now allows you to choose Portworx CSI with the PDS chart version 1.9.0 or newer.
For more information about the new storage options, see Add or manage a storage option template.

Ability to add user API keys

You can add user API keys, in the PDS Profile page, to authenticate and authorize API calls to PDS and automate your work with PDS.
For more information, see Add user API keys.

Filter data services and deployment targets

The new search and filter options in the data service deployments and the deployment targets pages help you find one or more specific entries from the entire list.
For more information, see Filter data services.

Anthos support

PDS now supports the Anthos platform version 1.21.

New data service versions

This release includes the following new data service versions:

  • Cassandra: 4.0.6

  • Kafka: 3.2.3

  • RabbitMQ: 3.10.9

IMPORTANT: From this release, you must install the PDS chart version 1.9.0 or newer to ensure new PostgreSQL versions are compatible with older versions (until the chart version 1.8.1).

New Kubernetes versions

PDS supports the following new Kubernetes versions in this release:

  • Vanilla Kubernetes: version 1.24.0

  • OCP: versions 4.11 and 4.10

Latest Portworx version compatibility

PDS is now compatible with the latest Portworx version 2.12.0.

You can view all supported target clusters and compatible Portworx versions in the Prerequisites topic.

Known issues

Issue NumberIssue Description
DS-3461Unable to connect to the PostgreSQL server when the storage reaches its maximum limit.

Workaround: Manually resize the PVC to connect to the PostgreSQL server:
kubectl edit pvc \<claim-name\>
DS-3494Data service deployment fails in the on-premises cluster, if you choose XFS as the filesystem type when adding a storage options template.

Note: This issue occurs only with the Portworx version 1.12.0.

Workaround: Choose the Ext4 filesystem type, instead, to deploy a data service.
DS-3653The filter option(s) that you selected in the All Deployment Targets dropdown are valid to only the selected data service. When you select another data service with the same filter options, then the search results will not be accurate.

Workaround: When you select another data service, reset the filter and then select new deployment targets from the dropdown to get accurate search results.

Release - 109; Build - 1011

October 18, 2022

New Features

Sample templates to configure data services

PDS provides the sample Application Configuration and Resource Settings templates with predefined parameters. You can copy these sample templates, modify the parameters (if necessary), and easily configure your data services for deployment.
For more information about using these sample templates, refer to the Configure data services topic.

Update a data service

PDS automatically detects if an updated version is available for a data service. You can then update the data service to the latest version with a single-click. For more information, refer to the Update a data service topic.

Availability of MySQL

PDS now includes the MySQL version 8.0.30 as a data service.

Ensure that you install the pds-target Helm chart 1.8.1 or a newer version before deploying the MySQL data service.

New target cluster

PDS now supports the Google Kubernetes Engine (GKE) version 1.23.8-gke.1900 as a target cluster.
For more information about all supported target clusters, refer to the Prerequisites topic.

Ensure that you install the pds-target Helm chart 1.8.1 or a newer version before deploying the target cluster.

New PostgreSQL version

PDS now supports the PostgreSQL version 14.5.
You can view the supported PostgreSQL data service versions here.


PDS has upgraded or enhanced functionality in the following areas:

  • Persistent Volumes created for data service deployments in a target cluster contain PDS labels to make them easier to identify.

  • The annotations or labels to mark loadbalancers in target clusters as internal were extended to cover more cloud providers.

Known issues

Issue NumberIssue Description
DS-3097A downtime of few seconds is expected when you upgrade the PostgreSQL and MySQL data service.
DS-3176In each data service deployment details page → Additional Details window → Connection tab → >Nodes list displays the 0 (zero) node twice.
DS-3211The URLs in the Settings -> Data Services -> <data-service> Templates pages are broken.

Workaround: Refer to the Configure data services section for more information about data services templates.
DS-3222You cannot backup a data service when it is getting updated.

Workaround: Do not select the Backup button, though it is enabled during the data service update process.
DS-3246During the data service deployment process, the deployment dashboard displays failure and warning messages.

Workaround: Ignore these messages, since the deployment will be eventually successful.
DS-3252In the MySQL metrics page -> Application Details section, limits get varied for the following metrics:
  • Connections chart → Max Connections metric
  • InnoDB Open Files chart → Open Files Limit metric
DS-3282The backup targets created in PDS are not reachable from the target clusters for TLS disabled S3 endpoints or TLS S3 endpoints not signed by a trusted certificate authority.

Workaround: Enable TLS with a trusted TLS certificate to reach backup targets from target clusters.

Release - 108; Build - 1007

September 15, 2022

New Features

New target clusters

PDS now supports vSphere with Tanzu, Rancher Kubernetes Engine (RKE1), and RKE2 as target clusters.

Ensure that you install the pds-target Helm chart 1.7.1 or a newer version before deploying these target clusters.

Google Cloud backup credential and target

You can now add Google Cloud compatible backup credentials and backup targets in PDS.
For more information, refer to the Configure backup credentials and Configure Google Cloud targets topics.

Known issue

Issue NumberIssue Description
PWX-26445On PDS clusters, volume creation fails with the unauthorized error message.

Workaround: Restart Portworx pods.

Note: If you are running Portworx using the Portworx Operator, then you can label your nodes with px/service=restart and the Operator will restart the specific Portworx node.
DS-2936On Tanzu Kubernetes clusters only, when you create or edit a ZooKeeper data service deployment, the pods will sometimes crash with the following error message: Cannot assign requested address (Bind failed)
After a few minutes, this issue will eventually resolve by itself and the pods will run normally.

Release - 107; Build - 1001

August 18, 2022

New Features

Upgrade Kubernetes cluster

In the SettingsDeployment Targets page → each deployed cluster, an Upgrade button is available now.
For more information, refer to the upgrade PDS system on a target Kubernetes cluster topic.

Release and build number

PDS now includes the About page in the Settings menu, which displays the current PDS release, build details, and the end user terms for reference.

Removal of advanced deployment settings

The dns_zone and load_balancer_source_ranges parameters in the data service deployment dialog box → Advanced section are removed from this release.

Known issues

Issue NumberIssue Description
DS-2628In the RabbitMQ deployments, the Application DetailsIncoming messages chart in the Metrics page displays only the messages that were sent with confirmation.
DS-2659The Cassandra data service fails to come up after rebooting the Kubernetes nodes.

Workaround: Delete the pod, which is in CrashLoopBackOff state, so that it re-spawns normally:

kubectl delete pod <crashing_pod_name> -n <name_space>

July 19, 2022

New Features

Availability of Redis

PDS now includes Redis version 7.0.2 as a data service.

Data service version and image selection

You can now deploy more than one data service version in PDS, and the corresponding image for that version.
For more information about selecting the version and image, refer to the Procedure to deploy a data service section.

Restrictions for selecting nodes per target cluster

PDS now allows you to select only a specific number of nodes to deploy each data service on a target cluster. You can select the nodes from the Deploy a data service dialog box → No. of Nodes dropdown.
For more information about the available number of nodes for each data service, refer to the Node restrictions section.

Add an empty application configuration template

You can now add an empty Application Configuration Template, and specify the application configuration parameters later when you deploy a data service.
For more information about adding an empty template, refer to the Add an empty template topic.

Known issue

Issue NumberIssue Description
DS-2399The Redis data service does not include the default, empty application configuration and resource settings templates, in this release.

Workaround: Before deploying the Redis data service in PDS, the Admin must add an empty Application Configuration template and a Resource Settings template.

June 30, 2022

This release provides a seamless experience with a reduced number of vulnerabilities reported in the earlier versions.

New Feature

You can now view the status of your deployments. To view real-time events:

  1. In the Deployments page, select a deployed data service.

  2. In the deployment details page, select the vertical ellipsis button next to Edit. From the options, select View Deployment Health.

  3. In the Deployment Health window, select the Events tab.


    You can also click the node hexagons, in the deployment details page, to view the Deployment Health window.

The status descriptions help you know the following information about your deployment:

  • whether it is failed or created successfully

  • reasons for the failure

  • timestamp

Known issue

Issue NumberIssue Description
DS-2334If your backup does not complete within the timeout value of 24 hours, then the backup eventually fails on the target cluster.

Workaround: Since the backup process will keep running inside the data service pod(s), you can terminate the backup process.

Jun 20, 2022

Known issue

Issue NumberIssue Description
DS-2181In the Metrics of a PostgreSQL deployment, under Application Details, the Server Session Count chart shows wrong Total count.
DS-2219As an Admin, after adding a backup target, you can only edit the Name of the backup target but cannot change the Cloud account, Bucket name, Container name and Region of the backup target.

To change the fields, Pure Storage recommends to delete the backup target and a new backup target with the desired options in the fields.

May 25, 2022

Known issue

Issue NumberIssue Description
DS-2078When multiple PDS data services are deployed on the Portworx cluster, deployments may fail due to a lack of free space on Portworx volumes. The filesystem enters read-only mode when the storage reaches 90% of its capacity, and it may be unavailable if some Portworx node pools go offline.

As PDS deployments depend on Portworx volumes, ensure that Portworx clusters are running without errors to avoid a data service deployment failure.

Apr 28, 2022

Announcing general availability for Portworx Data Services!

Known issues

Issue NumberIssue Description
DS-1113If you delete backup credentials manually using the pxctl credentials delete command, PDS fails to detect and recreate the credentials on the target cluster.
DS-1607In some edge cases when all RabbitMQ pods are terminated at once, the first pod fails to start and the pod’s log contains the following message:

Waiting for Mnesia tables for 30000 ms, X retries left

Workaround: Run kubectl exec -n <namespace> <pod_name> /srv/pds/pds-utils/ to fix the issue.
DS-1927Due to a bug in PostgreSQL exporter, an extra stale database connection does not allow deletion of a PostgreSQL database and shows the following error:

DROP DATABASE "database-name" ; ERROR: database "database-name" is being accessed by other users DETAIL: There is 1 other session using the database.

Force drop: Use DROP DATABASE <database-name> WITH (FORCE); instead of DROP DATABASE <database-name>;. It may fail if the database user does not have permissions to terminate existing database connections.

Exclude database from metrics collection: You can temporarily or permanently exclude a database from metrics collection which will not allow the postgresql exporter to connect to the database:
  1. Create new application configuration template called Exclude database metrics.
  2. Add deployment time variable called PG_EXPORTER_EXCLUDE_DATABASES.
  3. Set PG_EXPORTER_EXCLUDE_DATABASES to <database-name> when creating or editing a PostgreSQL data service deployment.
  4. Use DROP DATABASE <database-name>, to remove the database.