This document contains pertinent release information about VMware Tanzu for Postgres on Kubernetes. Obtain the most recent version of the distribution from Broadcom Support.
NoteVMware Tanzu for Postgres on Kubernetes (Tanzu for Postgres on Kubernetes for short) was previously called VMware Tanzu SQL with Postgres for Kubernetes.
Release Date: August 6, 2024
VMware Postgres Version | Component | Component Version | |
---|---|---|---|
3.0 | PostgreSQL | 15.7, 14.12, 13.15, 12.19, and 11.22 | |
pgBackRest | 2.51 | ||
pg_auto_failover | 2.1.0 | ||
postGIS | 3.4.0 | ||
Orafce | 4.10 | ||
pgAudit | 1.7.0 (for 15), 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
||
pgvector | 0.7.0 for (PostgreSQL version 15, 14, 13, and 11) |
The VMware Postgres Operator images are based on Ubuntu 22.04.
VMware Tanzu for Postgres on Kubernetes is intended to be used with any Kubernetes compliant platform of version 1.23 or later.
Specifically, this version of VMware Tanzu for Postgres on Kubernetes is tested on the following platforms:
VMware Tanzu Kubernetes Grid Integrated Edition ( TKGI)
NoteDue to an incompatibility with the
containerd
provided, TKGI 1.13.0 and 1.13.1 clusters must be configured with the docker container runtime instead of the defaultcontainerd
runtime. Existing clusters upgraded to TKGI 1.13 can continue to use the docker runtime. TKGI 1.13.2 is patched with version 1.5.9 of thecontainerd
runtime to avoid the incompatibility issue.
Google Kubernetes Engine (GKE)
Azure Kubernetes Service (AKS)
Amazon Elastic Kubernetes Service (Amazon EKS)
Red Hat Openshift - version 4.10+
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANTVMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator by using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
3.0.0 | 1.14.0 |
2.3.0, 2.2.1, 2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.13.0 |
2.2.1, 2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.12.0 |
2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.10.0 |
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.9.0 |
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.8.0 |
2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.1 |
2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.0 |
2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.6.0 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
For more information, see Installing using the Tanzu CLI.
To upgrade to Tanzu Postgres 3.0, review the Upgrading the Tanzu Postgres Operator and Instances page and the Important upgrade notes topic.
Release Date: January 22, 2024
VMware Postgres Version | Component | Component Version | |
---|---|---|---|
2.3.0 | PostgreSQL | 15.5, 14.10, 13.13, 12.17, and 11.22 | |
pgBackRest | 2.48 | ||
pg_auto_failover | 2.0.0 | ||
postGIS | 3.3.2 | ||
Orafce | 4.4 | ||
pgAudit | 1.7.0 (for 15), 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
||
pgvector | 0.4.4 for (PostgreSQL version 15, 14, 13, and 11) |
The VMware Postgres Operator images are based on Ubuntu 22.04.
VMware Tanzu for Postgres on Kubernetes is intended to be used with any Kubernetes compliant platform of version 1.23 or later.
Specifically, this version of VMware Tanzu for Postgres on Kubernetes is tested on the following platforms:
VMware Tanzu Kubernetes Grid Integrated Edition ( TKGI)
Note: Due to an incompatibilty with the containerd
provided, TKGI 1.13.0 and 1.13.1 clusters must be configured with the docker container runtime instead of the default containerd
runtime. Existing clusters upgraded to TKGI 1.13 can continue to use the docker runtime. TKGI 1.13.2 is patched with version 1.5.9 of the containerd
runtime to avoid the incompatibility issue.
Google Kubernetes Engine (GKE)
Azure Kubernetes Service (AKS)
Amazon Elastic Kubernetes Service (Amazon EKS)
Red Hat Openshift - version 4.10+
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANTVMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
2.3.0, 2.2.1, 2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.13.0 |
2.2.1, 2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.12.0 |
2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.10.0 |
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.9.0 |
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.8.0 |
2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.1 |
2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.0 |
2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.6.0 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
For more information, refer to Installing using the Tanzu CLI.
registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.13.0
. For more information, see Installing the Tanzu Operator using the Tanzu CLI.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
.To upgrade to Tanzu Postgres 2.3.0, review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic
Release Date: October 18, 2023
VMware Postgres Version | Component | Component Version | |
---|---|---|---|
2.2.1 | PostgreSQL | 15.4, 14.9, 13.12, 12.16, and 11.21 | |
pgBackRest | 2.47 | ||
pg_auto_failover | 2.0.0 | ||
postGIS | 3.3.2 | ||
Orafce | 4.4 | ||
pgAudit | 1.7.0 (for 15), 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
The VMware Postgres Operator images are based on Ubuntu 22.04.
VMware Tanzu for Postgres on Kubernetes is intended to be used with any Kubernetes compliant platform of version 1.21 or later.
Specifically, this version of VMware Tanzu for Postgres on Kubernetes is tested on the following platforms:
VMware Tanzu Kubernetes Grid Integrated Edition ( TKGI)
Note: Due to an incompatibilty with the containerd
provided, TKGI 1.13.0 and 1.13.1 clusters must be configured with the docker container runtime instead of the default containerd
runtime. Existing clusters upgraded to TKGI 1.13 can continue to use the docker runtime. TKGI 1.13.2 is patched with version 1.5.9 of the containerd
runtime to avoid the incompatibility issue.
Google Kubernetes Engine (GKE)
Azure Kubernetes Service (AKS)
Amazon Elastic Kubernetes Service (Amazon EKS)
Red Hat Openshift - version 4.10+
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANTVMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
2.2.1, 2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.12.0 |
2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.10.0 |
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.9.0 |
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.8.0 |
2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.1 |
2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.0 |
2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.6.0 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
For more information, refer to Installing using the Tanzu CLI.
registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.12.0
. For more information see Installing the Tanzu Operator using the Tanzu CLI.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
.To upgrade to Tanzu Postgres 2.2.1, review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic
Release Date: August 23, 2023
VMware Postgres Version | Component | Component Version | |
---|---|---|---|
2.2.0 | PostgreSQL | 15.4, 14.9, 13.12, 12.16, and 11.21 | |
pgBackRest | 2.47 | ||
pg_auto_failover | 2.0.0 | ||
postGIS | 3.3.2 | ||
Orafce | 4.4 | ||
pgAudit | 1.7.0 (for 15), 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
The VMware Postgres Operator images are based on Ubuntu 22.04.
VMware Tanzu for Postgres on Kubernetes is intended to be used with any Kubernetes compliant platform of version 1.21 or later.
Specifically, this version of VMware Tanzu for Postgres on Kubernetes is tested on the following platforms:
VMware Tanzu Kubernetes Grid Integrated Edition ( TKGI)
Note: Due to an incompatibilty with the containerd
provided, TKGI 1.13.0 and 1.13.1 clusters must be configured with the docker container runtime instead of the default containerd
runtime. Existing clusters upgraded to TKGI 1.13 can continue to use the docker runtime. TKGI 1.13.2 is patched with version 1.5.9 of the containerd
runtime to avoid the incompatibility issue.
Google Kubernetes Engine (GKE)
Azure Kubernetes Service (AKS)
Amazon Elastic Kubernetes Service (Amazon EKS)
Red Hat Openshift - version 4.10+
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANTVMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
2.2.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.10.0 |
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.9.0 |
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.8.0 |
2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.1 |
2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.0 |
2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.6.0 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
For more information, refer to Installing using the Tanzu CLI.
spec.pointInTime
field is now deprecated in favor of spec.pitr.type
set to time
.spec.customConfig
changes can be tracked status conditions on the Postgres resource.registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.10.0
. For more information see Installing the Tanzu Operator using the Tanzu CLI.Running
before the necessary database and users are created. This issue is fixed.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
.To upgrade to Tanzu Postgres 2.2.0 review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic.
Release Date: May 23, 2023
VMware Postgres Version | Component | Component Version |
---|---|---|
2.1.0 | PostgreSQL | 15.3, 14.8, 13.11, 12.15, 11.20 |
pgBackRest | 2.45 | |
pg_auto_failover | 2.0 | |
postGIS | 3.3.2 | |
Orafce | 4.2 | |
pgAudit | 1.7.0 (for 15), 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
The VMware Postgres Operator images are based on Ubuntu 22.04.
VMware Tanzu for Postgres on Kubernetes is intended to be used with any Kubernetes compliant platform that is version 1.21 or newer.
Specifically, this version of VMware Tanzu for Postgres on Kubernetes is tested on the following platforms:
NoteTKGI 1.13.0 and 1.13.1 clusters must be configured with the docker container runtime instead of the default
containerd
runtime due to an incompatibilty with thecontainerd
provided. Existing clusters upgraded to TKGI 1.13 will continue to use the docker runtime. TKGI 1.13.2 is patched with version 1.5.9 of thecontainerd
runtime to avoid the incompatibility issue.
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANTVMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
2.1.0, 2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.8.0 |
2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.1 |
2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.0 |
2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.6.0 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
For more information refer to Installing using the Tanzu CLI.
spec.customConfig.pghba
. For more details, see Configuring the pghba file.spec.cpu
and spec.memory
fields have been removed from the Postgres CRD.registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.8.0
. For more information see Installing the Tanzu Operator using the Tanzu CLI.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 2.1.0 review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic.
Release Date: April 5, 2023
VMware Postgres Version | Component | Component Version |
---|---|---|
2.0.2 | PostgreSQL | 15.2, 14.7, 13.10, 12.14, and 11.19 |
pgBackRest | 2.44 | |
pg_auto_failover | 2.0.0 | |
postGIS | 3.3.2 | |
Orafce | 4.1 | |
pgAudit | 1.7.0 (for 15), 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
The VMware Postgres Operator images are based on Ubuntu 22.04.
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
2.0.2, 2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.1 |
2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.0 |
2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.6.0 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
For more information refer to Installing using the Tanzu CLI.
registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.7.1
. For more information see Installing the Tanzu Operator using the Tanzu CLI.enableSSL
set to true
failed from version 2.0.0. This issue has been fixed in this version.root
. This issue has been fixed and the user has been updated to nonroot
.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 2.0.2 review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic.
Release Date: March 9th, 2023
VMware Postgres Version | Component | Component Version |
---|---|---|
2.0.1 | PostgreSQL | 15.2, 14.7, 13.10, 12.14, and 11.19 |
pgBackRest | 2.44 | |
pg_auto_failover | 2.0.0 | |
postGIS | 3.3.2 | |
Orafce | 4.1 | |
pgAudit | 1.7.0 (for 15), 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
The VMware Postgres Operator images are based on Ubuntu 22.04.
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
2.0.1, 2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.7.0 |
2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.6.0 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
For more information refer to Installing using the Tanzu CLI.
registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.7.0
. For more information see Installing the Tanzu Operator using the Tanzu CLI.log_directory
cannot be updated through the custom configmap.log_filename
parameter is changed. This issue has been fixed in this release.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 2.0.1 review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic.
Release Date: December 20th , 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
2.0.0 | PostgreSQL | 15.1, 14.6, 13.9, 12.13, and 11.18 |
pgBackRest | 2.41 | |
pg_auto_failover | 2.0 | |
postGIS | 3.3.1 (for 15), 3.2.3 (for 11, 12, 13, and 14) |
|
Orafce | 3.25 | |
pgAudit | 1.7 (for 15), 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
The VMware Postgres Operator images are based on Ubuntu 22.04.
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
2.0.0, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.6.0 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
For more information refer to Installing using the Tanzu CLI.
spec.highAvailability.readReplicas
. For more details see Postgres CRD API Reference.customConfig
. For details refer to Customizing the PostgreSQL Server, and customConfig.spec.expire
allows users to expire backups from the S3 location, and the Kubernetes Operator, when the instance no longer exists. For details refer to Expire Backups.kubectl describe postgres <name-of-instance>
.spec.sharedMemorySize
to the Postgres CRD, to facilitate large queries, and parallel workers. This field is only available for Kubernetes version 1.22 and higher. For details refer to sharedMemorySize.Message
field when describing an instance (kubectl describe postgres <postgres-instance-name>
), which displays any errors that might have occured during a task, or an operation. For more details refer to Troubleshooting.kubectl logs <instance-name> -c instance-logging
to view the logs. For details on updating server parameters refer to Updating PostgreSQL parameters.registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.6.0
. For more information see Installing the VMware Postgres Operator using the Tanzu CLI.md5
authentication any longer. Update any existing Postgres roles that use md5
password authentication to scram-sha-256
.kubectl rollout restart sts <name-of-instance>
, only one of the pods was restarted, instead of both. This issue has been fixed, and now both pods restart one after the another.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.Important: Due to the upgrade of the glibc library from 2.27 to 2.35, some indexes will be affected by collation changes and must be reindexed.
To upgrade to Tanzu Postgres 2.0.0 review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic.
Release Date: November 28th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.9.1 | PostgreSQL | 14.6, 13.9, 12.13, and 11.18 |
pgBackRest | 2.41 | |
pg_auto_failover | 2.0 | |
postGIS | 2.5.8 (for 11, 12), 3.2.3 (for 13, 14) | |
Orafce | 3.25 | |
pgAudit | 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
1.9.1, 1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.1 |
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.3.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.2.0 |
1.8.0, 1.7.2 | 1.1.0 |
1.7.3, 1.7.2, 1.7.1 | 1.0.2 |
1.7.2, 1.7.1 | 1.0.1 |
1.7.1 | 1.0.0 |
For more information refer to Installing using the Tanzu CLI.
registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.5.1
. For more information see Installing the Tanzu Operator using the Tanzu CLI.postgres-metrics-exporter
logs were filled with error messages caused by the lack of CONNECT privileges for metrics user postgres_exporter
, when attempting to collect pg_database_size_bytes
metric data. This issue has now been resolved.appUser
, readOnlyUser
, and readWriteUser
in the Postgres instance manifest cannot be altered after the instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 1.9.1 review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic.
Release Date: October 12th , 2022
VMware SQL with Postgres Version | Component | Component Version |
---|---|---|
1.9.0 | PostgreSQL | 14.5, 13.8, 12.12, and 11.17 |
pgBackRest | 2.40 | |
pg_auto_failover | 1.6.4 | |
postGIS | 2.5.8 (for 11, 12), 3.2.3 (for 13, 14) | |
Orafce | 3.21 | |
pgAudit | 1.6.2 (for 14), 1.5.2 (for 13), 1.4.3 (for 12), 1.3.4 (for 11) |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
To install the Tanzu Postgres Operator using the Tanzu CLI, use the following Postgres to TDS package mapping:
VMware SQL for Postgres Versions | TDS Package version |
---|---|
1.9.0, 1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.5.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.4.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.3.0 |
1.8.0, 1.7.3, 1.7.2, 1.7.1 | 1.2.0 |
1.8.0, 1.7.2 | 1.1.0 |
1.7.3, 1.7.2, 1.7.1 | 1.0.2 |
1.7.2, 1.7.1 | 1.0.1 |
1.7.1 | 1.0.0 |
For more information refer to Installing using the Tanzu CLI.
spec.persistentVolumeClaimPolicy
to the Postgres instance yaml, that specifies retention policy to the instance PVC after an instance deletion. For more information see Configure Persistent Volume Claim Retention Policy, and persistentVolumeClaimPolicy.enableSecurityContext
in the Operator values.yaml
, which must be changed to false
for Openshift deployments. For details see Installing a Tanzu Postgres Operator.seccompProfile
value in the Postgres instance CRD yaml, and generates an error if the user configures an unsupported value type.spec.pgConfig
field, readOnlyUser
and readWriteUser
, for the instance database named under pgConfig.dbname
. For further details refer to pgConfig in the Postgres CRD API Reference page, or Create custom database name and user account.registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.5.0
. For more information see Installing the Tanzu Operator using the Tanzu CLI.standard
as the default storage class for the data and monitor pods. The fields monitorStorageClassName
and storageClassName
if left unspecified, are configured using the default Kubernetes storage class (annotated with storageclass.kubernetes.io/is-default-class
). For more details refer to storageClassName in the Postgres CRD reference page.PostgresBackup version on the backup and the target instance don't match
. You can view the restore status by using a command like kubectl describe postgresrestore <name of restore object>
.public
schema for postgres
, and pgConfig.dbname
databases. Before upgrading to Tanzu Postgres 1.9.0, existing manually created roles with no explicitly granted permissions, or roles that relied on the default privileges for public
schema, will need to be updated. For upgrade details refer to the Notes in Upgrading the Tanzu Postgres Operator and Instances.appUser
, readOnlyUser
, and readWriteUser
in the Postgres instance manifest cannot be altered after the instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 1.9.0 review the Upgrading the Tanzu Postgres Operator and Instances page, and the Important upgrade notes topic.
Release Date: July 7th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.8.0 | PostgreSQL | 14.4, 13.7, 12.11, and 11.16 |
pgBackRest | 2.38 | |
pg_auto_failover | 1.6.4 | |
postGIS | 3.2.1 (for 11, 12,13 and 14) | |
Orafce | 3.21 | |
pgAudit | 1.6.1 (for 14), 1.5.1 (for 13), 1.4.1 (for 12), 1.3.1 (for 11), 1.2.1 (for 10) |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
spec.deployOptions.continuousRestoreTarget
, spec.deployOptions.sourceStanzaName
, and status.lastRestoreTime
. For more details see Configuring Disaster Recovery.pointInTime
. For more details see Perform a point-in-time restore, and Backup and Restore CRD API Reference.spec.resources.data.limits.cpu
, spec.resources.data.limits.memory
, spec.resources.data.requests.cpu
, and spec.resources.data.requests.cpu
. These fields replace the spec.cpu
and spec.memory
fields in previous Tanzu Postgres versions. Users should switch to the new resource optional fields, as the spec.cpu
and spec.memory
fields will be deprecated in a future release. For details see resources in the Postgres CRD API Reference page.kubectl get postgresbackup
now includes an additional column that shows the SOURCE NAMESPACE
of an instance's backup. This column helps uniquely identify backups when the same backup name is used across different namespaces.status.backups
fields in the Postgres Custom Resource Definition (CRD). The new fields, lastSuccessful
and lastCreated
, describe the most recent successful backup, and the most recently created backup. For more details see Postgres CRD API Reference.CREATE INDEX CONCURRENTLY
or REINDEX CONCURRENTLY
commands. For more details, review E.1.2 Changes, and PostgreSQL 14.4 Release Notes.registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.1.0
. For more information see Installing the Tanzu Operator using the Tanzu CLI.kubectl get postgresbackup
would show backups that were expried or deleted at the storage location. This issue has been fixed and PostgresBackup objects corresponding to expired backups will now be automatically deleted from Kubernetes.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 1.8.0 review the Upgrading the Tanzu Postgres Operator and Instances page.
Release Date: June 9th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.7.3 | PostgreSQL | 14.3, 13.7, 12.11, and 11.16 |
pgBackRest | 2.38 | |
pg_auto_failover | 1.6.4 | |
postGIS | 3.2.1 (for 11, 12,13 and 14) | |
Orafce | 3.21 | |
pgAudit | 1.6.1 (for 14), 1.5.1 (for 13), 1.4.1 (for 12), 1.3.1 (for 11), 1.2.1 (for 10) |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.0.2
. For more information see Installing the Tanzu Operator using the Tanzu CLI.process-max
and log-level-console
values under the additionalParameters
field in the PostgresBackupLocation resource was ignored.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.Release Date: May 19th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.7.2 | PostgreSQL | 14.3, 13.7, 12.11, and 11.16. |
pgBackRest | 2.38 | |
pg_auto_failover | 1.6.4 | |
postGIS | 3.2.1 (for 11, 12,13 and 14) | |
Orafce | 3.21 | |
pgAudit | 1.6.1 (for 14), 1.5.1 (for 13), 1.4.1 (for 12), 1.3.1 (for 11), 1.2.1 (for 10) |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.0.1
. For more information see Installing the Tanzu Operator using the Tanzu CLI.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.Release Date: April 25th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.7.1 | PostgreSQL | 11.15, 12.10, 13.6, 14.2 |
pgBackRest | 2.37 | |
pg_auto_failover | 1.6.3 | |
postGIS | 2.5.5 (for 11.14), 3.2.0 (for 12,13 and 14) | |
Orafce | 3.17 | |
pgAudit | 1.6.1 |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
The Tanzu Postgres 1.7.1 release supports Carvel tools, and the 1.7.1. container images are packaged as an image bundle that is distributed as a new OCI artifact: registry.tanzu.vmware.com/packages-for-vmware-tanzu-data-services/tds-packages:1.0.0
. For more information on image bundles see Resources in the Carvel documentation.
The Tanzu Postgres Operator can now be installed using the Tanzu CLI and the new Carvel image bundle. Tanzu Application Platform (TAP) users can now use the same toolchain to manage both products. For details on the Tanzu CLI installation process see Installing a Tanzu Postgres Operator.
appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.Release Date: April 15th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.7.0 | PostgreSQL | 11.15, 12.10, 13.6, 14.2 |
pgBackRest | 2.37 | |
pg_auto_failover | 1.6.3 | |
postGIS | 2.5.5 (for 11.14), 3.2.0 (for 12,13 and 14) | |
Orafce | 3.17 | |
pgAudit | 1.6.1 |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
additionalParameters
. For more information see Backup and Restore Deployment Properties.repo-s3-verify-tls
from pgBackRest, and replaces it with repo-storage-verify-tls
.pgConfig.adminUser
, pgConfig.appUser
, and pgConfig.dbName
. Creating an instance using reserved words now returns an error similar to: pgconfig.dbname cannot be postgres
./pgsql/logs/<namespace>-<instance-name>-backup.log
. Instead it will send logs to stdout and stderr. Use a log collector of your choice to store the logs in a custom location.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 1.7.0 review the Upgrading the Tanzu Postgres Operator and Instances page.
Release Date: April 1st, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.6.2 | PostgreSQL | 11.15.1, 12.10.1, 13.6.1, 14.2.1 |
psqlODBC | 13.02.0000 | |
pgjdbc | 42.3.2 | |
pgBackRest | 2.38 | |
pg_auto_failover | 1.6.3 | |
postGIS | 2.5.5 (for 11.14), 3.2.0 (for 12,13 and 14) | |
Orafce | 3.17 | |
pgAudit | 1.6.1 |
This version of VMware Postgres Operator is supported on the following platforms:
appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.Release Date: March 16th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.6.1 | PostgreSQL | 11.15.1, 12.10.1, 13.6.1, 14.2.1 |
psqlODBC | 13.02.0000 | |
pgjdbc | 42.3.2 | |
pgBackRest | 2.38 | |
pg_auto_failover | 1.6.3 | |
postGIS | 2.5.5 (for 11.14), 3.2.0 (for 12,13 and 14) | |
Orafce | 3.17 | |
pgAudit | 1.6.1 |
This version of VMware Postgres Operator is supported on the following platforms:
/pgsql/logs/<namespace>-<instance-name>-backup.log
prescribed file location. Instead it outputs log information to stdout and stderr. Users who wish to store the logs, are advised to configure a custom log collector.kubectl get postgresbackup
did not correctly display the time a backup had completed. The output of the command now displays the correct finish time of a backup.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.Release Date: February 28th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.6.0 | PostgreSQL | 11.15, 12.10, 13.6, 14.2 |
psqlODBC | 13.02.0000 | |
pgjdbc | 42.3.2 | |
pgBackRest | 2.37 | |
pg_auto_failover | 1.6.3 | |
postGIS | 2.5.5 (for 11.14), 3.2.0 (for 12,13 and 14) | |
Orafce | 3.17 | |
pgAudit | 1.6.1 |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support customer deployments that have modified the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
seccompProfile
. For more information, see seccompProfile in the Postgres API reference page.spec.retentionPolicy.fullRetention
and spec.retentionPolicy.diffRetention
. For more details see Backup and Restore CRD API Reference.appUser
. The Postgres database will automatically pickup up a refreshed secret.spec.imagePullSecret
in the Postgres instance CRD. Users can now replace the default regsecret
to their own registry secret.AGE
from the output of the command kubectl get postgresversion
.runc
process would restart repeatedly. Users can now set the seccompProfile
to Localhost
or Unconfined
. For more details on seccompProfile
see seccompProfile in the Postgres API reference page.appUser
secret for any application service-bindings would require manual secret reconfiguration.kubectl get postgresbackup
.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 1.6.0 review the Upgrading the Tanzu Postgres Operator and Instances page.
Release Date: January 7th, 2022
VMware Postgres Version | Component | Component Version |
---|---|---|
1.5.0 | PostgreSQL | 11.14, 12.9, 13.5, 14.1 |
psqlODBC | 13.2-0000 | |
pgjdbc | 42.3.1 | |
pgBackRest | 2.36 | |
pg_auto_failover | 1.6.3 | |
postGIS | 2.5.5 (for 11.14), 3.1.4 (for 12,13 and 14) | |
Orafce | 3.17 |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support deployments that have been modified by adding layers to the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
VMware Postgres Operator 1.5.0 has the following new features:
appUser
and an application secret <pg-instance-name>-app-user-db-secret
. For more information, see Creating Service Bindings.AGE
from the output of the command kubectl get postgresversion
.Running
even if the monitor stateful set was restarting. Now the Tanzu Postgres Operator will correctly mark the Postgres instance as Pending
while the monitor statefulset is not running.appUser
field in the Postgres instance manifest cannot be updated after the Postgres instance deployment.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 1.5.0 review the Upgrading the Tanzu Postgres Operator and Instances page.
Release Date: December 10th, 2021
VMware Postgres Version | Component | Component Version |
---|---|---|
1.4.1 | PostgreSQL | 11.14, 12.9, 13.5, 14.1 |
psqlODBC | 13.2-0000 | |
pgjdbc | 42.3.1 | |
pgBackRest | 2.36 | |
pg_auto_failover | 1.6.3 | |
postGIS | 2.5.5 (for 11.14), 3.1.4 (for 12,13 and 14) | |
Orafce | 3.17 |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support deployments that have been modified by adding layers to the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 1.4.1 review the Upgrading the Tanzu Postgres Operator and Instances page.
Existing Postgres instances will be associated with the PostgresVersion
resource named postgres-11
. If there are manifest files saved for those existing instances, please update the manifests to include spec.postgresVersion.name
as postgres-11
.
Release Date: November 22nd, 2021
VMware Postgres Version | Component | Component Version |
---|---|---|
1.4.0 | PostgreSQL | 11.14, 12.9, 13.5, 14.1 |
psqlODBC | 13.2-0000 | |
pgjdbc | 42.3.1 | |
pgBackRest | 2.36 | |
pg_auto_failover | 1.6.3 | |
postGIS | 2.5.5 (for 11.14), 3.1.4 (for 12,13 and 14) | |
Orafce | 3.17 |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support deployments that have been modified by adding layers to the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
VMware Postgres Operator 1.4.0 has the following new features:
ssl_min_protocol_version
and TLSv1.2 when users deploy 12, 13, or 14 Postgres instances. Users may use the psql client and the command select setting from pg_settings where name='ssl_min_protocol_version'
to confirm their instances TLS version.spec.backupLocationSecret
is now removed from the Tanzu Postgres manifest.pg_hba.conf
caused unsuccessful authentication between primary and mirrors. This issue has now been resolved by deploying wildcard authentication by subdomain.PostgresBackupSchedule
with incremental or differential backups, the backups were performed as full. This issue has now been fixed.target_session_attrs
needs to be set to target_session_attrs=read-write
, to ensure correct connection type handling for client applications.To upgrade to Tanzu Postgres 1.4.0 review the Upgrading the Tanzu Postgres Operator and Instances page.
Existing Postgres instances will be associated with the PostgresVersion
resource named postgres-11
. If there are manifest files saved for those existing instances, please update the manifests to include spec.postgresVersion.name
as postgres-11
.
Release Date: October 14th, 2021
VMware Postgres Version | Component | Component Version |
---|---|---|
1.3.0 | PostgreSQL | 11.13 |
psqlODBC | 11.0-0000 | |
pgjdbc | 42.2.5 | |
pgBackRest | 2.34 | |
pg_auto_failover | 1.6.2 | |
postGIS | 2.5.5 | |
Orafce | 3.15 | |
PL/Java Beta | 1.5.7 |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support deployments that have been modified by adding layers to the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
VMware Postgres Operator 1.3.0 has the following new features:
values.yaml
now contains just one variable for each, operatorImage
and postgresImage
.wal_keep_segments
value is now set to 0 by default. This provides greater flexibility and reduces space requirements for wal logs.dockerRegistrySecretName
in the Operator values.yaml
file was set to regsecret
and could not be changed to an alternative name. This issue has been resolved and users can specify an alternative secret name in the overrides file.Release Date: July 14, 2021
VMware Postgres Version | Component | Component Version |
---|---|---|
1.2.0 | PostgreSQL | 11.12 |
psqlODBC | 11.0-0000 | |
pgjdbc | 42.2.5 | |
pgBackRest | 2.28 | |
pg_auto_failover | 1.4.2 | |
postGIS | 2.5.5 | |
Orafce | 3.14 | |
PL/Java Beta | 1.5.7 |
This version of VMware Postgres Operator is supported on the following platforms:
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
IMPORTANT: VMware does not support deployments that have been modified by adding layers to the packaged Docker images, or deployments that reference images other than the VMware Postgres Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
VMware Postgres Operator 1.2.0 has the following new features:
Security Enhancements
ClusterIP
, to enhance security.Usability Enhancements
SELECT months_between(date '1995-02-02', date '1995-01-01');
. See Installing Postgres Extensions.plpython3u
.target_session_attrs
(for libpq) or targetServertype
(for JDBC) to connect to a writable instance.app=postgres-operator
. See Installing a Tanzu Postgres Operator.logLevel: Debug
when creating an instance. Debug logs can be shared with VMware support for troubleshooting. See Configuring a Postgres Instance.plpython3u
. For more information see Additional Supplied Modules in the Postgres documentation.--pg1-path
on the command line.StorageSize
field: "pg-small-instance.yaml": admission webhook "vpostgres.kb.io" denied the request: The field(s) StorageSize field needs to be at least 250MB are incorrectly formatted and could not be parsed.
StorageSize
field using M, Mi, or MB.stdout
.The High Availability configuration contains only one mirror.
The dockerRegistrySecretName
in the Operator values.yaml
file is set to regsecret
and cannot be changed to an alternative name in the overrides file .
Release Date: February 26, 2021
VMware Postgres Version | Component | Component Version |
---|---|---|
1.1.0 | PostgreSQL | 11.10 |
pgBackRest | 2.31 | |
pg_auto_failover | 1.4.0 |
VMware Postgres Operator 1.1.0 has the following features:
pgbackrest.conf
to pgbackrest.conf.template
.storageSize
parameter cannot be altered after Postgres instance creation. Any attempt to do so generates an error similar to: storageSize cannot be reduced after the instance is created. No changes have been made to the running instance.
verifyTLS: true
and a well-known Certificate Authority, would fail with an error similar to: 2020-12-18 01:01:43.460 P00 DEBUG: common/io/http/request::httpRequestProcess: retry CryptoError: unable to verify certificate presented by 's3.us-west-1.amazonaws.com:443': [20] unable to get local issuer certificate
This issue has been resolved.storageSize
updates affected more than one instance, if the instances had matching names in separate namespaces.s3-secret-example.yaml
file for S3 backups, and all parameters are now specified in double quotes.yaml
file, where parameters marked as "optional" but not configured would cause the backup operation to fail.archive_mode
flag was on
(in the postgresql.conf
file), but the backupLocationSecret
was left unconfigured in the instance configuration yaml
file, backups were still attempted. This issue has been resolved.info
.Release Date: October 30, 2020
VMware Postgres Operator 1.0.0 is the first release of VMware VMware Postgres Operator on Kubernetes.
VMware Postgres Version | Component | Component Version |
---|---|---|
1.0.0 | PostgreSQL | 11.9 |
psqlODBC | 11.0-0000 | |
pgjdbc | 42.2.5 | |
pgBackRest | 2.28 | |
pg_auto_failover | 1.4.0 | |
postGIS | 2.5.4 |
VMware Postgres Operator 1.0.0 has the following features:
storageSize
to 10G, and use an expandable storage class. See Deploying a Postgres Instance.