Pivotal Greenplum for Kubernetes 0.8.1 Release Notes

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.

Pivotal Greenplum for Kubernetes is an experimental release of Pivotal Greenplum Database on Kubernetes. Greenplum for Kubernetes 0.8.1 is a maintenance release that resolves a known issue; it is based on Pivotal Greenplum 5.16.0.

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

Components

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

Greenplum for Kubernetes Version Pivotal Greenplum Database Version
0.8.1, 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 0.8.1 runs on the following platforms:

  • Pivotal Container Service (PKS) 1.2 (contains Kubernetes 1.11)
  • Google Kubernetes Engine (GKE) Kubernetes 1.11

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

Resolved Issue

In previous releases, if you tried to deploy a second Greenplum cluster into the same Kubernetes namespace, the Greenplum for Kubernetes operator did not properly reject the request. This problem has been resolved in v0.8.1. You can deploy multiple Greenplum clusters into different Kubernetes namespaces, as described in the documentation

Upgrading

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

Note: After upgrading Greenplum for Kubernetes, you can also rollback to the previous version 0.7.0 software if necessary. To rollback to the previous version, use the same upgrade instructions, but delete the version 0.8.1 sofware and cluster, and install and upgrade using the older version 0.7.0 software. Keep in mind that when you upgrade or downgrade any deployed Greenplum cluster, you must first delete the deployed cluster and then re-create it with the desired Greenplum operator software, as discussed in Upgrade a Deployed Greenplum Cluster.

Known Issues and Limitations

  • Greenplum for Kubernetes does not support the built-in SNMP features that are available in Pivotal Greenplum Database.
  • 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 .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. In order to change attributes such as 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 secret objects, ConfigMap, Services.