Pivotal Greenplum for Kubernetes 1.12 Release Notes
Pivotal Greenplum for Kubernetes 1.12 introduces new features and bug fixes.
Refer to the Pivotal Greenplum Database documentation for detailed information about Pivotal Greenplum Database.
Pivotal Greenplum for Kubernetes includes the Pivotal Greenplum Database version identified below:
|Greenplum for Kubernetes Version||Pivotal Greenplum Database Version|
Pivotal Greenplum for Kubernetes 1.12 is supported on the following platforms:
- Pivotal Container Service (PKS) 1.6.0 (contains Kubernetes 1.15.5)
- Google Kubernetes Engine (GKE) Kubernetes 1.15.5
Additional Kubernetes environments, such as Minikube, can be used for testing or demonstration purposes.
This release introduces the following features and changes:
If you deploy the GPText service, Greenplum for Kubernetes automatically configures each each Solr and ZooKeeper JVM to use 75% of the memory available to its pod.
PXF is no longer a Beta feature in Greenplum for Kubernetes.
When deploying the PXF service, a warning message is displayed if the S3 location that provides the PXF configuration does not contain a valid directory structure, or contains extraneous files. In this case, the deployment succeeds but PXF is configured with a default
Greenplum Operator log files are now printed using JSON format.
The PXF service now uses status values of
Degradedto reflect the state of configured PXF pods.
Pendingindicates that configured PXF pods are initially starting up, and
Runningindicates that all configured pods are ready.
Degradedindicates that one or more of the configured PXF pods are not ready.
Ubuntu packages were updated in order to resolve the following Ubuntu Security Notification (USNs):
- USN-4231-1: NSS vulnerability
- USN-4233-1: GnuTLS update
- USN-4233-2: GnuTLS update
- USN-4236-2: Libgcrypt vulnerability
- USN-4243-1: libbsd vulnerabilities
- USN-4246-1: zlib vulnerabilities
- USN-4247-1: python-apt vulnerabilities
- USN-4247-2: python-apt regression
- USN-4249-1: e2fsprogs vulnerability
- USN-4256-1: Cyrus SASL vulnerability
- USN-4257-1: OpenJDK vulnerabilities
- USN-4263-1: Sudo vulnerability
- USN-4269-1: systemd vulnerabilities
- USN-4274-1: libxml2 vulnerabilities
To upgrade a Greenplum for Kubernetes operator and cluster from the prior release, follow the instructions in Upgrading Greenplum for Kubernetes.
- Pivotal 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. Pivotal does not support changing the contents of the deployed containers and pods in any way.
- Some common Greenplum Database backup and restore utilities are not supported. This includes
gprestoreutilities, and the related plug-ins for s3 and Data Domain Boost.
- 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.
- 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.
- Greenplum for Kubernetes does not support the built-in SNMP features that are available in Pivotal Greenplum Database.
- Greenplum for Kubernetes clusters do 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.