Pivotal Greenplum for Kubernetes 1.10 Release Notes

Pivotal Greenplum for Kubernetes 1.10 introduces new features and updated platform support, as compared to previous releases of the product.

Refer to the Pivotal Greenplum Database documentation for detailed information about Pivotal Greenplum Database.

Components

Pivotal Greenplum for Kubernetes includes the Pivotal Greenplum Database version identified below:

Greenplum for Kubernetes Version Pivotal Greenplum Database Version
1.10.0 5.23.0
1.9.0 5.22.0
1.8.1 5.21.5
1.7.2 5.21.4
1.7.1 5.21.3
1.7.0 5.21.2
1.6.0 5.21.0
1.4.0 5.20.0
1.3.2 5.19.0
1.2.0 5.19.0
1.1.0 5.18.0
1.0.0 5.17.0
0.8.0 5.16.0
0.7.0 5.15.1
0.6.0 5.12.1
0.5.0 5.12.1
0.4.0 5.11.3
0.3.0 5.11.3
0.2.0 5.11.0
0.1.0 5.10.0

Supported Platforms

Pivotal Greenplum for Kubernetes 1.10 is supported on the following platforms:

  • Pivotal Container Service (PKS) 1.5.0 (contains Kubernetes 1.14.5)
  • Google Kubernetes Engine (GKE) Kubernetes 1.14.5

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

Changes from Previous Release

This release introduces the following features and changes:

  • Greenplum for Kubernetes includes Pivotal Greenplum version 5.23.0.
  • When segment mirroring is disabled, Grreenplum segment pods automatically restart and re-join the cluster after a failure. (If segment mirroring is enabled, then you must continue to manually recover failed segments using the gprecoverseg utility.)
  • Greenplum clusters can be installed without using a standby master segment, using the standby: no property. If no standby master is deployed, then the master pod automaticallyl restarts after a failure.
  • The new protocol property was added to specify whether the S3 endpoint that hosts a PXF configuration uses http or https for connectivity.
  • You can automatically expand a cluster by increasing the value of primarySegmentCount in the deployment manifest. Greenplum automatically creates and initializes the new segments; manual steps are needed only for rebalancing your data and for removing the expansion schema. See Expanding a Greenplum Deployment.
  • Ubuntu packages were updated in order to resolve the following Ubuntu Security Notification (USN):

Upgrading

To upgrade your existing Greenplum for Kubernetes operator and clusters, follow the instructions in Upgrading Greenplum for Kubernetes.

Known Issues and Limitations

  • 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 gpcopy, the gpbackup and gprestore utilities, 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 gpperfmon database, 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 .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.