Pivotal Greenplum for Kubernetes 0.2.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 v0.2.0 is a minor release that includes several feature changes, and is based on Pivotal Greenplum Database 5.11.
Refer to the Pivotal Greenplum Database documentation for detailed information on Pivotal Greenplum Database.
Scope
Pivotal Greenplum for Kubernetes 0.2.0 deploys on PKS version 1.1.1 or later or Kubernetes version 1.10.4 or later (Minikube, GKE, etc.).
Components
Pivotal Greenplum for Kubernetes includes the Greenplum Database version identified below:
Greenplum for Kubernetes Version | Greenplum Database Version |
---|---|
0.2.0 | 5.11.0 |
0.1.0 | 5.10.0 |
Changes from Previous Release
This release introduces the following feature changes and improvements:
- The
deploy.sh
script no longer requires you to specify thekey.json
file as an argument. Instead, referencekey.json
in theValues-overrides.yml
file. - The
MASTER_DATA_DIRECTORY
variable was removed fromValues-common.yml
. This directory is always set to/greenplum/data-1
in Greenplum for Kubernetes. - The
PGPORT
value is now set automatically in the docker container; you do not need to manually setPGPORT
when activating a standby master. - The Kubernetes service account key (
key.json
) file is no longer specified as part of thedeploy.sh
command. Instead, you must specify the location of this file in theValues-common.yaml
file as the value ofdockerRegistryKeyJson
. See Deployment Configuration Options. - Pivotal Greenplum Database 5.11 supports using Fully Qualified Domain Names (FQDN) to do Host Based authentication in
pg_hba.conf
. In a Greenplum for Kubernetes deployment, thegpinitsystem_config
specifiesHBA_HOSTNAMES=1
to use a FQDN for all segments including master. You must use a FQDN when using eithergpinitsystem
orgpinitstandby
with Greenplum for Kubernetes. - All pods now rely on Kubernetes for DNS services, and they no longer use local files for hostname-to-IP resolution.
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.
- In order to install Greenplum Database package (
.gppkg
) files such as MADLib that use thegppkg
utility, you must first install thealien
utility onto Greenplum hosts (for example,sudo apt-get install alien
).