This document contains pertinent release information about VMware Tanzu SQL with Postges for Kubernetes. Obtain the most recent version of the distribution from VMware Tanzu Network.

Release 1.3.0

Release Date: October 14th, 2021

Software Component Versions

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

Supported Platforms

This version of Tanzu Postgres 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.

Features

Tanzu Postgres 1.3.0 has the following new features:

  • Release 1.3.0 supports Postgres 11.13.
  • This release updates the pgBackRest component to 2.34 and pg_auto_failover to 1.6.2.
  • This release supports Guaranteed Quality of Service (Qos) for critical pods. When the resource limits are higher than the requests, the QoS class is Burstable.
  • This release improves secrets handling, for Postgres instances and monitor.
  • Customers can now create Postgres instances in an environment with restricted security policies. For details, see Prerequisites in the Install Tanzu Operator page.
  • This release allows customers to configure the Postgres Operator pod resources. See Access the Resources in the Install the Tanzu Operator page.
  • The Postgres Operator 1.3.0 now recreates any Postgres database or Postgres monitor secrets that are deleted by accident.
  • The Tanzu Postgres administrator can now set the certificate issuer for the Postgres operator's certificate.

Backup and Restore

  • This release deprecates the BackupLocationSecret object. Customers using a previous release of Tanzu Postgres, should migrate to the new backup and restore strategy. For details see Migrating to Tanzu Postgres 1.3.0 Backup and Restore.
  • This release introduces four new Custom Resource Definitions for backup and restore: PostgresBackupLocation, PostgresBackup, PostgresBackupSchedule, and PostgresRestore. See Backing Up and Restoring Tanzu Postgres
  • Users can filter existing backups based on Postgres instance name. For details, see Listing Backup Resources.
  • Any changes to the backup location or backup secret are automatically applied to the related Postgres instances.
  • Customers can now monitor real time the backup logs during a backup operation.
  • Postgres restore now supports recovering to a brand new instance, to help users with disaster recovery or debug scenarios. For details see Restore to a different instance.

Monitoring

  • Tanzu Postgres 1.3.0 provides a Prometheus compatible endpoint for metrics collection. For details see Monitoring Postgres Instances.
  • Customers can configure the resource limits and requests of the Postgres exporter. The metrics resources can be edited in the Postgres manifest file. For further details, see Configuring a Postgres Instance.
  • This release supports TLS security for metrics collection.

Changes

  • This release improves error messages.
  • The Postgres Operator and Postgres Image tags for version and repository are combined into a single variable instead of two. The Operator values.yaml now contains just one variable for each, operatorImage and postgresImage.
  • The Postgres instance wal_keep_segments value is now set to 0 by default. This provides greater flexibility and reduces space requirements for wal logs.

Limitations and Known Issues

  • Tanzu Postgres does not support Helm version 3.7.
  • The High Availability configuration contains only one mirror.
  • Recovering a backup to a new Postgres instance is restricted to the same namespace.

Fixed Issues

  • The 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 1.2.0

Release Date: July 14, 2021

Software Component Versions

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

Supported Platforms

This version of Tanzu Postgres 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.

Features

Tanzu Postgres 1.2.0 has the following new features:

Security Enhancements

  • Tanzu Postgres 1.2.0 supports TLS security and user provided TLS certificates. See Creating a TLS Secret Manually.
  • Support for custom TLS issuer. See Configuring TLS for Tanzu Postgres Instances.
  • TLS certificates associated with cert-manager can be accidentally deleted and regenerated automatically.
  • Kubernetes secrets associated with a cert-manager certificate can be deleted and recovered automatically. A new certificate will be generated, and the Postgres server will restart. Applications will need to reconnect.
  • Tanzu Postgres instances are now created by default with service type ClusterIP, to enhance security.
  • New Postgres instances now use a crypto library/algorithm for enhanced password generation.

