API Reference - v1.22.4 v1

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

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

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

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

Specification of the desired behavior of the Pooler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

Most recently observed status of the Pooler. 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

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

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

Activates anti-affinity for the pods. The operator will define pods anti-affinity unless this field is explicitly set to false

TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that

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/

NodeAffinity describes node affinity scheduling rules for the pod. More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

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/

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

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.

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

GoArch is the name of the executable architecture

Hash is the hash of the executable

The connection string to be used

The storage account where to upload data

The storage account key to be used in conjunction with the storage account name

A shared-access-signature to be used in conjunction with the storage account name

Use the Azure AD based authentication without providing explicitly the keys.

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

The configuration for the barman-cloud tool suite

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. It's currently only applicable when using the BarmanObjectStore method.

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-standbyto have backups run preferably on the most updated standby, if available.

Name is the snapshot resource name

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

TablespaceName is the name of the snapshotted tablespace. Only set when type is PG_TABLESPACE

The elements list, populated with the gathered volume snapshots

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.

The cluster to backup

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.

The backup method to be used, possible options are barmanObjectStoreand volumeSnapshot. Defaults to: barmanObjectStore.

Whether the default type of backup with volume snapshots is online/hot (true, default) or offline/cold (false) Overrides the default setting specified in the cluster field '.spec.backup.volumeSnapshot.online'

Configuration parameters to control the online/hot backup with volume snapshots Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

The potential credentials for each cloud provider

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.

Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery

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.

The server name on S3, the cluster name is used if this parameter is omitted

Encryption method required to S3 API

The ID of the Barman backup

The Name of the Barman backup

The last backup status

When the backup was started

When the backup was terminated

The starting WAL

The ending WAL

The starting xlog

The ending xlog

The detected error

Unused. Retained for compatibility with old versions.

The backup command output in case of error

Backup label file content as returned by Postgres in case of online (hot) backups

Tablespace map file content as returned by Postgres in case of online (hot) backups

Information to identify the instance where the backup has been taken from

Status of the volumeSnapshot backup

The backup method being used

Whether the backup was online/hot (true) or offline/cold (false)

The credentials to use to upload data to Google Cloud Storage

The credentials to use to upload data to S3

The credentials to use to upload data to Azure Blob Storage

The potential credentials for each cloud provider

Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery

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

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

The server name on S3, the cluster name is used if this parameter is omitted

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.

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 is a list of key value pairs that will be passed to the Barman --tags option.

HistoryTags is a list of key value pairs that will be passed to the Barman --history-tags option.

Bootstrap the cluster via initdb

Bootstrap the cluster from a backup

Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance

Name of the database used by the application. Default: app.

Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key.

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

If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true

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.

Whether the -k option should be passed to initdb, enabling checksums on data pages (default: false)

The value to be passed as option --encoding for initdb (default:UTF8)

The value to be passed as option --lc-collate for initdb (default:C)

The value to be passed as option --lc-ctype for initdb (default:C)

The value in megabytes (1 to 1024) to be passed to the --wal-segsizeoption for initdb (default: empty, resulting in PostgreSQL default: 16MB)

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)

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)

List of SQL queries to be executed as a superuser in the template1after the cluster has been created - to be used with extreme care (by default empty)

Bootstraps the new cluster by importing data from an existing PostgreSQL instance using logical backup (pg_dump and pg_restore)

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)

The name of the server of which we need to take a physical backup

Name of the database used by the application. Default: app.

Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key.

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

The backup object containing the physical base backup from which to initiate the recovery procedure. Mutually exclusive with source and volumeSnapshots.

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.

The static PVC data source(s) from which to initiate the recovery procedure. Currently supporting VolumeSnapshotand PersistentVolumeClaim resources that map an existing PVC group, compatible with EDB Postgres for Kubernetes, 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.

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

Name of the database used by the application. Default: app.

Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key.

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

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.

Contains:

• ca.crt: CA that should be used to validate the server certificate, used as sslrootcert in client connection strings.
• ca.key: key used to generate Server SSL certs, if ServerTLSSecret is provided, this can be omitted.

The secret of type kubernetes.io/tls containing the server TLS certificate and key that will be set asssl_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.

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.

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.

Contains:

• ca.crt: CA that should be used to validate the client certificates, used as ssl_ca_file of all the instances.
• ca.key: key used to generate client certificates, if ReplicationTLSSecret is provided, this can be omitted.

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

Needed configurations to handle server certificates, initialized with default values, if needed.

Expiration dates for all certificates.

Description of this PostgreSQL cluster

Metadata that will be inherited by all objects related to the Cluster

Name of the container image, supporting both tags (<image>:<tag>) and digests for deterministic and repeatable deployments (<image>:<tag>@sha256:<digestValue>)

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

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/

