Pivotal Greenplum for Kubernetes 0.5.0 Release Notes
Pivotal Greenplum for Kubernetes is an experimental release of Pivotal Greenplum Database on Kubernetes. Greenplum for Kubernetes 0.5.0 is a minor release that introduces and changes some features; it is based on Pivotal Greenplum Database 5.12.1.
Refer to the Pivotal Greenplum Database documentation for detailed information on Pivotal Greenplum Database.
Pivotal Greenplum for Kubernetes 0.5.0 deploys on PKS version 1.1.1 or later or Kubernetes version 1.10.4 or later (Minikube, GKE, and so forth).
Pivotal Greenplum for Kubernetes includes the Greenplum Database version identified below:
|Greenplum for Kubernetes Version||Greenplum Database Version|
This release introduces the following new and changed features:
- The Greenplum Database Docker image now includes the MADlib analytics library software, v1.15.1. To use the MADlib library, install the MADlib functions as described in Using MADlib for Analytics.
- Greenplum for Kubernetes no longer requires that you install the
alienutility in order to use MADlib, as the MADlib software is included by default as a Debian package in the Greenplum Database Docker image.
- In the previous release, the Greenplum Operator and Greenplum Database were always installed into the
defaultKubernetes namespace. This version of the software installs into the namespace specified by the Kubernetes context, which can be set in the
helmcommand with the
- Pivotal Greenplum for Kubernetes is an experimental product and is not intended for use in a production environment. Experimental features are subject to change without notice in future releases.
- Greenplum for Kubernetes does not currently support cluster monitoring with Greenplum Command Center. Use system-level monitoring tools such as Prometheus and Grafana until Greenplum Command Center support is available.
- 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 in the v0.5.0 release.
- The Greenplum Operator does not yet support changing attribute values of a deployed Greenplum cluster. In order to change attributes such as the number of segments in the cluster, the cluster name, or segment resource usage, you must delete the cluster and then redeploy using the changed values.
- Certain Greenplum resources that are created during deployment are not yet labeled for convenient management with
kubectl. This includes Greenplum