VMware Tanzu Greenplum for Kubernetes Version 2.3 Release Notes

VMware Tanzu Greenplum for Kubernetes 2.3 is a minor release that introduces new features and bug fixes.

Refer to the VMware Tanzu Greenplum Database documentation for detailed information about VMware Tanzu Greenplum Database.

Note: Upgrading or migrating data from VMware Tanzu Greenplum version 1.x to version 2.x is not supported. You must uninstall VMware Tanzu Greenplum version 1.x using the instuctions in Uninstalling VMware Tanzu Greenplum for Kubernetes before installing version 2.x. Persistent volumes that were created for a version 1.x cluster cannot be used with version 2.x.

Components

VMware Tanzu Greenplum for Kubernetes includes the VMware Tanzu Greenplum Database version identified below:

VMware Tanzu Greenplum Version VMware Tanzu Greenplum Database Version
2.3.0 6.11.1
2.2.0 6.10.1
2.1.0, 2.0.1 6.8.1
2.0.0 6.8.0

Supported Platforms

This version of VMware Tanzu Greenplum for Kubernetes is supported on the following platforms:

  • VMware Tanzu Kubernetes Grid Integrated (TKGI) Edition 1.7.0 (contains Kubernetes 1.16.7)
  • Google Kubernetes Engine (GKE) Kubernetes 1.16.7
  • Amazon Elastic Kubernetes Service (Amazon EKS) 1.16

Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.

Release 2.3.0 Changes

VMware Tanzu Greenplum 2.3.0 is a minor release that includes these changes:

  • Greenplum Text is now a supported feature.
  • Greenplum Command Center installation files are now installed by default with Greenplum for Kubernetes. To use Command Center you must execute the Command Center installation after deploying a new cluster. See Using Greenplum Command Center.
  • gpbackup can back up Greenplum data either to local backup files, or to Minio S3 using the gpbackup S3 plugin. See Using the S3 Storage Plugin with gpbackup and gprestore in the Greenplum Backup and Restore documentation for more information on configuring the plugin.

Known Issues and Limitations for Kubernetes Deployments

  • Currently VMware Tanzu Greenplum for Kubernetes does not support automatic upgrades of Greenplum Text. If you installed an earlier version of Greenplum Text in VMware Tanzu Greenplum for Kubernetes and then upgrade to version 2.3, you must manually complete the Greenplum Text upgrade by executing gptext-installsql -c gpadmin && gptext-installsql gpadmin after the upgraded cluster is fully running.
  • The zkManager utility, used for checking the ZooKeeper cluster state and cluster management with Greenplum Text deployments, is not available with VMware Tanzu Greenplum for Kubernetes. As a workaround, use kubectl to manage the ZooKeeper cluster.
  • If you deploy a cluster with Greenplum Text, the gptext-state utility always throws the warning message: object of type 'NoneType' has no len(). This message can be safely ignored in most cases. However, note that the utility cannot detect if the ZooKeeper cluster is down.
  • 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 Greenplum Operator. VMware does not support changing the contents of the deployed containers and pods in any way.
  • Greenplum Database connector functionality is not supported. This includes Greenplum Streaming Server (gpss) and its API, Greenplum-Informatica Connector, Greenplum-Spark Connector, and the Greenplum-Kafka Integration.
  • VMware Tanzu Greenplum for Kubernetes does not support the built-in SNMP features that are available in VMware Tanzu Greenplum Database.
  • VMware Tanzu Greenplum for Kubernetes does not support installing Greenplum extensions that use the .gppkg format (and gppkg utility). Future releases will include these extensions as part of the distribution, as with MADlib.
  • The Greenplum Operator does not yet support changing all attribute values of a deployed Greenplum cluster. See Greenplum Operator Manifest File for details.