The UID of the postgres user inside the image, defaults to 26

The GID of the postgres user inside the image, defaults to 26

Number of instances required in the cluster

Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available.

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.

Configuration of the PostgreSQL server

Replication slots management configuration

Instructions to bootstrap this cluster

Replica cluster configuration

The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password

When this option is enabled, the operator will use the SuperuserSecretto 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 postgresuser by setting it to NULL. Disabled by default.

The configuration for the CA and related certificates

The list of pull secrets to be used to pull the images. If the license key contains a pull secret that secret will be automatically included.

Configuration of the storage of the instances

Configure the generation of the service account

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 3600). The startup probe failure threshold is derived from this value using the formula: ceiling(startDelay / 10).

The time in seconds that is allowed for a PostgreSQL instance to gracefully shutdown (default 1800)

Deprecated: please use SmartShutdownTimeout instead

The time in seconds that controls the window of time reserved for the smart shutdown of Postgres to complete. Make sure you reserve enough time for the operator to request a fast shutdown of Postgres (that is: stopDelay - smartShutdownTimeout).

The time in seconds that is allowed for a primary PostgreSQL instance to gracefully shutdown during a switchover. Default value is 3600 seconds (1 hour).

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

LivenessProbeTimeout is the time (in seconds) that is allowed for a PostgreSQL instance to successfully respond to the liveness probe (default 30). The Liveness probe failure threshold is derived from this value using the formula: ceiling(livenessProbe / 10).

Affinity/Anti-affinity rules for Pods

TopologySpreadConstraints specifies how to spread matching pods among the given topology. More info: https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

Resources requirements of every generated Pod. Please refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ for more information.

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral volumes

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

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)

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)

The configuration to be used for backups

Define a maintenance window for the Kubernetes nodes

The license key of the cluster. When empty, the cluster operates in trial mode and after the expiry date (default 30 days) the operator will cease any reconciliation attempt. For details, please refer to the license agreement that comes with the operator.

The reference to the license key. When this is set it take precedence over LicenseKey.

The configuration of the monitoring infrastructure of this cluster

The list of external clusters which are used in the configuration

The instances' log level, one of the following values: error, warning, info (default), debug, trace

Template to be used to define projected volumes, projected volumes will be mounted under /projected base folder

Env follows the Env format to pass environment variables to the pods created in the cluster

EnvFrom follows the EnvFrom format to pass environment variables sources to the pods to be used by Env

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

The SeccompProfile applied to every Pod and Container. Defaults to: RuntimeDefault

Manage the PodDisruptionBudget resources within the cluster. When configured as true (default setting), the pod disruption budgets will safeguard the primary node from being terminated. Conversely, setting it to false will result in the absence of anyPodDisruptionBudget resource, permitting the shutdown of all nodes hosting the PostgreSQL cluster. This latter configuration is advisable for any PostgreSQL cluster employed for development/staging purposes. Only available in 1.23 or later

The tablespaces configuration

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

InstancesStatus indicates in which status the instances are

The reported state of the instances during the last reconciliation loop

ManagedRolesStatus reports the state of the managed roles in the cluster

TablespacesStatus reports the state of the declarative tablespaces in the cluster

The timeline of the Postgres cluster

Instances topology.

ID of the latest generated node (used to avoid node name clashing)

Current primary instance

Target primary instance, this is different from the previous one during a switchover or a failover

How many PVCs have been created by this cluster

How many Jobs have been created by this cluster

List of all the PVCs created by this cluster and still available which are not attached to a Pod

List of all the PVCs that have ResizingPVC condition.

List of all the PVCs that are being initialized by this cluster

List of all the PVCs not dangling nor initializing

List of all the PVCs that are unusable because another PVC is missing

Status of the license

Current write pod

Current list of read pods

Current phase of the cluster

Reason for the current phase

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

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

The configuration for the CA and related certificates, initialized with defaults.

The first recoverability point, stored as a date in RFC3339 format. This field is calculated from the content of FirstRecoverabilityPointByMethod

The first recoverability point, stored as a date in RFC3339 format, per backup method type

Last successful backup, stored as a date in RFC3339 format This field is calculated from the content of LastSuccessfulBackupByMethod

Last successful backup, stored as a date in RFC3339 format, per backup method type

Stored as a date in RFC3339 format

The commit hash number of which this operator running

The timestamp when the last actual promotion to primary has occurred

The timestamp when the primary was detected to be unhealthy This field is reported when .spec.failoverDelay is populated or during online upgrades

The timestamp when the last request for a new primary has occurred

The integration needed by poolers referencing the cluster

The hash of the binary of the operator

AvailableArchitectures reports the available architectures of a cluster

Conditions for cluster object

List of instance names in the cluster

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

The name of the secret in the pod's namespace to select from.

