API Reference¶
CloudNativePG extends the Kubernetes API defining the following custom resources:
:ref:`Backup<Backup>`
:ref:`Cluster<Cluster>`
:ref:`Pooler<Pooler>`
:ref:`ScheduledBackup<ScheduledBackup>`
All the resources are defined in the postgresql.cnpg.io/v1 API.
Please refer to the Configuration Samples ” of the documentation for examples of usage.
Below you will find a description of the defined resources:
AffinityConfiguration¶
AffinityConfiguration contains the info we need to create the affinity rules for Pods
Name |
Description |
Type |
|---|---|---|
`enablePodAntiAffinity ` |
Activates anti-affinity for the pods. The operator will define pods anti-affinity unless this field is explicitly set to false |
*bool |
`topologyKey ` |
TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that - mandatory |
string |
`nodeSelector ` |
NodeSelector is map of key-value pairs used to define the nodes on which the pods can run. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ |
map[string]string |
`nodeAffinity ` |
NodeAffinity describes node affinity scheduling rules for the pod. More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity |
*corev1.NodeAffinity |
`tolerations ` |
Tolerations is a list of Tolerations that should be set for all the pods, in order to allow them to run on tainted nodes. More info: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/ |
[]corev1.Toleration |
`podAntiAffinityType ` |
PodAntiAffinityType allows the user to decide whether pod anti-affinity between cluster instance has to be considered a strong requirement during scheduling or not. Allowed values are: “preferred” (default if empty) or “required”. Setting it to “required”, could lead to instances remaining pending until new kubernetes nodes are added if all the existing nodes don’t match the required pod anti-affinity rule. More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity |
string |
additionalPodAntiAffinity |
AdditionalPodAntiAffinity allows to specify pod anti-affinity terms to be added to the ones generated by the operator if EnablePodAntiAffinity is set to true (default) or to be used exclusively if set to false. |
*corev1.PodAntiAffinity |
`additionalPodAffinity ` |
AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster’s pods. |
*corev1.PodAffinity |
AzureCredentials¶
AzureCredentials is the type for the credentials to be used to upload files to Azure Blob Storage. The connection string contains every needed information. If the connection string is not specified, we’ll need the storage account name and also one (and only one) of:
storageKey - storageSasToken
inheriting the credentials from the pod environment by setting inheritFromAzureAD to true
Name |
Description |
Type |
|---|---|---|
`connectionString ` |
The connection string to be used |
|
`storageAccount ` |
The storage account where to upload data |
|
`storageKey ` |
The storage account key to be used in conjunction with the storage account name |
|
`storageSasToken ` |
A shared-access-signature to be used in conjunction with the storage account name |
|
inheritFromAzureAD |
Use the Azure AD based authentication without providing explicitly the keys. - mandatory |
bool |
Backup¶
Backup is the Schema for the backups API
Name |
Description |
Type |
|---|---|---|
metadata |
||
`spec ` |
Specification of the desired behavior of the backup. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status |
|
`status ` |
Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status |
BackupConfiguration¶
BackupConfiguration defines how the backup of the cluster are taken. Currently the only supported backup method is barmanObjectStore. For details and examples refer to the Backup and Recovery section of the documentation
Name |
Description |
Type |
|---|---|---|
barmanObjectStore |
The configuration for the barman-cloud tool suite |
|
`retentionPolicy ` |
RetentionPolicy is the retention policy to be used for backups and WALs (i.e. ‘60d’). The retention policy is expressed in the form of XXu where XX is a positive integer and u is in [dwm] - days, weeks, months. |
string |
`target ` |
The policy to decide which instance should perform backups. Available options are empty string, which will default to prefer-standby policy, primary to have backups run always on primary instances, prefer-standby to have backups run preferably on the most updated standby, if available. |
BackupTarget |
BackupList¶
BackupList contains a list of Backup
Name |
Description |
Type |
|---|---|---|
metadata |
Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
|
`items ` |
List of backups - mandatory |
BackupSource¶
BackupSource contains the backup we need to restore from, plus some information that could be needed to correctly restore it.
Name |
Description |
Type |
|---|---|---|
endpointCA |
EndpointCA store the CA bundle of the barman endpoint. Useful when using self-signed certificates to avoid errors with certificate issuer and barman-cloud-wal-archive. |
BackupSpec¶
BackupSpec defines the desired state of Backup
Name |
Description |
Type |
|---|---|---|
cluster |
The cluster to backup |
|
`target ` |
The policy to decide which instance should perform this backup. If empty, it defaults to cluster.spec.backup.target. Available options are empty string, primary and prefer-standby. primary to have backups run always on primary instances, prefer-standby to have backups run preferably on the most updated standby, if available. |
BackupTarget |
BackupStatus¶
BackupStatus defines the observed state of Backup
Name |
Description |
Type |
|---|---|---|
`endpointCA ` |
EndpointCA store the CA bundle of the barman endpoint. Useful when using self-signed certificates to avoid errors with certificate issuer and barman-cloud-wal-archive. |
|
`endpointURL ` |
Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery |
string |
destinationPath |
The path where to store the backup (i.e. s3://bucket/path/to/folder) this path, with different destination folders, will be used for WALs and for data. This may not be populated in case of errors. |
string |
`serverName ` |
The server name on S3, the cluster name is used if this parameter is omitted |
string |
`encryption ` |
Encryption method required to S3 API |
string |
`backupId ` |
The ID of the Barman backup |
string |
`backupName ` |
The Name of the Barman backup |
string |
`phase ` |
The last backup status |
BackupPhase |
`startedAt ` |
When the backup was started |
|
`stoppedAt ` |
When the backup was terminated |
|
`beginWal ` |
The starting WAL |
string |
`endWal ` |
The ending WAL |
string |
`beginLSN ` |
The starting xlog |
string |
`endLSN ` |
The ending xlog |
string |
`error ` |
The detected error |
string |
`commandOutput ` |
Unused. Retained for compatibility with old versions. |
string |
`commandError ` |
The backup command output in case of error |
string |
`instanceID ` |
Information to identify the instance where the backup has been taken from |
BarmanCredentials¶
BarmanCredentials an object containing the potential credentials for each cloud provider
Name |
Description |
Type |
|---|---|---|
googleCredentials |
The credentials to use to upload data to Google Cloud Storage |
|
`s3Credentials ` |
The credentials to use to upload data to S3 |
|
`azureCredentials ` |
The credentials to use to upload data to Azure Blob Storage |
BarmanObjectStoreConfiguration¶
BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage
Name |
Description |
Type |
|---|---|---|
`endpointURL ` |
Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery |
string |
`endpointCA ` |
EndpointCA store the CA bundle of the barman endpoint. Useful when using self-signed certificates to avoid errors with certificate issuer and barman-cloud-wal-archive |
|
destinationPath |
The path where to store the backup (i.e. s3://bucket/path/to/folder) this path, with different destination folders, will be used for WALs and for data - mandatory |
string |
`serverName ` |
The server name on S3, the cluster name is used if this parameter is omitted |
string |
`wal ` |
The configuration for the backup of the WAL stream. When not defined, WAL files will be stored uncompressed and may be unencrypted in the object store, according to the bucket default policy. |
|
`data ` |
The configuration to be used to backup the data files When not defined, base backups files will be stored uncompressed and may be unencrypted in the object store, according to the bucket default policy. |
|
`tags ` |
Tags is a list of key value pairs that will be passed to the Barman –tags option. |
map[string]string |
`historyTags ` |
HistoryTags is a list of key value pairs that will be passed to the Barman –history-tags option. |
map[string]string |
BootstrapConfiguration¶
BootstrapConfiguration contains information about how to create the
PostgreSQL cluster. Only a single bootstrap method can be defined among
the supported ones. initdb will be used as the bootstrap method if
left unspecified. Refer to the Bootstrap page of the documentation for
more information.
Name |
Description |
Type |
|---|---|---|
`initdb ` |
Bootstrap the cluster via initdb |
|
`recovery ` |
Bootstrap the cluster from a backup |
|
pg_basebackup |
Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance |
BootstrapInitDB¶
BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information.
Name |
Description |
Type |
|---|---|---|
`database ` |
Name of the database used by the application. Default: app. - mandatory |
string |
`owner ` |
Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key. - mandatory |
string |
`secret ` |
Name of the secret containing the initial credentials for the owner of the user database. If empty a new secret will be created from scratch |
|
`options ` |
The list of options that must be passed to initdb when creating the cluster. Deprecated: This could lead to inconsistent configurations, please use the explicit provided parameters instead. If defined, explicit values will be ignored. |
[]string |
`dataChecksums ` |
Whether the -k option should be passed to initdb, enabling checksums on data pages (default: false) |
*bool |
`encoding ` |
The value to be passed as option –encoding for initdb (default:UTF8) |
string |
`localeCollate ` |
The value to be passed as option –lc-collate for initdb (default:C) |
string |
`localeCType ` |
The value to be passed as option –lc-ctype for initdb (default:C) |
string |
`walSegmentSize ` |
The value in megabytes (1 to 1024) to be passed to the –wal-segsize option for initdb (default: empty, resulting in PostgreSQL default: 16MB) |
int |
`postInitSQL ` |
List of SQL queries to be executed as a superuser immediately after the cluster has been created - to be used with extreme care (by default empty) |
[]string |
`postInitApplicationSQL ` |
List of SQL queries to be executed as a superuser in the application database right after is created - to be used with extreme care (by default empty) |
[]string |
`postInitTemplateSQL ` |
List of SQL queries to be executed as a superuser in the template1 after the cluster has been created - to be used with extreme care (by default empty) |
[]string |
`import ` |
Bootstraps the new cluster by importing data from an existing PostgreSQL instance using logical backup (pg_dump and pg_restore) |
|
postInitApplicationSQLRefs |
PostInitApplicationSQLRefs points references to ConfigMaps or Secrets which contain SQL files, the general implementation order to these references is from all Secrets to all ConfigMaps, and inside Secrets or ConfigMaps, the implementation order is same as the order of each array (by default empty) |
BootstrapPgBaseBackup¶
BootstrapPgBaseBackup contains the configuration required to take a physical backup of an existing PostgreSQL cluster
Name |
Description |
Type |
|---|---|---|
`source ` |
The name of the server of which we need to take a physical backup - mandatory |
string |
database |
Name of the database used by the application. Default: app. - mandatory |
string |
`owner ` |
Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key. - mandatory |
string |
`secret ` |
Name of the secret containing the initial credentials for the owner of the user database. If empty a new secret will be created from scratch |
BootstrapRecovery¶
BootstrapRecovery contains the configuration required to restore from an
existing cluster using 3 methodologies: external cluster, volume
snapshots or backup objects. Full recovery and Point-In-Time Recovery
are supported. The method can be also be used to create clusters in
continuous recovery (replica clusters), also supporting cascading
replication when instances > 1. Once the cluster exits recovery, the
password for the superuser will be changed through the provided secret.
Refer to the Bootstrap page of the documentation for more information.
Name |
Description |
Type |
|---|---|---|
`backup ` |
The backup object containing the physical base backup from which to initiate the recovery procedure. Mutually exclusive with source and volumeSnapshots. |
|
`source ` |
The external cluster whose backup we will restore. This is also used as the name of the folder under which the backup is stored, so it must be set to the name of the source cluster Mutually exclusive with backup and volumeSnapshots. |
string |
volumeSnapshots |
The static PVC data source(s) from which to initiate the recovery procedure. Currently supporting VolumeSnapshot and PersistentVolumeClaim resources that map an existing PVC group, compatible with CloudNativePG, and taken with a cold backup copy on a fenced Postgres instance (limitation which will be removed in the future when online backup will be implemented). Mutually exclusive with backup and source. |
|
`recoveryTarget ` |
By default, the recovery process applies all the available WAL files in the archive (full recovery). However, you can also end the recovery as soon as a consistent state is reached or recover to a point-in-time (PITR) by specifying a RecoveryTarget object, as expected by PostgreSQL (i.e., timestamp, transaction Id, LSN, …). More info: https://www.postgresql.org/docs/current/runtime-config-wal.html#RUNTIME-CONFIG-WAL-RECOVERY-TARGET |
|
`database ` |
Name of the database used by the application. Default: app. - mandatory |
string |
`owner ` |
Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key. - mandatory |
string |
`secret ` |
Name of the secret containing the initial credentials for the owner of the user database. If empty a new secret will be created from scratch |
CertificatesConfiguration¶
CertificatesConfiguration contains the needed configurations to handle server certificates.
Name |
Description |
Type |
|---|---|---|
`serverCASecret ` |
The secret containing the Server CA certificate. If not defined, a new secret will be created with a self-signed CA and will be used to generate the TLS certificate ServerTLSSecret.<br /> <br /> Contains:<br /> <br /> - ca.crt: CA that should be used to validate the server certificate, used as sslrootcert in client connection strings.<br /> - ca.key: key used to generate Server SSL certs, if ServerTLSSecret is provided, this can be omitted.<br /> |
string |
`serverTLSSecret ` |
The secret of type kubernetes.io/tls containing the server TLS certificate and key that will be set as ssl_cert_file and ssl_key_file so that clients can connect to postgres securely. If not defined, ServerCASecret must provide also ca.key and a new secret will be created using the provided CA. |
string |
replicationTLSSecret |
The secret of type kubernetes.io/tls containing the client certificate to authenticate as the streaming_replica user. If not defined, ClientCASecret must provide also ca.key, and a new secret will be created using the provided CA. |
string |
`clientCASecret ` |
The secret containing the Client CA certificate. If not defined, a new secret will be created with a self-signed CA and will be used to generate all the client certificates.<br /> <br /> Contains:<br /> <br /> - ca.crt: CA that should be used to validate the client certificates, used as ssl_ca_file of all the instances.<br /> - ca.key: key used to generate client certificates, if ReplicationTLSSecret is provided, this can be omitted.<br /> |
string |
`serverAltDNSNames ` |
The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. |
[]string |
CertificatesStatus¶
CertificatesStatus contains configuration certificates and related expiration dates.
Name |
Description |
Type |
|---|---|---|
expirations |
Expiration dates for all certificates. |
map[string]string |
Cluster¶
Cluster is the Schema for the PostgreSQL API
Name |
Description |
Type |
|---|---|---|
metadata |
||
`spec ` |
Specification of the desired behavior of the cluster. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status |
|
`status ` |
Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status |
ClusterList¶
ClusterList contains a list of Cluster
Name |
Description |
Type |
|---|---|---|
metadata |
Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
|
`items ` |
List of clusters - mandatory |
ClusterSpec¶
ClusterSpec defines the desired state of Cluster
Name |
Description |
Type |
|---|---|---|
`description ` |
Description of this PostgreSQL cluster |
string |
`inheritedMetadata ` |
Metadata that will be inherited by all objects related to the Cluster |
|
`imageName ` |
Name of the container image, supporting both tags (<image>:<tag>) and digests for deterministic and repeatable deployments (<image>:<tag>@sha256:<digestValue>) |
string |
`imagePullPolicy ` |
Image pull policy. One of Always, Never or IfNotPresent. If not defined, it defaults to IfNotPresent. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images |
corev1.PullPolicy |
`schedulerName ` |
If specified, the pod will be dispatched by specified Kubernetes scheduler. If not specified, the pod will be dispatched by the default scheduler. More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/ |
string |
`postgresUID ` |
The UID of the postgres user inside the image, defaults to 26 |
int64 |
`postgresGID ` |
The GID of the postgres user inside the image, defaults to 26 |
int64 |
`instances ` |
Number of instances required in the cluster - mandatory |
int |
`minSyncReplicas ` |
Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. |
int |
`maxSyncReplicas ` |
The target value for the synchronous replication quorum, that can be decreased if the number of ready standbys is lower than this. Undefined or 0 disable synchronous replication. |
int |
`postgresql ` |
Configuration of the PostgreSQL server |
|
`replicationSlots ` |
Replication slots management configuration |
|
`bootstrap ` |
Instructions to bootstrap this cluster |
|
`replica ` |
Replica cluster configuration |
|
`superuserSecret ` |
The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password |
|
`enableSuperuserAccess ` |
When this option is enabled, the operator will use the SuperuserSecret to update the postgres user password (if the secret is not present, the operator will automatically create one). When this option is disabled, the operator will ignore the SuperuserSecret content, delete it when automatically created, and then blank the password of the postgres user by setting it to NULL. Enabled by default. |
*bool |
`certificates ` |
The configuration for the CA and related certificates |
|
`imagePullSecrets ` |
The list of pull secrets to be used to pull the images |
|
`storage ` |
Configuration of the storage of the instances |
|
`serviceAccountTemplate ` |
Configure the generation of the service account |
|
`walStorage ` |
Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) |
|
`startDelay ` |
The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 30) |
int32 |
`stopDelay ` |
The time in seconds that is allowed for a PostgreSQL instance to gracefully shutdown (default 30) |
int32 |
`switchoverDelay ` |
The time in seconds that is allowed for a primary PostgreSQL instance to gracefully shutdown during a switchover. Default value is 40000000, greater than one year in seconds, big enough to simulate an infinite delay |
int32 |
`failoverDelay ` |
The amount of time (in seconds) to wait before triggering a failover after the primary PostgreSQL instance in the cluster was detected to be unhealthy |
int32 |
`affinity ` |
Affinity/Anti-affinity rules for Pods |
|
topologySpreadConstraints |
TopologySpreadConstraints specifies how to spread matching pods among the given topology. More info: https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ |
[]corev1.TopologySpreadConstraint |
`resources ` |
Resources requirements of every generated Pod. Please refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ for more information. |
|
`priorityClassName ` |
Name of the priority class which will be used in every generated Pod, if the PriorityClass specified does not exist, the pod will not be able to schedule. Please refer to https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass for more information |
string |
`primaryUpdateStrategy ` |
Deployment strategy to follow to upgrade the primary server during a rolling update procedure, after all replicas have been successfully updated: it can be automated (unsupervised - default) or manual (supervised) |
PrimaryUpdateStrategy |
`primaryUpdateMethod ` |
Method to follow to upgrade the primary server during a rolling update procedure, after all replicas have been successfully updated: it can be with a switchover (switchover) or in-place (restart - default) |
PrimaryUpdateMethod |
`backup ` |
The configuration to be used for backups |
|
`nodeMaintenanceWindow ` |
Define a maintenance window for the Kubernetes nodes |
|
`monitoring ` |
The configuration of the monitoring infrastructure of this cluster |
|
`externalClusters ` |
The list of external clusters which are used in the configuration |
|
`logLevel ` |
The instances’ log level, one of the following values: error, warning, info (default), debug, trace |
string |
`projectedVolumeTemplate ` |
Template to be used to define projected volumes, projected volumes will be mounted under /projected base folder |
*corev1.ProjectedVolumeSource |
`env ` |
Env follows the Env format to pass environment variables to the pods created in the cluster |
[]corev1.EnvVar |
`envFrom ` |
EnvFrom follows the EnvFrom format to pass environment variables sources to the pods to be used by Env |
[]corev1.EnvFromSource |
`managed ` |
The configuration that is used by the portions of PostgreSQL that are managed by the instance manager |
|
`seccompProfile ` |
The SeccompProfile applied to every Pod and Container. Defaults to: RuntimeDefault |
*corev1.SeccompProfile |
ClusterStatus¶
ClusterStatus defines the observed state of Cluster
Name |
Description |
Type |
|---|---|---|
`instances ` |
The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods. |
int |
`readyInstances ` |
The total number of ready instances in the cluster. It is equal to the number of ready instance pods. |
int |
`instancesStatus ` |
InstancesStatus indicates in which status the instances are |
map[utils.PodStatus][]string |
`instancesReportedState ` |
The reported state of the instances during the last reconciliation loop |
|
`managedRolesStatus ` |
ManagedRolesStatus reports the state of the managed roles in the cluster |
|
`timelineID ` |
The timeline of the Postgres cluster |
int |
`topology ` |
Instances topology. |
|
`latestGeneratedNode ` |
ID of the latest generated node (used to avoid node name clashing) |
int |
`currentPrimary ` |
Current primary instance |
string |
`targetPrimary ` |
Target primary instance, this is different from the previous one during a switchover or a failover |
string |
`pvcCount ` |
How many PVCs have been created by this cluster |
int32 |
`jobCount ` |
How many Jobs have been created by this cluster |
int32 |
`danglingPVC ` |
List of all the PVCs created by this cluster and still available which are not attached to a Pod |
[]string |
`resizingPVC ` |
List of all the PVCs that have ResizingPVC condition. |
[]string |
`initializingPVC ` |
List of all the PVCs that are being initialized by this cluster |
[]string |
`healthyPVC ` |
List of all the PVCs not dangling nor initializing |
[]string |
`unusablePVC ` |
List of all the PVCs that are unusable because another PVC is missing |
[]string |
`writeService ` |
Current write pod |
string |
`readService ` |
Current list of read pods |
string |
`phase ` |
Current phase of the cluster |
string |
`phaseReason ` |
Reason for the current phase |
string |
`secretsResourceVersion ` |
The list of resource versions of the secrets managed by the operator. Every change here is done in the interest of the instance manager, which will refresh the secret data |
|
`configMapResourceVersion ` |
The list of resource versions of the configmaps, managed by the operator. Every change here is done in the interest of the instance manager, which will refresh the configmap data |
|
`certificates ` |
The configuration for the CA and related certificates, initialized with defaults. |
|
`firstRecoverabilityPoint ` |
The first recoverability point, stored as a date in RFC3339 format |
string |
`lastSuccessfulBackup ` |
Stored as a date in RFC3339 format |
string |
`lastFailedBackup ` |
Stored as a date in RFC3339 format |
string |
`cloudNativePGCommitHash ` |
The commit hash number of which this operator running |
string |
`currentPrimaryTimestamp ` |
The timestamp when the last actual promotion to primary has occurred |
string |
currentPrimaryFailingSinceTimestamp |
The timestamp when the primary was detected to be unhealthy This field is reported when spec.failoverDelay is populated or during online upgrades |
string |
`targetPrimaryTimestamp ` |
The timestamp when the last request for a new primary has occurred |
string |
`poolerIntegrations ` |
The integration needed by poolers referencing the cluster |
|
`cloudNativePGOperatorHash ` |
The hash of the binary of the operator |
string |
`onlineUpdateEnabled ` |
OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster |
bool |
`azurePVCUpdateEnabled ` |
AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster |
bool |
`conditions ` |
Conditions for cluster object |
[]metav1.Condition |
`instanceNames ` |
List of instance names in the cluster |
[]string |
ConfigMapKeySelector¶
ConfigMapKeySelector contains enough information to let you locate the key of a ConfigMap
Name |
Description |
Type |
|---|---|---|
key |
The key to select - mandatory |
string |
ConfigMapResourceVersion¶
ConfigMapResourceVersion is the resource versions of the secrets managed by the operator
Name |
Description |
Type |
|---|---|---|
metrics |
A map with the versions of all the config maps used to pass metrics. Map keys are the config map names, map values are the versions |
map[string]string |
DataBackupConfiguration¶
DataBackupConfiguration is the configuration of the backup of the data directory
Name |
Description |
Type |
|---|---|---|
`compression ` |
Compress a backup file (a tar file per tablespace) while streaming it to the object store. Available options are empty string (no compression, default), gzip, bzip2 or snappy. |
CompressionType |
`encryption ` |
Whenever to force the encryption of files (if the bucket is not already configured for that). Allowed options are empty string (use the bucket policy, default), AES256 and aws:kms |
EncryptionType |
immediateCheckpoint |
Control whether the I/O workload for the backup initial checkpoint will be limited, according to the checkpoint_completion_target setting on the PostgreSQL server. If set to true, an immediate checkpoint will be used, meaning PostgreSQL will complete the checkpoint as soon as possible. false by default. |
bool |
`jobs ` |
The number of parallel jobs to be used to upload the backup, defaults to 2 |
*int32 |
DataSource¶
DataSource contains the configuration required to bootstrap a PostgreSQL cluster from an existing storage
Name |
Description |
Type |
|---|---|---|
`storage ` |
Configuration of the storage of the instances - mandatory |
corev1.TypedLocalObjectReference |
walStorage |
Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) |
*corev1.TypedLocalObjectReference |
EmbeddedObjectMetadata¶
EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster
Name |
Description |
Type |
|---|---|---|
`labels ` |
map[string]string |
|
annotations |
map[string]string |
ExternalCluster¶
ExternalCluster represents the connection parameters to an external cluster which is used in the other sections of the configuration
Name |
Description |
Type |
|---|---|---|
`name ` |
The server name, required - mandatory |
string |
connectionParameters |
The list of connection parameters, such as dbname, host, username, etc |
map[string]string |
`sslCert ` |
The reference to an SSL certificate to be used to connect to this instance |
|
`sslKey ` |
The reference to an SSL private key to be used to connect to this instance |
|
`sslRootCert ` |
The reference to an SSL CA public key to be used to connect to this instance |
|
`password ` |
The reference to the password to be used to connect to the server |
|
`barmanObjectStore ` |
The configuration for the barman-cloud tool suite |
GoogleCredentials¶
GoogleCredentials is the type for the Google Cloud Storage credentials. This needs to be specified even if we run inside a GKE environment.
Name |
Description |
Type |
|---|---|---|
`gkeEnvironment ` |
If set to true, will presume that it’s running inside a GKE environment, default to false. - mandatory |
bool |
applicationCredentials |
The secret containing the Google Cloud Storage JSON file with the credentials |
Import¶
Import contains the configuration to init a database from a logic snapshot of an externalCluster
Name |
Description |
Type |
|---|---|---|
`source ` |
The source of the import - mandatory |
|
`type ` |
The import type. Can be microservice or monolith. - mandatory |
SnapshotType |
`databases ` |
The databases to import - mandatory |
[]string |
`roles ` |
The roles to import |
[]string |
postImportApplicationSQL |
List of SQL queries to be executed as a superuser in the application database right after is imported - to be used with extreme care (by default empty). Only available in microservice type. |
[]string |
`schemaOnly ` |
When set to true, only the pre-data and post-data sections of pg_restore are invoked, avoiding data import. Default: false. |
bool |
ImportSource¶
ImportSource describes the source for the logical snapshot
Name |
Description |
Type |
|---|---|---|
externalCluster |
The name of the externalCluster used for import - mandatory |
string |
InstanceID¶
InstanceID contains the information to identify an instance
Name |
Description |
Type |
|---|---|---|
`podName ` |
The pod name |
string |
ContainerID |
The container ID |
string |
InstanceReportedState¶
InstanceReportedState describes the last reported state of an instance during a reconciliation loop
Name |
Description |
Type |
|---|---|---|
`isPrimary ` |
indicates if an instance is the primary one - mandatory |
bool |
timeLineID |
indicates on which TimelineId the instance is |
int |
LDAPBindAsAuth¶
LDAPBindAsAuth provides the required fields to use the bind authentication for LDAP
Name |
Description |
Type |
|---|---|---|
prefix |
Prefix for the bind authentication option |
string |
suffix |
Suffix for the bind authentication option |
string |
LDAPBindSearchAuth¶
LDAPBindSearchAuth provides the required fields to use the bind+search LDAP authentication process
Name |
Description |
Type |
|---|---|---|
`baseDN ` |
Root DN to begin the user search |
string |
`bindDN ` |
DN of the user to bind to the directory |
string |
`bindPassword ` |
Secret with the password for the user to bind to the directory |
|
searchAttribute |
Attribute to match against the username |
string |
`searchFilter ` |
Search filter to use when doing the search+bind authentication |
string |
LDAPConfig¶
LDAPConfig contains the parameters needed for LDAP authentication
Name |
Description |
Type |
|---|---|---|
`server ` |
LDAP hostname or IP address |
string |
`port ` |
LDAP server port |
int |
`scheme ` |
LDAP schema to be used, possible options are ldap and ldaps |
LDAPScheme |
`tls ` |
Set to ‘true’ to enable LDAP over TLS. ‘false’ is default |
bool |
`bindAsAuth ` |
Bind as authentication configuration |
|
bindSearchAuth |
Bind+Search authentication configuration |
LocalObjectReference¶
LocalObjectReference contains enough information to let you locate a local object with a known type inside the same namespace
Name |
Description |
Type |
|---|---|---|
name |
Name of the referent. - mandatory |
string |
ManagedConfiguration¶
ManagedConfiguration represents the portions of PostgreSQL that are managed by the instance manager
Name |
Description |
Type |
|---|---|---|
roles |
Database roles managed by the Cluster |
ManagedRoles¶
ManagedRoles tracks the status of a cluster’s managed roles
Name |
Description |
Type |
|---|---|---|
`byStatus ` |
ByStatus gives the list of roles in each state |
map[RoleStatus][]string |
cannotReconcile |
CannotReconcile lists roles that cannot be reconciled in PostgreSQL, with an explanation of the cause |
map[string][]string |
`passwordStatus ` |
PasswordStatus gives the last transaction id and password secret version for each managed role |
Metadata¶
Metadata is a structure similar to the metav1.ObjectMeta, but still parseable by controller-gen to create a suitable CRD for the user. The comment of PodTemplateSpec has an explanation of why we are not using the core data types.
Name |
Description |
Type |
|---|---|---|
`labels ` |
Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels |
map[string]string |
annotations |
Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations |
map[string]string |
MonitoringConfiguration¶
MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster
Name |
Description |
Type |
|---|---|---|
`disableDefaultQueries ` |
Whether the default queries should be injected. Set it to true if you don’t want to inject default queries into the cluster. Default: false. |
*bool |
customQueriesConfigMap |
The list of config maps containing the custom queries |
|
`customQueriesSecret ` |
The list of secrets containing the custom queries |
|
`enablePodMonitor ` |
Enable or disable the PodMonitor |
bool |
NodeMaintenanceWindow¶
NodeMaintenanceWindow contains information that the operator will use while upgrading the underlying node.
This option is only useful when the chosen storage prevents the Pods from being freely moved across nodes.
Name |
Description |
Type |
|---|---|---|
inProgress |
Is there a node maintenance activity in progress? - mandatory |
bool |
`reusePVC ` |
Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere - when instances >1) - mandatory |
*bool |
PasswordState¶
PasswordState represents the state of the password of a managed RoleConfiguration
Name |
Description |
Type |
|---|---|---|
`transactionID ` |
the last transaction ID to affect the role definition in PostgreSQL |
int64 |
resourceVersion |
the resource version of the password secret |
string |
PgBouncerIntegrationStatus¶
PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster
Name |
Description |
Type |
|---|---|---|
secrets |
[]string |
PgBouncerSecrets¶
PgBouncerSecrets contains the versions of the secrets used by pgbouncer
Name |
Description |
Type |
|---|---|---|
authQuery |
The auth query secret version |
PgBouncerSpec¶
PgBouncerSpec defines how to configure PgBouncer
Name |
Description |
Type |
|---|---|---|
`poolMode ` |
The pool mode - mandatory |
PgBouncerPoolMode |
authQuerySecret |
The credentials of the user that need to be used for the authentication query. In case it is specified, also an AuthQuery (e.g. “SELECT usename, passwd FROM pg_shadow WHERE usename=$1”) has to be specified and no automatic CNPG Cluster integration will be triggered. |
|
`authQuery ` |
The query that will be used to download the hash of the password of a certain user. Default: “SELECT usename, passwd FROM user_search($1)”. In case it is specified, also an AuthQuerySecret has to be specified and no automatic CNPG Cluster integration will be triggered. |
string |
`parameters ` |
Additional parameters to be passed to PgBouncer - please check the CNPG documentation for a list of options you can configure |
map[string]string |
`pg_hba ` |
PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) |
[]string |
`paused ` |
When set to true, PgBouncer will disconnect from the PostgreSQL server, first waiting for all queries to complete, and pause all new client connections until this value is set to false (default). Internally, the operator calls PgBouncer’s PAUSE and RESUME commands. |
*bool |
PodTemplateSpec¶
PodTemplateSpec is a structure allowing the user to set a template for Pod generation.
Unfortunately we can’t use the corev1.PodTemplateSpec type because the generated CRD won’t have the field for the metadata section.
References: https://github.com/kubernetes-sigs/controller-tools/issues/385 https://github.com/kubernetes-sigs/controller-tools/issues/448 https://github.com/prometheus-operator/prometheus-operator/issues/3041
Name |
Description |
Type |
|---|---|---|
metadata |
Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata |
|
`spec ` |
Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status |
corev1.PodSpec |
Pooler¶
Pooler is the Schema for the poolers API
Name |
Description |
Type |
|---|---|---|
metadata |
||
`spec ` |
||
`status ` |
PoolerIntegrations¶
PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster
Name |
Description |
Type |
|---|---|---|
pgBouncerIntegration |
PoolerList¶
PoolerList contains a list of Pooler
Name |
Description |
Type |
|---|---|---|
metadata |
||
`items ` |
|
PoolerMonitoringConfiguration¶
PoolerMonitoringConfiguration is the type containing all the monitoring configuration for a certain Pooler.
Mirrors the Cluster’s MonitoringConfiguration but without the custom queries part for now.
Name |
Description |
Type |
|---|---|---|
enablePodMonitor |
Enable or disable the PodMonitor |
bool |
PoolerSecrets¶
PoolerSecrets contains the versions of all the secrets used
Name |
Description |
Type |
|---|---|---|
`serverTLS ` |
The server TLS secret version |
|
`serverCA ` |
The server CA secret version |
|
`clientCA ` |
The client CA secret version |
|
pgBouncerSecrets |
The version of the secrets used by PgBouncer |
PoolerSpec¶
PoolerSpec defines the desired state of Pooler
Name |
Description |
Type |
|---|---|---|
`cluster ` |
This is the cluster reference on which the Pooler will work. Pooler name should never match with any cluster name within the same namespace. - mandatory |
|
`type ` |
Which instances we must forward traffic to? - mandatory |
PoolerType |
`instances ` |
The number of replicas we want - mandatory |
int32 |
`template ` |
The template of the Pod to be created |
|
`pgbouncer ` |
The PgBouncer configuration - mandatory |
|
deploymentStrategy |
The deployment strategy to use for pgbouncer to replace existing pods with new ones |
*appsv1.DeploymentStrategy |
`monitoring ` |
The configuration of the monitoring infrastructure of this pooler. |
PoolerStatus¶
PoolerStatus defines the observed state of Pooler
Name |
Description |
Type |
|---|---|---|
`secrets ` |
The resource version of the config object |
|
instances |
The number of pods trying to be scheduled |
int32 |
PostInitApplicationSQLRefs¶
PostInitApplicationSQLRefs points references to ConfigMaps or Secrets which contain SQL files, the general implementation order to these references is from all Secrets to all ConfigMaps, and inside Secrets or ConfigMaps, the implementation order is same as the order of each array
Name |
Description |
Type |
|---|---|---|
`secretRefs ` |
SecretRefs holds a list of references to Secrets |
|
configMapRefs |
ConfigMapRefs holds a list of references to ConfigMaps |
PostgresConfiguration¶
PostgresConfiguration defines the PostgreSQL configuration
Name |
Description |
Type |
|---|---|---|
`parameters ` |
PostgreSQL configuration options (postgresql.conf) |
map[string]string |
`pg_hba ` |
PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) |
[]string |
syncReplicaElectionConstraint |
Requirements to be met by sync replicas. This will affect how the “synchronous_standby_names” parameter will be set up. |
|
`promotionTimeout ` |
Specifies the maximum number of seconds to wait when promoting an instance to primary. Default value is 40000000, greater than one year in seconds, big enough to simulate an infinite timeout |
int32 |
`shared_preload_libraries ` |
Lists of shared preload libraries to add to the default ones |
[]string |
`ldap ` |
Options to specify LDAP configuration |
RecoveryTarget¶
RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive.
Name |
Description |
Type |
|---|---|---|
`backupID ` |
The ID of the backup from which to start the recovery process. If empty (default) the operator will automatically detect the backup based on targetTime or targetLSN if specified. Otherwise use the latest available backup in chronological order. |
string |
`targetTLI ` |
The target timeline (“latest” or a positive integer) |
string |
`targetXID ` |
The target transaction ID |
string |
`targetName ` |
The target name (to be previously created with pg_create_restore_point) |
string |
`targetLSN ` |
The target LSN (Log Sequence Number) |
string |
`targetTime ` |
The target time as a timestamp in the RFC3339 standard |
string |
targetImmediate |
End recovery as soon as a consistent state is reached |
*bool |
`exclusive ` |
Set the target to be exclusive. If omitted, defaults to false, so that in Postgres, recovery_target_inclusive will be true |
*bool |
ReplicaClusterConfiguration¶
ReplicaClusterConfiguration encapsulates the configuration of a replica cluster
Name |
Description |
Type |
|---|---|---|
enabled |
If replica mode is enabled, this cluster will be a replica of an existing cluster. Replica cluster can be created from a recovery object store or via streaming through pg_basebackup. Refer to the Replication page of the documentation for more information. - mandatory |
bool |
`source ` |
The name of the external cluster which is the replication origin - mandatory |
string |
ReplicationSlotsConfiguration¶
ReplicationSlotsConfiguration encapsulates the configuration of replication slots
Name |
Description |
Type |
|---|---|---|
highAvailability |
Replication slots for high availability configuration |
|
`updateInterval ` |
Standby will update the status of the local replication slots every updateInterval seconds (default 30). |
int |
ReplicationSlotsHAConfiguration¶
ReplicationSlotsHAConfiguration encapsulates the configuration of the replication slots that are automatically managed by the operator to control the streaming replication connections with the standby instances for high availability (HA) purposes. Replication slots are a PostgreSQL feature that makes sure that PostgreSQL automatically keeps WAL files in the primary when a streaming client (in this specific case a replica that is part of the HA cluster) gets disconnected.
Name |
Description |
Type |
|---|---|---|
`enabled ` |
If enabled, the operator will automatically manage replication slots on the primary instance and use them in streaming replication connections with all the standby instances that are part of the HA cluster. If disabled (default), the operator will not take advantage of replication slots in streaming connections with the replicas. This feature also controls replication slots in replica cluster, from the designated primary to its cascading replicas. This can only be set at creation time. - mandatory |
*bool |
slotPrefix |
Prefix for replication slots managed by the operator for HA. It may only contain lower case letters, numbers, and the underscore character. This can only be set at creation time. By default set to _cnpg_. |
string |
RoleConfiguration¶
RoleConfiguration is the representation, in Kubernetes, of a PostgreSQL role with the additional field Ensure specifying whether to ensure the presence or absence of the role in the database
The defaults of the CREATE ROLE command are applied Reference: https://www.postgresql.org/docs/current/sql-createrole.html
Name |
Description |
Type |
|---|---|---|
`name ` |
Name of the role - mandatory |
string |
`comment ` |
Description of the role |
string |
`ensure ` |
Ensure the role is present or absent - defaults to “present” |
EnsureOption |
`passwordSecret ` |
Secret containing the password of the role (if present) If null, the password will be ignored unless DisablePassword is set |
|
disablePassword |
DisablePassword indicates that a role’s password should be set to NULL in Postgres |
bool |
`superuser ` |
Whether the role is a superuser who can override all access restrictions within the database - superuser status is dangerous and should be used only when really needed. You must yourself be a superuser to create a new superuser. Defaults is false. |
bool |
`createdb ` |
When set to true, the role being defined will be allowed to create new databases. Specifying false (default) will deny a role the ability to create databases. |
bool |
`createrole ` |
Whether the role will be permitted to create, alter, drop, comment on, change the security label for, and grant or revoke membership in other roles. Default is false. |
bool |
`inherit ` |
Whether a role “inherits” the privileges of roles it is a member of. Defaults is true. |
*bool |
`login ` |
Whether the role is allowed to log in. A role having the login attribute can be thought of as a user. Roles without this attribute are useful for managing database privileges, but are not users in the usual sense of the word. Default is false. |
bool |
`replication ` |
Whether a role is a replication role. A role must have this attribute (or be a superuser) in order to be able to connect to the server in replication mode (physical or logical replication) and in order to be able to create or drop replication slots. A role having the replication attribute is a very highly privileged role, and should only be used on roles actually used for replication. Default is false. |
bool |
`bypassrls ` |
Whether a role bypasses every row-level security (RLS) policy. Default is false. |
bool |
connectionLimit |
If the role can log in, this specifies how many concurrent connections the role can make. -1 (the default) means no limit. |
int64 |
`validUntil ` |
Date and time after which the role’s password is no longer valid. When omitted, the password will never expire (default). |
|
`inRoles ` |
List of one or more existing roles to which this role will be immediately added as a new member. Default empty. |
[]string |
RollingUpdateStatus¶
RollingUpdateStatus contains the information about an instance which is being updated
Name |
Description |
Type |
|---|---|---|
imageName |
The image which we put into the Pod - mandatory |
string |
startedAt |
When the update has been started |
S3Credentials¶
S3Credentials is the type for the credentials to be used to upload files to S3. It can be provided in two alternative ways:
explicitly passing accessKeyId and secretAccessKey
inheriting the role from the pod environment by setting inheritFromIAMRole to true
Name |
Description |
Type |
|---|---|---|
`accessKeyId ` |
The reference to the access key id |
|
`secretAccessKey ` |
The reference to the secret access key |
|
`region ` |
The reference to the secret containing the region name |
|
`sessionToken ` |
The references to the session key |
|
inheritFromIAMRole |
Use the role based authentication without providing explicitly the keys. - mandatory |
bool |
ScheduledBackup¶
ScheduledBackup is the Schema for the scheduledbackups API
Name |
Description |
Type |
|---|---|---|
metadata |
||
`spec ` |
Specification of the desired behavior of the ScheduledBackup. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status |
|
`status ` |
Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status |
ScheduledBackupList¶
ScheduledBackupList contains a list of ScheduledBackup
Name |
Description |
Type |
|---|---|---|
metadata |
Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
|
`items ` |
List of clusters - mandatory |
ScheduledBackupSpec¶
ScheduledBackupSpec defines the desired state of ScheduledBackup
Name |
Description |
Type |
|---|---|---|
`suspend ` |
If this backup is suspended or not |
*bool |
`immediate ` |
If the first backup has to be immediately start after creation or not |
*bool |
`schedule ` |
The schedule does not follow the same format used in Kubernetes CronJobs as it includes an additional seconds specifier, see https://pkg.go.dev/github.com/robfig/cron#hdr-CRON_Expression_Format - mandatory |
string |
`cluster ` |
The cluster to backup |
|
backupOwnerReference |
Indicates which ownerReference should be put inside the created backup resources.<br /> - none: no owner reference for created backup objects (same behavior as before the field was introduced)<br /> - self: sets the Scheduled backup object as owner of the backup<br /> - cluster: set the cluster as owner of the backup<br /> |
string |
`target ` |
The policy to decide which instance should perform this backup. If empty, it defaults to cluster.spec.backup.target. Available options are empty string, primary and prefer-standby. primary to have backups run always on primary instances, prefer-standby to have backups run preferably on the most updated standby, if available. |
BackupTarget |
ScheduledBackupStatus¶
ScheduledBackupStatus defines the observed state of ScheduledBackup
Name |
Description |
Type |
|---|---|---|
`lastCheckTime ` |
The latest time the schedule |
|
lastScheduleTime |
Information when was the last time that backup was successfully scheduled. |
|
nextScheduleTime |
Next time we will run a backup |
SecretKeySelector¶
SecretKeySelector contains enough information to let you locate the key of a Secret
Name |
Description |
Type |
|---|---|---|
key |
The key to select - mandatory |
string |
SecretVersion¶
SecretVersion contains a secret name and its ResourceVersion
Name |
Description |
Type |
|---|---|---|
`name ` |
The name of the secret |
string |
version |
The ResourceVersion of the secret |
string |
SecretsResourceVersion¶
SecretsResourceVersion is the resource versions of the secrets managed by the operator
Name |
Description |
Type |
|---|---|---|
`superuserSecretVersion ` |
The resource version of the “postgres” user secret |
string |
replicationSecretVersion |
The resource version of the “streaming_replica” user secret |
string |
applicationSecretVersion |
The resource version of the “app” user secret |
string |
managedRoleSecretVersion |
The resource versions of the managed roles secrets |
map[string]string |
`caSecretVersion ` |
Unused. Retained for compatibility with old versions. |
string |
`clientCaSecretVersion ` |
The resource version of the PostgreSQL client-side CA secret version |
string |
`serverCaSecretVersion ` |
The resource version of the PostgreSQL server-side CA secret version |
string |
`serverSecretVersion ` |
The resource version of the PostgreSQL server-side secret version |
string |
`barmanEndpointCA ` |
The resource version of the Barman Endpoint CA if provided |
string |
`metrics ` |
A map with the versions of all the secrets used to pass metrics. Map keys are the secret names, map values are the versions |
map[string]string |
ServiceAccountTemplate¶
ServiceAccountTemplate contains the template needed to generate the service accounts
Name |
Description |
Type |
|---|---|---|
metadata |
Metadata are the metadata to be used for the generated service account - mandatory |
StorageConfiguration¶
StorageConfiguration is the configuration of the storage of the PostgreSQL instances
Name |
Description |
Type |
|---|---|---|
`storageClass ` |
StorageClass to use for database data (PGDATA). Applied after evaluating the PVC template, if available. If not specified, generated PVCs will be satisfied by the default storage class |
*string |
`size ` |
Size of the storage. Required if not already specified in the PVC template. Changes to this field are automatically reapplied to the created PVCs. Size cannot be decreased. |
string |
resizeInUseVolumes |
Resize existent PVCs, defaults to true |
*bool |
`pvcTemplate ` |
Template to be used to generate the Persistent Volume Claim |
SyncReplicaElectionConstraints¶
SyncReplicaElectionConstraints contains the constraints for sync replicas election.
For anti-affinity parameters two instances are considered in the same location if all the labels values match.
In future synchronous replica election restriction by name will be supported.
Name |
Description |
Type |
|---|---|---|
`enabled ` |
This flag enables the constraints for sync replicas - mandatory |
bool |
nodeLabelsAntiAffinity |
A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not |
[]string |
Topology¶
Topology contains the cluster topology
Name |
Description |
Type |
|---|---|---|
successfullyExtracted |
SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors in synchronous replica election in case of failures |
bool |
`instances ` |
Instances contains the pod topology of the instances |
map[PodName]PodTopologyLabels |
`nodesUsed ` |
NodesUsed represents the count of distinct nodes accommodating the instances. A value of ‘1’ suggests that all instances are hosted on a single node, implying the absence of High Availability (HA). Ideally, this value should be the same as the number of instances in the Postgres HA cluster, implying shared nothing architecture on the compute side. |
int32 |
WalBackupConfiguration¶
WalBackupConfiguration is the configuration of the backup of the WAL stream
Name |
Description |
Type |
|---|---|---|
compression |
Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), gzip, bzip2 or snappy. |
CompressionType |
`encryption ` |
Whenever to force the encryption of files (if the bucket is not already configured for that). Allowed options are empty string (use the bucket policy, default), AES256 and aws:kms |
EncryptionType |
maxParallel |
Number of WAL files to be either archived in parallel (when the PostgreSQL instance is archiving to a backup object store) or restored in parallel (when a PostgreSQL standby is fetching WAL files from a recovery object store). If not specified, WAL files will be processed one at a time. It accepts a positive integer as a value - with 1 being the minimum accepted value. |
int |