Usability Enhancements

  • The Tanzu Postgres Operator and instances are now available via the TanzuNet registry. See Installing a Postgres Operator for more information.
  • This release supports VMware Tanzu Kubernetes Grid multicloud on AWS.
  • PL/Java is bundled with the 1.2 release but currently provided as Beta.
  • Tanzu Postgres now supports the Orafce extension. Users can now run Oracle queries like SELECT months_between(date '1995-02-02', date '1995-01-01');. See Installing Postgres Extensions.
  • Release 1.2 now supports all Postgres contrib extensions, apart from plpython3u.
  • Connections to Postgres instances are now writable by default. This allows applications that cannot use connection parameters such as target_session_attrs(for libpq) or targetServertype(for JDBC) to connect to a writable instance.
  • Users can install the Tanzu Postgres Operator in a namespace of their choice.
  • The new release supports enhanced labels. Users can search the Kubernetes resources created by the Tanzu Postgres Helm chart by using a label such as app=postgres-operator. See Installing a Tanzu Postgres Operator.
  • Users can now set logLevel: Debug when creating an instance. Debug logs can be shared with VMware support for troubleshooting. See Configuring a Postgres Instance.
  • The Postgres instance Monitor pod resources can now be manually altered, to support resource constrained environments such as Minikube on a client laptop. For more details see Updating the Monitor Resources.
  • Release 1.2 now supports all Postgres contrib extensions, apart from plpython3u. For more information see Additional Supplied Modules in the Postgres documentation.

Fixed Issues

  • (175768688) - Users can now create backups of similarly named instances in the same S3 bucket.
  • (176064027) - When creating a backup operation, users do not need to specify the path --pg1-path on the command line.
  • (175771699) - This release improves the error message when specifying below the minimum accepted disk space for the 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.
  • (177225289) - Users can now specify the StorageSize field using M, Mi, or MB.
  • (176615909) - Non-admin users can now view Postgres objects in a specified namespace.
  • (178402085) - Fixes a log display issue where, if the instance was older than one day, the logs stopped displaying to stdout.
  • (177407650) - Fixes an issue where the database would be inaccessible for a period of time when scaling up from a single node to an HA configuration. The database is now accessible during the secondary node data copy period.
  • (178528901) - In a HA configuration, when the user configured a S3 backup secret, he also had to manually create the backup stanza. This issue has been resolved, and the backup stanza is created automatically when users apply the S3 secret.

Limitations

  • 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 1.1.0

Release Date: February 26, 2021

Software Components

VMware Postgres Version Component Component Version
1.1.0 PostgreSQL 11.10
pgBackRest 2.31
pg_auto_failover 1.4.0

Features

Tanzu Postgres 1.1.0 has the following features:

  • Support for upgrading from Tanzu Postgres 1.0.0 to 1.1.0. See Upgrading the Tanzu Postgres Operator and Instances.
  • Support for Postgres 11.10.
  • Enhanced security by implementing Postgres cluster communications via SSL.
  • Improved auto-healing, when instances or services are terminated abnormally or accidentally. The Postgres operator monitors and automatically restarts any deleted or stopped instances or agents.
  • Postgres instances with the same name, in different namespaces, can now be backed up to the same S3 location.

Changed Features

  • Updated the pgbackrest sample configuration file, from pgbackrest.conf to pgbackrest.conf.template.
  • The 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.

Fixed Issues

  • [166560384] - Tanzu Postgres backups to an S3 location, using the parameter 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.
  • [175791284] - Fixed an issue where storageSize updates affected more than one instance, if the instances had matching names in separate namespaces.
  • [175885808] - Updated the s3-secret-example.yaml file for S3 backups, and all parameters are now specified in double quotes.
  • [175618701] - Resolved an issue with the s3 secret yaml file, where parameters marked as "optional" but not configured would cause the backup operation to fail.
  • [175602831] - When the 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.
  • [176061339] - Changed the detail level of the pgbackrest console output to info.

Release 1.0.0

Release Date: October 30, 2020

Tanzu Postgres 1.0.0 is the first release of VMware Tanzu Postgres on Kubernetes.

Software Components

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

Features

Tanzu Postgres 1.0.0 has the following features:

Known Issues and Limitations

  • Upgrades from the Beta program releases to the Tanzu Postgres 1.0.0 release are not supported. Download and install the latest version.
  • The High Availability configuration contains only one mirror.
  • The default storage size for the Postgres instance is too limited for long term running Postgres environments. Change the storageSize to 10G, and use an expandable storage class. See Configuring a Postgres Instance.
  • During an upgrade from 1.0.0 to 1.1.0, in an HA scenario, the Postgres instances state does not show "Ready" until both the primary and the mirror nodes have restarted. This limitation stops the clients from connecting to a read-write instance during the upgrade.
check-circle-line exclamation-circle-line close-line
Scroll to top icon