The key to select

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

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.

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

The number of parallel jobs to be used to upload the backup, defaults to 2

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.

AdditionalCommandArgs represents additional arguments that can be appended to the 'barman-cloud-backup' command-line invocation. These arguments provide flexibility to customize the backup process further according to specific requirements or configurations.

Example: In a scenario where specialized backup options are required, such as setting a specific timeout or defining custom behavior, users can use this field to specify additional command arguments.

Note: It's essential to ensure that the provided arguments are valid and supported by the 'barman-cloud-backup' command, to avoid potential errors or unintended behavior during execution.

Configuration of the storage of the instances

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

Configuration of the storage for PostgreSQL tablespaces

If true enables edb_audit logging

TDE configuration

Shm is the size limit of the shared memory volume

TemporaryData is the size limit of the temporary data volume

The server name, required

The list of connection parameters, such as dbname, host, username, etc

The reference to an SSL certificate to be used to connect to this instance

The reference to an SSL private key to be used to connect to this instance

The reference to an SSL CA public key to be used to connect to this instance

The reference to the password to be used to connect to the server. If a password is provided, EDB Postgres for Kubernetes creates a PostgreSQL passfile at /controller/external/NAME/pass (where "NAME" is the cluster's name). This passfile is automatically referenced in the connection string when establishing a connection to the remote PostgreSQL server from the current PostgreSQL Cluster. This ensures secure and efficient password management for external clusters.

The configuration for the barman-cloud tool suite

The secret containing the Google Cloud Storage JSON file with the credentials

If set to true, will presume that it's running inside a GKE environment, default to false.

The source of the import

The import type. Can be microservice or monolith.

The databases to import

The roles to import

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.

When set to true, only the pre-data and post-data sections ofpg_restore are invoked, avoiding data import. Default: false.

The name of the externalCluster used for import

The pod name

The container ID

indicates if an instance is the primary one

indicates on which TimelineId the instance is

Prefix for the bind authentication option

Suffix for the bind authentication option

Root DN to begin the user search

DN of the user to bind to the directory

Secret with the password for the user to bind to the directory

Attribute to match against the username

Search filter to use when doing the search+bind authentication

LDAP hostname or IP address

LDAP server port

LDAP schema to be used, possible options are ldap and ldaps

Bind as authentication configuration

Bind+Search authentication configuration

Set to 'true' to enable LDAP over TLS. 'false' is default

Name of the referent.

Database roles managed by the Cluster

ByStatus gives the list of roles in each state

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, with an explanation of the cause

PasswordStatus gives the last transaction id and password secret version for each managed role

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

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

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.

The list of config maps containing the custom queries

The list of secrets containing the custom queries

Enable or disable the PodMonitor

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

The list of relabelings for the PodMonitor. Applied to samples before scraping.

Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere - when instances >1)

Is there a node maintenance activity in progress?

If false, the function will return immediately after the backup is completed, without waiting for WAL to be archived. This behavior is only useful with backup software that independently monitors WAL archiving. Otherwise, WAL required to make the backup consistent might be missing and make the backup useless. By default, or when this parameter is true, pg_backup_stop will wait for WAL to be archived when archiving is enabled. On a standby, this means that it will wait only when archive_mode = always. If write activity on the primary is low, it may be useful to run pg_switch_wal on the primary in order to trigger an immediate segment switch.

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.

the last transaction ID to affect the role definition in PostgreSQL

the resource version of the password secret

The auth query secret version

The pool mode. Default: session.

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_catalog.pg_shadow WHERE usename=$1") has to be specified and no automatic CNP Cluster integration will be triggered.

The query that will be used to download the hash of the password of a certain user. Default: "SELECT usename, passwd FROM public.user_search($1)". In case it is specified, also an AuthQuerySecret has to be specified and no automatic CNP Cluster integration will be triggered.

Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure

PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file)

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.

Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

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

Enable or disable the PodMonitor

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

The list of relabelings for the PodMonitor. Applied to samples before scraping.

The server TLS secret version

The server CA secret version

The client CA secret version

The version of the secrets used by PgBouncer

This is the cluster reference on which the Pooler will work. Pooler name should never match with any cluster name within the same namespace.

Type of service to forward traffic to. Default: rw.

The number of replicas we want. Default: 1.

The template of the Pod to be created

The PgBouncer configuration

The deployment strategy to use for pgbouncer to replace existing pods with new ones

The configuration of the monitoring infrastructure of this pooler.

The resource version of the config object

The number of pods trying to be scheduled

SecretRefs holds a list of references to Secrets

ConfigMapRefs holds a list of references to ConfigMaps

PostgreSQL configuration options (postgresql.conf)

PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file)

PostgreSQL User Name Maps rules (lines to be appended to the pg_ident.conf file)

