Greenplum Operator Manifest File
This section describes each of the properties that you can define in a Greenplum Operator manifest file.
Synopsis
apiVersion: "greenplum.pivotal.io/v1"
kind: "GreenplumCluster"
metadata:
name: <namespace>
spec:
masterAndStandby:
hostBasedAuthentication: |
[ host <database> <role> <address> <authentication-method> ]
[ ... ]
memory: "<memory-limit>"
cpu: "<cpu-limit>"
storageClassName: <storage-class>
storageSize: <size>
segments:
primarySegmentCount: <int>
memory: <memory-limit>
cpu: <cpu-limit>
storageClassName: <storage-class>
storageSize: <size>
Description
You specify Greenplum cluster configuration properties to the Greenplum Operator via a YAML-formatted manifest file. A sample manifest file is provided in workspace/my-greenplum-cluster.yaml
. The current version of the manifest supports configuring the cluster name, number of segments, and the memory, cpu, and storage settings for master and segment pods. See also Deploying a New Greenplum Cluster for information about deploying a new cluster using a manifest file.
Keywords and Values
Cluster Metadata
Name: <namespace>
kubectl
commands. For example, if you set the name to my-greenplum
then you can use commands like kubectl get all -l greenplum-cluster=my-greenplum
or kubectl get pvc -l greenplum-cluster=my-greenplum
. If you do not specify a name, the Greenplum Operator uses the namespace in the current kubectl
context.Segment Configuration
masterAndStandby:
, segments:
masterAndStandby:
settings apply only to both the master and standby master pods. All Greenplum for Kubernetes clusters include a standby master. The segments:
section applies to each primary segment and mirror segment pod. All Greenplum for Kubernetes clusters use segment mirroring.hostBasedAuthentication:
pg_hba.conf
file generated for the Greenplum cluster. Each entry (multiple entries are possible) must include the items host <database> <role> <address> <authentication-method>
in that order, to enable a role to access the indicated database (or all
databases) from the specified CIDR and authentication method. See Allowing Connections to Greenplum Database in the Greenplum Database documentation for more information about pg_hba.conf
file entries.primarySegmentCount: <int>
segment-<type>-<number>
where the segment <type>
is either a
for primary segments or b
for mirror segments. Segment numbering starts at zero.memory: <memory-limit>
4.5Gi
.). See Assign Memory Resources to Containers and Pods in the Kubernetes documentation for more information.
cpu: <cpu-limit>
cpu: "1.2"
). See Assign CPU Resources to Containers and Pods in the Kubernetes documentation for more information.
storageClassName: <storage-class>
For best performance, Pivotal recommends using persistent volumes that are backed by a local SSD with the XFS filesystem, using
readahead
cache for best performance. Use the mount options rw,nodev,noatime,nobarrier,inode64
to mount the volume. See Creating Local Persistent Volumes for Greenplum for information about manually provisioning local persistent volumes. See Optimizing Persistent Disk and Local SSD Performance in the Google Cloud documentation for information about the performance characteristics of different storage types.storageSize: <size>
100G
, 1T
).Examples
See the workspace/my-greenplum-cluster.yaml
for an example manifest.
See Also
Deploying a New Greenplum Cluster, Deleting a Greenplum Cluster, Installing Greenplum for Kubernetes.