Pivotal Greenplum for Kubernetes Version 2.2 Release Notes
Pivotal Greenplum for Kubernetes 2.0 is a new major release that introduces new features and bug fixes.
Refer to the Pivotal Greenplum Database documentation for detailed information about Pivotal Greenplum Database.
Note: Upgrading or migrating data from Pivotal Greenplum version 1.x to version 2.x is not supported. You must uninstall Pivotal Greenplum version 1.x using the instuctions in Uninstalling Pivotal Greenplum for Kubernetes before installing version 2.0. Persistent volumes that were created for a version 1.x cluster cannot be used with version 2.x.
Pivotal Greenplum for Kubernetes includes the Pivotal Greenplum Database version identified below:
|Pivotal Greenplum Version||Pivotal Greenplum Database Version|
This version of Pivotal 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.
Pivotal Greenplum 2.01 is a maintenance release that includes these changes:
- The Greenplum Database version was updated to 6.8.1. See the Greenplum Release Notes for information about fixes in version 6.8.1.
- New sample files are included to show how an Open Policy Agent (OPA) mutating webhook can be used to annotate Greenplum services. The sample Rego policy file adds an annotation to enable the service to use an AWS internal load balancer, and modifies the service
loadBalancerSourceRangesvalue to specify the address of the load balancer. See Annotating the Greenplum Service for information about deploying the sample OPA configuration and policy file.
Pivotal Greenplum 2.0.0 is a major new release that provides these features:
- Support for Greenplum Database 6.8 and later 6.x releases. Earlier versions of Pivotal Greenplum for Kubernetes support only Greenplum Database 5.x software.
- Support for mirrorless deployments. Standby master pods, segment mirroring, and anti affinity settings are now disabled by default and in the sample deployment manifests.
gpcopyutilities are now installed by default.
- New service accounts,
greenplum-system-pod, are created during installation and deployment. The accounts enable pods to interact with the Kubernetes API directly, and take actions on their behalf.
- All PVCs are tagged with the Greenplum Database major version, for example
- MADlib was updated to version 1.17.
- Example manifest files were updated to remove extraneous comments referencing the nonvalid
- Ubuntu packages were updated in order to resolve the following Ubuntu Security Notification (USNs):
- 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.
- Pivotal Greenplum for Kubernetes does not currently support cluster monitoring with Greenplum Command Center, the
gpperfmondatabase, or related utilities. Use system-level monitoring tools such as Prometheus and Grafana until Greenplum Command Center support is available.
- Pivotal Greenplum for Kubernetes does not support the built-in SNMP features that are available in Pivotal Greenplum Database.
- Pivotal Greenplum for Kubernetes does not support installing Greenplum extensions that use the
gppkgutility). 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.