EDB Postgres Advanced Server specific configurations

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up.

Lists of shared preload libraries to add to the default ones

Options to specify LDAP configuration

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

If this parameter is true, the user will be able to invoke ALTER SYSTEMon this EDB Postgres for Kubernetes Cluster. This should only be used for debugging and troubleshooting. Defaults to false.

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.

The target timeline ("latest" or a positive integer)

The target transaction ID

The target name (to be previously created with pg_create_restore_point)

The target LSN (Log Sequence Number)

The target time as a timestamp in the RFC3339 standard

End recovery as soon as a consistent state is reached

Set the target to be exclusive. If omitted, defaults to false, so that in Postgres, recovery_target_inclusive will be true

The name of the external cluster which is the replication origin

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 Replica clusters page of the documentation for more information.

Replication slots for high availability configuration

Standby will update the status of the local replication slots every updateInterval seconds (default 30).

If enabled (default), 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, 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.

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 _cnp_.

Name of the role

Description of the role

Ensure the role is present or absent - defaults to "present"

Secret containing the password of the role (if present) If null, the password will be ignored unless DisablePassword is set

If the role can log in, this specifies how many concurrent connections the role can make. -1 (the default) means no limit.

Date and time after which the role's password is no longer valid. When omitted, the password will never expire (default).

List of one or more existing roles to which this role will be immediately added as a new member. Default empty.

Whether a role "inherits" the privileges of roles it is a member of. Defaults is true.

DisablePassword indicates that a role's password should be set to NULL in Postgres

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.

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.

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.

Whether the role is allowed to log in. A role having the loginattribute 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.

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.

Whether a role bypasses every row-level security (RLS) policy. Default is false.

The reference to the access key id

The reference to the secret access key

The reference to the secret containing the region name

The references to the session key

Use the role based authentication without providing explicitly the keys.

If this backup is suspended or not

If the first backup has to be immediately start after creation or not

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

The cluster to backup

Indicates which ownerReference should be put inside the created backup resources.

• none: no owner reference for created backup objects (same behavior as before the field was introduced)
• self: sets the Scheduled backup object as owner of the backup
• cluster: set the cluster as owner of the backup

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.

The backup method to be used, possible options are barmanObjectStoreand volumeSnapshot. Defaults to: barmanObjectStore.

Whether the default type of backup with volume snapshots is online/hot (true, default) or offline/cold (false) Overrides the default setting specified in the cluster field '.spec.backup.volumeSnapshot.online'

Configuration parameters to control the online/hot backup with volume snapshots Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

The latest time the schedule

Information when was the last time that backup was successfully scheduled.

Next time we will run a backup

The name of the secret in the pod's namespace to select from.

The key to select

The name of the secret

The ResourceVersion of the secret

The resource version of the "postgres" user secret

The resource version of the "streaming_replica" user secret

The resource version of the "app" user secret

The resource versions of the managed roles secrets

Unused. Retained for compatibility with old versions.

The resource version of the PostgreSQL client-side CA secret version

The resource version of the PostgreSQL server-side CA secret version

The resource version of the PostgreSQL server-side secret version

The resource version of the Barman Endpoint CA if provided

The resource versions of the external cluster secrets

A map with the versions of all the secrets used to pass metrics. Map keys are the secret names, map values are the versions

Metadata are the metadata to be used for the generated service account

StorageClass to use for PVCs. Applied after evaluating the PVC template, if available. If not specified, the generated PVCs will use the default storage class

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.

Resize existent PVCs, defaults to true

Template to be used to generate the Persistent Volume Claim

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

This flag enables the constraints for sync replicas

True if we want to have TDE enabled

Reference to the secret that contains the encryption key

WrapCommand is the encrypt command provided by the user

UnwrapCommand is the decryption command provided by the user

PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt

The name of the tablespace

The storage configuration for the tablespace

Owner is the PostgreSQL user owning the tablespace

When set to true, the tablespace will be added as a temp_tablespacesentry in PostgreSQL, and will be available to automatically house temp database objects, or other temporary files. Please refer to PostgreSQL documentation for more information on the temp_tablespaces GUC.

Name is the name of the tablespace

Owner is the PostgreSQL user owning the tablespace

State is the latest reconciliation state

Error is the reconciliation error, if any

Instances contains the pod topology of the instances

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.

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors in synchronous replica election in case of failures

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

ClassName specifies the Snapshot Class to be used for PG_DATA PersistentVolumeClaim. It is the default class for the other types if no specific class is present

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. defaults to the PGDATA Snapshot Class, if set

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

Whether the default type of backup with volume snapshots is online/hot (true, default) or offline/cold (false)

Configuration parameters to control the online/hot backup with volume snapshots

Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), gzip, bzip2 or snappy.

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

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.