Pivotal Greenplum for Kubernetes 0.4.0 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.4.0 is a minor release that introduces a new feature; it is based on Pivotal Greenplum Database 5.11.3.

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

Scope

Pivotal Greenplum for Kubernetes 0.4.0 deploys on PKS version 1.1.1 or later or Kubernetes version 1.10.4 or later (Minikube, GKE, and so forth).

Components

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

Greenplum for Kubernetes Version Greenplum Database Version
0.4.0 5.11.3
0.3.0 5.11.3
0.2.0 5.11.0
0.1.0 5.10.0

Changes from Previous Release

This release introduces the following new feature:

  • The Greenplum Operator manifest file supports a new attribute named hostBasedAuthentication under the masterAndStandby key. You can use this attribute to insert entries into the pg_hba.conf file that is generated for a new Greenplum cluster. For example, the following configuration enables the gpadmin and gpuser accounts to access the Greenplum cluster from any external client address:

    masterAndStandby:
      # TYPE   DATABASE       USER           CIDR-ADDRESS      METHOD
      hostBasedAuthentication: |
        host   all            gpadmin        0.0.0.0/0         trust
        host   all            gpuser         0.0.0.0/0         md5
    

    See Allowing Connections to Greenplum Database in the Greenplum Database documentation for more information about pg_hba.conf file entries.

Known Issues and Limitations

  • 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.
  • 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.
  • In order to install Greenplum Database package (.gppkg) files, such as MADLib, with the gppkg utility, you must first install the alien utility onto Greenplum hosts (for example, sudo apt-get install alien).
  • Certain Greenplum resources that are created during deployment are not yet labeled for convenient management with kubectl. This includes Greenplum secret objects, ConfigMap, Services.