About Pivotal Greenplum for Kubernetes
Pivotal Greenplum for Kubernetes utilizes the Kubernetes platform to help you quickly and reliably deploy Greenplum clusters that are tailored for a variety of use cases, such as analytical processing with business intelligence tools or high-performance ETL operations for data scientists. Post-deployment, Greenplum for Kubernetes helps you maintain your Greenplum cluster by expanding it to accommodate additional processing requirements or activating standby servers to maintain high availability.
The Greenplum for Kubernetes distribution provides Docker images with the Pivotal Greenplum Database software and the Greenplum Operator running on Ubuntu. The Greenplum Operator registers Pivotal Greenplum as a first-class resource within Kubernetes, and orchestrates the deployment, management, and deletion of Greenplum in Kubernetes, as directed by your requests. In most cases, you simply specify the desired Greenplum configuration in a declarative YAML-formatted file, and provide that file to the Greenplum Operator.
Pivotal Greenplum for Kubernetes is functionally different from the Pivotal Greenplum Database product in these ways:
- Certain features that are optional in Pivotal Greenplum Database, such as MADlib, are installed automatically with Greenplum for Kubernetes.
- Greenplum for Kuberenetes uses Resource Group-based resource management by default, compared to Pivotal Greenplum, which uses Resource Queue-based resource management.
- 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.