diff --git a/product_docs/docs/postgres_for_kubernetes/1/backup.mdx b/product_docs/docs/postgres_for_kubernetes/1/backup.mdx index e2841a02e15..d9e9914fb09 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/backup.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/backup.mdx @@ -241,6 +241,13 @@ The schedule `"0 0 0 * * *"` triggers a backup every day at midnight (00:00:00). In Kubernetes CronJobs, the equivalent expression would be `0 0 * * *`, since seconds are not supported. +!!!warning + +The `spec.cluster` field is immutable after creation. To schedule backups +for a different `Cluster`, create a new `ScheduledBackup` resource instead +of updating an existing one. +!!! + ### Backup Frequency and RTO !!!tip Hint diff --git a/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx b/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx index dd7335e2224..8112f82c19c 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx @@ -388,6 +388,17 @@ cluster. An error in any of those queries will interrupt the bootstrap phase, leaving the cluster incomplete and requiring manual intervention. !!! +!!!note + +These queries run with the standard `"$user", public` `search_path`, even +though operator-issued connections otherwise pin a fixed `search_path` for +security reasons. +See [Schema resolution and `search_path` hardening](security.md#schema-resolution-and-search_path-hardening) +for details. +Schema-qualify object references if you need them to be independent of the +`search_path`. +!!! + !!!info Important Ensure the existence of entries inside the ConfigMaps or Secrets specified in `postInitSQLRefs`, `postInitTemplateSQLRefs`, and @@ -647,7 +658,7 @@ file on the source PostgreSQL instance: host replication streaming_replica all md5 ``` -The following manifest creates a new PostgreSQL 18.3 cluster, +The following manifest creates a new PostgreSQL 18.4 cluster, called `target-db`, using the `pg_basebackup` bootstrap method to clone an external PostgreSQL cluster defined as `source-db` (in the `externalClusters` array). As you can see, the `source-db` @@ -662,7 +673,7 @@ metadata: name: target-db spec: instances: 3 - imageName: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 + imageName: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 bootstrap: pg_basebackup: @@ -682,7 +693,7 @@ spec: ``` All the requirements must be met for the clone operation to work, including -the same PostgreSQL version (in our case 18.3). +the same PostgreSQL version (in our case 18.4). #### TLS certificate authentication @@ -698,7 +709,7 @@ This example can be easily adapted to cover an instance that resides outside the Kubernetes cluster. !!! -The manifest defines a new PostgreSQL 18.3 cluster called `cluster-clone-tls`, +The manifest defines a new PostgreSQL 18.4 cluster called `cluster-clone-tls`, which is bootstrapped using the `pg_basebackup` method from the `cluster-example` external cluster. The host is identified by the read/write service in the same cluster, while the `streaming_replica` user is authenticated @@ -713,7 +724,7 @@ metadata: name: cluster-clone-tls spec: instances: 3 - imageName: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 + imageName: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 bootstrap: pg_basebackup: diff --git a/product_docs/docs/postgres_for_kubernetes/1/certificates.mdx b/product_docs/docs/postgres_for_kubernetes/1/certificates.mdx index eaa65afcfc0..aaad7b4ec9a 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/certificates.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/certificates.mdx @@ -39,6 +39,15 @@ names in user-provided certificates for the `-rw` service used for communication within the cluster. !!! +!!!note + +Beyond the CA-managed certificates listed above, the operator also uses a +self-signed client certificate, generated in memory, to authenticate to the +instance manager's status port. This certificate is not signed by the client +CA: the instance manager trusts it by pinning its public-key fingerprint. See +[Operator-to-instance authentication](security.md#operator-to-instance-authentication). +!!! + ## Operator-Managed Mode By default, the operator automatically generates a single Certificate Authority diff --git a/product_docs/docs/postgres_for_kubernetes/1/cnpg_i.mdx b/product_docs/docs/postgres_for_kubernetes/1/cnpg_i.mdx index f90cca93508..b4b717f4586 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/cnpg_i.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/cnpg_i.mdx @@ -92,6 +92,12 @@ TCP gRPC endpoint behind a Service, with **mTLS** for secure communication. Standalone plugins are discovered dynamically by watching for Services with the required labels and annotations — no operator restart is needed. +When a standalone plugin's pods are rolled (for example, after upgrading its +image), the operator detects the change through the EndpointSlices backing the +plugin Service and reconciles every cluster using that plugin, so they start +interacting with the new pods promptly instead of waiting for the periodic +resync. + Example Deployment: ```yaml diff --git a/product_docs/docs/postgres_for_kubernetes/1/connection_pooling.mdx b/product_docs/docs/postgres_for_kubernetes/1/connection_pooling.mdx index 6c9cdd3d46f..5f34f7a8db9 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/connection_pooling.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/connection_pooling.mdx @@ -57,6 +57,13 @@ spec: The pooler name can't be the same as any cluster name in the same namespace. !!! +!!!warning + +The `spec.cluster` field is immutable after creation. To point a pooler at +a different `Cluster`, create a new `Pooler` resource instead of updating +an existing one. +!!! + This example creates a `Pooler` resource called `pooler-example-rw` that's strictly associated with the Postgres `Cluster` resource called `cluster-example`. It points to the primary, identified by the read/write @@ -190,15 +197,27 @@ GRANT CONNECT ON DATABASE postgres TO cnp_pooler_pgbouncer; Create the lookup function for password verification. This function is created in the `postgres` database with `SECURITY DEFINER` privileges and is used by -PgBouncer’s `auth_query` option: +PgBouncer’s `auth_query` option. Because it runs as the function owner, its +`search_path` is pinned to `pg_catalog, pg_temp` so that the function body +cannot resolve operators or objects through a caller- or +tenant-controlled `search_path`: ```sql CREATE OR REPLACE FUNCTION public.user_search(uname TEXT) RETURNS TABLE (usename name, passwd text) - LANGUAGE sql SECURITY DEFINER AS + LANGUAGE sql SECURITY DEFINER + SET search_path = pg_catalog, pg_temp AS 'SELECT usename, passwd FROM pg_catalog.pg_shadow WHERE usename=$1;'; ``` +!!!note + +Clusters created with an earlier version of {{name.ln}} carry a +`user_search` function without the pinned `search_path`. The operator +recreates the function with the `SET search_path` clause automatically +during reconciliation when the cluster is upgraded. +!!! + Restrict and grant permissions on the lookup function: ```sql @@ -280,10 +299,89 @@ spec: topologyKey: "kubernetes.io/hostname" ``` -#### Custom image and resource limits +#### Resource limits + +You can define resource requests and limits by adding a container named +`pgbouncer` to the `template` section: + +```yaml +# ... + template: + metadata: + # ... + spec: + containers: + # This name MUST be "pgbouncer" + - name: pgbouncer + resources: + requests: + cpu: "0.1" + memory: 100Mi + limits: + cpu: "0.5" + memory: 500Mi +``` + +## PgBouncer image + +By default, {{name.ln}} deploys the +[latest stable PgBouncer image](https://docker.enterprisedb.com/k8s/pgbouncer) +the operator was built against. You can override that default in three ways. +When more than one is set, the sources are evaluated top-down — the first +match in the list below is used; if none match, the operator's built-in +default applies: + +1. An explicit image set on the `pgbouncer` container inside + `spec.template.spec.containers` (escape hatch — see + [Pod-template override](#pod-template-override) below). +2. `spec.pgbouncer.image` — an image reference set directly on the `Pooler`. +3. `spec.pgbouncer.imageCatalogRef` — a reference to an entry in an + `ImageCatalog` or `ClusterImageCatalog`. + +`spec.pgbouncer.image` and `spec.pgbouncer.imageCatalogRef` are mutually +exclusive — set at most one. + +!!!warning Policy gating + +If you enforce admission policies that restrict which PgBouncer images +may run, those policies **must gate all three** image sources: +`spec.pgbouncer.image`, `spec.pgbouncer.imageCatalogRef`, and the +`image` field on a `pgbouncer` container inside +`spec.template.spec.containers`. A policy that covers only the first +two leaves the pod-template override as an unguarded escape hatch. +The same consideration applies to `Cluster.spec.imageName` and +`Cluster.spec.imageCatalogRef`. +!!! + +### Setting an explicit image + +Use `spec.pgbouncer.image` to pin a specific PgBouncer version or pull from +a private registry: + +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Pooler +metadata: + name: pooler-example-rw +spec: + cluster: + name: cluster-example + instances: 3 + type: rw + pgbouncer: + poolMode: session + image: docker.enterprisedb.com/k8s/pgbouncer:1.25.1-ubi9 +``` + +### Using an image catalog -You can specify a custom image and define resource requests/limits. Note that -the container name is explicitly set to `pgbouncer`. +The `Pooler` resource can manage the PgBouncer container image centrally via +an `ImageCatalog` or `ClusterImageCatalog`, following the same pattern as +`Cluster` resources (see [Image Catalog](image_catalog.md)). The catalog +entry is selected by the `key` defined in the catalog's `componentImages` +list. + +Reference a catalog entry with `spec.pgbouncer.imageCatalogRef`: ```yaml apiVersion: postgresql.k8s.enterprisedb.io/v1 @@ -295,29 +393,68 @@ spec: name: cluster-example instances: 3 type: rw + pgbouncer: + poolMode: session + imageCatalogRef: + apiGroup: postgresql.k8s.enterprisedb.io + kind: ImageCatalog + name: my-catalog + key: pgbouncer +``` + +To use a cluster-wide catalog instead, set `kind: ClusterImageCatalog` and +point `name` at the corresponding resource — the rest of the spec is +identical. + +When a catalog entry is updated, the operator automatically reconciles all +poolers referencing it and rolls out the new image without any change to the +`Pooler` spec. +### Pod-template override + +The pod template can also carry an `image` on the `pgbouncer` container, in +which case it overrides every other source (including `spec.pgbouncer.image` +and `spec.pgbouncer.imageCatalogRef`). Treat this as an **escape hatch** — +use it only when you need to customize other container-level settings +(resources, environment, security context) and happen to want to pin the +image in the same place. For routine image changes, prefer +`spec.pgbouncer.image` or an image catalog: those fields are validated, +mutually exclusive, and visible to admission policies that gate the +PgBouncer image (see [Pod templates](#pod-templates) for the broader +template mechanics): + +```yaml +# ... template: - metadata: - labels: - app: pooler spec: containers: - # This name MUST be "pgbouncer" - name: pgbouncer image: my-pgbouncer:latest - resources: - requests: - cpu: "0.1" - memory: 100Mi - limits: - cpu: "0.5" - memory: 500Mi ``` +### Monitoring the resolved image + +The operator stores the resolved image in `status.image` and reflects the +outcome in `status.phase`, one of `active`, `paused`, `inactive`, or +`failed`. On `failed`, `status.phaseReason` describes the cause (for +example, if the catalog or key does not exist). You can inspect the +current state with: + +```shell +kubectl get pooler pooler-example-rw -o jsonpath='{.status.image}' +``` + +!!!note API reference + +For details, see [`PgBouncerSpec`](pg4k.v1.md#pgbouncerspec) +in the API reference. +!!! + ## Service Template -Sometimes, your pooler will require some different labels, annotations, or even change -the type of the service, you can achieve that by using the `serviceTemplate` field: +Sometimes, your pooler will require some different labels, annotations, or +even a different Service type. You can achieve that by using the +`serviceTemplate` field: ```yaml apiVersion: postgresql.k8s.enterprisedb.io/v1 @@ -668,6 +805,42 @@ spec: - port: metrics ``` +### TLS for the Metrics Endpoint + +Set `.spec.monitoring.tls.enabled: true` to serve the metrics endpoint over +HTTPS. By default, the cluster's server certificate is being used. +The certificate is reloaded on every TLS handshake, so rotations are +picked up without restarting the pod. + +```yaml +spec: + monitoring: + tls: + enabled: true +``` + +When `.spec.pgbouncer.clientTLSSecret` is set, the metrics server presents +that certificate instead. + +```yaml +spec: + pgbouncer: + clientTLSSecret: + name: + monitoring: + tls: + enabled: true +``` + +The generated `PodMonitor` scrapes with `insecureSkipVerify=true` because +Prometheus scrapes pods by IP and the certificate's SANs do not generally +cover the pod IP. + +If you need strict verification, set `.spec.monitoring.enablePodMonitor: false` +and manage the `PodMonitor` yourself: the operator-generated one is hardcoded +to `insecureSkipVerify=true` and overwrites its spec on every reconcile, so a +manual patch on the generated `PodMonitor` would not survive. + ### Deprecation of Automatic `PodMonitor` Creation !!!warning Feature Deprecation Notice @@ -704,7 +877,7 @@ following example: ## Pausing connections The `Pooler` specification allows you to take advantage of PgBouncer's `PAUSE` -and `RESUME` commands, using only declarative configuration. You can ado this +and `RESUME` commands, using only declarative configuration. You can do this using the `paused` option, which by default is set to `false`. When set to `true`, the operator internally invokes the `PAUSE` command in PgBouncer, which: diff --git a/product_docs/docs/postgres_for_kubernetes/1/database_import.mdx b/product_docs/docs/postgres_for_kubernetes/1/database_import.mdx index 9c8c91b0644..ff8fa24e849 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/database_import.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/database_import.mdx @@ -22,8 +22,8 @@ As a result, the instructions in this section are suitable for both: - importing one or more databases from an existing PostgreSQL instance, even outside Kubernetes - importing the database from any PostgreSQL version to one that is either the - same or newer, enabling *major upgrades* of PostgreSQL (e.g. from version 13.x - to version 17.x) + same or newer, enabling *major upgrades* of PostgreSQL (e.g. from version 14.x + to version 18.x) !!!warning When performing major upgrades of PostgreSQL you are responsible for making diff --git a/product_docs/docs/postgres_for_kubernetes/1/declarative_database_management.mdx b/product_docs/docs/postgres_for_kubernetes/1/declarative_database_management.mdx index eef8fc3f085..c9dc0e502f5 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/declarative_database_management.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/declarative_database_management.mdx @@ -69,6 +69,13 @@ The `Database` object must reference a specific `Cluster`, determining where the database will be created. It is managed by the cluster's primary instance, ensuring the database is created or updated as needed. +!!!warning + +The `spec.cluster` field is immutable after creation. To target a +different `Cluster`, create a new `Database` resource instead of updating +an existing one. +!!! + !!!info The distinction between `metadata.name` and `spec.name` allows multiple `Database` resources to reference databases with the same name across different @@ -148,6 +155,11 @@ spec: Deleting this `Database` object will automatically remove the `two` database from the `cluster-example` cluster. +On a replica cluster the database is read-only, so deleting a `Database` object +releases its finalizer and removes the Kubernetes object without dropping the +PostgreSQL database, even with `databaseReclaimPolicy: delete`. Dropping the +database is left to the primary cluster, which owns it. + ### Declaratively Setting `ensure: absent` To remove a database, set the `ensure` field to `absent` like in the following diff --git a/product_docs/docs/postgres_for_kubernetes/1/declarative_hibernation.mdx b/product_docs/docs/postgres_for_kubernetes/1/declarative_hibernation.mdx index 49e9ce75f4c..bd8d1e0a0a4 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/declarative_hibernation.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/declarative_hibernation.mdx @@ -55,7 +55,7 @@ $ kubectl cnp status Cluster Summary Name: cluster-example Namespace: default -PostgreSQL Image: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 +PostgreSQL Image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 Primary instance: cluster-example-2 Status: Cluster in healthy state Instances: 3 diff --git a/product_docs/docs/postgres_for_kubernetes/1/declarative_role_management.mdx b/product_docs/docs/postgres_for_kubernetes/1/declarative_role_management.mdx index f4a04abeb36..70ad12a0657 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/declarative_role_management.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/declarative_role_management.mdx @@ -5,6 +5,8 @@ originalFilePath: 'src/declarative_role_management.md' +!!!info + From its inception, {{name.ln}} has managed the creation of specific roles required in PostgreSQL instances: @@ -13,13 +15,335 @@ required in PostgreSQL instances: - The application user, set as the low-privilege owner of the application database This process is described in the ["Bootstrap"](bootstrap.md) section. +!!! + +{{name.ln}} provides full lifecycle management for PostgreSQL database roles. +You can define roles either: + +1. as [standalone `DatabaseRole` resources](#the-databaserole-resource) (recommended), or +2. via [the `managed` stanza within the `Cluster` spec](#inline-managed-roles). + +## Coexistence and precedence + +The two methods are not mutually exclusive: you can manage different roles with +each one at the same time, which is what makes a gradual migration from the +inline stanza to `DatabaseRole` resources possible. They only need a rule for +the case where the same role name is defined in both places. + +In that case, **the Cluster specification (`managed.roles`) always takes +precedence**: the `DatabaseRole` is not reconciled and reports the conflict in +its status (see [Status of `DatabaseRole` resources](#status-of-databaserole-resources)). + +!!!important + +Declarative role management ignores roles that exist in the database but are +not included in either the Cluster spec or a `DatabaseRole`. The lifecycle of +those roles continues to be managed within PostgreSQL, allowing you to adopt +this feature at your convenience. +!!! + +* * * + +## General role configuration notes + +Regardless of the management method used, the role specification adheres to the +[PostgreSQL structure and naming conventions](https://www.postgresql.org/docs/current/sql-createrole.html). + +!!!tip + +Please refer to the [API reference](pg4k.v1.md#roleconfiguration) +for the full list of attributes. +!!! + +A few points are worth noting: + +1. The `ensure` attribute is **not** part of PostgreSQL. It enables + declarative role management to create (`present`, the default) or remove + (`absent`) a role, and is available **only** in the inline + [`managed.roles`](#inline-managed-roles) stanza. A `DatabaseRole` does not + support `ensure`; it expresses role removal through its + [reclaim policy](#role-reclaim-policy) instead. +2. The `inherit` attribute is true by default, following PostgreSQL + conventions. +3. The `connectionLimit` attribute defaults to -1, in line with PostgreSQL + conventions. +4. Role membership with `inRoles` defaults to no memberships. + +* * * + +## The `DatabaseRole` resource + +The `DatabaseRole` custom resource provides a dedicated, Kubernetes-native way to +manage PostgreSQL database roles. + +This is the recommended approach for modern environments and +GitOps workflows, as it decouples role lifecycle from the cluster +infrastructure. + +!!!note + +A `DatabaseRole` is applied when its specification or its password Secret +changes. Changes made directly in the database, such as a manual +`ALTER ROLE`, are not detected or reverted until the next time the resource +is applied. Inline managed roles, by contrast, are periodically compared +with the database catalog and brought back to their specification. +!!! + +See [Security](security.md#rbac-on-custom-resources) for the RBAC +implications of granting access to `DatabaseRole` resources. + +A `DatabaseRole` is namespace-scoped: the resource, the `Cluster` it references +through `spec.cluster`, and the `passwordSecret` it consumes must all live in +the same namespace. -With the `managed` stanza in the cluster spec, {{name.ln}} now provides full -lifecycle management for roles specified in `.spec.managed.roles`. +### Example manifest +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: DatabaseRole +metadata: + name: role-dante +spec: + cluster: + name: cluster-example + name: dante + comment: "Dante Alighieri" + login: true + superuser: false + createdb: true + databaseRoleReclaimPolicy: delete + inRoles: + - pg_monitor + passwordSecret: + name: cluster-example-dante +``` + +An example manifest for a role definition can be found in the file +[`role-examples.yaml`](../samples/role-examples.yaml). + +### Role reclaim policy + +The `databaseRoleReclaimPolicy` field defines the "final act" of the operator when a +`DatabaseRole` Custom Resource is removed from the Kubernetes API. +This mirrors the behavior of Kubernetes Persistent Volumes. + +- **`retain` (default):** The role is left in the database. This is the safest + setting for production, ensuring that even if a manifest is accidentally + deleted, the database user (and any objects they own) remains untouched. +- **`delete`:** The operator attempts to execute a `DROP ROLE` in PostgreSQL + before the Kubernetes object is finalized. This is ideal for ephemeral or + automated environments. + +!!!note + +If a role owns objects (tables, schemas, etc.), `DROP ROLE` fails and the +`DatabaseRole` stays in `Terminating`, retried periodically until those objects +are reassigned or dropped. The operator never drops owned objects on your +behalf: reassign or drop them in PostgreSQL, or switch to `retain`, to let the +deletion complete. +!!! + +### Removing a role + +How you remove a role depends on how it was created: + +- **Created through a `DatabaseRole`:** delete the resource. Whether the role is + also dropped from PostgreSQL is governed by its + [reclaim policy](#role-reclaim-policy). +- **Pre-existing, or managed elsewhere:** a `DatabaseRole` is not the tool to drop + it. Declare it `absent` through the inline [`managed.roles`](#inline-managed-roles) + stanza, or run `DROP ROLE` directly. + +!!!warning + +Creating a `DatabaseRole` for a role that already exists **adopts** it: the +operator alters the existing role so that **every** attribute matches the +manifest, including the attributes you omit, which are forced back to their +defaults. In particular, memberships not listed in `inRoles` are revoked, an +omitted `connectionLimit` is reset to `-1` (unlimited), and an omitted +`validUntil` becomes `infinity` if the role had an expiration date. Review +the current attributes and memberships of a role before adopting it, and do +not point a `DatabaseRole` at a role you only want to drop, since it will be +modified before it can be removed. +!!! + +### Status of `DatabaseRole` resources + +The `DatabaseRole` resource includes a dedicated `status` section for per-role +observability: + +```yaml +status: + applied: true + observedGeneration: 3 + conditions: + - lastTransitionTime: "2026-04-04T15:06:23Z" + message: "2051" + reason: ChangeDetected + status: "True" + type: PasswordSecretChange +``` + +The `PasswordSecretChange` condition is maintained by the operator as an +internal signal for the instance manager: its message carries the +`resourceVersion` of the password Secret the operator last observed, and a +change in that value triggers the re-application of the password. The +condition appears once a password Secret is in use and is removed when +`passwordSecret` is removed from the specification. + +If a `DatabaseRole` targets a name already managed in the Cluster spec +(see [Coexistence and precedence](#coexistence-and-precedence)), the `applied` +field will be `false` with the message: + +``` +database role is already managed by the CNP cluster +``` + +On a [replica cluster](replica_cluster.md) the role is owned by the primary +cluster, not reconciled locally. In that case the instance manager reports the +role as *unknown* rather than failed: the `applied` field is left unset (`nil`) +with an explanatory message. The role is reconciled normally once the cluster +is promoted to primary. + +### Client Certificate Generation + +The `DatabaseRole` resource supports opt-in generation of TLS client +certificates, signed by the cluster's client CA and stored in a Kubernetes +Secret. This enables [PostgreSQL `cert` authentication](https://www.postgresql.org/docs/current/auth-cert.html) +as an alternative to passwords: no passwords to rotate manually, and private +keys are stored as Kubernetes Secrets and never transmitted outside the cluster. + +To enable it, add a `clientCertificate` block to the spec: + +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: DatabaseRole +metadata: + name: role-dante +spec: + cluster: + name: cluster-example + name: dante + login: true + clientCertificate: + enabled: true + databaseRoleReclaimPolicy: retain +``` + +`clientCertificate.enabled` defaults to `true` when the block is present, so +`clientCertificate: {}` is equivalent to enabling it. Set `enabled: false` to +turn issuance off while keeping the block in place. + +!!!important + +`login: true` is required when `clientCertificate` issuance is enabled. The +operator enforces this via validation and will reject the resource otherwise. +!!! + +#### Generated Secret + +The operator creates a Secret named `-client-cert` in the +same namespace. It contains two keys: + +| Key | Contents | +| --------- | ----------------------------------------------------------------- | +| `tls.crt` | PEM-encoded client certificate, signed by the cluster's client CA | +| `tls.key` | PEM-encoded private key | + +The expiration time of the certificate is visible in +`status.clientCertificate.expiration`: + +```yaml +status: + clientCertificate: + expiration: "2026-07-01T12:00:00Z" +``` + +#### Configuring `pg_hba.conf` + +The operator generates the certificate but does **not** modify `pg_hba.conf` +automatically. You must add a `hostssl` rule with the `cert` method to the +cluster for the role to be able to authenticate: + +```yaml +spec: + postgresql: + pg_hba: + - hostssl all dante all cert +``` + +A working connection string using the generated Secret would look like: + +``` +psql "host=-rw..svc port=5432 dbname= user=dante \ + sslcert=/path/to/tls.crt sslkey=/path/to/tls.key \ + sslrootcert=/path/to/ca.crt sslmode=verify-full" +``` + +#### Renewal + +Client certificates inherit the operator's global certificate settings: they +are issued with a **90-day** lifetime by default and renewed automatically once +they fall within **7 days** of expiry. Both values are operator-wide and +configurable via the `CERTIFICATE_DURATION` and `EXPIRING_CHECK_THRESHOLD` +operator settings; they are not configurable per `DatabaseRole`. + +Renewal is driven by the reconcile loop: the operator checks whether the +certificate is approaching expiry and re-signs it if needed. Reconciles are +scheduled at least once per hour when `clientCertificate` issuance is enabled, +so renewal happens well before expiry even without a triggering event. The +current expiration is always reflected in `status.clientCertificate.expiration`. + +#### Deletion and opt-out + +| Scenario | Result | +| ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------- | +| `clientCertificate.enabled` set to `false`, or the `clientCertificate` block removed | The cert Secret is deleted; `status.clientCertificate` is cleared | +| `DatabaseRole` deleted | The cert Secret is garbage-collected via owner reference, regardless of `databaseRoleReclaimPolicy` | + +!!!note + +`databaseRoleReclaimPolicy: retain` retains the PostgreSQL role, not the generated +Secret. The Secret is only meaningful while the operator is managing the role, +so it is always cleaned up on deletion. +!!! + +#### Bring-your-own-CA limitation + +If the cluster's client CA Secret does not contain a private key (i.e. you +supplied your own CA via `spec.certificates.clientCASecret`), the operator +cannot sign new certificates. It will record the reason in +`status.clientCertificate.message` and stop retrying: + +```yaml +status: + clientCertificate: + message: 'client CA secret "my-ca" has no private key; bring-your-own-CA + clusters require manual certificate management' +``` + +In this case, you must issue and renew client certificates manually. + +!!!note + +CNP does not manage Certificate Revocation Lists (CRLs). If a certificate must +be invalidated before it expires, rotate the cluster's client CA: on the next +reconcile the operator detects that the existing certificates are no longer +signed by the current CA and re-issues all managed client certificates. +Alternatively, delete the certificate's Secret to have the operator issue a +fresh one signed by the current CA. +!!! + +* * * + +## Inline managed roles + +With the `managed` stanza in the cluster spec, {{name.ln}} provides +management for roles specified in `.spec.managed.roles`. This feature enables declarative management of existing roles, as well as the -creation of new roles if they are not already present in the database. Role -creation will occur *after* the database bootstrapping is complete. +creation of new roles if they are not already present. + +### Example manifest An example manifest for a cluster with declarative role management can be found in the file [`cluster-example-with-roles.yaml`](../samples/cluster-example-with-roles.yaml). @@ -42,48 +366,93 @@ spec: - pg_signal_backend ``` -The role specification in `.spec.managed.roles` adheres to the -[PostgreSQL structure and naming conventions](https://www.postgresql.org/docs/current/sql-createrole.html). -Please refer to the [API reference](pg4k.v1.md#roleconfiguration) for -the full list of attributes you can define for each role. +### Status of inline managed roles -A few points are worth noting: +When using the inline method, the `Cluster` status includes a comprehensive +summary: -1. The `ensure` attribute is **not** part of PostgreSQL. It enables declarative - role management to create and remove roles. The two possible values are - `present` (the default) and `absent`. -2. The `inherit` attribute is true by default, following PostgreSQL conventions. -3. The `connectionLimit` attribute defaults to -1, in line with PostgreSQL conventions. -4. Role membership with `inRoles` defaults to no memberships. +```yaml +status: + managedRolesStatus: + byStatus: + reconciled: + - dante + reserved: + - postgres + - streaming_replica + cannotReconcile: + petrarca: + - 'could not perform UPDATE_MEMBERSHIPS on role petrarca: role "poets" does not exist' +``` -Declarative role management ensures that PostgreSQL instances align with the -spec. If a user modifies role attributes directly in the database, the -{{name.ln}} operator will revert those changes during the next reconciliation -cycle. +Note the special sub-section `cannotReconcile` for operations the database (and +{{name.ln}}) cannot honor, and which require human intervention. -## Password management +This section covers roles reserved for operator use and those that are **not** +under declarative management, providing a comprehensive view of the roles in +the database instances. + +The [kubectl plugin](kubectl-plugin.md) also shows the status of managed roles +in its `status` sub-command: + +```txt +Managed roles status +Status Roles +------ ----- +pending-reconciliation petrarca +reconciled app,dante +reserved postgres,streaming_replica + +Irreconcilable roles +Role Errors +---- ------ +petrarca could not perform UPDATE_MEMBERSHIPS on role petrarca: role "poets" does not exist +``` + +* * * + +## Migrating from inline managed roles to a `DatabaseRole` + +You can move a role from the inline `managed.roles` stanza to a standalone +`DatabaseRole` without disruption: + +1. Create the `DatabaseRole` with the desired specification. Both methods + share the same [`RoleConfiguration`](pg4k.v1.md#roleconfiguration) + structure, so the stanza can be copied across as-is. +2. Remove the matching entry from `.spec.managed.roles` in the `Cluster` + manifest. +3. The operator detects the change and hands management over to the + `DatabaseRole`. -The declarative role management feature includes reconciling of role passwords. -Passwords are managed in fundamentally different ways in the Kubernetes world -and in PostgreSQL, and as a result there are a few things to note. +Because the Cluster spec takes precedence while both exist (see +[Coexistence and precedence](#coexistence-and-precedence)), the handover +happens only once the inline entry is gone, so there is no window in which the +role is left unmanaged. -Managed role configurations may optionally specify the name of a -**Secret** where the username and password are stored (encoded in Base64 -as is usual in Kubernetes). For example: +When converting a role that the inline stanza removed with `ensure: absent`, +note that a `DatabaseRole` does not support `ensure: absent`. Express removal +through the [reclaim policy](#role-reclaim-policy) instead: delete the resource +with `databaseRoleReclaimPolicy: delete` to drop the role, or keep the default +`retain` to leave it in place. See [Removing a role](#removing-a-role) for the +full behavior. + +* * * + +## Password management + +The declarative role management feature (both with a `DatabaseRole` and the +inline `managed.roles` stanza) includes reconciling of role passwords. +Managed role configurations may optionally specify the name of a **Secret** +where the username and password are stored: ```yaml - managed: - roles: - - name: dante - ensure: present - [… snipped …] - passwordSecret: - name: cluster-example-dante + passwordSecret: + name: cluster-example-dante ``` -This would assume the existence of a Secret called `cluster-example-dante`, -containing a username and password. The username should match the role we -are setting the password for. For example, : +The Secret must be of type `kubernetes.io/basic-auth`. The username (encoded in +*Base64* as is usual in Kubernetes) should match the role we are setting the +password for. For example: ```yaml apiVersion: v1 @@ -98,32 +467,36 @@ metadata: type: kubernetes.io/basic-auth ``` -If there is no `passwordSecret` specified for a role, the instance manager will -not try to CREATE / ALTER the role with a password. This keeps with PostgreSQL -conventions, where ALTER will not update passwords unless directed to with -`WITH PASSWORD`. +!!!important + +Label the Secret with `k8s.enterprisedb.io/reload: "true"`, as shown above. Password +changes in labeled Secrets are applied immediately, while changes in +unlabeled Secrets are only applied at a subsequent reconciliation, for +example when the operator refreshes its internal cache. +!!! + +If no `passwordSecret` is specified, the instance manager will not try to +`CREATE/ALTER` the role with a password, keeping with PostgreSQL conventions. -If a role was initially created with a password, and we would like to set the -password to NULL in PostgreSQL, this necessitates being explicit on the part of -the user of {{name.ln}}. -To distinguish "no password provided in spec" from "set the password to NULL", -the field `DisablePassword` should be used. +!!!important -Imagine we decided we would like to have no password on the `dante` role in the -database. In such case we would specify the following: +New roles created without `passwordSecret` will have a `NULL` password inside +PostgreSQL. +!!! + +### Disabling passwords + +To explicitly set a password to `NULL` in PostgreSQL (distinguished from simply +omitting a password update), use the `disablePassword` field: ```yaml - managed: - roles: - - name: dante - ensure: present - [… snipped …] - disablePassword: true + disablePassword: true ``` -NOTE: it is considered an error to set both `passwordSecret` and -`disablePassword` on a given role. -This configuration will be rejected by the validation webhook. +!!!note + +It is an error to set both `passwordSecret` and `disablePassword` on a given role. +!!! ### Password expiry, `VALID UNTIL` @@ -154,12 +527,7 @@ never expires, mirroring the behavior of PostgreSQL. Specifically: UNTIL` was not set to `NULL` in the database (this is due to PostgreSQL not allowing `VALID UNTIL NULL` in the `ALTER ROLE` SQL statement) -!!!warning -New roles created without `passwordSecret` will have a `NULL` password -inside PostgreSQL. -!!! - -### Password hashed +### Pre-hashed passwords You can also provide pre-encrypted passwords by specifying the password in MD5/SCRAM-SHA-256 hash format: @@ -177,23 +545,77 @@ stringData: password: SCRAM-SHA-256$:$: ``` +!!!warning + +The example above uses `stringData:`, where Kubernetes encodes the value +for you, which is the safest path for pre-hashed passwords. If you must +use `data:`, encode the bytes exactly with `printf '%s' "$hash" | base64` +(or `echo -n "$hash" | base64`). A trailing newline from a naive +`echo "$hash" | base64` makes the value miss the SCRAM/MD5 shadow-format +check, so the operator falls back to treating it as cleartext and +re-hashes it, and login stops working. +!!! + ### Safety when transmitting cleartext passwords -While role passwords are safely managed in Kubernetes using Secrets, -there is still a risk on the PostgreSQL side. If creating/altering a role with -password, PostgreSQL may print the password as part of the query statement -in some `postgres` logs, as mentioned in the [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-createrole.html): +Role passwords are safely managed in Kubernetes using Secrets, but the +SQL path between the operator and PostgreSQL is also a concern. As noted +in the [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-createrole.html): > The password will be transmitted to the server in cleartext, and it might > also be logged in the client's command history or the server log -{{name.ln}} adds a safety layer by temporarily suppressing both statement -logging (`log_statement`) and error statement logging -(`log_min_error_statement`) for any CREATE or ALTER operation on a role with -password, thus preventing leakage in both success and failure scenarios. +{{name.ln}} protects this path in two complementary ways: + +1. Before emitting `CREATE`/`ALTER ROLE ... PASSWORD '...'`, the operator + SCRAM-SHA-256 encodes any cleartext password operator-side (client-side + from PostgreSQL's point of view). This is the standard PostgreSQL + practice for keeping cleartext out of server logs and extensions like + `pg_stat_statements` or `pgaudit`, and is the same encoding that + `psql \password` and libpq's `PQencryptPasswordConn` perform. The + literal PostgreSQL receives is the SCRAM-SHA-256 verifier stored in + `pg_authid.rolpassword`. Passwords already provided in MD5 or + SCRAM-SHA-256 shadow form are forwarded unchanged. +2. The same `CREATE`/`ALTER ROLE` statements are executed inside a + transaction that temporarily suppresses both statement logging + (`log_statement`) and error statement logging + (`log_min_error_statement`), preventing leakage to the PostgreSQL log + in both success and failure scenarios. + The Status section of the cluster does not print the query statement for any managed role operation. +#### Opting out of operator-side encoding + +If you need PostgreSQL (not the operator) to decide how the password is +hashed (for example, on a cluster running `password_encryption = md5`), +set the annotation `k8s.enterprisedb.io/passwordPassthrough: "enabled"` on the +basic-auth Secret. The operator will then forward the password value +verbatim. + +!!!warning + +The `k8s.enterprisedb.io/passwordPassthrough` annotation must be set on the +**basic-auth Secret** itself, not on the `Cluster` resource. Placing it +on the `Cluster` has no effect, and the operator will continue to apply +SCRAM-SHA-256 encoding to the password before sending it to PostgreSQL. +!!! + +The opt-in is per-Secret and applies to every basic-auth Secret the +operator consumes (managed-role secrets, but also the superuser and +application-user secrets), so a single cluster can mix passthrough +secrets and operator-encoded secrets freely. The statement-logging +suppression layer described above still applies in both modes. + +!!!warning + +With `k8s.enterprisedb.io/passwordPassthrough: "enabled"`, the operator forwards +the Secret's `password` value verbatim. If that value is cleartext (the +common case on a `password_encryption = md5` cluster), extensions such +as `pg_stat_statements` or `pgaudit` will observe it. This is the +expected trade-off for letting PostgreSQL choose the hash format. +!!! + ## Unrealizable role configurations In PostgreSQL, in some cases, commands cannot be honored by the database and @@ -215,63 +637,6 @@ above could be fixed by creating the role `poets` or dropping the database `inferno` respectively, but they might have originated due to human error, and in such case, the "fix" proposed might be the wrong thing to do. -{{name.ln}} will record when such fundamental errors occur, and will display -them in the cluster Status. Which segues into… - -## Status of managed roles - -The Cluster status includes a section for the managed roles' status, as shown -below: - -```yaml -status: - […snipped…] - managedRolesStatus: - byStatus: - not-managed: - - app - pending-reconciliation: - - dante - - petrarca - reconciled: - - ariosto - reserved: - - postgres - - streaming_replica - cannotReconcile: - dante: - - 'could not perform DELETE on role dante: owner of database inferno' - petrarca: - - 'could not perform UPDATE_MEMBERSHIPS on role petrarca: role "poets" does not exist' -``` - -Note the special sub-section `cannotReconcile` for operations the database (and -{{name.ln}}) cannot honor, and which require human intervention. - -This section covers roles reserved for operator use and those that are **not** -under declarative management, providing a comprehensive view of the roles in -the database instances. - -The [kubectl plugin](kubectl-plugin.md) also shows the status of managed roles -in its `status` sub-command: - -```txt -Managed roles status -Status Roles ------- ----- -pending-reconciliation petrarca -reconciled app,dante -reserved postgres,streaming_replica - -Irreconcilable roles -Role Errors ----- ------ -petrarca could not perform UPDATE_MEMBERSHIPS on role petrarca: role "poets" does not exist -``` - -!!!info Important -In terms of backward compatibility, declarative role management is designed -to ignore roles that exist in the database but are not included in the spec. -The lifecycle of these roles will continue to be managed within PostgreSQL, -allowing {{name.ln}} users to adopt this feature at their convenience. -!!! +{{name.ln}} will record when such fundamental errors occur, and will display +them in the cluster Status, as described in +[Status of inline managed roles](#status-of-inline-managed-roles). diff --git a/product_docs/docs/postgres_for_kubernetes/1/failover.mdx b/product_docs/docs/postgres_for_kubernetes/1/failover.mdx index e0e1e4f43e9..ec966611d27 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/failover.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/failover.mdx @@ -51,6 +51,136 @@ and clients are forcibly disconnected, then the server is shut down. without a clean shutdown. !!! +## Safe primary election + +To ensure that at most one instance promotes itself to primary at any +given time, {{name.ln}} backs the election described above with a +Kubernetes `Lease` object, named after the `Cluster` and living in +its namespace. An instance must acquire and hold this lease before +it promotes to primary. On a clean shutdown the former primary +releases the lease, so an eligible replica can take over without +waiting for the lease to expire. + +### What the primary lease protects against + +Consider a replica catching up by reading WAL files from the archive +rather than streaming from the previous primary. PostgreSQL stops +replaying as soon as the archive returns "file not found" for the +next expected segment, treating it as the end of the WAL stream. If +a replica promotes while the previous primary still has WAL it has +not finished archiving, that signal arrives before the true end of +the stream: the replica forks a new timeline at an LSN earlier than +the last writes the previous primary acknowledged, and those writes +are lost. + +The lease holds promotion back until the previous primary releases +it. On a clean shutdown the release happens after PostgreSQL has +flushed and archived its remaining WAL, so the replica that takes +over sees the archive at its definitive end. If the previous primary +cannot release the lease (crash, node failure, or the instance +manager itself unreachable), the lease expires after +`leaseDurationSeconds` elapses and the replica can promote. In that +path the archive may not have caught up, and any writes the previous +primary did not finish archiving are lost. + +### Relationship with the primary isolation check + +The lease does not fence a primary that has lost connectivity to the +Kubernetes API server but is still running; that is the job of the +[primary isolation](instance_manager.md#primary-isolation) check. +The two mechanisms are complementary and both are enabled by default: + +- The lease prevents *premature* promotion: a replica cannot promote + while the former primary still holds the lease. +- The isolation check stops an *isolated* primary from continuing to + accept writes. + +Keep both enabled. Disabling the isolation check leaves the lease +alone responsible for primary safety, and the lease alone cannot +prevent split-brain when the former primary cannot reach the API +server but remains otherwise healthy. + +### Inspecting the primary lease + +The lease shares the cluster's name, so you can inspect it directly. For a +cluster called `cluster-example`: + +```sh +kubectl get lease cluster-example +``` + +The `HOLDER` column reports the pod that currently holds the lease, which is the +current primary: + +```console +NAME HOLDER AGE +cluster-example cluster-example-1 5m +``` + +For the full picture, including the lease duration in effect and the +last renewal time, use: + +```sh +kubectl get lease cluster-example -o yaml +``` + +### Tuning the primary lease + +The lease timings are exposed under `.spec.primaryLease` and default to values +suitable for most clusters. They map directly onto the underlying Kubernetes +leader-election parameters. + +| Field | Default | Description | +| ------------------------------ | ------- | ------------------------------------------------------------------------ | +| `leaseDurationSeconds` | `15` | How long the lease is valid before another instance may acquire it. | +| `renewDeadlineSeconds` | `10` | How long the primary keeps retrying to renew the lease before giving up. | +| `retryPeriodSeconds` | `2` | How frequently a non-holder retries acquiring or renewing the lease. | +| `releasedLeaseDurationSeconds` | `1` | TTL written when the primary releases the lease on a clean shutdown. | + +For example, to make the cluster more tolerant of a slow or briefly unreachable +API server: + +```yaml +spec: + primaryLease: + leaseDurationSeconds: 60 + renewDeadlineSeconds: 40 + retryPeriodSeconds: 15 +``` + +!!!warning + +Tune these values only if you understand the impact on failover timing: longer +intervals make the cluster more tolerant of transient API server unavailability +but slow down legitimate promotions. Two invariants are enforced by the +admission webhook: `leaseDurationSeconds` must be greater than +`renewDeadlineSeconds`, and `renewDeadlineSeconds` must be greater than +`retryPeriodSeconds` multiplied by `1.2`. Both mirror the requirements of the +underlying Kubernetes leader election. +!!! + +!!!note + +`leaseDurationSeconds` and `retryPeriodSeconds` govern two different timings. +After an abrupt primary loss (the previous primary did not release the lease), a +candidate must observe the lease unchanged for a full `leaseDurationSeconds` +before it may take over: this is what holds back a premature promotion while the +former primary may still be alive. After a clean switchover (the previous primary +released the lease), there is no such wait; the candidate simply notices the +released lease on its next poll, so the hand-over latency is bounded by +`retryPeriodSeconds`. Lowering `retryPeriodSeconds` speeds up switchover without +shortening the take-over wait that guards against premature promotion, at the +cost of more frequent lease renewals against the API server. +!!! + +!!!note + +The primary instance captures these timings the first time it acquires the +lease. Changing `.spec.primaryLease` on a running cluster therefore takes effect +only after the affected primary Pod restarts; until then the primary keeps using +the values it started with. +!!! + ## RTO and RPO impact Failover may result in the service being impacted ([RTO](before_you_start.md#postgresql-terminology)) diff --git a/product_docs/docs/postgres_for_kubernetes/1/faq.mdx b/product_docs/docs/postgres_for_kubernetes/1/faq.mdx index ceeb996cf05..cc4aa8b8706 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/faq.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/faq.mdx @@ -172,7 +172,7 @@ by creating the first instance, configuring the replication, cloning a second instance, and the third one. In a declarative approach, the state of a system is defined using -configuration, namely: there's a PostgreSQL 13 cluster with two replicas. +configuration, namely: there's a PostgreSQL 18 cluster with two replicas. This approach highly simplifies change management operations, and when these are stored in source control systems like Git, it enables the Infrastructure as Code capability. And Kubernetes takes it farther than diff --git a/product_docs/docs/postgres_for_kubernetes/1/image_catalog.mdx b/product_docs/docs/postgres_for_kubernetes/1/image_catalog.mdx index b6a47175de0..bd5eccfc3d8 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/image_catalog.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/image_catalog.mdx @@ -32,6 +32,9 @@ Both resources share a common schema: - **Uniqueness**: The `major` field must be unique within a single catalog. - **Extensions**: Support for certified extension container images (available for PostgreSQL 18+ via `extension_control_path`). +- **Component images**: An optional list of named images for non-PostgreSQL + components such as PgBouncer (see + [Component images](#component-images)). !!!warning @@ -43,6 +46,46 @@ must ensure the declared major version matches the actual PostgreSQL images to maintain compatibility. !!! +## Component images + +In addition to PostgreSQL images, a catalog can store images for other +components via the `componentImages` field. Each entry is identified by a string +**key** — a lowercase alphanumeric identifier (hyphens allowed, 1–63 +characters) that must be unique within the catalog. + +Currently, the only consumer of component images is the `Pooler` resource, +which can reference a component image entry to centrally manage the PgBouncer +container image (see +[Using an image catalog](connection_pooling.md#using-an-image-catalog)). + +The following example defines a namespaced `ImageCatalog` with a PgBouncer +component image: + +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: ImageCatalog +metadata: + name: my-catalog + namespace: default +spec: + images: + - major: 18 + image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 + componentImages: + - key: pgbouncer + image: docker.enterprisedb.com/k8s/pgbouncer:1.25.1-ubi9 +``` + +For a cluster-wide catalog, use `kind: ClusterImageCatalog` and drop the +`metadata.namespace` field (the `spec` is otherwise identical). + +!!!info + +A catalog may contain up to 32 component image entries. Keys are lowercase +alphanumeric characters or hyphens, starting and ending with an alphanumeric +character, up to 63 characters long. +!!! + ## Configuration examples ### Defining a catalog @@ -66,7 +109,7 @@ spec: - major: 17 image: docker.enterprisedb.com/k8s/postgresql:17.6-standard-ubi9 - major: 18 - image: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 + image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 ``` The following example defines a cluster-wide `ClusterImageCatalog`: @@ -85,7 +128,7 @@ spec: - major: 17 image: docker.enterprisedb.com/k8s/postgresql:17.6-standard-ubi9 - major: 18 - image: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 + image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 ``` ### Referencing a Catalog in a Cluster @@ -121,7 +164,7 @@ metadata: spec: images: - major: 18 - image: docker.enterprisedb.com/k8s_enterprise/postgresql:18.3-minimal-ubi9 + image: docker.enterprisedb.com/k8s/postgresql:18.4-minimal-ubi9 extensions: - name: foo image: @@ -221,7 +264,7 @@ You can install all the available catalogs by using the `kustomization` file present in the `image-catalogs` directory: ```shell -kubectl apply -k https://github.com/cloudnative-pg/artifacts//image-catalogs?ref=main +kubectl apply -k 'https://github.com/cloudnative-pg/artifacts//image-catalogs?ref=main' ``` You can then view all the catalogs deployed with: diff --git a/product_docs/docs/postgres_for_kubernetes/1/imagevolume_extensions.mdx b/product_docs/docs/postgres_for_kubernetes/1/imagevolume_extensions.mdx index 0eb46d1601e..61f3c64c3ad 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/imagevolume_extensions.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/imagevolume_extensions.mdx @@ -105,7 +105,10 @@ must be unique within the cluster. !!!important The `name` must consist of lowercase alphanumeric characters, underscores (`_`) -or hyphens (`-`) and must start and end with an alphanumeric character. +or hyphens (`-`) and must start and end with an alphanumeric character. It is +limited to 59 characters, leaving room for the prefix {{name.ln}} adds when +deriving the extension's Kubernetes volume name (capped at the RFC 1123 limit of +63 characters). !!! Each entry defines the configuration for a container image and specifies the diff --git a/product_docs/docs/postgres_for_kubernetes/1/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/index.mdx index 532aaf92292..5b494854703 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/index.mdx @@ -4,12 +4,9 @@ description: The {{name.ln}} operator is a fork based on CloudNativePG™ which originalFilePath: src/index.md indexCards: none directoryDefaults: - version: "1.29.1" - displayBanner: | - We're preparing the next release of {{name.ln}}, and a release candidate is available. - For more information, see the v1.30.0-rc1 documentation -#redirects: -# - /postgres_for_kubernetes/preview/:splat + version: "1.30.0" +redirects: + - /postgres_for_kubernetes/preview/:splat navigation: - rel_notes - '!commercial_support.mdx' diff --git a/product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx b/product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx index a040731a56c..1d56554a47c 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx @@ -71,12 +71,12 @@ kubectl create secret -n postgresql-operator-system docker-registry edb-pull-sec Now that the pull-secret has been added to the namespace, the operator can be installed like any other resource in Kubernetes, through a YAML manifest applied via `kubectl`. -You can install the [latest operator manifest](https://get.enterprisedb.io/pg4k/pg4k-1.29.1.yaml) +You can install the [latest operator manifest](https://get.enterprisedb.io/pg4k/pg4k-1.30.0.yaml) for this minor release as follows: ```sh kubectl apply --server-side -f \ - https://get.enterprisedb.io/pg4k/pg4k-1.29.1.yaml + https://get.enterprisedb.io/pg4k/pg4k-1.30.0.yaml ``` You can verify that with: @@ -288,45 +288,175 @@ When versions are not directly upgradable, the old version needs to be removed before installing the new one. This won't affect user data but only the operator itself. -### Upgrading to 1.29.1, 1.28.3, or 1.25.8 +### Upgrading to 1.30.0, 1.29.2, or 1.28.4 -Version 1.29.1, 1.28.3, and 1.25.8 ship the fix for `CVE-2026-44477` / -`GHSA-423p-g724-fr39`. The metrics exporter now authenticates as a -dedicated `cnp_metrics_exporter` role with `pg_monitor` privileges -only, instead of the `postgres` superuser. +!!!info Important -Custom monitoring queries that read user-owned tables, or use -`target_databases: '*'` against databases where `PUBLIC` `CONNECT` -has been revoked, need explicit `GRANT` statements to -`cnp_metrics_exporter`. See ["Custom query privileges and -safety"](monitoring.md#custom-query-privileges-and-safety) and ["Manually creating -the metrics exporter -role"](monitoring.md#manually-creating-the-metrics-exporter-role) in -the monitoring documentation. +We strongly recommend that all {{name.ln}} users upgrade to version +1.30.0, or at least to the latest stable version of your current minor release +(e.g., 1.29.2 or 1.28.4). +!!! -### Upgrading to 1.29.0 or 1.28.x +These releases introduce changes worth reviewing before you upgrade. Two are +security changes that apply to **1.30.0, 1.29.2, and 1.28.4**: operator-side +password encoding (`CVE-2026-55765`) and `search_path` hardening +(`CVE-2026-55769`). The other three are new in +**1.30.0** only: the `DatabaseRole` resource for declarative role management, +safe primary election via a per-cluster Lease, and operator-to-instance +authentication on the instance manager's status port (`GHSA-7qwx-x8ff-3px9`). +In addition, if you are upgrading from a release **older than 1.29.1, 1.28.3, or +1.25.8**, the metrics-exporter privilege separation from `CVE-2026-44477` also +applies. +Each is covered in its own subsection below. + +#### Operator-side password encoding (`CVE-2026-55765`) + +Starting from versions 1.30.0, 1.29.2, and 1.28.4, for security reasons +(`CVE-2026-55765` / `GHSA-w3gf-xc94-wvmj`), {{name.ln}} SCRAM-SHA-256 encodes +role passwords **operator-side** +(client-side from PostgreSQL's point of view) before issuing +`CREATE`/`ALTER ROLE` statements. As a result, the literal that reaches +the PostgreSQL parser (and that extensions such as `pg_stat_statements` +or `pgaudit` may observe) is the same hash that ends up in +`pg_authid.rolpassword`, never the cleartext secret. The encoding is +applied to every basic-auth `Secret` the operator consumes: the +`postgres` superuser secret, the application-user secret, and any +managed-role password secret. Passwords already supplied in MD5 or +SCRAM-SHA-256 shadow form are passed through unchanged. + +Since PostgreSQL [14](https://www.postgresql.org/docs/release/14.0/), +`password_encryption` defaults to `scram-sha-256`, so we do not expect +existing installations to be affected by this change. + +If your cluster has explicitly overridden `password_encryption` to a +value other than `scram-sha-256` (for example, `md5`) and you want +PostgreSQL (not the operator) to decide how the password is hashed, +opt out by setting the annotation `k8s.enterprisedb.io/passwordPassthrough: "enabled"` +on each basic-auth `Secret` the operator consumes. The operator will +then forward the password value verbatim, and PostgreSQL will encode it +according to its own `password_encryption` GUC. -!!!info Important +!!!warning -We strongly recommend that all {{name.ln}} users upgrade to version -1.29.0, or at least to the latest stable version of your current minor release -(e.g., 1.28.x). +The `k8s.enterprisedb.io/passwordPassthrough` annotation must be set on the +**basic-auth Secret** itself, not on the `Cluster` resource. Placing it +on the `Cluster` has no effect, and the operator will continue to apply +SCRAM-SHA-256 encoding to the password before sending it to PostgreSQL. !!! -### Upgrading to 1.27 from a previous minor version +!!!warning + +With `k8s.enterprisedb.io/passwordPassthrough: "enabled"` the operator forwards the +Secret's `password` value verbatim. If that value is cleartext, as is +common on `password_encryption = md5` clusters, extensions such as +`pg_stat_statements` or `pgaudit` will observe it. +!!! -Version 1.27 introduces a change in the default behavior of the -[liveness probe](instance_manager.md#liveness-probe): it now enforces the -[shutdown of an isolated primary](instance_manager.md#primary-isolation) -within the `livenessProbeTimeout` (30 seconds). +See ["Opting out of operator-side encoding"](declarative_role_management.md#opting-out-of-operator-side-encoding) +for details. + +#### `search_path` hardening (`CVE-2026-55769`) + +Also starting from versions 1.30.0, 1.29.2, and 1.28.4, for security reasons +(`CVE-2026-55769` / `GHSA-x8c2-3p4r-v9r6`), {{name.ln}} pins the `search_path` +to a fixed `pg_catalog, public, +pg_temp` on every connection it opens to PostgreSQL, so that a +tenant-controlled `ALTER DATABASE`/`ALTER ROLE` setting can no longer +influence how operator-issued queries resolve unqualified object names. +The `SECURITY DEFINER` lookup function used by the PgBouncer integration +is recreated automatically with its own pinned `search_path` during the +first reconciliation after the upgrade. +See [Schema resolution and `search_path` hardening](security.md#schema-resolution-and-search_path-hardening) +for the rationale. + +This change also affects custom monitoring queries, which now run inside +a transaction whose `search_path` is pinned to `pg_catalog, public, +pg_temp`. If any of your custom metrics reference objects that live in +other user-defined schemas through an unqualified name, schema-qualify +them (for example `myschema.mytable`) so they keep resolving after the +upgrade. User-authored bootstrap (`postInit*`) and logical-import +post-import SQL are unaffected: they continue to run with the standard +`"$user", public` resolution. + +#### Declarative role management with the `DatabaseRole` resource + +Starting from version 1.30.0, you can also manage a PostgreSQL role as a +standalone [`DatabaseRole`](declarative_role_management.md) resource instead +of declaring it inline in the Cluster's `.spec.managed.roles` stanza. This is +an opt-in enhancement and requires no action on upgrade: existing inline roles +keep working unchanged, and the inline `managed.roles` method remains fully +supported. + +To move an existing inline role under a `DatabaseRole` without disruption, +create the `DatabaseRole` first and only then remove the matching entry from +`.spec.managed.roles`. While both exist the Cluster spec always takes +precedence, so management is handed over only once the inline entry is gone. +See [Migrating from inline managed roles](declarative_role_management.md#migrating-from-inline-managed-roles-to-a-databaserole) +for the full procedure. + +A `DatabaseRole` does not support `ensure: absent`: where the inline +`managed.roles` stanza drops a role by setting `ensure: absent`, a +`DatabaseRole` instead relies on the `databaseRoleReclaimPolicy` field. Delete +the resource with `databaseRoleReclaimPolicy: delete` to drop the role from +PostgreSQL, or keep the default `retain` to leave the role in place. + +#### Safe primary election + +Starting from version 1.30.0, {{name.ln}} coordinates primary promotion +through a per-cluster Kubernetes `Lease`, ensuring that at most one instance +promotes itself at any given time. The behavior is enabled automatically and +requires no configuration; the lease timings can optionally be tuned via +`.spec.primaryLease` (see ["Safe primary election"](failover.md#safe-primary-election)). -If this behavior is not suitable for your environment, you can disable the -*isolation check* in the liveness probe with the following configuration: +!!!warning -```yaml -spec: - probes: - liveness: - isolationCheck: - enabled: false -``` +This feature requires the operator to manage `Lease` objects in the +`coordination.k8s.io` API group. The bundled operator manifest and the Helm +chart grant the required permissions automatically. If you manage the +operator's RBAC yourself, you must add the `create`, `get`, `list`, `update` +and `watch` verbs on `leases` in the `coordination.k8s.io` API group before +upgrading, otherwise primaries will be unable to promote. +!!! + +#### Operator-to-instance authentication (`GHSA-7qwx-x8ff-3px9`) + +Starting from version 1.30.0, the operator authenticates its calls to the +sensitive endpoints of the instance manager's status port (backup, +`pg_controldata`, partial WAL archive, and instance-manager upgrade) by pinning +an in-memory client certificate. This is enabled automatically and requires no +configuration. Status, health, and probe endpoints remain unauthenticated. +This hardening is not backported; on releases earlier than 1.30.0, continue to +restrict the status port (TCP 8000) with a `NetworkPolicy`, which remains its +security boundary there. See +[Operator-to-instance authentication](security.md#operator-to-instance-authentication) +for details. + +!!!warning + +This protection has a hard requirement: the status port **must** be served over +TLS, which has been the default since v1.24. Instances created by an operator +older than v1.24 serve the status port over plain HTTP; once their instance +manager is upgraded to 1.30.0 the operator can no longer authenticate to them +and every call to the protected endpoints is **permanently** rejected with +`401 Unauthorized`. If you still run such instances, perform a rolling update so +their Pods are recreated with a TLS-enabled status port. Instances created by +v1.24 or later are unaffected. +!!! + +#### Metrics exporter privilege separation (`CVE-2026-44477`) + +This applies only if you are upgrading from a release **older than 1.29.1, +1.28.3, or 1.25.8** (for example 1.29.0, 1.28.2, 1.25.7, or any earlier +version); installations already on 1.29.1, 1.28.3, 1.25.8, or later already +have this change. + +The fix for `CVE-2026-44477` / `GHSA-423p-g724-fr39` makes the metrics exporter +authenticate as a dedicated `cnp_metrics_exporter` role with `pg_monitor` +privileges only, instead of the `postgres` superuser. + +Custom monitoring queries that read user-owned tables, or use +`target_databases: '*'` against databases where `PUBLIC` `CONNECT` has been +revoked, need explicit `GRANT` statements to `cnp_metrics_exporter`. +See ["Custom query privileges and safety"](monitoring.md#custom-query-privileges-and-safety) +and ["Manually creating the metrics exporter role"](monitoring.md#manually-creating-the-metrics-exporter-role) +in the monitoring documentation. diff --git a/product_docs/docs/postgres_for_kubernetes/1/instance_manager.mdx b/product_docs/docs/postgres_for_kubernetes/1/instance_manager.mdx index 99f6dec3c0e..dc40ad1b96e 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/instance_manager.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/instance_manager.mdx @@ -242,6 +242,14 @@ spec: connectionTimeout: "2000" ``` +!!!info + +Primary isolation is distinct from the [safe primary election](failover.md#safe-primary-election) +mechanism. The isolation check *fences* a primary that has lost connectivity to +both the API server and the other instances, while the primary lease coordinates +*which instance is allowed to promote*. The two mechanisms are complementary. +!!! + ## Readiness Probe The readiness probe starts once the startup probe has successfully completed. diff --git a/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx b/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx index d4f8923d5ad..a80192fff6e 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/kubectl-plugin.mdx @@ -36,11 +36,11 @@ them in your systems. #### Debian packages -For example, let's install the 1.29.1 release of the plugin, for an Intel based +For example, let's install the 1.30.0 release of the plugin, for an Intel based 64 bit server. First, we download the right `.deb` file. ```sh -wget https://github.com/EnterpriseDB/kubectl-cnp/releases/download/v1.29.1/kubectl-cnp_1.29.1_linux_x86_64.deb \ +wget https://github.com/EnterpriseDB/kubectl-cnp/releases/download/v1.30.0/kubectl-cnp_1.30.0_linux_x86_64.deb \ --output-document kube-plugin.deb ``` @@ -51,17 +51,17 @@ $ sudo dpkg -i kube-plugin.deb Selecting previously unselected package cnp. (Reading database ... 6688 files and directories currently installed.) Preparing to unpack kube-plugin.deb ... -Unpacking kubectl-cnp (1.29.1) ... -Setting up kubectl-cnp (1.29.1) ... +Unpacking kubectl-cnp (1.30.0) ... +Setting up kubectl-cnp (1.30.0) ... ``` #### RPM packages -As in the example for `.rpm` packages, let's install the 1.29.1 release for an +As in the example for `.rpm` packages, let's install the 1.30.0 release for an Intel 64 bit machine. Note the `--output` flag to provide a file name. ```sh -curl -L https://github.com/EnterpriseDB/kubectl-cnp/releases/download/v1.29.1/kubectl-cnp_1.29.1_linux_x86_64.rpm \ +curl -L https://github.com/EnterpriseDB/kubectl-cnp/releases/download/v1.30.0/kubectl-cnp_1.30.0_linux_x86_64.rpm \ --output kube-plugin.rpm ``` @@ -75,7 +75,7 @@ Dependencies resolved. Package Architecture Version Repository Size ==================================================================================================== Installing: - cnp x86_64 1.29.1-1 @commandline 20 M + cnp x86_64 1.30.0-1 @commandline 20 M Transaction Summary ==================================================================================================== @@ -246,9 +246,9 @@ sandbox-3 0/604DE38 0/604DE38 0/604DE38 0/604DE38 00:00:00 00:00:00 00 Instances status Name Current LSN Replication role Status QoS Manager Version Node ---- ----------- ---------------- ------ --- --------------- ---- -sandbox-1 0/604DE38 Primary OK BestEffort 1.29.1 k8s-eu-worker -sandbox-2 0/604DE38 Standby (async) OK BestEffort 1.29.1 k8s-eu-worker2 -sandbox-3 0/604DE38 Standby (async) OK BestEffort 1.29.1 k8s-eu-worker +sandbox-1 0/604DE38 Primary OK BestEffort 1.30.0 k8s-eu-worker +sandbox-2 0/604DE38 Standby (async) OK BestEffort 1.30.0 k8s-eu-worker2 +sandbox-3 0/604DE38 Standby (async) OK BestEffort 1.30.0 k8s-eu-worker ``` If you require more detailed status information, use the `--verbose` option (or @@ -302,9 +302,9 @@ sandbox-primary primary 1 1 1 Instances status Name Current LSN Replication role Status QoS Manager Version Node ---- ----------- ---------------- ------ --- --------------- ---- -sandbox-1 0/6053720 Primary OK BestEffort 1.29.1 k8s-eu-worker -sandbox-2 0/6053720 Standby (async) OK BestEffort 1.29.1 k8s-eu-worker2 -sandbox-3 0/6053720 Standby (async) OK BestEffort 1.29.1 k8s-eu-worker +sandbox-1 0/6053720 Primary OK BestEffort 1.30.0 k8s-eu-worker +sandbox-2 0/6053720 Standby (async) OK BestEffort 1.30.0 k8s-eu-worker2 +sandbox-3 0/6053720 Standby (async) OK BestEffort 1.30.0 k8s-eu-worker ``` With an additional `-v` (e.g. `kubectl cnp status sandbox -v -v`), you can @@ -532,12 +532,12 @@ and previous logs are available, it will show them both. ```output ====== Begin of Previous Log ===== -2023-03-28T12:56:41.251711811Z {"level":"info","ts":"2023-03-28T12:56:41Z","logger":"setup","msg":"Starting EDB Postgres for Kubernetes Operator","version":"1.29.1","build":{"Version":"1.29.1+dev107","Commit":"cc9bab17","Date":"2023-03-28"}} +2023-03-28T12:56:41.251711811Z {"level":"info","ts":"2023-03-28T12:56:41Z","logger":"setup","msg":"Starting EDB Postgres for Kubernetes Operator","version":"1.30.0","build":{"Version":"1.30.0+dev107","Commit":"cc9bab17","Date":"2023-03-28"}} 2023-03-28T12:56:41.251851909Z {"level":"info","ts":"2023-03-28T12:56:41Z","logger":"setup","msg":"Starting pprof HTTP server","addr":"0.0.0.0:6060"} ====== End of Previous Log ===== -2023-03-28T12:57:09.854306024Z {"level":"info","ts":"2023-03-28T12:57:09Z","logger":"setup","msg":"Starting EDB Postgres for Kubernetes Operator","version":"1.29.1","build":{"Version":"1.29.1+dev107","Commit":"cc9bab17","Date":"2023-03-28"}} +2023-03-28T12:57:09.854306024Z {"level":"info","ts":"2023-03-28T12:57:09Z","logger":"setup","msg":"Starting EDB Postgres for Kubernetes Operator","version":"1.30.0","build":{"Version":"1.30.0+dev107","Commit":"cc9bab17","Date":"2023-03-28"}} 2023-03-28T12:57:09.854363943Z {"level":"info","ts":"2023-03-28T12:57:09Z","logger":"setup","msg":"Starting pprof HTTP server","addr":"0.0.0.0:6060"} ``` diff --git a/product_docs/docs/postgres_for_kubernetes/1/labels_annotations.mdx b/product_docs/docs/postgres_for_kubernetes/1/labels_annotations.mdx index ccf6cb654b8..e89ddf7ba80 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/labels_annotations.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/labels_annotations.mdx @@ -203,6 +203,14 @@ instead `k8s.enterprisedb.io/operatorVersion` : Version of the operator. +`k8s.enterprisedb.io/passwordPassthrough` +: When set to `enabled` on a basic-auth `Secret` consumed by the + operator (superuser, application user, or a managed-role password + secret), the operator forwards the password value verbatim in the + `CREATE`/`ALTER ROLE` statement instead of SCRAM-SHA-256 encoding + it operator-side. PostgreSQL then encodes the value according to its + own `password_encryption` setting. See [Opting out of operator-side encoding](declarative_role_management.md#opting-out-of-operator-side-encoding). + `k8s.enterprisedb.io/pgControldata` : Output of the `pg_controldata` command. This annotation replaces the old, deprecated `k8s.enterprisedb.io/hibernatePgControlData` annotation. @@ -214,10 +222,19 @@ instead : Annotation can be applied on a `Cluster` resource. ``` -When set to JSON-patch formatted patch, the patch will be applied on the instance Pods. +When set to a JSON-patch formatted patch, the patch will be applied to the +instance Pods. The patch can modify any field of the Pod specification, +including security-sensitive fields. The operator validates only that the +patch is syntactically correct and applicable. + +As with all Cluster fields that affect Pod specifications, enforcement of +security constraints is delegated to the Kubernetes admission control chain. +See the +[Trust Model and Security Boundaries](security.md#trust-model-and-security-boundaries) +section for details. **⚠️ WARNING:** This feature may introduce discrepancies between the -operator’s expectations and Kubernetes behavior. Use with caution and only as a +operator's expectations and Kubernetes behavior. Use with caution and only as a last resort. **IMPORTANT**: adding or changing this annotation won't trigger a rolling deployment diff --git a/product_docs/docs/postgres_for_kubernetes/1/logical_replication.mdx b/product_docs/docs/postgres_for_kubernetes/1/logical_replication.mdx index 3b8dbc128a0..fd0fc9c06c1 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/logical_replication.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/logical_replication.mdx @@ -147,6 +147,13 @@ The `Publication` object must reference a specific `Cluster`, determining where the publication will be created. It is managed by the cluster's primary instance, ensuring the publication is created or updated as needed. +!!!warning + +The `spec.cluster` field is immutable after creation. To create a +publication on a different `Cluster`, create a new `Publication` resource +instead of updating an existing one. +!!! + ### Reconciliation and Status After creating a `Publication`, {{name.ln}} manages it on the primary @@ -189,6 +196,11 @@ spec: In this case, deleting the `Publication` object also removes the `publisher` publication from the `app` database of the `freddie` cluster. +On a replica cluster the database is read-only, so deleting a `Publication` +object releases its finalizer and removes the Kubernetes object without dropping +the publication in PostgreSQL, even with `publicationReclaimPolicy: delete`. +Dropping the publication is left to the primary cluster, which owns it. + ## Subscriptions In PostgreSQL's publish-and-subscribe replication model, a @@ -285,6 +297,13 @@ where the subscription will be managed. {{name.ln}} ensures that the subscription is created or updated on the primary instance of the specified cluster. +!!!warning + +The `spec.cluster` field is immutable after creation. To manage the +subscription on a different `Cluster`, create a new `Subscription` +resource instead of updating an existing one. +!!! + ### Reconciliation and Status After creating a `Subscription`, {{name.ln}} manages it on the primary @@ -327,6 +346,11 @@ spec: In this case, deleting the `Subscription` object also removes the `subscriber` subscription from the `app` database of the `king` cluster. +On a replica cluster the database is read-only, so deleting a `Subscription` +object releases its finalizer and removes the Kubernetes object without dropping +the subscription in PostgreSQL, even with `subscriptionReclaimPolicy: delete`. +Dropping the subscription is left to the primary cluster, which owns it. + ### Resilience to Failovers To ensure that your logical replication subscriptions remain operational after @@ -386,6 +410,17 @@ resource: ```yaml apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: DatabaseRole +metadata: + name: freddie-app +spec: + cluster: + name: freddie + name: app + login: true + replication: true +--- +apiVersion: postgresql.k8s.enterprisedb.io/v1 kind: Cluster metadata: name: freddie @@ -403,12 +438,6 @@ spec: - CREATE TABLE n (i SERIAL PRIMARY KEY, m INTEGER) - INSERT INTO n (m) (SELECT generate_series(1, 10000)) - ALTER TABLE n OWNER TO app - - managed: - roles: - - name: app - login: true - replication: true --- apiVersion: postgresql.k8s.enterprisedb.io/v1 kind: Publication diff --git a/product_docs/docs/postgres_for_kubernetes/1/monitoring.mdx b/product_docs/docs/postgres_for_kubernetes/1/monitoring.mdx index 35f5442f0d4..1863ed31e74 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/monitoring.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/monitoring.mdx @@ -263,7 +263,7 @@ cnp_collector_up{cluster="cluster-example"} 1 # HELP cnp_collector_postgres_version Postgres version # TYPE cnp_collector_postgres_version gauge -cnp_collector_postgres_version{cluster="cluster-example",full="18.3"} 18.3 +cnp_collector_postgres_version{cluster="cluster-example",full="18.4"} 18.4 # HELP cnp_collector_last_failed_backup_timestamp The last failed backup as a unix timestamp (Deprecated) # TYPE cnp_collector_last_failed_backup_timestamp gauge @@ -534,6 +534,14 @@ collect per-database metrics across the whole cluster. Schema-qualify catalog references (`pg_catalog.now()`, `pg_catalog.current_database()`) to prevent `search_path` shadowing by user-owned objects. + +Custom monitoring queries run inside a transaction whose +`search_path` is pinned to `pg_catalog, public, pg_temp`, +regardless of any `search_path` configured on the database or the +role. Unqualified references to objects in other user-defined +schemas will therefore fail to resolve: schema-qualify them (e.g. +`myschema.mytable`) so the query does not depend on the +`search_path`. !!! #### Example of a user defined metric @@ -995,7 +1003,7 @@ metadata: spec: containers: - name: curl - image: curlimages/curl:8.17.0 + image: curlimages/curl:8.21.0 command: ['sleep', '3600'] EOF ``` diff --git a/product_docs/docs/postgres_for_kubernetes/1/object_stores.mdx b/product_docs/docs/postgres_for_kubernetes/1/object_stores.mdx index 5ab5b7c71f3..cd86ab30b8a 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/object_stores.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/object_stores.mdx @@ -167,6 +167,27 @@ spec: [...] ``` +!!!note + +Recent changes to the [boto3 implementation](https://github.com/boto/boto3/issues/4392) +of [Amazon S3 Data Integrity Protections](https://docs.aws.amazon.com/sdkref/latest/guide/feature-dataintegrity.html) +may lead to the `x-amz-content-sha256` error. If you encounter this issue, you +can apply the following workaround by setting specific environment variables at +the cluster level through `spec.env`: + +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +[...] +spec: + env: + - name: AWS_REQUEST_CHECKSUM_CALCULATION + value: when_required + - name: AWS_RESPONSE_CHECKSUM_VALIDATION + value: when_required +``` +!!! + ### Using Object Storage with a private CA Suppose you configure an Object Storage provider which uses a certificate diff --git a/product_docs/docs/postgres_for_kubernetes/1/operator_capability_levels.mdx b/product_docs/docs/postgres_for_kubernetes/1/operator_capability_levels.mdx index 5fdbe783be5..87b9bf0e29b 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/operator_capability_levels.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/operator_capability_levels.mdx @@ -43,9 +43,17 @@ We consider information security part of this level. ### Operator deployment via declarative configuration -The operator is installed in a declarative way using a Kubernetes manifest -that defines four major `CustomResourceDefinition` objects: `Cluster`, `Pooler`, -`Backup`, and `ScheduledBackup`. +The operator is installed in a declarative way using a Kubernetes manifest that +defines the core `CustomResourceDefinition` objects required to manage the +PostgreSQL lifecycle. These include: + +- **Configuration & Topology:** `Cluster`, `Pooler`, `ImageCatalog`, and + `ClusterImageCatalog`. +- **Identity & Schema:** `DatabaseRole` and `Database`. +- **Business Continuity:** `Backup`, `ScheduledBackup`, `Publication`, and + `Subscription`. +- **Runtime Orchestration:** `FailoverQuorum` (used by the operator for + consensus during automated failover). ### PostgreSQL cluster deployment via declarative configuration @@ -53,9 +61,13 @@ You define a PostgreSQL cluster (operand) using the `Cluster` custom resource in a fully declarative way. The PostgreSQL version is determined by the operand container image defined in the CR, which is automatically fetched from the requested registry. -When deploying an operand, the operator also creates the following resources: -`Pod`, `Service`, `Secret`, `ConfigMap`, `PersistentVolumeClaim`, -`PodDisruptionBudget`, `ServiceAccount`, `RoleBinding`, and `Role`. + +The operator orchestrates the deployment by creating and managing standard +Kubernetes resources (`Pod`, `Service`, `Secret`, `ConfigMap`, +`PersistentVolumeClaim`, `PodDisruptionBudget`, `ServiceAccount`, +`RoleBinding`, and `Role`), and reconciles user-defined CNP resources such as +`Database` and `DatabaseRole` to ensure the database environment matches the +desired state. You can optionally provide a pre-existing ServiceAccount for both `Cluster` and `Pooler` resources. This shared ServiceAccount support enables seamless @@ -83,6 +95,9 @@ Beyond just the core PostgreSQL engine, image catalogs now allow you to define ensuring that the database and its associated modules are always compatible, version-aligned, and treated as a single cohesive unit across your entire infrastructure. +The same catalog mechanism also governs [PgBouncer](connection_pooling.md) +pooler images, making image catalogs a unified supply-chain primitive across +the entire PostgreSQL stack managed by the operator. ### Labels and annotations @@ -184,8 +199,24 @@ authentication rules in the `postgresql` section of the CR. ### Configuration of Postgres roles, users, and groups {{name.ln}} supports -[management of PostgreSQL roles, users, and groups through declarative configuration](declarative_role_management.md) -using the `.spec.managed.roles` stanza. +[comprehensive management of PostgreSQL roles, users, and groups](declarative_role_management.md) +through two declarative methods: + +- The `DatabaseRole` CRD (Recommended): A standalone resource for granular lifecycle + management. It includes a `databaseRoleReclaimPolicy` (supporting `retain` or + `delete`) to define whether the database role should be dropped when the + Kubernetes resource is removed. + +- The `managed` stanza: For simpler requirements, roles can be defined inline + within the `.spec.managed.roles` section of the `Cluster` resource. + +Both methods provide automated reconciliation of role attributes (e.g., +`login`, `superuser`, `connectionLimit`) and secure, versioned password +management via Kubernetes Secrets. Passwords are SCRAM-SHA-256 encoded +operator-side before they are sent to PostgreSQL, so the cleartext value never +reaches the server log or extensions. A `DatabaseRole` can additionally request +a TLS client certificate that the operator generates and renews automatically, +enabling password-free `cert` authentication. ### Configuration of Postgres extensions @@ -401,6 +432,10 @@ consistency and initiates a job to validate upgrade conditions and execute files, and tablespaces before re-creating the replicas. This structured workflow provides a reliable path for major version transitions and supports automatic rollback cleanup when the user reverts the image after a failure. +Clusters that use Image Volume extensions are also supported: the source- and +target-version extension images are mounted side by side during the upgrade +job, so the old server keeps its libraries and a failed upgrade reverts +cleanly. ### Display cluster availability status during upgrade @@ -605,7 +640,12 @@ The operator allows you to scale up and down the number of instances in a PostgreSQL cluster. New replicas are started up from the primary server and participate in the cluster's HA infrastructure. The CRD declares a "scale" subresource that allows you to use the -`kubectl scale` command. +`kubectl scale` command. The scale subresource also publishes the label +selector of the managed instance pods, which lets autoscalers discover them. +See the [Vertical Pod Autoscaler integration](resource_management.md#integration-with-the-vertical-pod-autoscaler-vpa) +for the recommended use, and the +[Horizontal Pod Autoscaler integration](resource_management.md#integration-with-the-horizontal-pod-autoscaler-hpa) +for the caveats that apply to HPA. ### Maintenance window and PodDisruptionBudget for Kubernetes nodes @@ -654,6 +694,10 @@ to clone the data from the primary again. The operator allows administrators to control and manage resource usage by the cluster's pods in the `resources` section of the manifest. In particular, you can set `requests` and `limits` values for both CPU and RAM. +Because the `Cluster` exposes a label selector through its scale subresource, +it can also be used as a target for the +[Vertical Pod Autoscaler](resource_management.md#integration-with-the-vertical-pod-autoscaler-vpa) +in recommendation-only mode, to obtain sizing suggestions for these values. ### Connection pooling with PgBouncer @@ -665,15 +709,23 @@ to access the database. This optimizes the query flow toward the instances and makes the use of the underlying PostgreSQL resources more efficient. Instead of connecting directly to a PostgreSQL service, applications can now connect to the PgBouncer service and start reusing any existing connection. +The PgBouncer image can be managed centrally through an `ImageCatalog` or +`ClusterImageCatalog` (via `spec.pgbouncer.imageCatalogRef`), and the `Pooler` +metrics endpoint can optionally be served over TLS. ### Logical Replication {{name.ln}} supports PostgreSQL's logical replication in a declarative manner -using `Publication` and `Subscription` custom resource definitions. +using the `Publication` and `Subscription` custom resource definitions. + +Logical replication is particularly useful for: -Logical replication is particularly useful together with the import facility -for online data migrations (even from public DBaaS solutions) and major -PostgreSQL upgrades. +- Online data migrations: Moving data from external PostgreSQL instances or + public DBaaS solutions with minimal downtime. +- Major PostgreSQL upgrades: Facilitating near-zero-downtime upgrades between + major versions. +- Selective Data Distribution: Replicating specific tables or data sets across + different clusters for reporting or localized workloads. ### Integration with external backup tools for Kubernetes @@ -769,6 +821,16 @@ the cluster. It does this by either becoming the new primary or by following it. In case the former primary comes back up, the same mechanism avoids a split-brain by preventing applications from reaching it, running `pg_rewind` on the server and restarting it as a standby. +The operator further coordinates primary promotion through a per-cluster +Kubernetes `Lease` that acts as a mutex, ensuring at most one instance promotes +at any given time: an instance must hold the lease before acting as primary and +releases it on a clean shutdown, so replicas can promote without waiting for the +full TTL. +If synchronous failover quorum is enabled, the operator's "Auto Pilot" logic +becomes even more sophisticated: it will actively block a promotion if a quorum +of replicas cannot verify the transaction state. This prevents accidental data +loss during complex failure scenarios, such as network partitions affecting +both the primary and its synchronous standby. ### Automated recreation of a standby diff --git a/product_docs/docs/postgres_for_kubernetes/1/operator_conf.mdx b/product_docs/docs/postgres_for_kubernetes/1/operator_conf.mdx index aa39c3c4bc5..cf1f194f4cf 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/operator_conf.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/operator_conf.mdx @@ -43,31 +43,43 @@ As a result, if a parameter is defined in both places, the one in the Secret wil The operator looks for the following environment variables to be defined in the `ConfigMap`/`Secret`: -| Name | Description | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `CERTIFICATE_DURATION` | Determines the lifetime of the generated certificates in days. Default is 90. | -| `CLUSTERS_ROLLOUT_DELAY` | The duration (in seconds) to wait between the roll-outs of different clusters during an operator upgrade. This setting controls the timing of upgrades across clusters, spreading them out to reduce system impact. The default value is `0` which means no delay between PostgreSQL cluster upgrades. | -| `CREATE_ANY_SERVICE` | When set to `true`, will create `-any` service for the cluster. Default is `false` | -| `DRAIN_TAINTS` | Specifies the taint keys that should be interpreted as indicators of node drain. By default, it includes the taints commonly applied by [kubectl](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/), [Cluster Autoscaler](https://github.com/kubernetes/autoscaler), and [Karpenter](https://github.com/aws/karpenter-provider-aws): `node.kubernetes.io/unschedulable`, `ToBeDeletedByClusterAutoscaler`, `karpenter.sh/disrupted`, `karpenter.sh/disruption`. | -| `EDB_LICENSE_KEY` | Default license key (to be used only if the cluster does not define one, and preferably in the `Secret`) | -| `ENABLE_INSTANCE_MANAGER_INPLACE_UPDATES` | When set to `true`, enables in-place updates of the instance manager after an update of the operator, avoiding rolling updates of the cluster (default `false`) | -| `ENABLE_REDWOOD_BY_DEFAULT` | Enable the Redwood compatibility by default when using EPAS. | -| `EXPIRING_CHECK_THRESHOLD` | Determines the threshold, in days, for identifying a certificate as expiring. Default is 7. | -| `EXTERNAL_BACKUP_ADDON_CONFIGURATION` | Configuration for the `external-backup-adapter` add-on. (See ["Customizing the adapter" in Add-ons](addons.md#customizing-the-adapter)) | -| `INCLUDE_PLUGINS` | A comma-separated list of plugins to be always included in the Cluster's reconciliation. | -| `INHERITED_ANNOTATIONS` | List of annotation names that, when defined in a `Cluster` metadata, will be inherited by all the generated resources, including pods | -| `INHERITED_LABELS` | List of label names that, when defined in a `Cluster` metadata, will be inherited by all the generated resources, including pods | -| `INSTANCES_ROLLOUT_DELAY` | The duration (in seconds) to wait between roll-outs of individual PostgreSQL instances within the same cluster during an operator upgrade. The default value is `0`, meaning no delay between upgrades of instances in the same PostgreSQL cluster. | -| `KUBERNETES_CLUSTER_DOMAIN` | Defines the domain suffix for service FQDNs within the Kubernetes cluster. If left unset, it defaults to "cluster.local". | -| `METRICS_CERT_DIR` | The directory where TLS certificates for the operator metrics server are stored. When set, enables TLS for the metrics endpoint on port 8080. The directory must contain `tls.crt` and `tls.key` files following standard Kubernetes TLS secret conventions. If not set, the metrics server operates without TLS (default behavior). | -| `MONITORING_QUERIES_CONFIGMAP` | The name of a ConfigMap in the operator's namespace with a set of default queries (to be specified under the key `queries`) to be applied to all created Clusters | -| `MONITORING_QUERIES_SECRET` | The name of a Secret in the operator's namespace with a set of default queries (to be specified under the key `queries`) to be applied to all created Clusters | -| `OPERATOR_IMAGE_NAME` | The name of the operator image used to bootstrap Pods. Defaults to the image specified during installation. | -| `PGBOUNCER_IMAGE_NAME` | The name of the PgBouncer image used by default for new poolers. Defaults to the version specified in the operator. | -| `POSTGRES_IMAGE_NAME` | The name of the PostgreSQL image used by default for new clusters. Defaults to the version specified in the operator. | -| `PULL_SECRET_NAME` | Name of an additional pull secret to be defined in the operator's namespace and to be used to download images | -| `STANDBY_TCP_USER_TIMEOUT` | Defines the [`TCP_USER_TIMEOUT` socket option](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-TCP-USER-TIMEOUT) in milliseconds for replication connections from standby instances to the primary. Default is 5000 (5 seconds). Set to `0` to use the system's default. | -| `WATCH_NAMESPACE` | Specifies the namespace(s) where the operator should watch for resources. Multiple namespaces can be specified separated by commas. If not set, the operator watches all namespaces (cluster-wide mode). | +| Name | Description | +| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `CERTIFICATE_DURATION` | Determines the lifetime of the generated certificates in days. Default is 90. | +| `CLUSTERS_ROLLOUT_DELAY` | The duration (in seconds) to wait between the roll-outs of different clusters during an operator upgrade. This setting controls the timing of upgrades across clusters, spreading them out to reduce system impact. The default value is `0` which means no delay between PostgreSQL cluster upgrades. | +| `CREATE_ANY_SERVICE` | When set to `true`, will create `-any` service for the cluster. Default is `false` | +| `DRAIN_TAINTS` | Specifies the taint keys that should be interpreted as indicators of node drain. By default, it includes the taints commonly applied by [kubectl](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/), [Cluster Autoscaler](https://github.com/kubernetes/autoscaler), and [Karpenter](https://github.com/aws/karpenter-provider-aws): `node.kubernetes.io/unschedulable`, `ToBeDeletedByClusterAutoscaler`, `karpenter.sh/disrupted`, `karpenter.sh/disruption`. | +| `EDB_LICENSE_KEY` | Default license key (to be used only if the cluster does not define one, and preferably in the `Secret`) | +| `ENABLE_INSTANCE_MANAGER_INPLACE_UPDATES` | When set to `true`, enables in-place updates of the instance manager after an update of the operator, avoiding rolling updates of the cluster (default `false`) | +| `ENABLE_REDWOOD_BY_DEFAULT` | Enable the Redwood compatibility by default when using EPAS. | +| `ENABLE_WEBHOOK_NAMESPACE_SUFFIX` | When set to `true`, the operator looks up its `MutatingWebhookConfiguration` and `ValidatingWebhookConfiguration` under names suffixed with `-` (e.g. `postgresql-operator-mutating-webhook-configuration-postgresql-operator-team-a` and `postgresql-operator-validating-webhook-configuration-postgresql-operator-team-a`). Use this when running multiple namespaced operator instances on the same cluster to avoid name collisions. The operator does not create the suffixed configurations; you must create them before starting the operator with this flag enabled. If `OPERATOR_NAMESPACE` is not set when this flag is enabled, the operator will refuse to start. Default is `false`. | +| `EXPIRING_CHECK_THRESHOLD` | Determines the threshold, in days, for identifying a certificate as expiring. Default is 7. | +| `EXTERNAL_BACKUP_ADDON_CONFIGURATION` | Configuration for the `external-backup-adapter` add-on. (See ["Customizing the adapter" in Add-ons](addons.md#customizing-the-adapter)) | +| `INCLUDE_PLUGINS` | A comma-separated list of plugins to be always included in the Cluster's reconciliation. | +| `INHERITED_ANNOTATIONS` | List of annotation names that, when defined in a `Cluster` metadata, will be inherited by all the generated resources, including pods | +| `INHERITED_LABELS` | List of label names that, when defined in a `Cluster` metadata, will be inherited by all the generated resources, including pods | +| `INSTANCES_ROLLOUT_DELAY` | The duration (in seconds) to wait between roll-outs of individual PostgreSQL instances within the same cluster during an operator upgrade. The default value is `0`, meaning no delay between upgrades of instances in the same PostgreSQL cluster. | +| `KUBERNETES_CLUSTER_DOMAIN` | Defines the domain suffix for service FQDNs within the Kubernetes cluster. If left unset, it defaults to "cluster.local". | +| `MANAGE_WEBHOOK_CONFIGURATIONS` | When set to `true` (default), the operator injects its CA bundle into the `MutatingWebhookConfiguration` and `ValidatingWebhookConfiguration`. Set to `false` when the CA bundle is injected externally, for example by cert-manager's CA injector or by GitOps. This is independent of the webhook serving certificate, which the operator always manages when it owns its PKI. | +| `METRICS_CERT_DIR` | The directory where TLS certificates for the operator metrics server are stored. When set, enables TLS for the metrics endpoint on port 8080. The directory must contain `tls.crt` and `tls.key` files following standard Kubernetes TLS secret conventions. If not set, the metrics server operates without TLS (default behavior). | +| `MONITORING_QUERIES_CONFIGMAP` | The name of a ConfigMap in the operator's namespace with a set of default queries (to be specified under the key `queries`) to be applied to all created Clusters | +| `MONITORING_QUERIES_SECRET` | The name of a Secret in the operator's namespace with a set of default queries (to be specified under the key `queries`) to be applied to all created Clusters | +| `OPERATOR_IMAGE_NAME` | The name of the operator image used to bootstrap Pods. Defaults to the image specified during installation. | +| `PGBOUNCER_IMAGE_NAME` | The name of the PgBouncer image used by default for new poolers. Defaults to the version specified in the operator. | +| `POSTGRES_IMAGE_NAME` | The name of the PostgreSQL image used by default for new clusters. Defaults to the version specified in the operator. | +| `PULL_SECRET_NAME` | Name of an additional pull secret to be defined in the operator's namespace and to be used to download images | +| `STANDBY_TCP_USER_TIMEOUT` | Defines the [`TCP_USER_TIMEOUT` socket option](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-TCP-USER-TIMEOUT) in milliseconds for replication connections from standby instances to the primary. Default is 5000 (5 seconds). Set to `0` to use the system's default. | +| `WATCH_NAMESPACE` | Specifies the namespace(s) where the operator should watch for resources. Multiple namespaces can be specified separated by commas. If not set, the operator watches all namespaces (cluster-wide mode). | + +!!!warning + +{{name.ln}} does NOT currently support running multiple operators on +the same cluster. While this can be achieved through the use of namespaced +deployments using `ENABLE_WEBHOOK_NAMESPACE_SUFFIX` and `WATCH_NAMESPACE`, +multiple operators still use the same set of shared CRDs. We cannot +guarantee a backwards compatible upgrade across multiple concurrently +running operators. +!!! Values in `INHERITED_ANNOTATIONS` and `INHERITED_LABELS` support path-like wildcards. For example, the value `example.com/*` will match both the value `example.com/one` and `example.com/two`. @@ -161,6 +173,24 @@ Following the above example, if the `Cluster` definition contains a `categories` annotation and any of the `environment`, `workload`, or `app` labels, these will be inherited by all the resources generated by the deployment. +## Defaulting and validation without admission webhooks + +{{name.ln}} normally defaults and validates its resources through admission +webhooks. When the webhooks are not installed, or are temporarily unable to +respond, the operator performs the same defaulting and validation during +reconciliation as a fallback. + +If a resource fails validation, reconciliation stops and the reason is surfaced +on the resource status: `Cluster` and `Backup` move to the `Invalid cluster +definition` and `invalid backup definition` phases respectively, while `Pooler` +and `ScheduledBackup` report it in `.status.error`. The status lists only the +offending field paths; the full validation error, which may contain field +values, is written to the operator logs only. Correcting the spec clears the +error and resumes reconciliation. + +Validation performed during reconciliation honors the `k8s.enterprisedb.io/validation: +disabled` annotation, exactly as the admission webhook does. + ## Profiling tools The operator can expose a pprof HTTP server on `localhost:6060`. diff --git a/product_docs/docs/postgres_for_kubernetes/1/pg4k.v1/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/pg4k.v1/index.mdx index 0b539baec76..dd76c54e78a 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/pg4k.v1/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/pg4k.v1/index.mdx @@ -1,9 +1,11 @@ --- -title: API Reference - v1.29.1 +title: API Reference - v1.30.0 originalFilePath: src/pg4k.v1.md navTitle: API Reference navigation: + - v1.30.0 - v1.29.1 + - v1.29.0 - v1.28.1 - v1.28.0 - v1.27.1 @@ -126,6 +128,8 @@ Package v1 contains API Schema definitions for the postgresql v1 API group - [Cluster](#cluster) - [ClusterImageCatalog](#clusterimagecatalog) - [Database](#database) +- [DatabaseRole](#databaserole) +- [DatabaseRoleList](#databaserolelist) - [FailoverQuorum](#failoverquorum) - [ImageCatalog](#imagecatalog) - [Pooler](#pooler) @@ -447,6 +451,19 @@ The method can be also be used to create clusters in continuous recovery | `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | | `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | +#### CatalogComponentImage + +CatalogComponentImage is a named image entry for a non-PostgreSQL component. + +*Appears in:* + +- [ImageCatalogSpec](#imagecatalogspec) + +| Field | Description | Required | Default | Validation | +| ---------------- | --------------------------------------------------------------- | -------- | ------- | --------------------------------------------------------------------- | +| `key` *string* | Key is the unique identifier for this image within the catalog. | True | | MaxLength: 63
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| +| `image` *string* | Image is the container image reference. | True | | | + #### CatalogImage CatalogImage defines the image and major version @@ -495,6 +512,32 @@ CertificatesStatus contains configuration certificates and related expiration da | `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | | `expirations` *object (keys:string, values:string)* | Expiration dates for all certificates. | | | | +#### ClientCertificateConfiguration + +ClientCertificateConfiguration configures operator-managed issuance of a TLS +client certificate for a DatabaseRole. + +*Appears in:* + +- [DatabaseRoleSpec](#databaserolespec) + +| Field | Description | Required | Default | Validation | +| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | +| `enabled` *boolean* | Enabled turns on client certificate issuance for this role. When true,
the role must have login enabled. Defaults to true when the block is present. | | true | | + +#### ClientCertificateState + +ClientCertificateState holds the observed state of the generated TLS client certificate. + +*Appears in:* + +- [DatabaseRoleStatus](#databaserolestatus) + +| Field | Description | Required | Default | Validation | +| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | +| `expiration` *string* | Expiration is the expiration time of the generated client certificate, in RFC3339 format. | | | | +| `message` *string* | Message contains a human-readable explanation of the current certificate status,
such as why issuance was skipped or why an existing Secret was left untouched. | | | | + #### Cluster Cluster defines the API schema for a highly available PostgreSQL database cluster @@ -600,6 +643,7 @@ ClusterSpec defines the desired state of a PostgreSQL cluster managed by | `enablePDB` *boolean* | 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 any
`PodDisruptionBudget` 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. | | true | | | `plugins` *[PluginConfiguration](#pluginconfiguration) array* | The plugins configuration, containing
any plugin to be loaded with the corresponding configuration | | | | | `probes` *[ProbesConfiguration](#probesconfiguration)* | The configuration of the probes to be injected
in the PostgreSQL Pods. | | | | +| `primaryLease` *[PrimaryLeaseConfiguration](#primaryleaseconfiguration)* | Configuration of the Kubernetes `Lease` used to coordinate safe primary
election within the cluster. When omitted, the operator applies built-in
defaults; tune these values only if you understand the consequences for
failover timing. | | | | #### ClusterStatus @@ -610,57 +654,60 @@ ClusterStatus defines the observed state of a PostgreSQL cluster managed by - [Cluster](#cluster) -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *integer* | The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods. | | | | -| `readyInstances` *integer* | The total number of ready instances in the cluster. It is equal to the number of ready instance pods. | | | | -| `instancesStatus` *object (keys:[PodStatus](#podstatus), values:string array)* | InstancesStatus indicates in which status the instances are | | | | -| `instancesReportedState` *object (keys:[PodName](#podname), values:[InstanceReportedState](#instancereportedstate))* | The reported state of the instances during the last reconciliation loop | | | | -| `managedRolesStatus` *[ManagedRoles](#managedroles)* | ManagedRolesStatus reports the state of the managed roles in the cluster | | | | -| `tablespacesStatus` *[TablespaceState](#tablespacestate) array* | TablespacesStatus reports the state of the declarative tablespaces in the cluster | | | | -| `podSelectorRefs` *[PodSelectorRefStatus](#podselectorrefstatus) array* | PodSelectorRefs contains the resolved pod IPs for each named selector
defined in spec.podSelectorRefs. | | | | -| `timelineID` *integer* | The timeline of the Postgres cluster | | | | -| `topology` *[Topology](#topology)* | Instances topology. | | | | -| `latestGeneratedNode` *integer* | ID of the latest generated node (used to avoid node name clashing) | | | | -| `currentPrimary` *string* | Current primary instance | | | | -| `targetPrimary` *string* | Target primary instance, this is different from the previous one
during a switchover or a failover | | | | -| `lastPromotionToken` *string* | LastPromotionToken is the last verified promotion token that
was used to promote a replica cluster | | | | -| `pvcCount` *integer* | How many PVCs have been created by this cluster | | | | -| `jobCount` *integer* | How many Jobs have been created by this cluster | | | | -| `danglingPVC` *string array* | List of all the PVCs created by this cluster and still available
which are not attached to a Pod | | | | -| `resizingPVC` *string array* | List of all the PVCs that have ResizingPVC condition. | | | | -| `initializingPVC` *string array* | List of all the PVCs that are being initialized by this cluster | | | | -| `healthyPVC` *string array* | List of all the PVCs not dangling nor initializing | | | | -| `unusablePVC` *string array* | List of all the PVCs that are unusable because another PVC is missing | | | | -| `licenseStatus` *Status* | Status of the license | | | | -| `writeService` *string* | Current write pod | | | | -| `readService` *string* | Current list of read pods | | | | -| `phase` *string* | Current phase of the cluster | | | | -| `phaseReason` *string* | Reason for the current phase | | | | -| `secretsResourceVersion` *[SecretsResourceVersion](#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` *[ConfigMapResourceVersion](#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` *[CertificatesStatus](#certificatesstatus)* | The configuration for the CA and related certificates, initialized with defaults. | | | | -| `firstRecoverabilityPoint` *string* | The first recoverability point, stored as a date in RFC3339 format.
This field is calculated from the content of FirstRecoverabilityPointByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `firstRecoverabilityPointByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | The first recoverability point, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackup` *string* | Last successful backup, stored as a date in RFC3339 format.
This field is calculated from the content of LastSuccessfulBackupByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackupByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | Last successful backup, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastFailedBackup` *string* | Last failed backup, stored as a date in RFC3339 format.
Deprecated: the field is not set for backup plugins. | | | | -| `cloudNativePostgresqlCommitHash` *string* | The commit hash number of which this operator running | | | | -| `currentPrimaryTimestamp` *string* | The timestamp when the last actual promotion to primary has occurred | | | | -| `currentPrimaryFailingSinceTimestamp` *string* | The timestamp when the primary was detected to be unhealthy
This field is reported when `.spec.failoverDelay` is populated or during online upgrades | | | | -| `targetPrimaryTimestamp` *string* | The timestamp when the last request for a new primary has occurred | | | | -| `poolerIntegrations` *[PoolerIntegrations](#poolerintegrations)* | The integration needed by poolers referencing the cluster | | | | -| `cloudNativePostgresqlOperatorHash` *string* | The hash of the binary of the operator | | | | -| `availableArchitectures` *[AvailableArchitecture](#availablearchitecture) array* | AvailableArchitectures reports the available architectures of a cluster | | | | -| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for cluster object | | | | -| `instanceNames` *string array* | List of instance names in the cluster | | | | -| `onlineUpdateEnabled` *boolean* | OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster | | | | -| `image` *string* | Image contains the image name used by the pods | | | | -| `pgDataImageInfo` *[ImageInfo](#imageinfo)* | PGDataImageInfo contains the details of the latest image that has run on the current data directory. | | | | -| `pluginStatus` *[PluginStatus](#pluginstatus) array* | PluginStatus is the status of the loaded plugins | | | | -| `switchReplicaClusterStatus` *[SwitchReplicaClusterStatus](#switchreplicaclusterstatus)* | SwitchReplicaClusterStatus is the status of the switch to replica cluster | | | | -| `demotionToken` *string* | DemotionToken is a JSON token containing the information
from pg_controldata such as Database system identifier, Latest checkpoint's
TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO
WAL file, and Time of latest checkpoint | | | | -| `systemID` *string* | SystemID is the latest detected PostgreSQL SystemID | | | | +| Field | Description | Required | Default | Validation | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | +| `instances` *integer* | The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods. | | | | +| `readyInstances` *integer* | The total number of ready instances in the cluster. It is equal to the number of ready instance pods. | | | | +| `selector` *string* | Selector is the serialized form of the label selector that identifies
the pods managed by this cluster. Populated by the operator and exposed
through the scale sub-resource so an autoscaler (such as HPA or VPA)
can discover the managed instance pods. | | | | +| `instancesStatus` *object (keys:[PodStatus](#podstatus), values:string array)* | InstancesStatus indicates in which status the instances are | | | | +| `instancesReportedState` *object (keys:[PodName](#podname), values:[InstanceReportedState](#instancereportedstate))* | The reported state of the instances during the last reconciliation loop | | | | +| `managedRolesStatus` *[ManagedRoles](#managedroles)* | ManagedRolesStatus reports the state of the managed roles in the cluster | | | | +| `tablespacesStatus` *[TablespaceState](#tablespacestate) array* | TablespacesStatus reports the state of the declarative tablespaces in the cluster | | | | +| `podSelectorRefs` *[PodSelectorRefStatus](#podselectorrefstatus) array* | PodSelectorRefs contains the resolved pod IPs for each named selector
defined in spec.podSelectorRefs. | | | | +| `timelineID` *integer* | The timeline of the Postgres cluster | | | | +| `topology` *[Topology](#topology)* | Instances topology. | | | | +| `latestGeneratedNode` *integer* | ID of the latest generated node (used to avoid node name clashing)
Deprecated: this field is not set anymore | | | | +| `currentPrimary` *string* | Current primary instance | | | | +| `targetPrimary` *string* | Target primary instance, this is different from the previous one
during a switchover or a failover | | | | +| `lastPromotionToken` *string* | LastPromotionToken is the last verified promotion token that
was used to promote a replica cluster | | | | +| `pvcCount` *integer* | How many PVCs have been created by this cluster | | | | +| `jobCount` *integer* | How many Jobs have been created by this cluster | | | | +| `danglingPVC` *string array* | List of all the PVCs created by this cluster and still available
which are not attached to a Pod | | | | +| `resizingPVC` *string array* | List of all the PVCs that have ResizingPVC condition. | | | | +| `initializingPVC` *string array* | List of all the PVCs that are being initialized by this cluster | | | | +| `healthyPVC` *string array* | List of all the PVCs not dangling nor initializing | | | | +| `unusablePVC` *string array* | List of all the PVCs that are unusable because another PVC is missing | | | | +| `licenseStatus` *Status* | Status of the license | | | | +| `writeService` *string* | Current write pod | | | | +| `readService` *string* | Current list of read pods | | | | +| `phase` *string* | Current phase of the cluster | | | | +| `phaseReason` *string* | Reason for the current phase | | | | +| `secretsResourceVersion` *[SecretsResourceVersion](#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` *[ConfigMapResourceVersion](#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` *[CertificatesStatus](#certificatesstatus)* | The configuration for the CA and related certificates, initialized with defaults. | | | | +| `firstRecoverabilityPoint` *string* | The first recoverability point, stored as a date in RFC3339 format.
This field is calculated from the content of FirstRecoverabilityPointByMethod.
Deprecated: the field is not set for backup plugins. | | | | +| `firstRecoverabilityPointByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | The first recoverability point, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | +| `lastSuccessfulBackup` *string* | Last successful backup, stored as a date in RFC3339 format.
This field is calculated from the content of LastSuccessfulBackupByMethod.
Deprecated: the field is not set for backup plugins. | | | | +| `lastSuccessfulBackupByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | Last successful backup, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | +| `lastFailedBackup` *string* | Last failed backup, stored as a date in RFC3339 format.
Deprecated: the field is not set for backup plugins. | | | | +| `cloudNativePostgresqlCommitHash` *string* | The commit hash number of which this operator running | | | | +| `currentPrimaryTimestamp` *string* | The timestamp when the last actual promotion to primary has occurred | | | | +| `currentPrimaryFailingSinceTimestamp` *string* | The timestamp when the primary was detected to be unhealthy
This field is reported when `.spec.failoverDelay` is populated or during online upgrades | | | | +| `targetPrimaryTimestamp` *string* | The timestamp when the last request for a new primary has occurred | | | | +| `poolerIntegrations` *[PoolerIntegrations](#poolerintegrations)* | The integration needed by poolers referencing the cluster | | | | +| `cloudNativePostgresqlOperatorHash` *string* | The hash of the binary of the operator | | | | +| `operatorCertificateFingerprint` *string* | OperatorCertificateFingerprint is the SHA256 fingerprint of the operator's
in-memory client certificate public key. The instance manager pins this
fingerprint to authenticate requests from the operator. | | | | +| `availableArchitectures` *[AvailableArchitecture](#availablearchitecture) array* | AvailableArchitectures reports the available architectures of a cluster | | | | +| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for cluster object | | | | +| `instanceNames` *string array* | List of instance names in the cluster | | | | +| `onlineUpdateEnabled` *boolean* | OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster | | | | +| `image` *string* | Image contains the image name used by the pods | | | | +| `pgDataImageInfo` *[ImageInfo](#imageinfo)* | PGDataImageInfo contains the details of the latest image that has run on the current data directory. | | | | +| `targetPgDataImageInfo` *[ImageInfo](#imageinfo)* | TargetPGDataImageInfo contains the details of the target image for an
in-progress major upgrade. It is set before the upgrade Job is created,
and cleared on successful completion or when the upgrade is rolled back. | | | | +| `pluginStatus` *[PluginStatus](#pluginstatus) array* | PluginStatus is the status of the loaded plugins | | | | +| `switchReplicaClusterStatus` *[SwitchReplicaClusterStatus](#switchreplicaclusterstatus)* | SwitchReplicaClusterStatus is the status of the switch to replica cluster | | | | +| `demotionToken` *string* | DemotionToken is a JSON token containing the information
from pg_controldata such as Database system identifier, Latest checkpoint's
TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO
WAL file, and Time of latest checkpoint | | | | +| `systemID` *string* | SystemID is the latest detected PostgreSQL SystemID | | | | #### ConfigMapResourceVersion @@ -764,6 +811,48 @@ DatabaseReclaimPolicy describes a policy for end-of-life maintenance of database | `delete` | DatabaseReclaimDelete means the database will be deleted from its PostgreSQL Cluster on release
from its claim.
| | `retain` | DatabaseReclaimRetain means the database will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| +#### DatabaseRole + +DatabaseRole is the Schema for the databaseroles API + +*Appears in:* + +- [DatabaseRoleList](#databaserolelist) + +| Field | Description | Required | Default | Validation | +| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | +| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | +| `kind` *string* | `DatabaseRole` | True | | | +| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | +| `spec` *[DatabaseRoleSpec](#databaserolespec)* | Specification of the desired DatabaseRole.
More info: | True | | | +| `status` *[DatabaseRoleStatus](#databaserolestatus)* | Most recently observed status of the DatabaseRole. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | + +#### DatabaseRoleList + +DatabaseRoleList contains a list of DatabaseRoles + +| Field | Description | Required | Default | Validation | +| -------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | -------- | ------- | ---------- | +| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | +| `kind` *string* | `DatabaseRoleList` | True | | | +| `metadata` *[ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#listmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | +| `items` *[DatabaseRole](#databaserole) array* | | True | | | + +#### DatabaseRoleReclaimPolicy + +*Underlying type:* *string* + +DatabaseRoleReclaimPolicy describes a policy for end-of-life maintenance of Roles. + +*Appears in:* + +- [DatabaseRoleSpec](#databaserolespec) + +| Field | Description | +| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `delete` | DatabaseRoleReclaimDelete means the Role will be deleted from Kubernetes on release
from its claim.
| +| `retain` | DatabaseRoleReclaimRetain means the Role will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| + #### DatabaseRoleRef DatabaseRoleRef is a reference an a role available inside PostgreSQL @@ -776,6 +865,52 @@ DatabaseRoleRef is a reference an a role available inside PostgreSQL | --------------- | ----------- | -------- | ------- | ---------- | | `name` *string* | | | | | +#### DatabaseRoleSpec + +DatabaseRoleSpec represents a role in Postgres + +*Appears in:* + +- [DatabaseRole](#databaserole) + +| Field | Description | Required | Default | Validation | +| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | +| `name` *string* | Name of the role | True | | | +| `comment` *string* | Description of the role | | | | +| `ensure` *[EnsureOption](#ensureoption)* | Ensure the role is `present` or `absent` - defaults to "present" | | present | Enum: [present absent]
| +| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present).
If null, the password will be ignored unless DisablePassword is set.
When set, the secret must follow the `kubernetes.io/basic-auth` format
and contain both a `username` and a `password` field. | | | | +| `connectionLimit` *integer* | If the role can log in, this specifies how many concurrent
connections the role can make. `-1` (the default) means no limit. | | -1 | | +| `validUntil` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Date and time after which the role's password is no longer valid.
When omitted, the password will never expire (default). | | | | +| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty.
Changes to the list are applied to an existing role through
`GRANT` and `REVOKE` statements, not only at role creation. | | | | +| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Default is `true`. | | true | | +| `disablePassword` *boolean* | DisablePassword indicates that a role's password should be set to NULL in Postgres | | | | +| `superuser` *boolean* | 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`. | | | | +| `createdb` *boolean* | 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. | | | | +| `createrole` *boolean* | 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`. | | | | +| `login` *boolean* | 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`. | | | | +| `replication` *boolean* | 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`. | | | | +| `bypassrls` *boolean* | Whether a role bypasses every row-level security (RLS) policy.
Default is `false`. | | | | +| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The corresponding cluster | True | | | +| `databaseRoleReclaimPolicy` *[DatabaseRoleReclaimPolicy](#databaserolereclaimpolicy)* | The policy for end-of-life maintenance of this role | | retain | Enum: [delete retain]
| +| `clientCertificate` *[ClientCertificateConfiguration](#clientcertificateconfiguration)* | ClientCertificate configures the operator to generate and renew a TLS client
certificate for this role, signed by the cluster's client CA. The certificate
is stored in a Secret named `-client-cert`.
Requires login to be true. | | | | + +#### DatabaseRoleStatus + +DatabaseRoleStatus defines the observed state of a DatabaseRole + +*Appears in:* + +- [DatabaseRole](#databaserole) + +| Field | Description | Required | Default | Validation | +| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | +| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | +| `applied` *boolean* | Applied is true if the role was reconciled correctly | | | | +| `message` *string* | Message is the reconciliation error message | | | | +| `secretResourceVersion` *string* | SecretResourceVersion is the resource version of the password secret
last applied to the role; a change to it triggers reconciliation. | | | | +| `clientCertificate` *[ClientCertificateState](#clientcertificatestate)* | ClientCertificate holds the observed state of the generated TLS client
certificate, when client certificate issuance is enabled. | | | | +| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for the DatabaseRole object | | | | + #### DatabaseSpec DatabaseSpec is the specification of a Postgresql Database, built around the @@ -866,6 +1001,7 @@ a Role in a PostgreSQL instance *Appears in:* - [DatabaseObjectSpec](#databaseobjectspec) +- [DatabaseRoleSpec](#databaserolespec) - [DatabaseSpec](#databasespec) - [ExtensionSpec](#extensionspec) - [FDWSpec](#fdwspec) @@ -904,15 +1040,15 @@ PostgreSQL extensions to the Cluster. - [ImageInfo](#imageinfo) - [PostgresConfiguration](#postgresconfiguration) -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------------------------------------------- | -| `name` *string* | The name of the extension, required | True | | MinLength: 1
Pattern: `^[a-z0-9]([-a-z0-9_]*[a-z0-9])?$`
| -| `image` *[ImageVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#imagevolumesource-v1-core)* | The image containing the extension. | | | | -| `extension_control_path` *string array* | The list of directories inside the image which should be added to extension_control_path.
If not defined, defaults to "/share". | | | | -| `dynamic_library_path` *string array* | The list of directories inside the image which should be added to dynamic_library_path.
If not defined, defaults to "/lib". | | | | -| `ld_library_path` *string array* | The list of directories inside the image which should be added to ld_library_path. | | | | -| `bin_path` *string array* | A list of directories within the image to be appended to the
PostgreSQL process's `PATH` environment variable. | | | | -| `env` *[ExtensionEnvVar](#extensionenvvar) array* | Env is a list of custom environment variables to be set in the
PostgreSQL process for this extension. It is the responsibility of the
cluster administrator to ensure the variables are correct for the
specific extension. Note that changes to these variables require
a manual cluster restart to take effect. | | | | +| Field | Description | Required | Default | Validation | +| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------------------------------------------------------------------- | +| `name` *string* | The name of the extension, required. The limit of 59 characters
leaves room for the prefix the operator adds when deriving the
extension's Kubernetes Volume name (capped at 63 characters). | True | | MaxLength: 59
MinLength: 1
Pattern: `^[a-z0-9]([-a-z0-9_]*[a-z0-9])?$`
| +| `image` *[ImageVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#imagevolumesource-v1-core)* | The image containing the extension. | | | | +| `extension_control_path` *string array* | The list of directories inside the image which should be added to extension_control_path.
If not defined, defaults to "/share". | | | | +| `dynamic_library_path` *string array* | The list of directories inside the image which should be added to dynamic_library_path.
If not defined, defaults to "/lib". | | | | +| `ld_library_path` *string array* | The list of directories inside the image which should be added to ld_library_path. | | | | +| `bin_path` *string array* | A list of directories within the image to be appended to the
PostgreSQL process's `PATH` environment variable. | | | | +| `env` *[ExtensionEnvVar](#extensionenvvar) array* | Env is a list of custom environment variables to be set in the
PostgreSQL process for this extension. It is the responsibility of the
cluster administrator to ensure the variables are correct for the
specific extension. Note that changes to these variables require
a manual cluster restart to take effect. | | | | #### ExtensionEnvVar @@ -1022,6 +1158,22 @@ ImageCatalog is the Schema for the imagecatalogs API | `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | | `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ImageCatalog.
More info: | True | | | +#### ImageCatalogComponentRef + +ImageCatalogComponentRef identifies a named image within the componentImages list of an +ImageCatalog or ClusterImageCatalog. + +*Appears in:* + +- [PgBouncerSpec](#pgbouncerspec) + +| Field | Description | Required | Default | Validation | +| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------------------------------------------- | +| `apiGroup` *string* | APIGroup is the group for the resource being referenced.
If APIGroup is not specified, the specified Kind must be in the core API group.
For any other third-party types, APIGroup is required. | | | | +| `kind` *string* | Kind is the type of resource being referenced | True | | | +| `name` *string* | Name is the name of resource being referenced | True | | | +| `key` *string* | Key identifies the entry within the catalog's componentImages list. | True | | MaxLength: 63
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| + #### ImageCatalogRef ImageCatalogRef defines the reference to a major version in an ImageCatalog @@ -1046,9 +1198,10 @@ ImageCatalogSpec defines the desired ImageCatalog - [ClusterImageCatalog](#clusterimagecatalog) - [ImageCatalog](#imagecatalog) -| Field | Description | Required | Default | Validation | -| ---------------------------------------------- | ---------------------------------------------- | -------- | ------- | ------------------------------------ | -| `images` *[CatalogImage](#catalogimage) array* | List of CatalogImages available in the catalog | True | | MaxItems: 8
MinItems: 1
| +| Field | Description | Required | Default | Validation | +| ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------ | +| `images` *[CatalogImage](#catalogimage) array* | List of CatalogImages available in the catalog | True | | MaxItems: 8
MinItems: 1
| +| `componentImages` *[CatalogComponentImage](#catalogcomponentimage) array* | ComponentImages is a list of named images for components other than PostgreSQL
(e.g. pgbouncer). Keys must be unique within a catalog. | | | MaxItems: 32
| #### ImageInfo @@ -1244,11 +1397,11 @@ ManagedRoles tracks the status of a cluster's managed roles - [ClusterStatus](#clusterstatus) -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `byStatus` *object (keys:[RoleStatus](#rolestatus), values:string array)* | ByStatus gives the list of roles in each state | | | | -| `cannotReconcile` *object (keys:string, values:string array)* | CannotReconcile lists roles that cannot be reconciled in PostgreSQL,
with an explanation of the cause | | | | -| `passwordStatus` *object (keys:string, values:[PasswordState](#passwordstate))* | PasswordStatus gives the last transaction id and password secret version for each managed role | | | | +| Field | Description | Required | Default | Validation | +| ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | +| `byStatus` *object (keys:[RoleStatus](#rolestatus), values:string array)* | ByStatus gives the list of roles in each state | | | | +| `cannotReconcile` *object (keys:string, values:string array)* | CannotReconcile lists roles that cannot be reconciled, with an
explanation of the cause. Failures may originate in PostgreSQL
(e.g. dropping a role that owns objects) or in Kubernetes (e.g.
the referenced password Secret cannot be fetched). | | | | +| `passwordStatus` *object (keys:string, values:[PasswordState](#passwordstate))* | PasswordStatus gives the last transaction id and password secret version for each managed role | | | | #### ManagedService @@ -1436,6 +1589,8 @@ PgBouncerSpec defines how to configure PgBouncer | `parameters` *object (keys:string, values:string)* | Additional parameters to be passed to PgBouncer - please check
the CNP documentation for a list of options you can configure | | | | | `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file) | | | | | `paused` *boolean* | 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. | | false | | +| `image` *string* | Image is the pgbouncer container image to use. When set, it takes
precedence over ImageCatalogRef and the operator default, but is
overridden by an explicit image set in the pod template. | | | | +| `imageCatalogRef` *[ImageCatalogComponentRef](#imagecatalogcomponentref)* | ImageCatalogRef points to an entry in an ImageCatalog or ClusterImageCatalog.
Mutually exclusive with Image. | | | | #### PluginConfiguration @@ -1592,11 +1747,46 @@ part for now. - [PoolerSpec](#poolerspec) -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor` | | false | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping. | | | | +| Field | Description | Required | Default | Validation | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | +| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor`
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | false | | +| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | +| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | +| `tls` *[PoolerMonitoringTLSConfiguration](#poolermonitoringtlsconfiguration)* | Configure TLS communication for the metrics endpoint.
Changing tls.enabled option will force a rollout of all instances. | | | | + +#### PoolerMonitoringTLSConfiguration + +PoolerMonitoringTLSConfiguration is the type containing the TLS configuration +for the pooler monitoring + +*Appears in:* + +- [PoolerMonitoringConfiguration](#poolermonitoringconfiguration) + +| Field | Description | Required | Default | Validation | +| ------------------- | -------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | +| `enabled` *boolean* | Enable TLS for the monitoring endpoint.
Changing this option will force a rollout of all instances. | | false | | + +#### PoolerPhase + +*Underlying type:* *string* + +PoolerPhase represents the lifecycle phase of a Pooler. + +*Validation:* + +- Enum: [active paused inactive failed] + +*Appears in:* + +- [PoolerStatus](#poolerstatus) + +| Field | Description | +| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `active` | PoolerPhaseActive means the pooler is running normally and serving traffic.
| +| `paused` | PoolerPhasePaused means PgBouncer is up and running but holding new client
connections in the queue because spec.pgbouncer.paused is true. The Deployment
keeps reconciling; lifting the pause transitions back to Active.
| +| `inactive` | PoolerPhaseInactive means the pooler cannot make progress because a
prerequisite resource is missing (cluster, secret, certificate). The
controller retries periodically until the prerequisite shows up. Check
status.phaseReason for the specific cause.
| +| `failed` | PoolerPhaseFailed means the pooler cannot be reconciled due to a
configuration error. Check status.phaseReason for details.
| #### PoolerSecrets @@ -1630,7 +1820,7 @@ PoolerSpec defines the desired state of Pooler | `template` *[PodTemplateSpec](#podtemplatespec)* | The template of the Pod to be created | | | | | `pgbouncer` *[PgBouncerSpec](#pgbouncerspec)* | The PgBouncer configuration | True | | | | `deploymentStrategy` *[DeploymentStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#deploymentstrategy-v1-apps)* | The deployment strategy to use for pgbouncer to replace existing pods with new ones | | | | -| `monitoring` *[PoolerMonitoringConfiguration](#poolermonitoringconfiguration)* | The configuration of the monitoring infrastructure of this pooler.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | +| `monitoring` *[PoolerMonitoringConfiguration](#poolermonitoringconfiguration)* | The configuration of the monitoring infrastructure of this pooler. | | | | | `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | Template for the Service to be created | | | | | `serviceAccountName` *string* | Name of an existing ServiceAccount in the same namespace to use for the pooler.
When specified, the operator will not create a new ServiceAccount
but will use the provided one. This is useful for sharing a single
ServiceAccount across multiple poolers (e.g., for cloud IAM configurations).
If not specified, a ServiceAccount will be created with the pooler name. | | | MaxLength: 253
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| @@ -1642,10 +1832,14 @@ PoolerStatus defines the observed state of Pooler - [Pooler](#pooler) -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `secrets` *[PoolerSecrets](#poolersecrets)* | The resource version of the config object | | | | -| `instances` *integer* | The number of pods trying to be scheduled | | | | +| Field | Description | Required | Default | Validation | +| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | -------------------------------------------- | +| `secrets` *[PoolerSecrets](#poolersecrets)* | The resource version of the config object | | | | +| `instances` *integer* | The number of pods trying to be scheduled | | | | +| `phase` *[PoolerPhase](#poolerphase)* | Phase summarizes the overall lifecycle state of the Pooler. | | | Enum: [active paused inactive failed]
| +| `phaseReason` *string* | PhaseReason is a human-readable explanation of the current Phase. | | | | +| `image` *string* | Image is the resolved pgbouncer container image that the operator is
using for this Pooler, including any override coming from spec.template.
While Phase is Active or Paused this field reflects what the Deployment
actually runs; while Phase is Inactive or Failed it may carry the last
successfully resolved value (or be empty if the Pooler has never reconciled
successfully). | | | | +| `error` *string* | Error is the latest admission validation error | | | | #### PoolerType @@ -1684,6 +1878,24 @@ PostgresConfiguration defines the PostgreSQL configuration | `enableAlterSystem` *boolean* | If this parameter is true, the user will be able to invoke `ALTER SYSTEM`
on this {{name.ln}} Cluster.
This should only be used for debugging and troubleshooting.
Defaults to false. | | | | | `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | +#### PrimaryLeaseConfiguration + +PrimaryLeaseConfiguration configures the timings of the Kubernetes `Lease` +that the primary instance holds and renews to coordinate a safe primary +election. These values map directly onto the underlying Kubernetes +leader-election parameters. + +*Appears in:* + +- [ClusterSpec](#clusterspec) + +| Field | Description | Required | Default | Validation | +| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------- | +| `leaseDurationSeconds` *integer* | How long, in seconds, the primary lease is considered valid before it
expires and another instance may acquire it. It must be greater than
`renewDeadlineSeconds`.
Defaults to 15. | | 15 | Minimum: 1
| +| `renewDeadlineSeconds` *integer* | How long, in seconds, the current primary keeps retrying to renew the
lease before giving up and stopping. It must be smaller than
`leaseDurationSeconds`.
Defaults to 10. | | 10 | Minimum: 1
| +| `retryPeriodSeconds` *integer* | How frequently, in seconds, a non-holder instance retries acquiring or
renewing the lease.
Defaults to 2. | | 2 | Minimum: 1
| +| `releasedLeaseDurationSeconds` *integer* | The TTL, in seconds, written when the primary explicitly releases the
lease on a clean shutdown, allowing a replica to promote without waiting
for the full lease duration to expire.
Defaults to 1. | | 1 | Minimum: 1
| + #### PrimaryUpdateMethod *Underlying type:* *string* @@ -1971,6 +2183,7 @@ Reference: *Appears in:* +- [DatabaseRoleSpec](#databaserolespec) - [ManagedConfiguration](#managedconfiguration) | Field | Description | Required | Default | Validation | @@ -1978,11 +2191,11 @@ Reference: | `name` *string* | Name of the role | True | | | | `comment` *string* | Description of the role | | | | | `ensure` *[EnsureOption](#ensureoption)* | Ensure the role is `present` or `absent` - defaults to "present" | | present | Enum: [present absent]
| -| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present)
If null, the password will be ignored unless DisablePassword is set | | | | +| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present).
If null, the password will be ignored unless DisablePassword is set.
When set, the secret must follow the `kubernetes.io/basic-auth` format
and contain both a `username` and a `password` field. | | | | | `connectionLimit` *integer* | If the role can log in, this specifies how many concurrent
connections the role can make. `-1` (the default) means no limit. | | -1 | | | `validUntil` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Date and time after which the role's password is no longer valid.
When omitted, the password will never expire (default). | | | | -| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty. | | | | -| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Defaults is `true`. | | true | | +| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty.
Changes to the list are applied to an existing role through
`GRANT` and `REVOKE` statements, not only at role creation. | | | | +| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Default is `true`. | | true | | | `disablePassword` *boolean* | DisablePassword indicates that a role's password should be set to NULL in Postgres | | | | | `superuser` *boolean* | 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`. | | | | | `createdb` *boolean* | 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. | | | | @@ -2071,6 +2284,7 @@ ScheduledBackupStatus defines the observed state of ScheduledBackup | `lastCheckTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | The latest time the schedule | | | | | `lastScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Information when was the last time that backup was successfully scheduled. | | | | | `nextScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Next time we will run a backup | | | | +| `error` *string* | Error is the latest admission validation error | | | | #### SchemaSpec diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.30.0-rc1.mdx b/product_docs/docs/postgres_for_kubernetes/1/pg4k.v1/v1.30.0.mdx similarity index 99% rename from product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.30.0-rc1.mdx rename to product_docs/docs/postgres_for_kubernetes/1/pg4k.v1/v1.30.0.mdx index 59968041ee5..1776c568cd3 100644 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.30.0-rc1.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/pg4k.v1/v1.30.0.mdx @@ -1,6 +1,6 @@ --- -title: API Reference - v1.30.0-rc1 -navTitle: v1.30.0-rc1 +title: API Reference - v1.30.0 +navTitle: v1.30.0 pdfExclude: 'true' --- diff --git a/product_docs/docs/postgres_for_kubernetes/1/postgres_upgrades.mdx b/product_docs/docs/postgres_for_kubernetes/1/postgres_upgrades.mdx index ada5d60639c..905ebb68a74 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/postgres_upgrades.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/postgres_upgrades.mdx @@ -7,15 +7,15 @@ originalFilePath: 'src/postgres_upgrades.md' PostgreSQL upgrades fall into two categories: -- [Minor version upgrades](#minor-version-upgrades) (e.g., from 17.0 to 17.1) -- [Major version upgrades](#major-version-upgrades) (e.g., from 16.x to 17.0) +- [Minor version upgrades](#minor-version-upgrades) (e.g., from 18.0 to 18.1) +- [Major version upgrades](#major-version-upgrades) (e.g., from 16.x to 18.0) ## Minor Version Upgrades PostgreSQL version numbers follow a `major.minor` format. For instance, in -version 17.1: +version 18.1: -- `17` is the major version +- `18` is the major version - `1` is the minor version Minor releases are fully compatible with earlier and later minor releases of @@ -68,7 +68,7 @@ operating system distribution. For example, if your previous version uses a There is a bug in PostgreSQL 17.0 through 17.5 that prevents successful upgrades if the `max_slot_wal_keep_size` parameter is set to any value other than `-1`. The upgrade process will fail with an error related to replication slot configuration. -This issue has been [fixed in PostgreSQL 17.6 and 18beta2 or later versions](https://github.com/postgres/postgres/commit/f36e5774). +This issue has been [fixed in PostgreSQL 17.6 and 18 or later versions](https://github.com/postgres/postgres/commit/f36e5774). If you are using PostgreSQL 17.0 through 17.5, ensure that you upgrade to at least PostgreSQL 17.6 before attempting a major upgrade, or make sure to temporarily set the `max_slot_wal_keep_size` parameter to `-1` in your cluster configuration. @@ -156,6 +156,62 @@ usually possible, without having to perform a full recovery from a backup. Ensure you monitor the process closely and take corrective action if needed. !!! +#### Extensions during a major upgrade + +When a cluster declares image-volume extensions, the upgrade `Job` mounts both +the source-version and the target-version extension images side by side. +Source-version extensions are needed so the old server can start with its +existing shared libraries already in place. +Target-version extensions (built for the new PostgreSQL major) must also be +present so that `pg_upgrade` can properly perform the upgrade to the new major: + +- Source-version extensions are mounted at `/extensions/` (the + steady-state path), so `dynamic_library_path` and `extension_control_path` + GUCs in the old `PGDATA` keep the existing values. + This ensures that, in case of major upgrade failure, a revert to the old + major version will work seamlessly. +- Target-version extensions are temporarily mounted at `/new-extensions/` + just during the upgrade job, and `dynamic_library_path` and `extension_control_path` + are configured accordingly for the `PGDATA` of the new major. + +`LD_LIBRARY_PATH` and `PATH` are extended with both sets, so binaries and +shared objects from either version are reachable. +Environment variables declared via `extensions[].env` obey the rules +described in [Precedence and Conflict Resolution](imagevolume_extensions.md#precedence-and-conflict-resolution). + +!!!note + +Target-version entries are applied **after** source-version entries. When the +same variable is defined for both, the target-version value takes precedence. +!!! + +#### When `pg_upgrade` emits `update_extensions.sql` + +`pg_upgrade` emits an `update_extensions.sql` script inside the `PGDATA` +when a target cluster contains extensions whose `default_version` is +newer than the version `pg_upgrade` left installed. Until that script is +applied, the SQL-level extension metadata in `pg_catalog` lags the +shared libraries actually loaded by the running server. + +The script lives inside the primary pod's `PGDATA`. +You can execute it using the database superuser (`postgres`) to +update those extensions in all databases: + +```sh +PRIMARY=$(kubectl get cluster -o jsonpath='{.status.currentPrimary}') +SCRIPT=/var/lib/postgresql/data/pgdata/update_extensions.sql + +kubectl exec -i "$PRIMARY" -- psql -f "$SCRIPT" +``` + +!!!note + +The script path above assumes the default `PGDATA` location used by the +{{name.ln}} operand images. The operator also logs the resolved path when +`pg_upgrade` emits the script, so check the operator logs if your operand image +uses a different `PGDATA`. +!!! + ### Backup and WAL Archive Considerations When performing a major upgrade, `pg_upgrade` creates a new database system @@ -190,7 +246,7 @@ Before upgrade (PostgreSQL 16): ```yaml spec: - imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:16-minimal-ubi9 + imageName: docker.enterprisedb.com/k8s/postgresql:16-minimal-ubi9 plugins: - name: plugin-barman-cloud enabled: true @@ -203,18 +259,18 @@ To trigger the upgrade, change both `imageName` and `serverName` together: ```yaml spec: - imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:17-minimal-ubi9 + imageName: docker.enterprisedb.com/k8s/postgresql:18-minimal-ubi9 plugins: - name: plugin-barman-cloud enabled: true parameters: destinationPath: s3://my-bucket/ - serverName: cluster-example-pg17 + serverName: cluster-example-pg18 ``` With this configuration, the old archive at `cluster-example-pg16` remains intact for pre-upgrade recovery, while the upgraded cluster writes to -`cluster-example-pg17`. +`cluster-example-pg18`. !!!info The deprecated in-tree `barmanObjectStore` implementation also requires manual @@ -249,8 +305,8 @@ This will return output similar to: PostgreSQL 16.x ... ``` -To upgrade the cluster to version 17, update the `imageName` field by changing -the major version tag from `16` to `17`: +To upgrade the cluster to version 18, update the `imageName` field by changing +the major version tag from `16` to `18`: ```yaml apiVersion: postgresql.k8s.enterprisedb.io/v1 @@ -258,7 +314,7 @@ kind: Cluster metadata: name: cluster-example spec: - imageName: docker.enterprisedb.com/k8s/postgresql:17-minimal-ubi9 + imageName: docker.enterprisedb.com/k8s/postgresql:18-minimal-ubi9 instances: 3 storage: size: 1Gi @@ -275,7 +331,7 @@ spec: - The PVC groups of the replicas (`cluster-example-2` and `cluster-example-3`) are removed. - The primary pod is restarted. - - Two new replicas (`cluster-example-4` and `cluster-example-5`) are + - Two new replicas (`cluster-example-2` and `cluster-example-3`) are re-cloned from the upgraded primary. Once the upgrade is complete, you can verify the new major version by running @@ -288,7 +344,7 @@ kubectl cnp psql cluster-example -- -qAt -c 'SELECT version()' This should now return output similar to: ```console -PostgreSQL 17.x ... +PostgreSQL 18.x ... ``` You can now update the statistics by running `ANALYZE` on the `app` database: diff --git a/product_docs/docs/postgres_for_kubernetes/1/preview_version.mdx b/product_docs/docs/postgres_for_kubernetes/1/preview_version.mdx index 8d9e2a24805..f9883e76ca0 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/preview_version.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/preview_version.mdx @@ -17,13 +17,7 @@ They should only be deployed in staging or dedicated testing environments. ## Current Preview Version -The current preview version is **1.30.0-rc1**. - -For more information on the current preview version and how to test, please view the links below: - - -- [Announcement](/postgres_for_kubernetes/preview/rel_notes/1_30_0-rc1_rel_notes) -- [Documentation](/postgres_for_kubernetes/preview/) +There are currently no preview versions available. ## Purpose of Release Candidates @@ -72,7 +66,7 @@ non-production environment: - **Report Issues:** **Immediately report any issues or unexpected behavior** by opening a GitHub issue and clearly marking it with a **`Release Candidate`** tag or label, along with the RC version number - (e.g., `1.29.0-rc1`). + (e.g., `1.31.0-rc1`). ## Usage Advisory diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_25_9_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_25_9_rel_notes.mdx new file mode 100644 index 00000000000..62149d6e0a7 --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_25_9_rel_notes.mdx @@ -0,0 +1,253 @@ +--- +# IMPORTANT: Do not edit this file directly - it is generated from yaml source. +title: EDB CloudNativePG Cluster 1.25.9 release notes +navTitle: Version 1.25.9 +originalFilePath: product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.25.9_rel_notes.yml +editTarget: originalFilePath +--- + +Released: 29 June 2026 + +This release of EDB CloudNativePG Cluster is part of the LTS series for 1.25.x. +EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support +policy](/postgres_for_kubernetes/1/#long-term-support). + +!!! Warning EDB CloudNativePG Cluster 1.25 approaches End-of-Life. + +Users are encouraged to start planning their upgrade to a newer minor +version before that date. + +!!! + +This release of EDB CloudNativePG Cluster includes the following: + +## Highlights + +The `cluster` reference is now immutable on the `Database`, `Pooler`, +`Publication`, `Subscription`, and `ScheduledBackup` resources. Pointing one +of these objects at a different cluster has no well-defined semantics and +previously left the controllers in an inconsistent state; the update is now +rejected at the API server via a CEL validation rule. +([#10743](https://github.com/cloudnative-pg/cloudnative-pg/pull/10743)) + +## Enhancements + + + + + +
DescriptionAddresses
Added a label selector to the Cluster scale subresource (status.selector), +making a Cluster a valid targetRef for the Vertical Pod Autoscaler (VPA) +and Horizontal Pod Autoscaler (HPA), which can now map a Cluster to its +instance pods. +

Contributed by @sebv004.

+
#8996
The operator now emits a `Warning` `PrimaryStatusCheckFailed` event on the +`Cluster` when the primary pod is `Ready` from the kubelet perspective but the +operator's `/pg/status` check fails and failover is deferred, giving users +visibility into the deferral via `kubectl describe cluster`. +#10509
The operator now reloads a CNPG-i plugin automatically when its pods are +rolled: it watches the `EndpointSlices` backing plugin `Services` and +re-enqueues every cluster using the plugin once the new pods become `Ready`, +so an upgraded plugin is picked up without waiting for the next resync. +#10836
+ + +## Security Fixes + + + + +
DescriptionAddresses
CVE-2026-55769 / GHSA-x8c2-3p4r-v9r6: search_path pinning on +operator-issued connections +

a database owner could plant overloaded built-in operators in the public +schema and alter the search_path so that operator introspection probes, +running as the cluster superuser, resolved those overloads before +pg_catalog, a CWE-426 privilege-escalation chain (same class as +CVE-2018-1058) that could lead to in-pod RCE via COPY ... FROM PROGRAM. +The operator now pins search_path = pg_catalog, public, pg_temp on every +pooled connection so it ships in the startup message and takes precedence over +tenant-controlled defaults.

+
#10774, GHSA-x8c2-3p4r-v9r6
CVE-2026-55765 / GHSA-w3gf-xc94-wvmj: operator-side SCRAM-SHA-256 password +encoding +

the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuing +CREATE/ALTER ROLE ... PASSWORD, so the literal PostgreSQL parses (and that +extensions such as pg_stat_statements or pgaudit may capture) is the SCRAM +verifier rather than the cleartext secret. Pre-hashed (MD5 or SCRAM) values +are forwarded unchanged, and the per-Secret annotation +k8s.enterprisedb.io/passwordPassthrough: "enabled" opts out.

+
#10724, GHSA-w3gf-xc94-wvmj
+ + +## Changes + + + + +
DescriptionAddresses
Updated the default PostgreSQL version to 18.4. +#10719
Updated the Kubernetes versions used to test the operator on public cloud +providers. +#10720, #10563, #11033
+ + +## Bug Fixes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
DescriptionAddresses
Fixed `spec.postgresql.parameters` accepting keys that are not valid +PostgreSQL parameter names, which could inject arbitrary directives into +`postgresql.conf`; key names are now validated by the webhook. +#11029
Fixed declarative `Database`, `Publication`, and `Subscription` objects +reporting a stale primary-side status forever after their cluster was demoted +to a replica; the controller now re-checks the replica condition and watches +the `Cluster` so a demotion is detected promptly. +#10871
Fixed non-sequential pod names (for example `-1`, `-3`) caused by the instance +serial counter being advanced before the corresponding `Job` and PVCs were +created; the bump is now persisted only after those resources exist. +#10491
Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an +existing cluster: with primaryUpdateMethod: switchover the primary could not +be rolled out because a clean demotion needs the archiver sidecar that is +still missing. +

The operator now recreates the primary Pod in place so the sidecar is injected +and archiving resumes. The check also covers plugins that inject the archiver +as a native sidecar (an init container with restartPolicy: Always), such as +the Barman Cloud plugin.

+
#11032, #11059
Fixed a cluster staying in `Setting up primary` indefinitely when the +instance-creation Job exhausted its backoff limit; the operator now detects +the terminal Job failure and marks the cluster unrecoverable, naming the +failed Job and pointing to its logs. +#11035
Fixed deletion of a Database, Publication, or Subscription getting stuck +in Terminating on a replica cluster, where the replica gate ran before the +finalizer reconciler and the finalizer was never released. +

On a replica the PostgreSQL object is left to the primary cluster.

+
#10853
Fixed a conflicting duplicate `Database` or `Subscription` with a `delete` +reclaim policy dropping the PostgreSQL object owned by the surviving CR; the +drop is now gated on a recorded reconciliation. +#10870
Fixed the postgres superuser being left locked out after superuser access +was disabled and then re-enabled, because the cached secret version was not +invalidated and the password was never re-applied. +

Diagnosed by @mhartmann-jaconi.

+
#10834
Fixed resource leaks when concurrent Backup objects raced: backups now run +in strict creation-time order, so an already-executing backup is never +preempted by a newer one and its replication slot and PostgreSQL session are +no longer orphaned on the primary. +

Contributed by @GabriFedi97.

+
#10747
Fixed role reconciliation clearing the password on a PostgreSQL role when the +referenced Secret could not be fetched; the role is now left untouched until +the Secret becomes available, and per-action errors are aggregated for better +visibility. +#10053
Fixed a bootstrap failure where a metrics-exporter setup error (commonly a +duplicate-key race with the controller) rolled back streaming_replica +creation and wedged replica joins. +

The metrics-exporter step now runs in a separate transaction. Contributed by +@BlaiseAntony.

+
#10749
Fixed a `ScheduledBackup` controller loop that occurred when a `Backup` was +created but its status patch never landed; the controller now adopts an +existing `Backup` for the next iteration instead of looping on +`AlreadyExists`. +#10612
Fixed bootstrap log handling so that all named log pipes (`postgres`, +`postgres.csv`, and `postgres.json`) get consumers during +`WithActiveInstance`, preventing regular files from being created in place of +the named pipes. +#10043
Fixed generation of invalid IPv6 URLs by wrapping the address in square +brackets. +

Contributed by @Infinoid.

+
#10682
Fixed an external cluster plugin still being treated as active when its +configuration set `enabled: false`. +#10932
Fixed a race during bootstrap recovery from an object store where the restore +job could read a stale Cluster (primary not yet recorded and timeline still +unset) and have its .history files rejected by the split-brain guard. +

When this happened, recovery stopped at the base backup's timeline and +silently dropped transactions committed on later timelines. History files are +now allowed while the cluster timeline is unset. Contributed by @dennispidun.

+
#10818
Fixed a cache race during cluster creation when the server and client CA +resolve to the same Secret (the default): a stale informer cache triggered a +redundant Create that failed with AlreadyExists and could leave the +cluster stuck in Unable to create required cluster objects. +

The operator now reuses the already-fetched CA Secret when the names match.

+
#10989
Fixed the `pg_basebackup` bootstrap path overwriting or failing on a +pre-existing `PGDATA` (for example after a replica Pod restart) by enforcing +the same pre-flight directory check already applied by the other bootstrap +methods; this also protects statically provisioned PVCs from being silently +overwritten. +#11006
Fixed the Cluster phase flapping between Healthy and a plugin-failure +phase when a post-reconcile plugin hook returned an error; the Healthy phase +is now registered as the last step of a successful reconciliation, so a loop +that ends in a plugin error never reports Healthy. +

Contributed by @GabriFedi97.

+
#10421
Fixed stale certificate data and partial reads after an external server's +Secret was rotated (for example a CA bundle shrinking from two certificates to +one): the file is now written atomically, so libpq always reads either the old +or the new value, never a mix. +

Contributed by @Anand-240.

+
#10975
Fixed plugin connectivity to use the plugin Service FQDN instead of its +short name, avoiding failures when a cluster-level proxy is automatically +injected into pods. +

Contributed by @kdautrey.

+
#10921
Fixed excessive operator log noise from the per-request `Cluster` +create/update validation webhook messages, now logged at `debug` instead of +`info`. +#10984
Fixed a first-primary bootstrap deadlock where a status-patch conflict after +the data PVC was created but before the initialization Job was started left +the orphan Pending PVC counted as an instance, blocking the bootstrap gate; +the PVC-state reconciler now recreates the bootstrap Job reusing the assigned +serial. +#11039
Fixed external cluster names and secret selector references being joined into +filesystem paths without validation, letting a .. component or path +separator escape the external secrets directory when the instance manager +dumps connection material; these values are now rejected at the validating +webhook and re-checked at the write site. +

Reported by @r0binak.

+
#11045
Fixed a declarative VolumeSnapshot backup being permanently marked as failed +when a stale cache made the operator re-create a snapshot it had already +provisioned, failing with AlreadyExists. +

The operator now tolerates the collision when the existing snapshot carries +this backup's label and adopts it; a collision with a foreign snapshot still +surfaces as an error.

+
#11071
Fixed a volume snapshot backup being discarded on a transient instance-manager +connection error (for example a dial timeout from a brief pod-network +disruption) during the finalize step, even when its snapshots were already +provisioned; such network errors are now retried instead of treated as +terminal. +#11069
Fixed a replica switchover losing its `status.demotionToken` when a reconcile +was requeued between storing the token and cleaning up the transition metadata +(for example a cleanup patch failing against a flaky webhook); the empty +no-change token is no longer patched back over the stored value. +#11075
Fixed kubectl cnp psql on Windows, where execution relied on a Unix-only +system call and failed with "not supported by windows"; Windows now launches +kubectl exec as a child process. +

Contributed by @Utkarsh-sharma47.

+
#10972
Fixed an unbounded memory leak in kubectl cnp logs -f on busy clusters, +where a per-log-group timer was never released; timers are now reused across +iterations. +

Contributed by @Anand-240.

+
#10976
+ + diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_28_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_28_4_rel_notes.mdx new file mode 100644 index 00000000000..7f119704ba9 --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_28_4_rel_notes.mdx @@ -0,0 +1,258 @@ +--- +# IMPORTANT: Do not edit this file directly - it is generated from yaml source. +title: EDB CloudNativePG Cluster 1.28.4 release notes +navTitle: Version 1.28.4 +originalFilePath: product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.28.4_rel_notes.yml +editTarget: originalFilePath +--- + +Released: 29 June 2026 + +This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: + +## Highlights + +Updated the deprecation notice for native (in-tree) Barman Cloud support to +reflect that it will now be removed in EDB Postgres for Kubernetes 1.31.0, +rather than 1.30.0. Users are still encouraged to migrate to the Barman Cloud +Plugin. +([#11083](https://github.com/cloudnative-pg/cloudnative-pg/pull/11083)) + +The `cluster` reference is now immutable on the `Database`, `Pooler`, +`Publication`, `Subscription`, and `ScheduledBackup` resources. Pointing one +of these objects at a different cluster has no well-defined semantics and +previously left the controllers in an inconsistent state; the update is now +rejected at the API server via a CEL validation rule. +([#10743](https://github.com/cloudnative-pg/cloudnative-pg/pull/10743)) + +## Enhancements + + + + + +
DescriptionAddresses
Added a label selector to the Cluster scale subresource (status.selector), +making a Cluster a valid targetRef for the Vertical Pod Autoscaler (VPA) +and Horizontal Pod Autoscaler (HPA), which can now map a Cluster to its +instance pods. +

Contributed by @sebv004.

+
#8996
The operator now emits a `Warning` `PrimaryStatusCheckFailed` event on the +`Cluster` when the primary pod is `Ready` from the kubelet perspective but the +operator's `/pg/status` check fails and failover is deferred, giving users +visibility into the deferral via `kubectl describe cluster`. +#10509
The operator now reloads a CNPG-i plugin automatically when its pods are +rolled: it watches the `EndpointSlices` backing plugin `Services` and +re-enqueues every cluster using the plugin once the new pods become `Ready`, +so an upgraded plugin is picked up without waiting for the next resync. +#10836
+ + +## Security Fixes + + + + +
DescriptionAddresses
CVE-2026-55769 / GHSA-x8c2-3p4r-v9r6: search_path pinning on +operator-issued connections +

a database owner could plant overloaded built-in operators in the public +schema and alter the search_path so that operator introspection probes, +running as the cluster superuser, resolved those overloads before +pg_catalog, a CWE-426 privilege-escalation chain (same class as +CVE-2018-1058) that could lead to in-pod RCE via COPY ... FROM PROGRAM. +The operator now pins search_path = pg_catalog, public, pg_temp on every +pooled connection so it ships in the startup message and takes precedence over +tenant-controlled defaults.

+
#10774, GHSA-x8c2-3p4r-v9r6
CVE-2026-55765 / GHSA-w3gf-xc94-wvmj: operator-side SCRAM-SHA-256 password +encoding +

the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuing +CREATE/ALTER ROLE ... PASSWORD, so the literal PostgreSQL parses (and that +extensions such as pg_stat_statements or pgaudit may capture) is the SCRAM +verifier rather than the cleartext secret. Pre-hashed (MD5 or SCRAM) values +are forwarded unchanged, and the per-Secret annotation +k8s.enterprisedb.io/passwordPassthrough: "enabled" opts out.

+
#10724, GHSA-w3gf-xc94-wvmj
+ + +## Changes + + + + + +
DescriptionAddresses
Added support for Kubernetes 1.35 and enabled unit tests on Kubernetes 1.36. +#10900
Updated the default PostgreSQL version to 18.4. +#10719
Updated the Kubernetes versions used to test the operator on public cloud +providers. +#10720, #10563, #11033
+ + +## Bug Fixes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
DescriptionAddresses
Fixed `spec.postgresql.parameters` accepting keys that are not valid +PostgreSQL parameter names, which could inject arbitrary directives into +`postgresql.conf`; key names are now validated by the webhook. +#11029
Fixed declarative `Database`, `Publication`, and `Subscription` objects +reporting a stale primary-side status forever after their cluster was demoted +to a replica; the controller now re-checks the replica condition and watches +the `Cluster` so a demotion is detected promptly. +#10871
Fixed non-sequential pod names (for example `-1`, `-3`) caused by the instance +serial counter being advanced before the corresponding `Job` and PVCs were +created; the bump is now persisted only after those resources exist. +#10491
Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an +existing cluster: with primaryUpdateMethod: switchover the primary could not +be rolled out because a clean demotion needs the archiver sidecar that is +still missing. +

The operator now recreates the primary Pod in place so the sidecar is injected +and archiving resumes. The check also covers plugins that inject the archiver +as a native sidecar (an init container with restartPolicy: Always), such as +the Barman Cloud plugin.

+
#11032, #11059
Fixed a cluster staying in `Setting up primary` indefinitely when the +instance-creation Job exhausted its backoff limit; the operator now detects +the terminal Job failure and marks the cluster unrecoverable, naming the +failed Job and pointing to its logs. +#11035
Fixed deletion of a Database, Publication, or Subscription getting stuck +in Terminating on a replica cluster, where the replica gate ran before the +finalizer reconciler and the finalizer was never released. +

On a replica the PostgreSQL object is left to the primary cluster.

+
#10853
Fixed a conflicting duplicate `Database` or `Subscription` with a `delete` +reclaim policy dropping the PostgreSQL object owned by the surviving CR; the +drop is now gated on a recorded reconciliation. +#10870
Fixed the postgres superuser being left locked out after superuser access +was disabled and then re-enabled, because the cached secret version was not +invalidated and the password was never re-applied. +

Diagnosed by @mhartmann-jaconi.

+
#10834
Fixed backups getting stuck in the `started` phase when the instance manager +running them was restarted (for example by the in-place upgrade following an +operator upgrade) before the backup reached `running`; the reconciliation is +now rescheduled so the lost session is detected. +#10859
Fixed resource leaks when concurrent Backup objects raced: backups now run +in strict creation-time order, so an already-executing backup is never +preempted by a newer one and its replication slot and PostgreSQL session are +no longer orphaned on the primary. +

Contributed by @GabriFedi97.

+
#10747
Fixed role reconciliation clearing the password on a PostgreSQL role when the +referenced Secret could not be fetched; the role is now left untouched until +the Secret becomes available, and per-action errors are aggregated for better +visibility. +#10053
Fixed a bootstrap failure where a metrics-exporter setup error (commonly a +duplicate-key race with the controller) rolled back streaming_replica +creation and wedged replica joins. +

The metrics-exporter step now runs in a separate transaction. Contributed by +@BlaiseAntony.

+
#10749
Fixed a `ScheduledBackup` controller loop that occurred when a `Backup` was +created but its status patch never landed; the controller now adopts an +existing `Backup` for the next iteration instead of looping on +`AlreadyExists`. +#10612
Fixed a nil-pointer panic when reconciling a `Pooler` whose `Cluster` has been +deleted. +#10667
Fixed bootstrap log handling so that all named log pipes (`postgres`, +`postgres.csv`, and `postgres.json`) get consumers during +`WithActiveInstance`, preventing regular files from being created in place of +the named pipes. +#10043
Fixed generation of invalid IPv6 URLs by wrapping the address in square +brackets. +

Contributed by @Infinoid.

+
#10682
Fixed an external cluster plugin still being treated as active when its +configuration set `enabled: false`. +#10932
Fixed a race during bootstrap recovery from an object store where the restore +job could read a stale Cluster (primary not yet recorded and timeline still +unset) and have its .history files rejected by the split-brain guard. +

When this happened, recovery stopped at the base backup's timeline and +silently dropped transactions committed on later timelines. History files are +now allowed while the cluster timeline is unset. Contributed by @dennispidun.

+
#10818
Fixed a cache race during cluster creation when the server and client CA +resolve to the same Secret (the default): a stale informer cache triggered a +redundant Create that failed with AlreadyExists and could leave the +cluster stuck in Unable to create required cluster objects. +

The operator now reuses the already-fetched CA Secret when the names match.

+
#10989
Fixed the `pg_basebackup` bootstrap path overwriting or failing on a +pre-existing `PGDATA` (for example after a replica Pod restart) by enforcing +the same pre-flight directory check already applied by the other bootstrap +methods; this also protects statically provisioned PVCs from being silently +overwritten. +#11006
Fixed the Cluster phase flapping between Healthy and a plugin-failure +phase when a post-reconcile plugin hook returned an error; the Healthy phase +is now registered as the last step of a successful reconciliation, so a loop +that ends in a plugin error never reports Healthy. +

Contributed by @GabriFedi97.

+
#10421
Fixed stale certificate data and partial reads after an external server's +Secret was rotated (for example a CA bundle shrinking from two certificates to +one): the file is now written atomically, so libpq always reads either the old +or the new value, never a mix. +

Contributed by @Anand-240.

+
#10975
Fixed plugin connectivity to use the plugin Service FQDN instead of its +short name, avoiding failures when a cluster-level proxy is automatically +injected into pods. +

Contributed by @kdautrey.

+
#10921
Fixed excessive operator log noise from the per-request `Cluster` +create/update validation webhook messages, now logged at `debug` instead of +`info`. +#10984
Fixed a first-primary bootstrap deadlock where a status-patch conflict after +the data PVC was created but before the initialization Job was started left +the orphan Pending PVC counted as an instance, blocking the bootstrap gate; +the PVC-state reconciler now recreates the bootstrap Job reusing the assigned +serial. +#11039
Fixed external cluster names and secret selector references being joined into +filesystem paths without validation, letting a .. component or path +separator escape the external secrets directory when the instance manager +dumps connection material; these values are now rejected at the validating +webhook and re-checked at the write site. +

Reported by @r0binak.

+
#11045
Fixed a declarative VolumeSnapshot backup being permanently marked as failed +when a stale cache made the operator re-create a snapshot it had already +provisioned, failing with AlreadyExists. +

The operator now tolerates the collision when the existing snapshot carries +this backup's label and adopts it; a collision with a foreign snapshot still +surfaces as an error.

+
#11071
Fixed a volume snapshot backup being discarded on a transient instance-manager +connection error (for example a dial timeout from a brief pod-network +disruption) during the finalize step, even when its snapshots were already +provisioned; such network errors are now retried instead of treated as +terminal. +#11069
Fixed a replica switchover losing its `status.demotionToken` when a reconcile +was requeued between storing the token and cleaning up the transition metadata +(for example a cleanup patch failing against a flaky webhook); the empty +no-change token is no longer patched back over the stored value. +#11075
Fixed kubectl cnp psql on Windows, where execution relied on a Unix-only +system call and failed with "not supported by windows"; Windows now launches +kubectl exec as a child process. +

Contributed by @Utkarsh-sharma47.

+
#10972
Fixed an unbounded memory leak in kubectl cnp logs -f on busy clusters, +where a per-log-group timer was never released; timers are now reused across +iterations. +

Contributed by @Anand-240.

+
#10976
+ + diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_29_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_29_2_rel_notes.mdx new file mode 100644 index 00000000000..4ee2bf1e6c9 --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_29_2_rel_notes.mdx @@ -0,0 +1,275 @@ +--- +# IMPORTANT: Do not edit this file directly - it is generated from yaml source. +title: EDB CloudNativePG Cluster 1.29.2 release notes +navTitle: Version 1.29.2 +originalFilePath: product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.29.2_rel_notes.yml +editTarget: originalFilePath +--- + +Released: 29 June 2026 + +This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: + +## Highlights + +Updated the deprecation notice for native (in-tree) Barman Cloud support to +reflect that it will now be removed in EDB Postgres for Kubernetes 1.31.0, +rather than 1.30.0. Users are still encouraged to migrate to the Barman Cloud +Plugin. +([#11083](https://github.com/cloudnative-pg/cloudnative-pg/pull/11083)) + +The `cluster` reference is now immutable on the `Database`, `Pooler`, +`Publication`, `Subscription`, and `ScheduledBackup` resources. Pointing one +of these objects at a different cluster has no well-defined semantics and +previously left the controllers in an inconsistent state; the update is now +rejected at the API server via a CEL validation rule. +([#10743](https://github.com/cloudnative-pg/cloudnative-pg/pull/10743)) + +## Enhancements + + + + + + +
DescriptionAddresses
Enabled pg_upgrade in-place major upgrades to PostgreSQL 19 or later for +clusters that use Image Volume extensions, building on the extension-path +support added to pg_upgrade in PostgreSQL 19. +

During the upgrade Job, the source- and target-version extension images are +mounted side by side, so the old server keeps its libraries and a failed +upgrade reverts cleanly.

+
#10366
Added a label selector to the Cluster scale subresource (status.selector), +making a Cluster a valid targetRef for the Vertical Pod Autoscaler (VPA) +and Horizontal Pod Autoscaler (HPA), which can now map a Cluster to its +instance pods. +

Contributed by @sebv004.

+
#8996
The operator now emits a `Warning` `PrimaryStatusCheckFailed` event on the +`Cluster` when the primary pod is `Ready` from the kubelet perspective but the +operator's `/pg/status` check fails and failover is deferred, giving users +visibility into the deferral via `kubectl describe cluster`. +#10509
The operator now reloads a CNPG-i plugin automatically when its pods are +rolled: it watches the `EndpointSlices` backing plugin `Services` and +re-enqueues every cluster using the plugin once the new pods become `Ready`, +so an upgraded plugin is picked up without waiting for the next resync. +#10836
+ + +## Security Fixes + + + + +
DescriptionAddresses
CVE-2026-55769 / GHSA-x8c2-3p4r-v9r6: search_path pinning on +operator-issued connections +

a database owner could plant overloaded built-in operators in the public +schema and alter the search_path so that operator introspection probes, +running as the cluster superuser, resolved those overloads before +pg_catalog, a CWE-426 privilege-escalation chain (same class as +CVE-2018-1058) that could lead to in-pod RCE via COPY ... FROM PROGRAM. +The operator now pins search_path = pg_catalog, public, pg_temp on every +pooled connection so it ships in the startup message and takes precedence over +tenant-controlled defaults.

+
#10774, GHSA-x8c2-3p4r-v9r6
CVE-2026-55765 / GHSA-w3gf-xc94-wvmj: operator-side SCRAM-SHA-256 password +encoding +

the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuing +CREATE/ALTER ROLE ... PASSWORD, so the literal PostgreSQL parses (and that +extensions such as pg_stat_statements or pgaudit may capture) is the SCRAM +verifier rather than the cleartext secret. Pre-hashed (MD5 or SCRAM) values +are forwarded unchanged, and the per-Secret annotation +k8s.enterprisedb.io/passwordPassthrough: "enabled" opts out.

+
#10724, GHSA-w3gf-xc94-wvmj
+ + +## Changes + + + + + +
DescriptionAddresses
Added support for Kubernetes 1.36. +#10900
Updated the default PostgreSQL version to 18.4. +#10719
Updated the Kubernetes versions used to test the operator on public cloud +providers. +#10720, #10563, #11033
+ + +## Bug Fixes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
DescriptionAddresses
Fixed `spec.postgresql.parameters` accepting keys that are not valid +PostgreSQL parameter names, which could inject arbitrary directives into +`postgresql.conf`; key names are now validated by the webhook. +#11029
Fixed declarative `Database`, `Publication`, and `Subscription` objects +reporting a stale primary-side status forever after their cluster was demoted +to a replica; the controller now re-checks the replica condition and watches +the `Cluster` so a demotion is detected promptly. +#10871
Fixed non-sequential pod names (for example `-1`, `-3`) caused by the instance +serial counter being advanced before the corresponding `Job` and PVCs were +created; the bump is now persisted only after those resources exist. +#10491
Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an +existing cluster: with primaryUpdateMethod: switchover the primary could not +be rolled out because a clean demotion needs the archiver sidecar that is +still missing. +

The operator now recreates the primary Pod in place so the sidecar is injected +and archiving resumes. The check also covers plugins that inject the archiver +as a native sidecar (an init container with restartPolicy: Always), such as +the Barman Cloud plugin.

+
#11032, #11059
Fixed a cluster staying in `Setting up primary` indefinitely when the +instance-creation Job exhausted its backoff limit; the operator now detects +the terminal Job failure and marks the cluster unrecoverable, naming the +failed Job and pointing to its logs. +#11035
Fixed deletion of a Database, Publication, or Subscription getting stuck +in Terminating on a replica cluster, where the replica gate ran before the +finalizer reconciler and the finalizer was never released. +

On a replica the PostgreSQL object is left to the primary cluster.

+
#10853
Fixed a conflicting duplicate `Database` or `Subscription` with a `delete` +reclaim policy dropping the PostgreSQL object owned by the surviving CR; the +drop is now gated on a recorded reconciliation. +#10870
Fixed the postgres superuser being left locked out after superuser access +was disabled and then re-enabled, because the cached secret version was not +invalidated and the password was never re-applied. +

Diagnosed by @mhartmann-jaconi.

+
#10834
Fixed backups getting stuck in the `started` phase when the instance manager +running them was restarted (for example by the in-place upgrade following an +operator upgrade) before the backup reached `running`; the reconciliation is +now rescheduled so the lost session is detected. +#10859
Fixed exec/attach streaming to negotiate WebSocket with a SPDY fallback, +restoring compatibility both with Kubernetes versions that have removed SPDY +and with platforms such as OpenShift that reject WebSocket exec upgrades. +

Contributed by @bartscheers.

+
#10876, #10933
Fixed resource leaks when concurrent Backup objects raced: backups now run +in strict creation-time order, so an already-executing backup is never +preempted by a newer one and its replication slot and PostgreSQL session are +no longer orphaned on the primary. +

Contributed by @GabriFedi97.

+
#10747
Fixed role reconciliation clearing the password on a PostgreSQL role when the +referenced Secret could not be fetched; the role is now left untouched until +the Secret becomes available, and per-action errors are aggregated for better +visibility. +#10053
Fixed a bootstrap failure where a metrics-exporter setup error (commonly a +duplicate-key race with the controller) rolled back streaming_replica +creation and wedged replica joins. +

The metrics-exporter step now runs in a separate transaction. Contributed by +@BlaiseAntony.

+
#10749
Fixed a `ScheduledBackup` controller loop that occurred when a `Backup` was +created but its status patch never landed; the controller now adopts an +existing `Backup` for the next iteration instead of looping on +`AlreadyExists`. +#10612
Fixed a nil-pointer panic when reconciling a `Pooler` whose `Cluster` has been +deleted. +#10667
Fixed bootstrap log handling so that all named log pipes (`postgres`, +`postgres.csv`, and `postgres.json`) get consumers during +`WithActiveInstance`, preventing regular files from being created in place of +the named pipes. +#10043
Fixed generation of invalid IPv6 URLs by wrapping the address in square +brackets. +

Contributed by @Infinoid.

+
#10682
Fixed an external cluster plugin still being treated as active when its +configuration set `enabled: false`. +#10932
Fixed a race during bootstrap recovery from an object store where the restore +job could read a stale Cluster (primary not yet recorded and timeline still +unset) and have its .history files rejected by the split-brain guard. +

When this happened, recovery stopped at the base backup's timeline and +silently dropped transactions committed on later timelines. History files are +now allowed while the cluster timeline is unset. Contributed by @dennispidun.

+
#10818
Fixed a cache race during cluster creation when the server and client CA +resolve to the same Secret (the default): a stale informer cache triggered a +redundant Create that failed with AlreadyExists and could leave the +cluster stuck in Unable to create required cluster objects. +

The operator now reuses the already-fetched CA Secret when the names match.

+
#10989
Fixed the `pg_basebackup` bootstrap path overwriting or failing on a +pre-existing `PGDATA` (for example after a replica Pod restart) by enforcing +the same pre-flight directory check already applied by the other bootstrap +methods; this also protects statically provisioned PVCs from being silently +overwritten. +#11006
Fixed the Cluster phase flapping between Healthy and a plugin-failure +phase when a post-reconcile plugin hook returned an error; the Healthy phase +is now registered as the last step of a successful reconciliation, so a loop +that ends in a plugin error never reports Healthy. +

Contributed by @GabriFedi97.

+
#10421
Fixed stale certificate data and partial reads after an external server's +Secret was rotated (for example a CA bundle shrinking from two certificates to +one): the file is now written atomically, so libpq always reads either the old +or the new value, never a mix. +

Contributed by @Anand-240.

+
#10975
Fixed plugin connectivity to use the plugin Service FQDN instead of its +short name, avoiding failures when a cluster-level proxy is automatically +injected into pods. +

Contributed by @kdautrey.

+
#10921
Fixed excessive operator log noise from the per-request `Cluster` +create/update validation webhook messages, now logged at `debug` instead of +`info`. +#10984
Fixed a first-primary bootstrap deadlock where a status-patch conflict after +the data PVC was created but before the initialization Job was started left +the orphan Pending PVC counted as an instance, blocking the bootstrap gate; +the PVC-state reconciler now recreates the bootstrap Job reusing the assigned +serial. +#11039
Fixed external cluster names and secret selector references being joined into +filesystem paths without validation, letting a .. component or path +separator escape the external secrets directory when the instance manager +dumps connection material; these values are now rejected at the validating +webhook and re-checked at the write site. +

Reported by @r0binak.

+
#11045
Fixed a backup getting stuck in pending forever: the concurrent-backup gate +ran on every reconcile and could overwrite an already-completed phase written +asynchronously by the instance manager. +

The gate now runs only while the backup phase is still unset or pending.

+
#11056
Fixed a declarative VolumeSnapshot backup being permanently marked as failed +when a stale cache made the operator re-create a snapshot it had already +provisioned, failing with AlreadyExists. +

The operator now tolerates the collision when the existing snapshot carries +this backup's label and adopts it; a collision with a foreign snapshot still +surfaces as an error.

+
#11071
Fixed a volume snapshot backup being discarded on a transient instance-manager +connection error (for example a dial timeout from a brief pod-network +disruption) during the finalize step, even when its snapshots were already +provisioned; such network errors are now retried instead of treated as +terminal. +#11069
Fixed a replica switchover losing its `status.demotionToken` when a reconcile +was requeued between storing the token and cleaning up the transition metadata +(for example a cleanup patch failing against a flaky webhook); the empty +no-change token is no longer patched back over the stored value. +#11075
Fixed kubectl cnp psql on Windows, where execution relied on a Unix-only +system call and failed with "not supported by windows"; Windows now launches +kubectl exec as a child process. +

Contributed by @Utkarsh-sharma47.

+
#10972
Fixed an unbounded memory leak in kubectl cnp logs -f on busy clusters, +where a per-log-group timer was never released; timers are now reused across +iterations. +

Contributed by @Anand-240.

+
#10976
+ + diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_30_0-rc1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_30_0_rel_notes.mdx similarity index 59% rename from product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_30_0-rc1_rel_notes.mdx rename to product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_30_0_rel_notes.mdx index f308c3b7e39..9b3e586a4da 100644 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_30_0-rc1_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_30_0_rel_notes.mdx @@ -1,17 +1,23 @@ --- # IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.30.0-rc1 release notes -navTitle: Version 1.30.0-rc1 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.30.0_rel_notes.yml +title: EDB CloudNativePG Cluster 1.30.0 release notes +navTitle: Version 1.30.0 +originalFilePath: product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.30.0_rel_notes.yml editTarget: originalFilePath --- -Released: 19 June 2026 +Released: 29 June 2026 This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: ## Highlights +Updated the deprecation notice for native (in-tree) Barman Cloud support to +reflect that it will now be removed in EDB Postgres for Kubernetes 1.31.0, +rather than 1.30.0. Users are still encouraged to migrate to the Barman Cloud +Plugin. +([#11083](https://github.com/cloudnative-pg/cloudnative-pg/pull/11083)) + The `cluster` reference is now immutable on the `Database`, `Pooler`, `Publication`, `Subscription`, and `ScheduledBackup` resources. Pointing one of these objects at a different cluster has no well-defined semantics and @@ -27,8 +33,8 @@ rejected at the API server via a CEL validation rule. a mutex serializing primary promotion: the instance manager must hold the lease before acting as primary and releases it on clean shutdown so replicas can promote without waiting for the full TTL. Timings are configurable via the -new .spec.primaryLease stanza. The lease is a promotion gate, not a fence — -primary isolation remains responsible for fencing.

+new .spec.primaryLease stanza. The lease is a promotion gate, not a fence. +Primary isolation remains responsible for fencing.

#10627
DatabaseRole CRD for declarative role management

introduced a DatabaseRole custom resource that manages a PostgreSQL role as @@ -57,7 +63,7 @@ centralizing PgBouncer image management. When a catalog entry is updated, all referencing Poolers are automatically reconciled and roll out the new image without any change to their spec. The resolved image is reported in status.image, and a new status.phase (active, paused, inactive, or -failed) — also surfaced as a Phase column in kubectl get pooler — +failed), also surfaced as a Phase column in kubectl get pooler, summarizes the lifecycle.

#10568 @@ -123,32 +129,38 @@ the resource status instead of failing silently later.

## Security Fixes - - - + + +
DescriptionAddresses
search_path pinning on operator-issued connections +
CVE-2026-55769 / GHSA-x8c2-3p4r-v9r6: search_path pinning on +operator-issued connections

a database owner could plant overloaded built-in operators in the public schema and alter the search_path so that operator introspection probes, -running as the cluster superuser, resolved those overloads before pg_catalog -— a CWE-426 privilege-escalation chain (same class as CVE-2018-1058) that -could lead to in-pod RCE via COPY ... FROM PROGRAM. The operator now pins -search_path = pg_catalog, public, pg_temp on every pooled connection so it -ships in the startup message and takes precedence over tenant-controlled -defaults.

-
#10774
Authenticated operator-to-instance-manager calls -

the instance manager's remote webserver previously accepted unauthenticated -requests, so any process on the pod network could trigger backups, instance -manager upgrades, or WAL archival. The operator now generates an in-memory -ECDSA P-256 client certificate at startup and reconciles its SHA-256 -fingerprint into the cluster status; the instance manager rejects requests to -sensitive endpoints that do not present a matching certificate.

-
#10579
Operator-side SCRAM-SHA-256 password encoding +running as the cluster superuser, resolved those overloads before +pg_catalog, a CWE-426 privilege-escalation chain (same class as +CVE-2018-1058) that could lead to in-pod RCE via COPY ... FROM PROGRAM. +The operator now pins search_path = pg_catalog, public, pg_temp on every +pooled connection so it ships in the startup message and takes precedence over +tenant-controlled defaults.

+
#10774, GHSA-x8c2-3p4r-v9r6
GHSA-7qwx-x8ff-3px9: authenticated operator-to-instance-manager calls +

the instance manager's remote webserver relied on network isolation rather +than authentication for its operator-only control endpoints, so any party able +to reach the pod's status port could invoke them, disrupting backup +orchestration and WAL archival and reading operational metadata. (The upgrade +endpoint is SHA-256-pinned, so this did not permit arbitrary code execution.) +The operator now generates an in-memory ECDSA P-256 client certificate at +startup and reconciles its SHA-256 fingerprint into the cluster status; the +instance manager rejects requests to sensitive endpoints that do not present a +matching certificate. This hardening is not backported; earlier releases +should continue to restrict the status port with a NetworkPolicy.

+
#10579, GHSA-7qwx-x8ff-3px9
CVE-2026-55765 / GHSA-w3gf-xc94-wvmj: operator-side SCRAM-SHA-256 password +encoding

the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuing CREATE/ALTER ROLE ... PASSWORD, so the literal PostgreSQL parses (and that extensions such as pg_stat_statements or pgaudit may capture) is the SCRAM verifier rather than the cleartext secret. Pre-hashed (MD5 or SCRAM) values are forwarded unchanged, and the per-Secret annotation k8s.enterprisedb.io/passwordPassthrough: "enabled" opts out.

-
#10724
#10724, GHSA-w3gf-xc94-wvmj
@@ -161,7 +173,7 @@ are forwarded unchanged, and the per-Secret annotation #10719 Updated the Kubernetes versions used to test the operator on public cloud providers. -#10720, #10563 +#10720, #10563, #11033 @@ -245,6 +257,111 @@ unset) and have its .history files rejected by the split-brain guar silently dropped transactions committed on later timelines. History files are now allowed while the cluster timeline is unset. Contributed by @dennispidun.

#10818 +
Fixed a race where deleting an instance's PVCs could leave the instance +permanently stuck: if the data PVC was removed while a WAL PVC was still +terminating, the operator recreated the instance bound to the terminating +volume, leaving the Pod unschedulable and blocking all further reconciliation. +

The operator now waits for terminating PVCs to be fully removed before +recreating or reattaching an instance, and surfaces the wait through a log +line and the cluster phase.

+
#11017 +
Fixed a cache race during cluster creation when the server and client CA +resolve to the same Secret (the default): a stale informer cache triggered a +redundant Create that failed with AlreadyExists and could leave the +cluster stuck in Unable to create required cluster objects. +

The operator now reuses the already-fetched CA Secret when the names match.

+
#10989 +Fixed the `pg_basebackup` bootstrap path overwriting or failing on a +pre-existing `PGDATA` (for example after a replica Pod restart) by enforcing +the same pre-flight directory check already applied by the other bootstrap +methods; this also protects statically provisioned PVCs from being silently +overwritten. +#11006 +
Fixed the Cluster phase flapping between Healthy and a plugin-failure +phase when a post-reconcile plugin hook returned an error; the Healthy phase +is now registered as the last step of a successful reconciliation, so a loop +that ends in a plugin error never reports Healthy. +

Contributed by @GabriFedi97.

+
#10421 +
Fixed stale certificate data and partial reads after an external server's +Secret was rotated (for example a CA bundle shrinking from two certificates to +one): the file is now written atomically, so libpq always reads either the old +or the new value, never a mix. +

Contributed by @Anand-240.

+
#10975 +
Fixed plugin connectivity to use the plugin Service FQDN instead of its +short name, avoiding failures when a cluster-level proxy is automatically +injected into pods. +

Contributed by @kdautrey.

+
#10921 +Fixed excessive operator log noise from the per-request `Cluster` +create/update validation webhook messages, now logged at `debug` instead of +`info`. +#10984 +Fixed `spec.postgresql.parameters` accepting keys that are not valid +PostgreSQL parameter names, which could inject arbitrary directives into +`postgresql.conf`; key names are now validated by the webhook. +#11029 +
Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an +existing cluster: with primaryUpdateMethod: switchover the primary could not +be rolled out because a clean demotion needs the archiver sidecar that is +still missing. +

The operator now recreates the primary Pod in place so the sidecar is injected +and archiving resumes. The check also covers plugins that inject the archiver +as a native sidecar (an init container with restartPolicy: Always), such as +the Barman Cloud plugin.

+
#11032, #11059 +Fixed a cluster staying in `Setting up primary` indefinitely when the +instance-creation Job exhausted its backoff limit; the operator now detects +the terminal Job failure and marks the cluster unrecoverable, naming the +failed Job and pointing to its logs. +#11035 +Fixed a first-primary bootstrap deadlock where a status-patch conflict after +the data PVC was created but before the initialization Job was started left +the orphan Pending PVC counted as an instance, blocking the bootstrap gate; +the PVC-state reconciler now recreates the bootstrap Job reusing the assigned +serial. +#11039 +
Fixed external cluster names and secret selector references being joined into +filesystem paths without validation, letting a .. component or path +separator escape the external secrets directory when the instance manager +dumps connection material; these values are now rejected at the validating +webhook and re-checked at the write site. +

Reported by @r0binak.

+
#11045 +
Fixed a backup getting stuck in pending forever: the concurrent-backup gate +ran on every reconcile and could overwrite an already-completed phase written +asynchronously by the instance manager. +

The gate now runs only while the backup phase is still unset or pending.

+
#11056 +
Fixed a declarative VolumeSnapshot backup being permanently marked as failed +when a stale cache made the operator re-create a snapshot it had already +provisioned, failing with AlreadyExists. +

The operator now tolerates the collision when the existing snapshot carries +this backup's label and adopts it; a collision with a foreign snapshot still +surfaces as an error.

+
#11071 +Fixed a volume snapshot backup being discarded on a transient instance-manager +connection error (for example a dial timeout from a brief pod-network +disruption) during the finalize step, even when its snapshots were already +provisioned; such network errors are now retried instead of treated as +terminal. +#11069 +Fixed a replica switchover losing its `status.demotionToken` when a reconcile +was requeued between storing the token and cleaning up the transition metadata +(for example a cleanup patch failing against a flaky webhook); the empty +no-change token is no longer patched back over the stored value. +#11075 +
Fixed kubectl cnp psql on Windows, where execution relied on a Unix-only +system call and failed with "not supported by windows"; Windows now launches +kubectl exec as a child process. +

Contributed by @Utkarsh-sharma47.

+
#10972 +
Fixed an unbounded memory leak in kubectl cnp logs -f on busy clusters, +where a per-log-group timer was never released; timers are now reused across +iterations. +

Contributed by @Anand-240.

+
#10976 diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx index 3b91c66a211..0978559fab1 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/index.mdx @@ -7,8 +7,11 @@ indexCards: none redirects: - ../release_notes navigation: + - 1_30_0_rel_notes + - 1_29_2_rel_notes - 1_29_1_rel_notes - 1_29_0_rel_notes + - 1_28_4_rel_notes - 1_28_3_rel_notes - 1_28_2_rel_notes - 1_28_1_rel_notes @@ -22,6 +25,7 @@ navigation: - 1_26_2_rel_notes - 1_26_1_rel_notes - 1_26_0_rel_notes + - 1_25_9_rel_notes - 1_25_8_rel_notes - 1_25_7_rel_notes - 1_25_6_rel_notes @@ -147,8 +151,11 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | Version | Release date | Upstream merges | |---|---|---| +| [1.30.0](./1_30_0_rel_notes) | 29 Jun 2026 | Upstream [1.30.0](https://cloudnative-pg.io/docs/1.30/release_notes/v1.30/) | +| [1.29.2](./1_29_2_rel_notes) | 29 Jun 2026 | Upstream [1.29.2](https://cloudnative-pg.io/docs/1.29/release_notes/v1.29/) | | [1.29.1](./1_29_1_rel_notes) | 08 May 2026 | Upstream [1.29.1](https://cloudnative-pg.io/docs/1.29/release_notes/v1.29/) | | [1.29.0](./1_29_0_rel_notes) | 31 Mar 2026 | Upstream [1.29.0](https://cloudnative-pg.io/releases/cloudnative-pg-1-29.0-released/) | +| [1.28.4](./1_28_4_rel_notes) | 29 Jun 2026 | Upstream [1.28.4](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) | | [1.28.3](./1_28_3_rel_notes) | 08 May 2026 | Upstream [1.28.3](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) | | [1.28.2](./1_28_2_rel_notes) | 31 Mar 2026 | Upstream [1.28.2](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) | | [1.28.1](./1_28_1_rel_notes) | 10 Feb 2026 | Upstream [1.28.1](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) | @@ -162,6 +169,7 @@ The EDB Postgres for Kubernetes documentation describes the major version of EDB | [1.26.2](./1_26_2_rel_notes) | 24 Oct 2025 | Upstream [1.26.2](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) | | [1.26.1](./1_26_1_rel_notes) | 25 Jul 2025 | Upstream [1.26.1](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) | | [1.26.0](./1_26_0_rel_notes) | 23 May 2025 | Upstream [1.26.0](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) | +| [1.25.9](./1_25_9_rel_notes) | 29 Jun 2026 | None | | [1.25.8](./1_25_8_rel_notes) | 08 May 2026 | None | | [1.25.7](./1_25_7_rel_notes) | 02 Apr 2026 | None | | [1.25.6](./1_25_6_rel_notes) | 10 Feb 2026 | None | diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.25.9_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.25.9_rel_notes.yml new file mode 100644 index 00000000000..5dfceafd00f --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.25.9_rel_notes.yml @@ -0,0 +1,424 @@ +# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json +product: EDB CloudNativePG Cluster +version: 1.25.9 +date: 29 June 2026 +intro: | + This release of EDB CloudNativePG Cluster is part of the LTS series for 1.25.x. + EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support + policy](/postgres_for_kubernetes/1/#long-term-support). + + !!! Warning EDB CloudNativePG Cluster 1.25 approaches End-of-Life. + + Users are encouraged to start planning their upgrade to a newer minor + version before that date. + + !!! + + This release of EDB CloudNativePG Cluster includes the following: +components: + "Operator": 1.25.9 + "CNP plugin": 1.25.9 + upstream-merge: None +highlights: | + The `cluster` reference is now immutable on the `Database`, `Pooler`, + `Publication`, `Subscription`, and `ScheduledBackup` resources. Pointing one + of these objects at a different cluster has no well-defined semantics and + previously left the controllers in an inconsistent state; the update is now + rejected at the API server via a CEL validation rule. + ([#10743](https://github.com/cloudnative-pg/cloudnative-pg/pull/10743)) +relnotes: +- relnote: | + Added a label selector to the `Cluster` scale subresource (`status.selector`), + making a `Cluster` a valid `targetRef` for the Vertical Pod Autoscaler (VPA) + and Horizontal Pod Autoscaler (HPA), which can now map a `Cluster` to its + instance pods. + details: | + Contributed by @sebv004. + jira: + addresses: #8996 + type: Enhancement + impact: High + +- relnote: | + The operator now emits a `Warning` `PrimaryStatusCheckFailed` event on the + `Cluster` when the primary pod is `Ready` from the kubelet perspective but the + operator's `/pg/status` check fails and failover is deferred, giving users + visibility into the deferral via `kubectl describe cluster`. + jira: + addresses: #10509 + type: Enhancement + impact: High + +- relnote: | + The operator now reloads a CNPG-i plugin automatically when its pods are + rolled: it watches the `EndpointSlices` backing plugin `Services` and + re-enqueues every cluster using the plugin once the new pods become `Ready`, + so an upgraded plugin is picked up without waiting for the next resync. + jira: + addresses: #10836 + type: Enhancement + impact: High + +- relnote: | + `CVE-2026-55769` / `GHSA-x8c2-3p4r-v9r6`: `search_path` pinning on + operator-issued connections + details: | + a database owner could plant overloaded built-in operators in the `public` + schema and alter the `search_path` so that operator introspection probes, + running as the cluster superuser, resolved those overloads before + `pg_catalog`, a `CWE-426` privilege-escalation chain (same class as + `CVE-2018-1058`) that could lead to in-pod RCE via `COPY ... FROM PROGRAM`. + The operator now pins `search_path = pg_catalog, public, pg_temp` on every + pooled connection so it ships in the startup message and takes precedence over + tenant-controlled defaults. + jira: + addresses: #10774, GHSA-x8c2-3p4r-v9r6 + type: Security + impact: High + +- relnote: | + `CVE-2026-55765` / `GHSA-w3gf-xc94-wvmj`: operator-side SCRAM-SHA-256 password + encoding + details: | + the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuing + `CREATE`/`ALTER ROLE ... PASSWORD`, so the literal PostgreSQL parses (and that + extensions such as `pg_stat_statements` or `pgaudit` may capture) is the SCRAM + verifier rather than the cleartext secret. Pre-hashed (MD5 or SCRAM) values + are forwarded unchanged, and the per-Secret annotation + `k8s.enterprisedb.io/passwordPassthrough: "enabled"` opts out. + jira: + addresses: #10724, GHSA-w3gf-xc94-wvmj + type: Security + impact: High + +- relnote: | + Updated the default PostgreSQL version to 18.4. + jira: + addresses: #10719 + type: Change + impact: High + +- relnote: | + Updated the Kubernetes versions used to test the operator on public cloud + providers. + jira: + addresses: #10720, #10563, #11033 + type: Change + impact: High + +- relnote: | + Fixed `spec.postgresql.parameters` accepting keys that are not valid + PostgreSQL parameter names, which could inject arbitrary directives into + `postgresql.conf`; key names are now validated by the webhook. + jira: + addresses: #11029 + type: Bug Fix + impact: High + +- relnote: | + Fixed declarative `Database`, `Publication`, and `Subscription` objects + reporting a stale primary-side status forever after their cluster was demoted + to a replica; the controller now re-checks the replica condition and watches + the `Cluster` so a demotion is detected promptly. + jira: + addresses: #10871 + type: Bug Fix + impact: High + +- relnote: | + Fixed non-sequential pod names (for example `-1`, `-3`) caused by the instance + serial counter being advanced before the corresponding `Job` and PVCs were + created; the bump is now persisted only after those resources exist. + jira: + addresses: #10491 + type: Bug Fix + impact: High + +- relnote: | + Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an + existing cluster: with `primaryUpdateMethod: switchover` the primary could not + be rolled out because a clean demotion needs the archiver sidecar that is + still missing. + details: | + The operator now recreates the primary Pod in place so the sidecar is injected + and archiving resumes. The check also covers plugins that inject the archiver + as a native sidecar (an init container with `restartPolicy: Always`), such as + the Barman Cloud plugin. + jira: + addresses: #11032, #11059 + type: Bug Fix + impact: High + +- relnote: | + Fixed a cluster staying in `Setting up primary` indefinitely when the + instance-creation Job exhausted its backoff limit; the operator now detects + the terminal Job failure and marks the cluster unrecoverable, naming the + failed Job and pointing to its logs. + jira: + addresses: #11035 + type: Bug Fix + impact: High + +- relnote: | + Fixed deletion of a `Database`, `Publication`, or `Subscription` getting stuck + in `Terminating` on a replica cluster, where the replica gate ran before the + finalizer reconciler and the finalizer was never released. + details: | + On a replica the PostgreSQL object is left to the primary cluster. + jira: + addresses: #10853 + type: Bug Fix + impact: High + +- relnote: | + Fixed a conflicting duplicate `Database` or `Subscription` with a `delete` + reclaim policy dropping the PostgreSQL object owned by the surviving CR; the + drop is now gated on a recorded reconciliation. + jira: + addresses: #10870 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `postgres` superuser being left locked out after superuser access + was disabled and then re-enabled, because the cached secret version was not + invalidated and the password was never re-applied. + details: | + Diagnosed by @mhartmann-jaconi. + jira: + addresses: #10834 + type: Bug Fix + impact: High + +- relnote: | + Fixed resource leaks when concurrent `Backup` objects raced: backups now run + in strict creation-time order, so an already-executing backup is never + preempted by a newer one and its replication slot and PostgreSQL session are + no longer orphaned on the primary. + details: | + Contributed by @GabriFedi97. + jira: + addresses: #10747 + type: Bug Fix + impact: High + +- relnote: | + Fixed role reconciliation clearing the password on a PostgreSQL role when the + referenced Secret could not be fetched; the role is now left untouched until + the Secret becomes available, and per-action errors are aggregated for better + visibility. + jira: + addresses: #10053 + type: Bug Fix + impact: High + +- relnote: | + Fixed a bootstrap failure where a metrics-exporter setup error (commonly a + duplicate-key race with the controller) rolled back `streaming_replica` + creation and wedged replica joins. + details: | + The metrics-exporter step now runs in a separate transaction. Contributed by + @BlaiseAntony. + jira: + addresses: #10749 + type: Bug Fix + impact: High + +- relnote: | + Fixed a `ScheduledBackup` controller loop that occurred when a `Backup` was + created but its status patch never landed; the controller now adopts an + existing `Backup` for the next iteration instead of looping on + `AlreadyExists`. + jira: + addresses: #10612 + type: Bug Fix + impact: High + +- relnote: | + Fixed bootstrap log handling so that all named log pipes (`postgres`, + `postgres.csv`, and `postgres.json`) get consumers during + `WithActiveInstance`, preventing regular files from being created in place of + the named pipes. + jira: + addresses: #10043 + type: Bug Fix + impact: High + +- relnote: | + Fixed generation of invalid IPv6 URLs by wrapping the address in square + brackets. + details: | + Contributed by @Infinoid. + jira: + addresses: #10682 + type: Bug Fix + impact: High + +- relnote: | + Fixed an external cluster plugin still being treated as active when its + configuration set `enabled: false`. + jira: + addresses: #10932 + type: Bug Fix + impact: High + +- relnote: | + Fixed a race during bootstrap recovery from an object store where the restore + job could read a stale `Cluster` (primary not yet recorded and timeline still + unset) and have its `.history` files rejected by the split-brain guard. + details: | + When this happened, recovery stopped at the base backup's timeline and + silently dropped transactions committed on later timelines. History files are + now allowed while the cluster timeline is unset. Contributed by @dennispidun. + jira: + addresses: #10818 + type: Bug Fix + impact: High + +- relnote: | + Fixed a cache race during cluster creation when the server and client CA + resolve to the same Secret (the default): a stale informer cache triggered a + redundant `Create` that failed with `AlreadyExists` and could leave the + cluster stuck in `Unable to create required cluster objects`. + details: | + The operator now reuses the already-fetched CA Secret when the names match. + jira: + addresses: #10989 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `pg_basebackup` bootstrap path overwriting or failing on a + pre-existing `PGDATA` (for example after a replica Pod restart) by enforcing + the same pre-flight directory check already applied by the other bootstrap + methods; this also protects statically provisioned PVCs from being silently + overwritten. + jira: + addresses: #11006 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `Cluster` phase flapping between `Healthy` and a plugin-failure + phase when a post-reconcile plugin hook returned an error; the `Healthy` phase + is now registered as the last step of a successful reconciliation, so a loop + that ends in a plugin error never reports `Healthy`. + details: | + Contributed by @GabriFedi97. + jira: + addresses: #10421 + type: Bug Fix + impact: High + +- relnote: | + Fixed stale certificate data and partial reads after an external server's + Secret was rotated (for example a CA bundle shrinking from two certificates to + one): the file is now written atomically, so libpq always reads either the old + or the new value, never a mix. + details: | + Contributed by @Anand-240. + jira: + addresses: #10975 + type: Bug Fix + impact: High + +- relnote: | + Fixed plugin connectivity to use the plugin `Service` FQDN instead of its + short name, avoiding failures when a cluster-level proxy is automatically + injected into pods. + details: | + Contributed by @kdautrey. + jira: + addresses: #10921 + type: Bug Fix + impact: High + +- relnote: | + Fixed excessive operator log noise from the per-request `Cluster` + create/update validation webhook messages, now logged at `debug` instead of + `info`. + jira: + addresses: #10984 + type: Bug Fix + impact: High + +- relnote: | + Fixed a first-primary bootstrap deadlock where a status-patch conflict after + the data PVC was created but before the initialization Job was started left + the orphan Pending PVC counted as an instance, blocking the bootstrap gate; + the PVC-state reconciler now recreates the bootstrap Job reusing the assigned + serial. + jira: + addresses: #11039 + type: Bug Fix + impact: High + +- relnote: | + Fixed external cluster names and secret selector references being joined into + filesystem paths without validation, letting a `..` component or path + separator escape the external secrets directory when the instance manager + dumps connection material; these values are now rejected at the validating + webhook and re-checked at the write site. + details: | + Reported by @r0binak. + jira: + addresses: #11045 + type: Bug Fix + impact: High + +- relnote: | + Fixed a declarative `VolumeSnapshot` backup being permanently marked as failed + when a stale cache made the operator re-create a snapshot it had already + provisioned, failing with `AlreadyExists`. + details: | + The operator now tolerates the collision when the existing snapshot carries + this backup's label and adopts it; a collision with a foreign snapshot still + surfaces as an error. + jira: + addresses: #11071 + type: Bug Fix + impact: High + +- relnote: | + Fixed a volume snapshot backup being discarded on a transient instance-manager + connection error (for example a dial timeout from a brief pod-network + disruption) during the finalize step, even when its snapshots were already + provisioned; such network errors are now retried instead of treated as + terminal. + jira: + addresses: #11069 + type: Bug Fix + impact: High + +- relnote: | + Fixed a replica switchover losing its `status.demotionToken` when a reconcile + was requeued between storing the token and cleaning up the transition metadata + (for example a cleanup patch failing against a flaky webhook); the empty + no-change token is no longer patched back over the stored value. + jira: + addresses: #11075 + type: Bug Fix + impact: High + +- relnote: | + Fixed `kubectl cnp psql` on Windows, where execution relied on a Unix-only + system call and failed with "not supported by windows"; Windows now launches + `kubectl exec` as a child process. + details: | + Contributed by @Utkarsh-sharma47. + jira: + addresses: #10972 + type: Bug Fix + impact: High + +- relnote: | + Fixed an unbounded memory leak in `kubectl cnp logs -f` on busy clusters, + where a per-log-group timer was never released; timers are now reused across + iterations. + details: | + Contributed by @Anand-240. + jira: + addresses: #10976 + type: Bug Fix + impact: High + diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.28.4_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.28.4_rel_notes.yml new file mode 100644 index 00000000000..aae038c851c --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.28.4_rel_notes.yml @@ -0,0 +1,444 @@ +# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json +product: EDB CloudNativePG Cluster +version: 1.28.4 +date: 29 June 2026 +intro: | + This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: +components: + "Operator": 1.28.4 + "CNP plugin": 1.28.4 + upstream-merge: Upstream [1.28.4](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) +highlights: | + Updated the deprecation notice for native (in-tree) Barman Cloud support to + reflect that it will now be removed in EDB Postgres for Kubernetes 1.31.0, + rather than 1.30.0. Users are still encouraged to migrate to the Barman Cloud + Plugin. + ([#11083](https://github.com/cloudnative-pg/cloudnative-pg/pull/11083)) + + The `cluster` reference is now immutable on the `Database`, `Pooler`, + `Publication`, `Subscription`, and `ScheduledBackup` resources. Pointing one + of these objects at a different cluster has no well-defined semantics and + previously left the controllers in an inconsistent state; the update is now + rejected at the API server via a CEL validation rule. + ([#10743](https://github.com/cloudnative-pg/cloudnative-pg/pull/10743)) +relnotes: +- relnote: | + Added a label selector to the `Cluster` scale subresource (`status.selector`), + making a `Cluster` a valid `targetRef` for the Vertical Pod Autoscaler (VPA) + and Horizontal Pod Autoscaler (HPA), which can now map a `Cluster` to its + instance pods. + details: | + Contributed by @sebv004. + jira: + addresses: #8996 + type: Enhancement + impact: High + +- relnote: | + The operator now emits a `Warning` `PrimaryStatusCheckFailed` event on the + `Cluster` when the primary pod is `Ready` from the kubelet perspective but the + operator's `/pg/status` check fails and failover is deferred, giving users + visibility into the deferral via `kubectl describe cluster`. + jira: + addresses: #10509 + type: Enhancement + impact: High + +- relnote: | + The operator now reloads a CNPG-i plugin automatically when its pods are + rolled: it watches the `EndpointSlices` backing plugin `Services` and + re-enqueues every cluster using the plugin once the new pods become `Ready`, + so an upgraded plugin is picked up without waiting for the next resync. + jira: + addresses: #10836 + type: Enhancement + impact: High + +- relnote: | + `CVE-2026-55769` / `GHSA-x8c2-3p4r-v9r6`: `search_path` pinning on + operator-issued connections + details: | + a database owner could plant overloaded built-in operators in the `public` + schema and alter the `search_path` so that operator introspection probes, + running as the cluster superuser, resolved those overloads before + `pg_catalog`, a `CWE-426` privilege-escalation chain (same class as + `CVE-2018-1058`) that could lead to in-pod RCE via `COPY ... FROM PROGRAM`. + The operator now pins `search_path = pg_catalog, public, pg_temp` on every + pooled connection so it ships in the startup message and takes precedence over + tenant-controlled defaults. + jira: + addresses: #10774, GHSA-x8c2-3p4r-v9r6 + type: Security + impact: High + +- relnote: | + `CVE-2026-55765` / `GHSA-w3gf-xc94-wvmj`: operator-side SCRAM-SHA-256 password + encoding + details: | + the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuing + `CREATE`/`ALTER ROLE ... PASSWORD`, so the literal PostgreSQL parses (and that + extensions such as `pg_stat_statements` or `pgaudit` may capture) is the SCRAM + verifier rather than the cleartext secret. Pre-hashed (MD5 or SCRAM) values + are forwarded unchanged, and the per-Secret annotation + `k8s.enterprisedb.io/passwordPassthrough: "enabled"` opts out. + jira: + addresses: #10724, GHSA-w3gf-xc94-wvmj + type: Security + impact: High + +- relnote: | + Added support for Kubernetes 1.35 and enabled unit tests on Kubernetes 1.36. + jira: + addresses: #10900 + type: Change + impact: High + +- relnote: | + Updated the default PostgreSQL version to 18.4. + jira: + addresses: #10719 + type: Change + impact: High + +- relnote: | + Updated the Kubernetes versions used to test the operator on public cloud + providers. + jira: + addresses: #10720, #10563, #11033 + type: Change + impact: High + +- relnote: | + Fixed `spec.postgresql.parameters` accepting keys that are not valid + PostgreSQL parameter names, which could inject arbitrary directives into + `postgresql.conf`; key names are now validated by the webhook. + jira: + addresses: #11029 + type: Bug Fix + impact: High + +- relnote: | + Fixed declarative `Database`, `Publication`, and `Subscription` objects + reporting a stale primary-side status forever after their cluster was demoted + to a replica; the controller now re-checks the replica condition and watches + the `Cluster` so a demotion is detected promptly. + jira: + addresses: #10871 + type: Bug Fix + impact: High + +- relnote: | + Fixed non-sequential pod names (for example `-1`, `-3`) caused by the instance + serial counter being advanced before the corresponding `Job` and PVCs were + created; the bump is now persisted only after those resources exist. + jira: + addresses: #10491 + type: Bug Fix + impact: High + +- relnote: | + Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an + existing cluster: with `primaryUpdateMethod: switchover` the primary could not + be rolled out because a clean demotion needs the archiver sidecar that is + still missing. + details: | + The operator now recreates the primary Pod in place so the sidecar is injected + and archiving resumes. The check also covers plugins that inject the archiver + as a native sidecar (an init container with `restartPolicy: Always`), such as + the Barman Cloud plugin. + jira: + addresses: #11032, #11059 + type: Bug Fix + impact: High + +- relnote: | + Fixed a cluster staying in `Setting up primary` indefinitely when the + instance-creation Job exhausted its backoff limit; the operator now detects + the terminal Job failure and marks the cluster unrecoverable, naming the + failed Job and pointing to its logs. + jira: + addresses: #11035 + type: Bug Fix + impact: High + +- relnote: | + Fixed deletion of a `Database`, `Publication`, or `Subscription` getting stuck + in `Terminating` on a replica cluster, where the replica gate ran before the + finalizer reconciler and the finalizer was never released. + details: | + On a replica the PostgreSQL object is left to the primary cluster. + jira: + addresses: #10853 + type: Bug Fix + impact: High + +- relnote: | + Fixed a conflicting duplicate `Database` or `Subscription` with a `delete` + reclaim policy dropping the PostgreSQL object owned by the surviving CR; the + drop is now gated on a recorded reconciliation. + jira: + addresses: #10870 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `postgres` superuser being left locked out after superuser access + was disabled and then re-enabled, because the cached secret version was not + invalidated and the password was never re-applied. + details: | + Diagnosed by @mhartmann-jaconi. + jira: + addresses: #10834 + type: Bug Fix + impact: High + +- relnote: | + Fixed backups getting stuck in the `started` phase when the instance manager + running them was restarted (for example by the in-place upgrade following an + operator upgrade) before the backup reached `running`; the reconciliation is + now rescheduled so the lost session is detected. + jira: + addresses: #10859 + type: Bug Fix + impact: High + +- relnote: | + Fixed resource leaks when concurrent `Backup` objects raced: backups now run + in strict creation-time order, so an already-executing backup is never + preempted by a newer one and its replication slot and PostgreSQL session are + no longer orphaned on the primary. + details: | + Contributed by @GabriFedi97. + jira: + addresses: #10747 + type: Bug Fix + impact: High + +- relnote: | + Fixed role reconciliation clearing the password on a PostgreSQL role when the + referenced Secret could not be fetched; the role is now left untouched until + the Secret becomes available, and per-action errors are aggregated for better + visibility. + jira: + addresses: #10053 + type: Bug Fix + impact: High + +- relnote: | + Fixed a bootstrap failure where a metrics-exporter setup error (commonly a + duplicate-key race with the controller) rolled back `streaming_replica` + creation and wedged replica joins. + details: | + The metrics-exporter step now runs in a separate transaction. Contributed by + @BlaiseAntony. + jira: + addresses: #10749 + type: Bug Fix + impact: High + +- relnote: | + Fixed a `ScheduledBackup` controller loop that occurred when a `Backup` was + created but its status patch never landed; the controller now adopts an + existing `Backup` for the next iteration instead of looping on + `AlreadyExists`. + jira: + addresses: #10612 + type: Bug Fix + impact: High + +- relnote: | + Fixed a nil-pointer panic when reconciling a `Pooler` whose `Cluster` has been + deleted. + jira: + addresses: #10667 + type: Bug Fix + impact: High + +- relnote: | + Fixed bootstrap log handling so that all named log pipes (`postgres`, + `postgres.csv`, and `postgres.json`) get consumers during + `WithActiveInstance`, preventing regular files from being created in place of + the named pipes. + jira: + addresses: #10043 + type: Bug Fix + impact: High + +- relnote: | + Fixed generation of invalid IPv6 URLs by wrapping the address in square + brackets. + details: | + Contributed by @Infinoid. + jira: + addresses: #10682 + type: Bug Fix + impact: High + +- relnote: | + Fixed an external cluster plugin still being treated as active when its + configuration set `enabled: false`. + jira: + addresses: #10932 + type: Bug Fix + impact: High + +- relnote: | + Fixed a race during bootstrap recovery from an object store where the restore + job could read a stale `Cluster` (primary not yet recorded and timeline still + unset) and have its `.history` files rejected by the split-brain guard. + details: | + When this happened, recovery stopped at the base backup's timeline and + silently dropped transactions committed on later timelines. History files are + now allowed while the cluster timeline is unset. Contributed by @dennispidun. + jira: + addresses: #10818 + type: Bug Fix + impact: High + +- relnote: | + Fixed a cache race during cluster creation when the server and client CA + resolve to the same Secret (the default): a stale informer cache triggered a + redundant `Create` that failed with `AlreadyExists` and could leave the + cluster stuck in `Unable to create required cluster objects`. + details: | + The operator now reuses the already-fetched CA Secret when the names match. + jira: + addresses: #10989 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `pg_basebackup` bootstrap path overwriting or failing on a + pre-existing `PGDATA` (for example after a replica Pod restart) by enforcing + the same pre-flight directory check already applied by the other bootstrap + methods; this also protects statically provisioned PVCs from being silently + overwritten. + jira: + addresses: #11006 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `Cluster` phase flapping between `Healthy` and a plugin-failure + phase when a post-reconcile plugin hook returned an error; the `Healthy` phase + is now registered as the last step of a successful reconciliation, so a loop + that ends in a plugin error never reports `Healthy`. + details: | + Contributed by @GabriFedi97. + jira: + addresses: #10421 + type: Bug Fix + impact: High + +- relnote: | + Fixed stale certificate data and partial reads after an external server's + Secret was rotated (for example a CA bundle shrinking from two certificates to + one): the file is now written atomically, so libpq always reads either the old + or the new value, never a mix. + details: | + Contributed by @Anand-240. + jira: + addresses: #10975 + type: Bug Fix + impact: High + +- relnote: | + Fixed plugin connectivity to use the plugin `Service` FQDN instead of its + short name, avoiding failures when a cluster-level proxy is automatically + injected into pods. + details: | + Contributed by @kdautrey. + jira: + addresses: #10921 + type: Bug Fix + impact: High + +- relnote: | + Fixed excessive operator log noise from the per-request `Cluster` + create/update validation webhook messages, now logged at `debug` instead of + `info`. + jira: + addresses: #10984 + type: Bug Fix + impact: High + +- relnote: | + Fixed a first-primary bootstrap deadlock where a status-patch conflict after + the data PVC was created but before the initialization Job was started left + the orphan Pending PVC counted as an instance, blocking the bootstrap gate; + the PVC-state reconciler now recreates the bootstrap Job reusing the assigned + serial. + jira: + addresses: #11039 + type: Bug Fix + impact: High + +- relnote: | + Fixed external cluster names and secret selector references being joined into + filesystem paths without validation, letting a `..` component or path + separator escape the external secrets directory when the instance manager + dumps connection material; these values are now rejected at the validating + webhook and re-checked at the write site. + details: | + Reported by @r0binak. + jira: + addresses: #11045 + type: Bug Fix + impact: High + +- relnote: | + Fixed a declarative `VolumeSnapshot` backup being permanently marked as failed + when a stale cache made the operator re-create a snapshot it had already + provisioned, failing with `AlreadyExists`. + details: | + The operator now tolerates the collision when the existing snapshot carries + this backup's label and adopts it; a collision with a foreign snapshot still + surfaces as an error. + jira: + addresses: #11071 + type: Bug Fix + impact: High + +- relnote: | + Fixed a volume snapshot backup being discarded on a transient instance-manager + connection error (for example a dial timeout from a brief pod-network + disruption) during the finalize step, even when its snapshots were already + provisioned; such network errors are now retried instead of treated as + terminal. + jira: + addresses: #11069 + type: Bug Fix + impact: High + +- relnote: | + Fixed a replica switchover losing its `status.demotionToken` when a reconcile + was requeued between storing the token and cleaning up the transition metadata + (for example a cleanup patch failing against a flaky webhook); the empty + no-change token is no longer patched back over the stored value. + jira: + addresses: #11075 + type: Bug Fix + impact: High + +- relnote: | + Fixed `kubectl cnp psql` on Windows, where execution relied on a Unix-only + system call and failed with "not supported by windows"; Windows now launches + `kubectl exec` as a child process. + details: | + Contributed by @Utkarsh-sharma47. + jira: + addresses: #10972 + type: Bug Fix + impact: High + +- relnote: | + Fixed an unbounded memory leak in `kubectl cnp logs -f` on busy clusters, + where a per-log-group timer was never released; timers are now reused across + iterations. + details: | + Contributed by @Anand-240. + jira: + addresses: #10976 + type: Bug Fix + impact: High + diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.29.2_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.29.2_rel_notes.yml new file mode 100644 index 00000000000..c52d80316b0 --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.29.2_rel_notes.yml @@ -0,0 +1,479 @@ +# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json +product: EDB CloudNativePG Cluster +version: 1.29.2 +date: 29 June 2026 +intro: | + This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: +components: + "Operator": 1.29.2 + "CNP plugin": 1.29.2 + upstream-merge: Upstream [1.29.2](https://cloudnative-pg.io/docs/1.29/release_notes/v1.29/) +highlights: | + Updated the deprecation notice for native (in-tree) Barman Cloud support to + reflect that it will now be removed in EDB Postgres for Kubernetes 1.31.0, + rather than 1.30.0. Users are still encouraged to migrate to the Barman Cloud + Plugin. + ([#11083](https://github.com/cloudnative-pg/cloudnative-pg/pull/11083)) + + The `cluster` reference is now immutable on the `Database`, `Pooler`, + `Publication`, `Subscription`, and `ScheduledBackup` resources. Pointing one + of these objects at a different cluster has no well-defined semantics and + previously left the controllers in an inconsistent state; the update is now + rejected at the API server via a CEL validation rule. + ([#10743](https://github.com/cloudnative-pg/cloudnative-pg/pull/10743)) +relnotes: +- relnote: | + Enabled `pg_upgrade` in-place major upgrades to PostgreSQL 19 or later for + clusters that use Image Volume extensions, building on the extension-path + support added to `pg_upgrade` in PostgreSQL 19. + details: | + During the upgrade `Job`, the source- and target-version extension images are + mounted side by side, so the old server keeps its libraries and a failed + upgrade reverts cleanly. + jira: + addresses: #10366 + type: Enhancement + impact: High + +- relnote: | + Added a label selector to the `Cluster` scale subresource (`status.selector`), + making a `Cluster` a valid `targetRef` for the Vertical Pod Autoscaler (VPA) + and Horizontal Pod Autoscaler (HPA), which can now map a `Cluster` to its + instance pods. + details: | + Contributed by @sebv004. + jira: + addresses: #8996 + type: Enhancement + impact: High + +- relnote: | + The operator now emits a `Warning` `PrimaryStatusCheckFailed` event on the + `Cluster` when the primary pod is `Ready` from the kubelet perspective but the + operator's `/pg/status` check fails and failover is deferred, giving users + visibility into the deferral via `kubectl describe cluster`. + jira: + addresses: #10509 + type: Enhancement + impact: High + +- relnote: | + The operator now reloads a CNPG-i plugin automatically when its pods are + rolled: it watches the `EndpointSlices` backing plugin `Services` and + re-enqueues every cluster using the plugin once the new pods become `Ready`, + so an upgraded plugin is picked up without waiting for the next resync. + jira: + addresses: #10836 + type: Enhancement + impact: High + +- relnote: | + `CVE-2026-55769` / `GHSA-x8c2-3p4r-v9r6`: `search_path` pinning on + operator-issued connections + details: | + a database owner could plant overloaded built-in operators in the `public` + schema and alter the `search_path` so that operator introspection probes, + running as the cluster superuser, resolved those overloads before + `pg_catalog`, a `CWE-426` privilege-escalation chain (same class as + `CVE-2018-1058`) that could lead to in-pod RCE via `COPY ... FROM PROGRAM`. + The operator now pins `search_path = pg_catalog, public, pg_temp` on every + pooled connection so it ships in the startup message and takes precedence over + tenant-controlled defaults. + jira: + addresses: #10774, GHSA-x8c2-3p4r-v9r6 + type: Security + impact: High + +- relnote: | + `CVE-2026-55765` / `GHSA-w3gf-xc94-wvmj`: operator-side SCRAM-SHA-256 password + encoding + details: | + the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuing + `CREATE`/`ALTER ROLE ... PASSWORD`, so the literal PostgreSQL parses (and that + extensions such as `pg_stat_statements` or `pgaudit` may capture) is the SCRAM + verifier rather than the cleartext secret. Pre-hashed (MD5 or SCRAM) values + are forwarded unchanged, and the per-Secret annotation + `k8s.enterprisedb.io/passwordPassthrough: "enabled"` opts out. + jira: + addresses: #10724, GHSA-w3gf-xc94-wvmj + type: Security + impact: High + +- relnote: | + Added support for Kubernetes 1.36. + jira: + addresses: #10900 + type: Change + impact: High + +- relnote: | + Updated the default PostgreSQL version to 18.4. + jira: + addresses: #10719 + type: Change + impact: High + +- relnote: | + Updated the Kubernetes versions used to test the operator on public cloud + providers. + jira: + addresses: #10720, #10563, #11033 + type: Change + impact: High + +- relnote: | + Fixed `spec.postgresql.parameters` accepting keys that are not valid + PostgreSQL parameter names, which could inject arbitrary directives into + `postgresql.conf`; key names are now validated by the webhook. + jira: + addresses: #11029 + type: Bug Fix + impact: High + +- relnote: | + Fixed declarative `Database`, `Publication`, and `Subscription` objects + reporting a stale primary-side status forever after their cluster was demoted + to a replica; the controller now re-checks the replica condition and watches + the `Cluster` so a demotion is detected promptly. + jira: + addresses: #10871 + type: Bug Fix + impact: High + +- relnote: | + Fixed non-sequential pod names (for example `-1`, `-3`) caused by the instance + serial counter being advanced before the corresponding `Job` and PVCs were + created; the bump is now persisted only after those resources exist. + jira: + addresses: #10491 + type: Bug Fix + impact: High + +- relnote: | + Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an + existing cluster: with `primaryUpdateMethod: switchover` the primary could not + be rolled out because a clean demotion needs the archiver sidecar that is + still missing. + details: | + The operator now recreates the primary Pod in place so the sidecar is injected + and archiving resumes. The check also covers plugins that inject the archiver + as a native sidecar (an init container with `restartPolicy: Always`), such as + the Barman Cloud plugin. + jira: + addresses: #11032, #11059 + type: Bug Fix + impact: High + +- relnote: | + Fixed a cluster staying in `Setting up primary` indefinitely when the + instance-creation Job exhausted its backoff limit; the operator now detects + the terminal Job failure and marks the cluster unrecoverable, naming the + failed Job and pointing to its logs. + jira: + addresses: #11035 + type: Bug Fix + impact: High + +- relnote: | + Fixed deletion of a `Database`, `Publication`, or `Subscription` getting stuck + in `Terminating` on a replica cluster, where the replica gate ran before the + finalizer reconciler and the finalizer was never released. + details: | + On a replica the PostgreSQL object is left to the primary cluster. + jira: + addresses: #10853 + type: Bug Fix + impact: High + +- relnote: | + Fixed a conflicting duplicate `Database` or `Subscription` with a `delete` + reclaim policy dropping the PostgreSQL object owned by the surviving CR; the + drop is now gated on a recorded reconciliation. + jira: + addresses: #10870 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `postgres` superuser being left locked out after superuser access + was disabled and then re-enabled, because the cached secret version was not + invalidated and the password was never re-applied. + details: | + Diagnosed by @mhartmann-jaconi. + jira: + addresses: #10834 + type: Bug Fix + impact: High + +- relnote: | + Fixed backups getting stuck in the `started` phase when the instance manager + running them was restarted (for example by the in-place upgrade following an + operator upgrade) before the backup reached `running`; the reconciliation is + now rescheduled so the lost session is detected. + jira: + addresses: #10859 + type: Bug Fix + impact: High + +- relnote: | + Fixed `exec`/`attach` streaming to negotiate WebSocket with a SPDY fallback, + restoring compatibility both with Kubernetes versions that have removed SPDY + and with platforms such as OpenShift that reject WebSocket exec upgrades. + details: | + Contributed by @bartscheers. + jira: + addresses: #10876, #10933 + type: Bug Fix + impact: High + +- relnote: | + Fixed resource leaks when concurrent `Backup` objects raced: backups now run + in strict creation-time order, so an already-executing backup is never + preempted by a newer one and its replication slot and PostgreSQL session are + no longer orphaned on the primary. + details: | + Contributed by @GabriFedi97. + jira: + addresses: #10747 + type: Bug Fix + impact: High + +- relnote: | + Fixed role reconciliation clearing the password on a PostgreSQL role when the + referenced Secret could not be fetched; the role is now left untouched until + the Secret becomes available, and per-action errors are aggregated for better + visibility. + jira: + addresses: #10053 + type: Bug Fix + impact: High + +- relnote: | + Fixed a bootstrap failure where a metrics-exporter setup error (commonly a + duplicate-key race with the controller) rolled back `streaming_replica` + creation and wedged replica joins. + details: | + The metrics-exporter step now runs in a separate transaction. Contributed by + @BlaiseAntony. + jira: + addresses: #10749 + type: Bug Fix + impact: High + +- relnote: | + Fixed a `ScheduledBackup` controller loop that occurred when a `Backup` was + created but its status patch never landed; the controller now adopts an + existing `Backup` for the next iteration instead of looping on + `AlreadyExists`. + jira: + addresses: #10612 + type: Bug Fix + impact: High + +- relnote: | + Fixed a nil-pointer panic when reconciling a `Pooler` whose `Cluster` has been + deleted. + jira: + addresses: #10667 + type: Bug Fix + impact: High + +- relnote: | + Fixed bootstrap log handling so that all named log pipes (`postgres`, + `postgres.csv`, and `postgres.json`) get consumers during + `WithActiveInstance`, preventing regular files from being created in place of + the named pipes. + jira: + addresses: #10043 + type: Bug Fix + impact: High + +- relnote: | + Fixed generation of invalid IPv6 URLs by wrapping the address in square + brackets. + details: | + Contributed by @Infinoid. + jira: + addresses: #10682 + type: Bug Fix + impact: High + +- relnote: | + Fixed an external cluster plugin still being treated as active when its + configuration set `enabled: false`. + jira: + addresses: #10932 + type: Bug Fix + impact: High + +- relnote: | + Fixed a race during bootstrap recovery from an object store where the restore + job could read a stale `Cluster` (primary not yet recorded and timeline still + unset) and have its `.history` files rejected by the split-brain guard. + details: | + When this happened, recovery stopped at the base backup's timeline and + silently dropped transactions committed on later timelines. History files are + now allowed while the cluster timeline is unset. Contributed by @dennispidun. + jira: + addresses: #10818 + type: Bug Fix + impact: High + +- relnote: | + Fixed a cache race during cluster creation when the server and client CA + resolve to the same Secret (the default): a stale informer cache triggered a + redundant `Create` that failed with `AlreadyExists` and could leave the + cluster stuck in `Unable to create required cluster objects`. + details: | + The operator now reuses the already-fetched CA Secret when the names match. + jira: + addresses: #10989 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `pg_basebackup` bootstrap path overwriting or failing on a + pre-existing `PGDATA` (for example after a replica Pod restart) by enforcing + the same pre-flight directory check already applied by the other bootstrap + methods; this also protects statically provisioned PVCs from being silently + overwritten. + jira: + addresses: #11006 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `Cluster` phase flapping between `Healthy` and a plugin-failure + phase when a post-reconcile plugin hook returned an error; the `Healthy` phase + is now registered as the last step of a successful reconciliation, so a loop + that ends in a plugin error never reports `Healthy`. + details: | + Contributed by @GabriFedi97. + jira: + addresses: #10421 + type: Bug Fix + impact: High + +- relnote: | + Fixed stale certificate data and partial reads after an external server's + Secret was rotated (for example a CA bundle shrinking from two certificates to + one): the file is now written atomically, so libpq always reads either the old + or the new value, never a mix. + details: | + Contributed by @Anand-240. + jira: + addresses: #10975 + type: Bug Fix + impact: High + +- relnote: | + Fixed plugin connectivity to use the plugin `Service` FQDN instead of its + short name, avoiding failures when a cluster-level proxy is automatically + injected into pods. + details: | + Contributed by @kdautrey. + jira: + addresses: #10921 + type: Bug Fix + impact: High + +- relnote: | + Fixed excessive operator log noise from the per-request `Cluster` + create/update validation webhook messages, now logged at `debug` instead of + `info`. + jira: + addresses: #10984 + type: Bug Fix + impact: High + +- relnote: | + Fixed a first-primary bootstrap deadlock where a status-patch conflict after + the data PVC was created but before the initialization Job was started left + the orphan Pending PVC counted as an instance, blocking the bootstrap gate; + the PVC-state reconciler now recreates the bootstrap Job reusing the assigned + serial. + jira: + addresses: #11039 + type: Bug Fix + impact: High + +- relnote: | + Fixed external cluster names and secret selector references being joined into + filesystem paths without validation, letting a `..` component or path + separator escape the external secrets directory when the instance manager + dumps connection material; these values are now rejected at the validating + webhook and re-checked at the write site. + details: | + Reported by @r0binak. + jira: + addresses: #11045 + type: Bug Fix + impact: High + +- relnote: | + Fixed a backup getting stuck in `pending` forever: the concurrent-backup gate + ran on every reconcile and could overwrite an already-completed phase written + asynchronously by the instance manager. + details: | + The gate now runs only while the backup phase is still unset or `pending`. + jira: + addresses: #11056 + type: Bug Fix + impact: High + +- relnote: | + Fixed a declarative `VolumeSnapshot` backup being permanently marked as failed + when a stale cache made the operator re-create a snapshot it had already + provisioned, failing with `AlreadyExists`. + details: | + The operator now tolerates the collision when the existing snapshot carries + this backup's label and adopts it; a collision with a foreign snapshot still + surfaces as an error. + jira: + addresses: #11071 + type: Bug Fix + impact: High + +- relnote: | + Fixed a volume snapshot backup being discarded on a transient instance-manager + connection error (for example a dial timeout from a brief pod-network + disruption) during the finalize step, even when its snapshots were already + provisioned; such network errors are now retried instead of treated as + terminal. + jira: + addresses: #11069 + type: Bug Fix + impact: High + +- relnote: | + Fixed a replica switchover losing its `status.demotionToken` when a reconcile + was requeued between storing the token and cleaning up the transition metadata + (for example a cleanup patch failing against a flaky webhook); the empty + no-change token is no longer patched back over the stored value. + jira: + addresses: #11075 + type: Bug Fix + impact: High + +- relnote: | + Fixed `kubectl cnp psql` on Windows, where execution relied on a Unix-only + system call and failed with "not supported by windows"; Windows now launches + `kubectl exec` as a child process. + details: | + Contributed by @Utkarsh-sharma47. + jira: + addresses: #10972 + type: Bug Fix + impact: High + +- relnote: | + Fixed an unbounded memory leak in `kubectl cnp logs -f` on busy clusters, + where a per-log-group timer was never released; timers are now reused across + iterations. + details: | + Contributed by @Anand-240. + jira: + addresses: #10976 + type: Bug Fix + impact: High + diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.30.0_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.30.0_rel_notes.yml similarity index 59% rename from product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.30.0_rel_notes.yml rename to product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.30.0_rel_notes.yml index e500a99b5f9..934c77ca5de 100644 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.30.0_rel_notes.yml +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/src/1.30.0_rel_notes.yml @@ -1,14 +1,20 @@ # yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json product: EDB CloudNativePG Cluster -version: 1.30.0-rc1 -date: 19 June 2026 +version: 1.30.0 +date: 29 June 2026 intro: | This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: components: "Operator": 1.30.0 "CNP plugin": 1.30.0 - upstream-merge: Upstream [1.30.0-rc1](https://cloudnative-pg.io/docs/1.30/release_notes/v1.30/) + upstream-merge: Upstream [1.30.0](https://cloudnative-pg.io/docs/1.30/release_notes/v1.30/) highlights: | + Updated the deprecation notice for native (in-tree) Barman Cloud support to + reflect that it will now be removed in EDB Postgres for Kubernetes 1.31.0, + rather than 1.30.0. Users are still encouraged to migrate to the Barman Cloud + Plugin. + ([#11083](https://github.com/cloudnative-pg/cloudnative-pg/pull/11083)) + The `cluster` reference is now immutable on the `Database`, `Pooler`, `Publication`, `Subscription`, and `ScheduledBackup` resources. Pointing one of these objects at a different cluster has no well-defined semantics and @@ -23,8 +29,8 @@ relnotes: a mutex serializing primary promotion: the instance manager must hold the lease before acting as primary and releases it on clean shutdown so replicas can promote without waiting for the full TTL. Timings are configurable via the - new `.spec.primaryLease` stanza. The lease is a promotion gate, not a fence — - primary isolation remains responsible for fencing. + new `.spec.primaryLease` stanza. The lease is a promotion gate, not a fence. + Primary isolation remains responsible for fencing. jira: addresses: #10627 type: Feature @@ -71,7 +77,7 @@ relnotes: referencing `Poolers` are automatically reconciled and roll out the new image without any change to their spec. The resolved image is reported in `status.image`, and a new `status.phase` (`active`, `paused`, `inactive`, or - `failed`) — also surfaced as a `Phase` column in `kubectl get pooler` — + `failed`), also surfaced as a `Phase` column in `kubectl get pooler`, summarizes the lifecycle. jira: addresses: #10568 @@ -176,37 +182,43 @@ relnotes: impact: High - relnote: | - `search_path` pinning on operator-issued connections + `CVE-2026-55769` / `GHSA-x8c2-3p4r-v9r6`: `search_path` pinning on + operator-issued connections details: | a database owner could plant overloaded built-in operators in the `public` schema and alter the `search_path` so that operator introspection probes, - running as the cluster superuser, resolved those overloads before `pg_catalog` - — a `CWE-426` privilege-escalation chain (same class as `CVE-2018-1058`) that - could lead to in-pod RCE via `COPY ... FROM PROGRAM`. The operator now pins - `search_path = pg_catalog, public, pg_temp` on every pooled connection so it - ships in the startup message and takes precedence over tenant-controlled - defaults. - jira: - addresses: #10774 + running as the cluster superuser, resolved those overloads before + `pg_catalog`, a `CWE-426` privilege-escalation chain (same class as + `CVE-2018-1058`) that could lead to in-pod RCE via `COPY ... FROM PROGRAM`. + The operator now pins `search_path = pg_catalog, public, pg_temp` on every + pooled connection so it ships in the startup message and takes precedence over + tenant-controlled defaults. + jira: + addresses: #10774, GHSA-x8c2-3p4r-v9r6 type: Security impact: High - relnote: | - Authenticated operator-to-instance-manager calls + `GHSA-7qwx-x8ff-3px9`: authenticated operator-to-instance-manager calls details: | - the instance manager's remote webserver previously accepted unauthenticated - requests, so any process on the pod network could trigger backups, instance - manager upgrades, or WAL archival. The operator now generates an in-memory - ECDSA P-256 client certificate at startup and reconciles its SHA-256 - fingerprint into the cluster status; the instance manager rejects requests to - sensitive endpoints that do not present a matching certificate. - jira: - addresses: #10579 + the instance manager's remote webserver relied on network isolation rather + than authentication for its operator-only control endpoints, so any party able + to reach the pod's status port could invoke them, disrupting backup + orchestration and WAL archival and reading operational metadata. (The upgrade + endpoint is SHA-256-pinned, so this did not permit arbitrary code execution.) + The operator now generates an in-memory ECDSA P-256 client certificate at + startup and reconciles its SHA-256 fingerprint into the cluster status; the + instance manager rejects requests to sensitive endpoints that do not present a + matching certificate. This hardening is not backported; earlier releases + should continue to restrict the status port with a `NetworkPolicy`. + jira: + addresses: #10579, GHSA-7qwx-x8ff-3px9 type: Security impact: High - relnote: | - Operator-side SCRAM-SHA-256 password encoding + `CVE-2026-55765` / `GHSA-w3gf-xc94-wvmj`: operator-side SCRAM-SHA-256 password + encoding details: | the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuing `CREATE`/`ALTER ROLE ... PASSWORD`, so the literal PostgreSQL parses (and that @@ -215,7 +227,7 @@ relnotes: are forwarded unchanged, and the per-Secret annotation `k8s.enterprisedb.io/passwordPassthrough: "enabled"` opts out. jira: - addresses: #10724 + addresses: #10724, GHSA-w3gf-xc94-wvmj type: Security impact: High @@ -237,7 +249,7 @@ relnotes: Updated the Kubernetes versions used to test the operator on public cloud providers. jira: - addresses: #10720, #10563 + addresses: #10720, #10563, #11033 type: Change impact: High @@ -405,3 +417,209 @@ relnotes: type: Bug Fix impact: High +- relnote: | + Fixed a race where deleting an instance's PVCs could leave the instance + permanently stuck: if the data PVC was removed while a WAL PVC was still + terminating, the operator recreated the instance bound to the terminating + volume, leaving the Pod unschedulable and blocking all further reconciliation. + details: | + The operator now waits for terminating PVCs to be fully removed before + recreating or reattaching an instance, and surfaces the wait through a log + line and the cluster phase. + jira: + addresses: #11017 + type: Bug Fix + impact: High + +- relnote: | + Fixed a cache race during cluster creation when the server and client CA + resolve to the same Secret (the default): a stale informer cache triggered a + redundant `Create` that failed with `AlreadyExists` and could leave the + cluster stuck in `Unable to create required cluster objects`. + details: | + The operator now reuses the already-fetched CA Secret when the names match. + jira: + addresses: #10989 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `pg_basebackup` bootstrap path overwriting or failing on a + pre-existing `PGDATA` (for example after a replica Pod restart) by enforcing + the same pre-flight directory check already applied by the other bootstrap + methods; this also protects statically provisioned PVCs from being silently + overwritten. + jira: + addresses: #11006 + type: Bug Fix + impact: High + +- relnote: | + Fixed the `Cluster` phase flapping between `Healthy` and a plugin-failure + phase when a post-reconcile plugin hook returned an error; the `Healthy` phase + is now registered as the last step of a successful reconciliation, so a loop + that ends in a plugin error never reports `Healthy`. + details: | + Contributed by @GabriFedi97. + jira: + addresses: #10421 + type: Bug Fix + impact: High + +- relnote: | + Fixed stale certificate data and partial reads after an external server's + Secret was rotated (for example a CA bundle shrinking from two certificates to + one): the file is now written atomically, so libpq always reads either the old + or the new value, never a mix. + details: | + Contributed by @Anand-240. + jira: + addresses: #10975 + type: Bug Fix + impact: High + +- relnote: | + Fixed plugin connectivity to use the plugin `Service` FQDN instead of its + short name, avoiding failures when a cluster-level proxy is automatically + injected into pods. + details: | + Contributed by @kdautrey. + jira: + addresses: #10921 + type: Bug Fix + impact: High + +- relnote: | + Fixed excessive operator log noise from the per-request `Cluster` + create/update validation webhook messages, now logged at `debug` instead of + `info`. + jira: + addresses: #10984 + type: Bug Fix + impact: High + +- relnote: | + Fixed `spec.postgresql.parameters` accepting keys that are not valid + PostgreSQL parameter names, which could inject arbitrary directives into + `postgresql.conf`; key names are now validated by the webhook. + jira: + addresses: #11029 + type: Bug Fix + impact: High + +- relnote: | + Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an + existing cluster: with `primaryUpdateMethod: switchover` the primary could not + be rolled out because a clean demotion needs the archiver sidecar that is + still missing. + details: | + The operator now recreates the primary Pod in place so the sidecar is injected + and archiving resumes. The check also covers plugins that inject the archiver + as a native sidecar (an init container with `restartPolicy: Always`), such as + the Barman Cloud plugin. + jira: + addresses: #11032, #11059 + type: Bug Fix + impact: High + +- relnote: | + Fixed a cluster staying in `Setting up primary` indefinitely when the + instance-creation Job exhausted its backoff limit; the operator now detects + the terminal Job failure and marks the cluster unrecoverable, naming the + failed Job and pointing to its logs. + jira: + addresses: #11035 + type: Bug Fix + impact: High + +- relnote: | + Fixed a first-primary bootstrap deadlock where a status-patch conflict after + the data PVC was created but before the initialization Job was started left + the orphan Pending PVC counted as an instance, blocking the bootstrap gate; + the PVC-state reconciler now recreates the bootstrap Job reusing the assigned + serial. + jira: + addresses: #11039 + type: Bug Fix + impact: High + +- relnote: | + Fixed external cluster names and secret selector references being joined into + filesystem paths without validation, letting a `..` component or path + separator escape the external secrets directory when the instance manager + dumps connection material; these values are now rejected at the validating + webhook and re-checked at the write site. + details: | + Reported by @r0binak. + jira: + addresses: #11045 + type: Bug Fix + impact: High + +- relnote: | + Fixed a backup getting stuck in `pending` forever: the concurrent-backup gate + ran on every reconcile and could overwrite an already-completed phase written + asynchronously by the instance manager. + details: | + The gate now runs only while the backup phase is still unset or `pending`. + jira: + addresses: #11056 + type: Bug Fix + impact: High + +- relnote: | + Fixed a declarative `VolumeSnapshot` backup being permanently marked as failed + when a stale cache made the operator re-create a snapshot it had already + provisioned, failing with `AlreadyExists`. + details: | + The operator now tolerates the collision when the existing snapshot carries + this backup's label and adopts it; a collision with a foreign snapshot still + surfaces as an error. + jira: + addresses: #11071 + type: Bug Fix + impact: High + +- relnote: | + Fixed a volume snapshot backup being discarded on a transient instance-manager + connection error (for example a dial timeout from a brief pod-network + disruption) during the finalize step, even when its snapshots were already + provisioned; such network errors are now retried instead of treated as + terminal. + jira: + addresses: #11069 + type: Bug Fix + impact: High + +- relnote: | + Fixed a replica switchover losing its `status.demotionToken` when a reconcile + was requeued between storing the token and cleaning up the transition metadata + (for example a cleanup patch failing against a flaky webhook); the empty + no-change token is no longer patched back over the stored value. + jira: + addresses: #11075 + type: Bug Fix + impact: High + +- relnote: | + Fixed `kubectl cnp psql` on Windows, where execution relied on a Unix-only + system call and failed with "not supported by windows"; Windows now launches + `kubectl exec` as a child process. + details: | + Contributed by @Utkarsh-sharma47. + jira: + addresses: #10972 + type: Bug Fix + impact: High + +- relnote: | + Fixed an unbounded memory leak in `kubectl cnp logs -f` on busy clusters, + where a per-log-group timer was never released; timers are now reused across + iterations. + details: | + Contributed by @Anand-240. + jira: + addresses: #10976 + type: Bug Fix + impact: High + diff --git a/product_docs/docs/postgres_for_kubernetes/1/resource_management.mdx b/product_docs/docs/postgres_for_kubernetes/1/resource_management.mdx index 74ef4be2d81..afa3cf0c6fd 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/resource_management.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/resource_management.mdx @@ -114,3 +114,76 @@ For more details on resource management, please refer to the ["Managing Compute Resources for Containers"](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/) page from the Kubernetes documentation. !!! + +## Integration with the Vertical Pod Autoscaler (VPA) + +The `Cluster` CRD exposes the `scale` subresource together with the label +selector for its instance pods. This makes a `Cluster` a valid `targetRef` for the +[Vertical Pod Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler) +(VPA), so VPA can observe the instance pods and emit CPU and memory +recommendations for them. + +We recommend running VPA in **recommendation-only** mode +(`updatePolicy.updateMode: Off`). In this mode VPA only reports its +recommendations, which an operator can then apply to `spec.resources` of the +`Cluster` through a normal manifest update; {{name.ln}} performs the rolling +update of the instances using its usual switchover-aware procedure. VPA +produces a recommendation per container: use the one for the `postgres` +container, since that is what `spec.resources` configures. + +Example targeting a `Cluster`: + +```yaml +apiVersion: autoscaling.k8s.io/v1 +kind: VerticalPodAutoscaler +metadata: + name: cluster-example-vpa +spec: + targetRef: + apiVersion: postgresql.k8s.enterprisedb.io/v1 + kind: Cluster + name: cluster-example + updatePolicy: + updateMode: "Off" +``` + +!!!warning + +Do not use `updateMode: Auto`, `Recreate`, or `Initial` against a +{{name.ln}}-managed `Cluster`. The operator owns the pod specification and +treats `spec.resources` of the `Cluster` as the source of truth: it does not +adopt the resources VPA writes onto a running pod, so the live pod and the +declared `spec.resources` silently diverge. Any tuning you sized against the +declared resources (for example a `shared_buffers` value the operator +validated against the memory request) no longer matches the pod's actual +limits. VPA also evicts pods through the Kubernetes eviction API, bypassing +the operator's switchover-aware sequencing; the default primary +`PodDisruptionBudget` then blocks eviction of the primary, so VPA stalls +instead of completing. Apply the VPA recommendations to the `Cluster` manifest +manually instead. +!!! + +## Integration with the Horizontal Pod Autoscaler (HPA) + +The `scale` subresource also exposes `spec.instances`, so a +[Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) +(HPA) can technically change the number of instances in a `Cluster`. +In practice this is **not recommended** for a PostgreSQL cluster, for several +reasons. + +Scaling a `Cluster` only adds or removes standby replicas; it never relieves +write load on the primary. The selector exposed through the scale subresource +matches the primary and all replicas, which have opposite workload profiles +(write-heavy primary, read-only replicas), so the per-pod average that HPA +computes from a CPU or memory metric is not a meaningful signal for any of +them. Adding a replica only dilutes that average further without addressing a +hot primary. + +HPA is also unaware of {{name.ln}}' own constraints on `spec.instances`. If +you configure synchronous replicas, a scale-down below `maxSyncReplicas + 1` +instances is rejected by the validating webhook, and HPA keeps retrying a +value it cannot satisfy. +If you nonetheless drive `spec.instances` from an HPA, base it on a custom +metric that actually reflects read replica load, and set `minReplicas` above +the synchronous-replica floor. Review the impact on replication and quorum +carefully first. diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples.mdx b/product_docs/docs/postgres_for_kubernetes/1/samples.mdx index a8a5727ee62..6b58b94f0cf 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/samples.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/samples.mdx @@ -145,6 +145,11 @@ For a list of available options, see [API reference](pg4k.v1.md). Declares a role with the `managed` stanza. Includes password management with Kubernetes secrets. +**Declarative role management with the `DatabaseRole` resource** +: [`role-examples.yaml`](../samples/role-examples.yaml): + Standalone `DatabaseRole` resources targeting an existing cluster, including + password management with a Kubernetes secret. + ## Managed services **Cluster with managed services** diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-full.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-full.yaml index 988cd2596eb..60f5fbac53e 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-full.yaml +++ b/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-full.yaml @@ -35,7 +35,7 @@ metadata: name: cluster-example-full spec: description: "Example of cluster" - imageName: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 + imageName: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 # imagePullSecret is only required if the images are located in a private registry # imagePullSecrets: # - name: private_registry_access diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-logical-source.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-logical-source.yaml index 9f9e355a85e..23180b33481 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-logical-source.yaml +++ b/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-logical-source.yaml @@ -1,4 +1,15 @@ apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: DatabaseRole +metadata: + name: cluster-example-app +spec: + cluster: + name: cluster-example + name: app + login: true + replication: true +--- +apiVersion: postgresql.k8s.enterprisedb.io/v1 kind: Cluster metadata: name: cluster-example @@ -29,12 +40,6 @@ spec: highAvailability: synchronizeLogicalDecoding: true - managed: - roles: - - name: app - login: true - replication: true - postgresql: parameters: hot_standby_feedback: 'on' diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-example-cluster-image-catalog.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/pooler-example-cluster-image-catalog.yaml similarity index 100% rename from product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-example-cluster-image-catalog.yaml rename to product_docs/docs/postgres_for_kubernetes/1/samples/pooler-example-cluster-image-catalog.yaml diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-example-explicit-image.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/pooler-example-explicit-image.yaml similarity index 100% rename from product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-example-explicit-image.yaml rename to product_docs/docs/postgres_for_kubernetes/1/samples/pooler-example-explicit-image.yaml diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-example-image-catalog.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/pooler-example-image-catalog.yaml similarity index 100% rename from product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-example-image-catalog.yaml rename to product_docs/docs/postgres_for_kubernetes/1/samples/pooler-example-image-catalog.yaml diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples/postgis-example.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/postgis-example.yaml index 99491f8322f..21ce41aec04 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/samples/postgis-example.yaml +++ b/product_docs/docs/postgres_for_kubernetes/1/samples/postgis-example.yaml @@ -3,7 +3,7 @@ kind: Cluster metadata: name: postgis-example spec: - imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:18.3-minimal-ubi9 + imageName: docker.enterprisedb.com/k8s/postgresql:18.4-minimal-ubi9 instances: 1 storage: diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/role-examples.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/role-examples.yaml similarity index 100% rename from product_docs/docs/postgres_for_kubernetes/preview/samples/role-examples.yaml rename to product_docs/docs/postgres_for_kubernetes/1/samples/role-examples.yaml diff --git a/product_docs/docs/postgres_for_kubernetes/1/scheduling.mdx b/product_docs/docs/postgres_for_kubernetes/1/scheduling.mdx index 30af886cee0..c746900f66d 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/scheduling.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/scheduling.mdx @@ -46,7 +46,7 @@ metadata: name: cluster-example spec: instances: 3 - imageName: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 + imageName: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 affinity: enablePodAntiAffinity: true # Default value diff --git a/product_docs/docs/postgres_for_kubernetes/1/security.mdx b/product_docs/docs/postgres_for_kubernetes/1/security.mdx index 4fd0ad4ac25..77063aea444 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/security.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/security.mdx @@ -1,9 +1,12 @@ --- title: 'Security' +originalFilePath: 'src/security.md' --- -This section contains information about security for {{name.ln}}, -that are analyzed at 3 different layers: Code, Container and Cluster. +{{name.ln}} is designed to be secure by default, following the "Least Privilege" +principle across all layers of the stack. This document outlines our security +governance, supply chain integrity, and the technical controls analyzed at three +distinct layers: Code, Container, and Cluster. !!! Warning The information contained in this page must not exonerate you from @@ -100,10 +103,139 @@ container-level security: Security at the cluster level takes into account all Kubernetes components that form both the control plane and the nodes, as well as the applications that run in -the cluster (PostgreSQL included). +the cluster (PostgreSQL included). We start by defining the trust model and the +security boundaries that frame the rest of this section. + +### Trust Model and Security Boundaries + +{{name.ln}} follows a clear separation of responsibilities between the +operator and the Kubernetes platform for enforcing security policies. The +subsections below describe who is trusted to influence the PostgreSQL Pods, +where the enforcement boundary actually lies, how the operator confines the +resources it manages, and how access to all of this is governed by RBAC. + +#### Trusted Cluster Resource Writers + +Any user with create or update permissions on the `Cluster` custom resource is +trusted to define the full specification of the PostgreSQL Pods that the +operator manages. This includes security-sensitive fields such as +`spec.securityContext`, `spec.podSecurityContext`, and +`spec.serviceAccountName`. The operator applies these settings as instructed. +When a Cluster writer does not override them, the operator applies a hardened +default Pod and container security context (see +[Pod and Container Security Contexts](#pod-and-container-security-contexts)). + +This is consistent with how all Kubernetes operators work: the operator acts as +a privileged agent that translates high-level intent into low-level Kubernetes +resources. Granting someone write access to a Cluster resource is equivalent +to granting them control over the resulting Pods, Services, PVCs, and other +managed resources. + +The same principle applies to [CNPG-I plugins](cnpg_i.md). A plugin hooks into +the Pod lifecycle and can modify any field of the Pod specification before the +Pod is created. Installing a plugin is therefore an explicit trust decision +made by the cluster administrator, on par with granting write access to a +Cluster resource. + +The same authority extends into the database itself: because the operator +reconciles PostgreSQL as the superuser, a Cluster writer gains superuser-level +influence over the resulting cluster through documented, intended fields, +including: + +- the bootstrap SQL hooks `postInitSQL`, `postInitApplicationSQL`, and + `postInitTemplateSQL`, executed as the `postgres` superuser at initialization + (see [Executing Queries After Initialization](bootstrap.md#executing-queries-after-initialization)); +- [inline managed roles](declarative_role_management.md#inline-managed-roles) + (`spec.managed.roles`), which may set `superuser: true` or grant membership of + existing roles, and can use PostgreSQL features such as `COPY ... FROM PROGRAM` + to run commands inside the operand Pod; +- custom PostgreSQL configuration, including + [`pg_hba`](postgresql_conf.md#the-pg_hba-section) rules (for example `trust` + authentication) and parameters that shape the cluster's security posture and + durability, such as `password_encryption`, `fsync`, and memory-related + settings. + +This is the intended trust model, not a privilege escalation. + +Code running in the operand Pod also runs under its mounted `ServiceAccount`, +which can read the Secrets associated with its own cluster (see +[Calls to the API server made by the instance manager](#calls-to-the-api-server-made-by-the-instance-manager) +and ["Secrets"](applications.md#secrets)). A Cluster writer can therefore read +those Secrets, confined by [Namespace Isolation](#namespace-isolation) to the +Cluster's own namespace. + +!!!note +These trust boundaries are also covered in the project's +[self security assessment](https://github.com/cloudnative-pg/cloudnative-pg/blob/main/.github/threat-catalog.yaml). +!!! + +#### Kubernetes Admission Control + +The operator creates Pods through the standard Kubernetes API, meaning every +Pod goes through the full admission control chain configured on the cluster. +This includes +[Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/) +(PSA), the built-in Kubernetes mechanism that enforces +[Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/) +at the namespace level, as well as any third-party policy engine in use. If a +namespace enforces the PSA `restricted` or `baseline` profile, the Kubernetes +API server rejects any Pod that violates the policy, including Pods created by +the operator. + +Because the trusted Cluster writers described above can set any Pod field, this +admission control chain (not the operator) is the boundary that enforces Pod +security policies in your environment. + +#### Namespace Isolation + +The operator confines all managed resources to the namespace of their parent +Cluster. Instance Pods are always created in the same namespace as their +Cluster, set explicitly and deterministically rather than inferred from any +other relationship. Because Kubernetes owner references are confined to a +single namespace, the operator also cannot establish ownership of resources in +any other namespace. + +#### RBAC on Custom Resources + +Access to {{name.ln}} custom resources is governed by standard Kubernetes +RBAC. Since write access to a Cluster resource implies control over the +resulting Pods, annotations like `k8s.enterprisedb.io/podPatch` (which applies a +user-supplied patch to the managed Pods), `k8s.enterprisedb.io/validation`, and +`k8s.enterprisedb.io/reconciliationLoop` are subject to the same RBAC rules as the +Cluster resource itself. + +In particular, setting `k8s.enterprisedb.io/validation` to `disabled` bypasses the +operator's own validating admission webhook for that Cluster, including the +syntactic and applicability checks performed on `k8s.enterprisedb.io/podPatch`. +{{name.ln}}' webhook validation is therefore advisory: it can be turned off +by the same actor who can write the Cluster, so it is not a security boundary. +Kubernetes admission control still applies to the resulting Pods regardless of +this annotation. + +The same reasoning applies to the `DatabaseRole` resource: its specification +allows `superuser: true` and membership of any existing role through +`inRoles`, including the `postgres` role itself. Write access to +`DatabaseRole` objects in a namespace is therefore equivalent to superuser +access on the PostgreSQL clusters in that namespace, and deserves the same +care as write access to the `Cluster` resource. + +Treat write access to these resources as a high-privilege grant: for +multi-tenant deployments, isolate tenants in separate namespaces and scope it +per namespace with Kubernetes RBAC, relying on +[Namespace Isolation](#namespace-isolation) to bound the impact. + +The RBAC discussed here governs access to {{name.ln}}' own custom resources. +The next section covers the complementary side: the RBAC that the operator +itself relies on to manage Kubernetes resources on your behalf. + ### Role Based Access Control (RBAC) +This section covers the operator's *own* RBAC (the service account and roles it +uses to manage Kubernetes resources on your behalf), as opposed to the user +access to custom resources discussed in +[RBAC on Custom Resources](#rbac-on-custom-resources) above. + The operator interacts with the Kubernetes API server using a dedicated service account named `postgresql-operator-manager`. This service account is typically installed in the operator namespace, commonly `postgresql-operator-system`. However, the namespace may vary @@ -123,8 +255,8 @@ For OpenShift specificities on this matter, please consult the The above permissions are exclusively reserved for the operator's service account to interact with the Kubernetes API server. They are not directly accessible by the users of the operator that interact only with `Cluster`, - `Pooler`, `Backup`, `ScheduledBackup`, `ImageCatalog` and - `ClusterImageCatalog` resources. + `Pooler`, `Backup`, `ScheduledBackup`, `Database`, `Publication`, + `Subscription`, `ImageCatalog` and `ClusterImageCatalog` resources. Below we provide some examples and, most importantly, the reasons why {{name.ln}} requires full or partial management of standard Kubernetes @@ -189,6 +321,7 @@ namespaced or non-namespaced resources. the creation of pods on unscheduled nodes, or triggering a switchover if the primary lives in an unscheduled node. + #### Deployments and `ClusterRole` Resources As mentioned above, each deployment method may have variations in the namespace @@ -223,6 +356,14 @@ The operator currently requires `ClusterRole` permissions to read `nodes` and `ClusterImageCatalog` objects. All other permissions can be namespace-scoped (i.e., `Role`) or cluster-wide (i.e., `ClusterRole`). +If you remove the `ClusterRoles` permissions, +the operator will crash unless you explicitly set the experimental `--no-cluster-roles=true` +command-line argument by editing the operator's `Deployment` definition. +Note that enabling this flag will disable the operator's ability +to work with `ClusterImageCatalog` objects and respond to changes in `Node` status. +This also affects Pooler resources: any Pooler referencing a `ClusterImageCatalog` +for its PgBouncer image will not react to catalog updates. + Even with these permissions, if someone gains access to the `ServiceAccount`, they will only have `get`, `list`, and `watch` permissions, which are limited to viewing resources. However, if an unauthorized user gains access to the @@ -244,6 +385,96 @@ PostgreSQL `Cluster` resource name. The operand can only access a specific and limited subset of resources through the API server. A service account is the [recommended way to access the API server from within a Pod](https://kubernetes.io/docs/tasks/run-application/access-api-from-pod/). +#### Using a shared ServiceAccount + +By default, {{name.ln}} creates a dedicated `ServiceAccount` for each cluster, +named after the cluster itself. However, in cloud environments using IAM roles +(such as AWS IRSA, GCP Workload Identity, or Azure Workload Identity), each +cluster creating its own `ServiceAccount` requires individual IAM configuration +for every new cluster, making it difficult to scale when managing multiple +clusters. + +{{name.ln}} allows multiple clusters to share a single `ServiceAccount` by +specifying the `serviceAccountName` field in the cluster specification. This +enables one-time IAM configuration that works across all clusters using that +`ServiceAccount`. + +!!!important +When using a shared `ServiceAccount`, you are responsible for creating and +managing the `ServiceAccount` yourself. The operator will validate that the +specified `ServiceAccount` exists but will not create or modify it. +!!! + +Here's an example of using a shared `ServiceAccount`: + +```yaml +# Create the shared ServiceAccount once +apiVersion: v1 +kind: ServiceAccount +metadata: + name: postgres-cloud-sa + annotations: + # AWS IRSA annotation + eks.amazonaws.com/role-arn: arn:aws:iam:us-east-1:123456789012:role/PostgresRole +--- +# Reference it from multiple clusters +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +metadata: + name: cluster-prod +spec: + serviceAccountName: postgres-cloud-sa + instances: 3 + storage: + size: 100Gi +``` + +!!!note +The `serviceAccountName` field is mutually exclusive with +`serviceAccountTemplate`. You can either let the operator manage the +`ServiceAccount` (optionally customizing it with `serviceAccountTemplate`) +or reference an existing one with `serviceAccountName`, but not both. +!!! + +!!!warning +The `serviceAccountName` field is immutable once set. If you need to change +the `ServiceAccount`, you must recreate the cluster. +!!! + +!!!note +When multiple clusters share a `ServiceAccount`, the operator creates +a separate `Role` and `RoleBinding` for each cluster. The shared +`ServiceAccount` accumulates the Kubernetes RBAC permissions of all +clusters using it. Each `Role` is narrowly scoped to the specific +cluster's resources, so this does not constitute a privilege escalation. +!!! + +#### Using a shared ServiceAccount with Poolers + +The same shared `ServiceAccount` feature is available for `Pooler` resources. +When deploying PgBouncer poolers in cloud environments with IAM integration, +you can specify the `serviceAccountName` field in the Pooler spec to reference +an existing `ServiceAccount` instead of having the operator create one per pooler. + +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Pooler +metadata: + name: pooler-prod +spec: + cluster: + name: cluster-prod + serviceAccountName: pgbouncer-cloud-sa + instances: 3 + pgbouncer: + poolMode: session +``` + +!!!warning +As with clusters, the `serviceAccountName` field on poolers is immutable +once set. If you need to change the `ServiceAccount`, you must recreate +the pooler. +!!! For transparency, the permissions associated with the service account are defined in the [roles.go](https://github.com/cloudnative-pg/cloudnative-pg/blob/main/pkg/specs/roles.go) @@ -302,28 +533,130 @@ Here instead, we provide the same summary for resources specific to : The instance manager requires to `update` and `patch` the status of any `Backup` resource in the namespace -### Pod Security Policies +### Pod and Container Security Contexts -!!! Important - Starting from Kubernetes v1.21, the use of `PodSecurityPolicy` has been - deprecated, and as of Kubernetes v1.25, it has been completely removed. Despite - this deprecation, we acknowledge that the operator is currently undergoing - testing in older and unsupported versions of Kubernetes. Therefore, this - section is retained for those specific scenarios. +A [Security Context](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) +defines privilege and access control settings for a pod or container. -A [Pod Security Policy](https://kubernetes.io/docs/concepts/policy/pod-security-policy/) -is the Kubernetes way to define security rules and specifications that a pod needs to meet -to run in a cluster. -For InfoSec reasons, every Kubernetes platform should implement them. +{{name.ln}} does not require *privileged* mode for container execution. +The PostgreSQL containers run as the `postgres` system user. No component +whatsoever requires running as `root`. -{{name.ln}} does not require *privileged* mode for containers execution. -The PostgreSQL containers run as `postgres` system user. No component whatsoever requires running as `root`. +Likewise, Volume access does not require *privileged* mode nor `root` +privileges. Proper permissions must be assigned by the Kubernetes platform +and/or administrators. The PostgreSQL containers run with a read-only root +filesystem (i.e. no writable layer). -Likewise, Volumes access does not require *privileges* mode or `root` privileges either. -Proper permissions must be properly assigned by the Kubernetes platform and/or administrators. -The PostgreSQL containers run with a read-only root filesystem (i.e. no writable layer). +The operator manages the setting of security contexts for all pods and +containers of a PostgreSQL cluster. The [Seccomp Profile](https://kubernetes.io/docs/tutorials/security/seccomp/) +to be used for the PostgreSQL containers can be configured with the +`spec.seccompProfile` section of the `Cluster` resource. If this section is left +blank, the containers will use a seccompProfile `Type` of `RuntimeDefault`, that +is, the container runtime default. -The operator explicitly sets the required security contexts. +The security context of PostgreSQL containers using the default `seccompProfile` +will look like this: + +``` +securityContext: + allowPrivilegeEscalation: false + capabilities: + drop: + - ALL + privileged: false + readOnlyRootFilesystem: true + runAsNonRoot: true + seccompProfile: + type: RuntimeDefault +``` + +#### Customizing Security Contexts + +{{name.ln}} provides fine-grained control over security contexts for both +pods and containers through the `spec.podSecurityContext` and +`spec.securityContext` fields respectively. + +!!! info Important + Changing security contexts can significantly affect the security posture + of your PostgreSQL clusters and may prevent pods from starting or + operating correctly. Before making changes, review which fields you will + override and how they merge with the operator defaults, test changes + in a non-production environment, and apply the minimal, well-documented + modifications necessary. + + +**Pod Security Context** (`spec.podSecurityContext`): +This allows you to override the default `PodSecurityContext` applied to all +PostgreSQL cluster pods. When specified, it will merge with the operator's +default settings, with your values taking precedence for explicitly set fields. + +Example: + +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +metadata: + name: cluster-example +spec: + instances: 3 + podSecurityContext: + runAsUser: 26 + runAsGroup: 26 + fsGroup: 26 + supplementalGroups: [2000, 3000] + fsGroupChangePolicy: "OnRootMismatch" +``` + +**Container Security Context** (`spec.securityContext`): +This allows you to override the default `SecurityContext` applied to all +containers within the PostgreSQL cluster pods. Like `podSecurityContext`, it +merges with the operator's defaults. + +Example: + +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +metadata: + name: cluster-example +spec: + instances: 3 + securityContext: + allowPrivilegeEscalation: false + # Note: capabilities are not merged with operator defaults. + # If specified, they fully replace any defaults. + capabilities: + drop: + - ALL + add: + - NET_BIND_SERVICE + readOnlyRootFilesystem: true + runAsNonRoot: true +``` + +!!! info Important + For any fields you don't explicitly set, the operator will apply its + secure defaults. This ensures that even partial configurations maintain + security best practices. + + +!!! note + These fields are particularly useful when working with the + [Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/) + `restricted` profile, which has strict requirements for pod and container + security contexts. As described in + [Kubernetes Admission Control](#kubernetes-admission-control), it is this + admission chain (not the operator) that enforces such profiles on the + resulting Pods. + + +#### Security Context Constraints + +When running in an environment that is utilizing +[Security Context Constraints (SCC)](https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html) +the operator does not explicitly set the security context of the PostgreSQL +cluster pods, but rather allows the pods to inherit the restricted Security +Context Constraints that are already defined. On Red Hat OpenShift, Cloud Native PostgreSQL runs in `restricted` security context constraint, the most restrictive one. The goal is to limit the execution of a pod to a namespace allocated UID @@ -348,18 +681,17 @@ You can assign an [AppArmor](https://kubernetes.io/docs/tutorials/security/apparmor/) profile to the `postgres`, `initdb`, `join`, `full-recovery` and `bootstrap-controller` containers inside every `Cluster` pod through the `container.apparmor.security.beta.kubernetes.io` annotation. - -!!!Seealso "Example of cluster annotations" +For example: + +```yaml +kind: Cluster +metadata: + name: cluster-apparmor + annotations: + container.apparmor.security.beta.kubernetes.io/postgres: runtime/default + container.apparmor.security.beta.kubernetes.io/initdb: runtime/default + container.apparmor.security.beta.kubernetes.io/join: runtime/default ``` - kind: Cluster - metadata: - name: cluster-apparmor - annotations: - container.apparmor.security.beta.kubernetes.io/postgres: runtime/default - container.apparmor.security.beta.kubernetes.io/initdb: runtime/default - container.apparmor.security.beta.kubernetes.io/join: runtime/default -``` -!!! !!! Warning Using this kind of annotations can result in your cluster to stop working. @@ -408,13 +740,50 @@ section of the Kubernetes documentation for further information. levels, as listed in the table below: | System | Port number | Exposing | Name | TLS | Authentication | -| :--------------- | :---------- | :------------------ | :--------------- | :------- | :------------- | +|:-----------------|:------------|:--------------------|:-----------------|:---------|:---------------| | operator | 9443 | webhook server | `webhook-server` | Yes | Yes | | operator | 8080 | metrics | `metrics` | No | No | | instance manager | 9187 | metrics | `metrics` | Optional | No | -| instance manager | 8000 | status | `status` | Yes | No | +| instance manager | 8000 | status | `status` | Yes | Partial (1) | | operand | 5432 | PostgreSQL instance | `postgresql` | Optional | Yes | +(1) Status, health, and probe endpoints are unauthenticated. Sensitive +endpoints (backup, `pg_controldata`, partial WAL archive, and instance-manager +upgrade) require the operator's client certificate, as described in +[Operator-to-instance authentication](#operator-to-instance-authentication) +below. + +#### Operator-to-instance authentication + +The operator generates a self-signed ECDSA client certificate in memory at +startup and publishes its SHA-256 public-key fingerprint in the cluster's +`.status.operatorCertificateFingerprint`. The instance manager pins that +fingerprint and rejects any call to its sensitive endpoints (backup, +`pg_controldata`, partial WAL archive, and instance-manager upgrade) that does +not present a matching certificate. Status, health, and probe endpoints remain +unauthenticated. + +The certificate is never written to disk and is regenerated on every operator +restart, so trust derives from fingerprint pinning rather than CA validation. + +This protection has a hard requirement: the status port **must** be served over +TLS, which has been the default since v1.24. A client certificate can only be +presented over a TLS connection, so the protected endpoints are reachable by the +operator only when the status port uses TLS. + +!!!warning +If the status port is not served over TLS, the instance manager cannot +authenticate the operator and **permanently** rejects every call to its +protected endpoints (backup, `pg_controldata`, partial WAL archive, and +instance-manager upgrade) with `401 Unauthorized`. This is not a transient +condition and will not resolve on its own. It can affect instances created by an +operator older than v1.24 (whose status port serves plain HTTP) once their +instance manager is upgraded to a version that enforces this authentication: such +instances must be rolled out so their Pods are recreated with a TLS-enabled status +port. Newly created instances always enable TLS on the status port and are +unaffected. +!!! + ### PostgreSQL The current implementation of {{name.ln}} automatically creates @@ -444,6 +813,13 @@ versions it is set to `md5`. remove it (if previously generated by the operator) and set the password of the `postgres` user to `NULL` (de facto disabling remote access through password authentication). +!!! info Important + PostgreSQL may include cleartext role passwords in its logs for some role + operations, as mentioned in the [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-createrole.html). + {{name.ln}} ensures that `postgres` logging (both statement logging and + error statement logging) is temporarily suppressed for CREATE/ALTER ROLE + operations with passwords, thus preventing any password leakage. + See the ["Secrets" section in the "Connecting from an application" page](applications.md#secrets) for more information. You can use those files to configure application access to the database. @@ -452,7 +828,7 @@ By default, every replica is automatically configured to connect in **physical async streaming replication** with the current primary instance, with a special user called `streaming_replica`. The connection between nodes is **encrypted** and authentication is via **TLS client certificates** (please refer to the -["Client TLS/SSL Connections"]\(ssl_connections.md#"Client TLS/SSL Connections") page +["Client TLS/SSL Connections"](ssl_connections.md) page for details). By default, the operator requires TLS v1.3 connections. Currently, the operator allows administrators to add `pg_hba.conf` lines directly in the manifest @@ -471,6 +847,45 @@ For further detail on how `pg_ident.conf` is managed by the operator, see the !!! Important Examples assume that the Kubernetes cluster runs in a private and secure network. +#### Schema resolution and `search_path` hardening + +A user with privileges on a database can plant objects (functions, +operators, tables, or types) in a writable schema such as `public` and +change the database- or role-level `search_path` (for example with +`ALTER DATABASE ... SET search_path` or `ALTER ROLE ... SET +search_path`). A privileged session that later connects to that database +inherits the tenant-controlled `search_path`, so an unqualified +reference in one of its queries could resolve to the planted object +instead of the intended one. This is a privilege-escalation vector +analogous to +[CWE-426 (Untrusted Search Path)](https://cwe.mitre.org/data/definitions/426.html), +and the same class of issue as the well-known +[CVE-2018-1058](https://www.postgresql.org/support/security/CVE-2018-1058/). + +To prevent this, {{name.ln}} pins the `search_path` on every +connection it opens to PostgreSQL to a fixed value of +`pg_catalog, public, pg_temp`, regardless of any `search_path` +configured on the database or the connecting role: + +- `pg_catalog` is searched first, so a built-in object always takes + precedence over a same-named object planted in another schema; +- `pg_temp` (the session-private temporary schema) is searched last + rather than first, so it cannot shadow relations or data types. + +In addition, the `SECURITY DEFINER` lookup function used by the +PgBouncer integration is created with its own pinned `search_path`, and +the monitoring queries run inside a transaction whose `search_path` is +pinned as described in the ["Monitoring" page](monitoring.md). + +!!!note +User-authored SQL — `postInitSQL`/`postInitApplicationSQL`/`postInitTemplateSQL` +during bootstrap, and the post-import queries of a logical import — runs +with the standard `"$user", public` resolution so that it keeps behaving +as it would in a plain PostgreSQL session. Schema-qualify object +references in those scripts if you need them to be independent of the +`search_path`. +!!! + ### Storage {{name.ln}} delegates encryption at rest to the underlying storage class. For diff --git a/product_docs/docs/postgres_for_kubernetes/1/ssl_connections.mdx b/product_docs/docs/postgres_for_kubernetes/1/ssl_connections.mdx index 7db15e04a83..e569bff942b 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/ssl_connections.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/ssl_connections.mdx @@ -180,7 +180,7 @@ Output: version -------------------------------------------------------------------------------------- ------------------ -PostgreSQL 18.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat +PostgreSQL 18.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5), 64-bit (1 row) ``` diff --git a/product_docs/docs/postgres_for_kubernetes/1/storage.mdx b/product_docs/docs/postgres_for_kubernetes/1/storage.mdx index 050fa804d57..1b365d3ad3d 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/storage.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/storage.mdx @@ -339,10 +339,76 @@ $ kubectl get pods NAME READY STATUS RESTARTS AGE cluster-example-1 1/1 Running 0 5m58s cluster-example-2 1/1 Running 0 5m43s -cluster-example-4-join-v2 0/1 Completed 0 17s -cluster-example-4 1/1 Running 0 10s +cluster-example-3-join-v2 0/1 Completed 0 17s +cluster-example-3 1/1 Running 0 10s ``` +## Volume reduction + +Kubernetes does not provide an API to shrink a PVC, and {{name.ln}}' +validating webhook rejects any attempt to decrease `.spec.storage.size`, +`.spec.walStorage.size` or any tablespace storage size in `.spec.tablespaces`. +You can still reduce the storage of a cluster, but only by recreating +each instance with a smaller volume, as described below. + +!!!warning + +{{name.ln}} does not support automated volume shrinking, as it is a +delicate operation that can lead to data loss if performed incorrectly. For +the time being, it can only be achieved manually, through the supervised +procedure described below. +This procedure requires you to temporarily disable the validating webhook. +While validation is disabled, the operator accepts spec changes that would +normally be rejected, including unsafe or destructive ones. Proceed with +caution and at your own risk, and re-enable validation as soon as possible. + +Before you start, make sure the cluster's current data, WAL, and any tablespace +data comfortably fit within the new, smaller sizes. If they don't, the instances +recreated on smaller volumes can fail to rejoin or quickly run out of space. +!!! + +To reduce the size of the persistent volumes: + +1. Disable the validating webhook by setting the `k8s.enterprisedb.io/validation: disabled` + annotation on the `Cluster`, set `.spec.storage.size` (and, if present, + `.spec.walStorage.size` or tablespace storage size in `.spec.tablespaces`) + to the new, smaller value, and increase `.spec.instances` by 1 to provide a + spare instance during the rollout. + +2. Re-enable validation by removing the `k8s.enterprisedb.io/validation` annotation (or + setting it to `enabled`). The new, smaller size is now stored in the spec + and is applied to every instance the operator recreates from this point on. + Existing instances keep their current volumes; for each one, the operator + logs an informational `cannot decrease storage requirement` message until + that instance is recreated. This is expected and harmless. + +3. Destroy one standby that still has a volume of the old size. The operator + provisions a replacement instance — reusing the name of the one you + destroyed, since instance serials are recycled — on the new, smaller volume: + + ```sh + kubectl-cnp destroy CLUSTER INSTANCE + ``` + +4. Wait for the operator to create the replacement instance and for it to + become healthy. + +5. Repeat steps 3 and 4 for every remaining standby that still has an + old-size volume. + +6. Promote one of the newly created standbys so that the current primary — + which still has an old-size volume — is demoted to a standby: + + ```sh + kubectl-cnp promote CLUSTER INSTANCE + ``` + +7. Destroy the former primary (now a standby with an old-size volume) so the + operator provisions its replacement on the new, smaller volume, and wait + until all instances are healthy. + +8. Decrease `.spec.instances` back to its original value. + ## Static provisioning of persistent volumes {{name.ln}} was designed to work with dynamic volume provisioning. This diff --git a/product_docs/docs/postgres_for_kubernetes/1/troubleshooting.mdx b/product_docs/docs/postgres_for_kubernetes/1/troubleshooting.mdx index 836febe699b..f1368e32c73 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/troubleshooting.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/troubleshooting.mdx @@ -221,7 +221,7 @@ Cluster in healthy state Name: cluster-example Namespace: default System ID: 7044925089871458324 -PostgreSQL Image: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 +PostgreSQL Image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 Primary instance: cluster-example-1 Instances: 3 Ready instances: 3 @@ -290,7 +290,7 @@ kubectl describe cluster -n | grep "Image Name" Output: ```shell - Image Name: docker.enterprisedb.com/k8s/postgresql:18.3-standard-ubi9 + Image Name: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 ``` !!!note diff --git a/product_docs/docs/postgres_for_kubernetes/preview/addons.mdx b/product_docs/docs/postgres_for_kubernetes/preview/addons.mdx deleted file mode 100644 index fe8935148bf..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/addons.mdx +++ /dev/null @@ -1,580 +0,0 @@ ---- -title: 'Add-ons' -originalFilePath: 'src/addons.md' ---- - -{{name.ln}} supports add-ons that can be enabled on a -per-cluster basis. These add-ons are: - -1. [External backup adapter](#external-backup-adapter) -2. [Kasten](#kasten) -3. [Velero](#velero) - -!!!info -If you are planning to use Velero in OpenShift, please refer to the -[OADP section](openshift.md#oadp-for-velero) in the Openshift documentation. -!!! - -All add-ons will automatically be available to the operator and to be used will -need to be enabled at the cluster level via the `k8s.enterprisedb.io/addons` -annotation. - -## External Backup Adapter - -The external backup adapter add-ons provide a generic way to integrate -{{name.ln}} in a third-party tool for backups through -customizable ways to identify via labels and/or annotations: - -- which PVC group to backup -- which PVCs to exclude, in case the cluster has one or more active replicas -- the Pod running the PostgreSQL instance that has been selected for the backup - (a standby or, if not available, the primary) - -You can choose between two add-ons that only differ from each other for the way -they allow you to configure the adapter for your backup system: - -- `external-backup-adapter`: in case you want to customize the behavior at the - operator's configuration level via either a config map or a secret - and share - it with all the Postgres clusters that are managed by the operator's deployment - (see [the `external-backup-adapter` section below](#the-external-backup-adapter-add-on)) -- `external-backup-adapter-cluster`: in case you want to customize the behavior - of the adapter at the Postgres cluster level, through a specific annotation - (see [the `external-backup-adapter-cluster` section below](#the-external-backup-adapter-cluster-add-on)) - -Such add-ons allow you to define the names of the annotations that will contain -the commands to be run before or after taking a backup in the pod selected by -the operator. - -As a result, any third-party backup tool for Kubernetes can rely on the above -to coordinate itself with a PostgreSQL cluster, or a set of them. - -Recovery simply relies on the operator to reconcile the cluster from an -existing PVC group. - -!!!info Important -The External Backup Adapter is not a tool to perform backups. It simply -provides a generic interface that any third-party backup tool in the Kubernetes -space can use. Such tools are responsible for safely storing the PVC -and/or the content, and make it available at recovery time together with -all the necessary resource definitions of your Kubernetes cluster. -!!! - -### Customizing the adapter - -As mentioned above, the adapter can be configured in two ways, which then -determines the actual `add-on` you need to use in your `Cluster` resource. - -If you are planning to define the same behavior for all the Postgres `Cluster` -resources managed by the operator, we recommend that you use the -`external-backup-adapter` add-on, and configure the annotations/labels in the -operator's configuration. - -If you are planning to have different behaviors for a subset of the Postgres -`Cluster` resources that you have, we recommend that you use the -`external-backup-adapter-cluster` add-on. - -Both add-ons share the same capabilities in terms of customization, which needs -to be defined as a YAML object having the following keys: - -- `electedResourcesDecorators` -- `excludedResourcesDecorators` -- `excludedResourcesSelector` -- `backupInstanceDecorators` -- `preBackupHookConfiguration` -- `postBackupHookConfiguration` - -Each section is explained below. Further down you'll find the instructions on -how to customize each of the two add-ons, with some examples. - -#### The `electedResourcesDecorators` section - -This section allows you to configure an array of labels and/or annotations that -will be put on every elected PVC group. - -Each element of the array must have the following fields: - -`key` -: the name of the key for the label or annotation - -`metadataType` -: the type of metadata, either `"label"` or `"annotation"` - -`value` -: the value that will be assigned to the label or annotation - -#### The `excludedResourcesDecorators` section - -This section allows you to configure an array of labels and/or annotations that -will be placed on every excluded pod and PVC. - -Each element of the array must have the same fields as the -`electedResourcesDecorators` section above. - -#### The `excludedResourcesSelector` section - -This section selects Pods and PVCs that are applied to the -`excludedResourcesDecorators`. It accepts a [label selector rule](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors) -as value. When empty, all the Pods and every PVC that is not elected will be excluded. - -#### The `backupInstanceDecorators` section - -This section allows you to configure an array of labels and/or annotations that -will be placed on the instance that has been selected for the backup by the operator -and which contains the hooks to be run. - -Each element of the array must have the same fields as the -`electedResourcesDecorators` section above. - -#### The `preBackupHookConfiguration` section - -This section allows you to control the names of the annotations in which the -operator will place the name of the container, the command to run before taking -the backup, and the command to run in case of error/abort on the third-party -tool side. Such metadata will be applied on the instance that's been selected by -the operator for the backup (see `backupInstanceDecorators` above). - -The following fields must be provided: - -`container` -: Specifies where to place the information about the container - that will run the pre-backup command. The container name is a fixed value and - cannot be configured. Will be saved in the annotations. To decorate the pod - with hooks refer to: `instanceWithHookDecorators` - -`command` -: Specifies where to place the information about the command that - will be executed before the backup is taken. The command that will be - executed is a fixed value and cannot be configured. Will be saved in the - annotations. To decorate the pod with hooks refer to: - `instanceWithHookDecorators` - -`onError` -: Specifies where to place the information about the command that - will be executed in case of an error. The command that will be executed is a - fixed value and cannot be configured. Will be saved in the annotations. To - decorate the pod with hooks refer to: `instanceWithHookDecorators` - -#### The `postBackupHookConfiguration` section - -This section allows you to control the names of the annotations in which the -operator will place the name of the container and the command to run after taking -the backup. Such metadata will be applied on the instance that's been selected by -the operator for the backup (see `backupInstanceDecorators` above). - -The following fields must be provided: - -`container` -: Specifies where to place the information about the container - that will run the post-backup command. The container name is a fixed value - and cannot be configured. Will be saved in the annotations. To decorate the pod - with hooks refer to: `instanceWithHookDecorators` - -`command` -: Specifies where to place the information about the command that - will be executed after the backup is taken. The command that will be executed - is a fixed value and cannot be configured. Will be saved in the annotations. To - decorate the pod with hooks refer to: `instanceWithHookDecorators` - -### The `external-backup-adapter` add-on - -The `external-backup-adapter` add-on can be entirely configured at operator's -level via the `EXTERNAL_BACKUP_ADDON_CONFIGURATION` field in the operator's -`ConfigMap`/`Secret`. - -For more information, please refer to the provided sample file at the end of -this section, or the example below: - -```yaml -apiVersion: v1 -kind: ConfigMap -metadata: - name: postgresql-operator-controller-manager-config - namespace: postgresql-operator-system -data: - # ... - EXTERNAL_BACKUP_ADDON_CONFIGURATION: |- - electedResourcesDecorators: - - key: "app.example.com/elected" - metadataType: "label" - value: "true" - excludedResourcesSelector: app=xyz,env=prod - excludedResourcesDecorators: - - key: "app.example.com/excluded" - metadataType: "label" - value: "true" - - key: "app.example.com/excluded-reason" - metadataType: "annotation" - value: "Not necessary for backup" - backupInstanceDecorators: - - key: "app.example.com/hasHooks" - metadataType: "label" - value: "true" - preBackupHookConfiguration: - container: - key: "app.example.com/pre-backup-container" - command: - key: "app.example.com/pre-backup-command" - onError: - key: "app.example.com/pre-backup-on-error" - postBackupHookConfiguration: - container: - key: "app.example.com/post-backup-container" - command: - key: "app.example.com/post-backup-command" -``` - -The add-on can be activated by adding the following annotation to the `Cluster` -resource: - -```yaml -k8s.enterprisedb.io/addons: '["external-backup-adapter"]' -``` - -### The `external-backup-adapter-cluster` add-on - -The `external-backup-adapter-cluster` add-on must be configured in each -`Cluster` resource you intend to use it through the -`k8s.enterprisedb.io/externalBackupAdapterClusterConfig` annotation - which -accepts the YAML object as content - as outlined in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example - annotations: - "k8s.enterprisedb.io/addons": '["external-backup-adapter-cluster"]' - "k8s.enterprisedb.io/externalBackupAdapterClusterConfig": |- - electedResourcesDecorators: - - key: "app.example.com/elected" - metadataType: "label" - value: "true" - excludedResourcesSelector: app=xyz,env=prod - excludedResourcesDecorators: - - key: "app.example.com/excluded" - metadataType: "label" - value: "true" - - key: "app.example.com/excluded-reason" - metadataType: "annotation" - value: "Not necessary for backup" - backupInstanceDecorators: - - key: "app.example.com/hasHooks" - metadataType: "label" - value: "true" - preBackupHookConfiguration: - container: - key: "app.example.com/pre-backup-container" - command: - key: "app.example.com/pre-backup-command" - onError: - key: "app.example.com/pre-backup-on-error" - postBackupHookConfiguration: - container: - key: "app.example.com/post-backup-container" - command: - key: "app.example.com/post-backup-command" -spec: - instances: 3 - storage: - size: 1Gi -``` - -### About the fencing annotation - -If the configured external backup adapter backs up annotations, the fencing -annotation will be set by the pre-backup hook and persist to the restored -cluster. After restoring the cluster, you will need to manually remove the -fencing annotation from the `Cluster` object to fix this. - -This can be done with the `cnp` plugin for kubectl: - -```shell -kubectl cnp fencing off -``` - -Or, if you don't have the `cnp` plugin, you can remove the fencing annotation -manually with the following command: - -```shell -kubectl annotate cluster k8s.enterprisedb.io/fencedInstances- -``` - -Please refer to the [fencing documentation](fencing.md) for more information. - -### Limitations - -As far as the backup part is concerned, currently, the EDB Postgres for -Kubernetes integration with `external-backup-adapter` and -`external-backup-adapter-cluster` supports **cold backups** only. These are -also referred to as **offline backups**. This means that the selected replica -is temporarily fenced so that `external-backup-adapter` and -`external-backup-adapter-cluster` can take a physical snapshot of the PVC group - -namely the `PGDATA` volume and, where available, the WAL volume. - -In this short timeframe, the standby cannot accept read-only connections. -If no standby is available - usually because we're in a single instance cluster - -and the annotation `k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary` is -set to true, `external-backup-adapter` and `external-backup-adapter-cluster` -will temporarily fence the primary, causing downtime in terms of read-write -operations. This use case is normally left to development environments. - -#### Full example of YAML file - -Here is a full example of YAML content to be placed in either: - -- the `EXTERNAL_BACKUP_ADDON_CONFIGURATION` option as part of the - the operator's configuration process described above for the - `external-backup-adapter` add-on, or -- in the `k8s.enterprisedb.io/externalBackupAdapterClusterConfig` annotation - for the `external-backup-adapter-cluster` add-on - -!!!tip Hint -Copy the content below and paste it inside the `ConfigMap` or `Secret` that -you use to configure the operator or the annotation in the `Cluster`, making -sure you use the `|` character that [YAML reserves for literals](https://yaml.org/spec/1.2.2/#812-literal-style), -as well as proper indentation. Use the comments to help you customize the -options for your tool. -!!! - -```yaml -# An array of labels and/or annotations that will be placed -# on the elected PVC group -electedResourcesDecorators: - - key: "backup.example.com/elected" - metadataType: "label" - value: "true" - -# An array of labels and/or annotations that will be placed -# on every excluded pod and PVC -excludedResourcesDecorators: - - key: "backup.example.com/excluded" - metadataType: "label" - value: "true" - - key: "backup.example.com/excluded-reason" - metadataType: "annotation" - value: "Not necessary for backup" - -# A LabelSelector containing the labels being used to filter Pods -# and PVCs to decorate with excludedResourcesDecorators. -# It accepts a label selector rule as value. -# See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors -# When empty, all the Pods and every PVC that is not elected will be excluded. -excludedResourcesSelector: app=xyz,env=prod - -# An array of labels and/or annotations that will be placed -# on the instance pod that's been selected for the backup by -# the operator and which contains the hooks. -# At least one element is required -backupInstanceDecorators: - - key: "backup.example.com/hasHooks" - metadataType: "label" - value: "true" - -# The pre-backup hook configuration allows you to control the names -# of the annotations in which the operator will place the container -# name, the command to run before taking the backup, and the command -# to run in case of error/abort on the third-party tool side. -# Such metadata will be applied on the instance that's been selected -# by the operator for the backup (see `backupInstanceDecorators`) -preBackupHookConfiguration: - # Where to place the information about the container that will run - # the pre-backup command. The container name is a fixed value and - # cannot be configured. Will be saved in the annotations. - # To decorate the pod with the hooks refer to: instanceWithHookDecorators - container: - key: "app.example.com/pre-backup-container" - # Where to place the information about the command that will be - # executed before the backup is taken. The command is a fixed value - # and cannot be configured. Will be saved in the annotations. - # To decorate the pod with the hooks refer to: instanceWithHookDecorators - command: - key: "app.example.com/pre-backup-command" - # Where to place the information about the command that will be - # executed in case of an error on the third-party tool side. - # The command is a fixed value and cannot be configured. - # Will be saved in the annotations. - # To decorate the pod with the hooks refer to: instanceWithHookDecorators - onError: - key: "app.example.com/pre-backup-on-error" - -# The post-backup hook configuration allows you to control the names -# of the annotations in which the operator will place the container -# name and the command to run after taking the backup. -# Such metadata will be applied on the instance that's been selected by -# the operator for the backup (see `backupInstanceDecorators`). -postBackupHookConfiguration: - # Where to place the information about the container that will run - # the post-backup command. The container name is a fixed value and - # cannot be configured. Will be saved in the annotations. - # To decorate the pod with hooks refer to: instanceWithHookDecorators - container: - key: "app.example.com/post-backup-container" - # Where to place the information about the command that will be - # executed after the backup is taken. The command is a fixed value - # and cannot be configured. Will be saved in the annotations. - # To decorate the pod with hooks refer to: instanceWithHookDecorators - command: - key: "app.example.com/post-backup-command" -``` - -## Kasten - -Kasten is a very popular data protection tool for Kubernetes, enabling backup -and restore, disaster recovery, and application mobility for Kubernetes -applications. For more information, see the [Kasten -website](https://www.kasten.io/) and the [Kasten by Veeam Implementation -Guide](/partner_docs/KastenbyVeeam/) - -In brief, to enable transparent integration with Kasten on an EDB Postgres for -Kubernetes Cluster, you just need to add the `kasten` value to the -`k8s.enterprisedb.io/addons` annotation in a `Cluster` spec. For example: - -```yaml - kind: Cluster - metadata: - name: one-instance - annotations: - k8s.enterprisedb.io/addons: '["kasten"]' - k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary: enabled - spec: - instances: 1 - storage: - size: 1Gi - walStorage: - size: 1Gi -``` - -Once the cluster is created and healthy, the operator will select the farthest -ahead replica instance to be the designated backup and will add Kasten-specific -backup hooks through annotations and labels to that instance. - -!!!info Important -The operator will refuse to shut down a primary instance to take a cold -backup unless the Cluster is annotated with -`k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary: enabled` -!!! - -For further guidance on how to configure and use Kasten, see the Implementation Guide's -[Configuration](/partner_docs/KastenbyVeeam/04-ConfiguringVeeamKasten/) and -[Using](/partner_docs/KastenbyVeeam/05-UsingVeeamKasten/) sections. - -### Limitations - -As far as the backup part is concerned, currently, the EDB Postgres for -Kubernetes integration with Kasten supports **cold backups** only. These are -also referred to as **offline backups**. This means that the selected replica -is temporarily fenced so that external-backup-adapter can take a physical -snapshot of the PVC group - namely the `PGDATA` volume and, where available, -the WAL volume. - -In this short timeframe, the standby cannot accept read-only connections. -If no standby is available - usually because we're in a single instance cluster - -and the annotation `k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary` is -set to true, Kasten will temporarily fence the primary, causing downtime in -terms of read-write operations. This use case is normally left to development -environments. - -In terms of recovery, the integration with Kasten supports snapshot recovery -only. No Point-in-Time Recovery (PITR) is available at the moment with the -Kasten add-on, and RPO is determined by the frequency of the snapshots in your -Kasten environment. If your organization relies on Kasten, this usually is -acceptable, but if you need PITR we recommend you look at the native continuous -backup method on object stores. - -## Velero - -Velero is an open-source tool to safely back up, restore, perform disaster -recovery, and migrate Kubernetes cluster resources and persistent volumes. For -more information, see the [Velero documentation](https://velero.io/docs/latest/). -To enable Velero compatibility with an {{name.ln}} Cluster, add -the `velero` value to the `k8s.enterprisedb.io/addons` annotation in a Cluster -spec. -For example: - -```yaml - kind: Cluster - metadata: - name: one-instance - annotations: - k8s.enterprisedb.io/addons: '["velero"]' - k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary: enabled - spec: - instances: 1 - storage: - size: 1Gi - walStorage: - size: 1Gi -``` - -Once the cluster is created and healthy, the operator will select the farthest -ahead replica instance to be the designated backup and will add Velero-specific -backup hooks as annotations to that instance. - -These [annotations](https://velero.io/docs/latest/backup-hooks/) are used by -Velero to run the commands to prepare the Postgres instance to be backed up. - -!!!info Important -The operator will refuse to shut down a primary instance to take a cold -backup unless the Cluster is annotated with -`k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary: enabled` -!!! - -### Limitations - -As far as the backup part is concerned, currently, the EDB Postgres for -Kubernetes integration with Velero supports **cold backups** only. These are -also referred to as **offline backups**. This means that the selected replica -is temporarily fenced so that external-backup-adapter can take a physical -snapshot of the PVC group - namely the `PGDATA` volume and, where available, -the WAL volume. - -In this short timeframe, the standby cannot accept read-only connections. -If no standby is available - usually because we're in a single instance cluster - -and the annotation `k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary` is -set to true, Velero will temporarily fence the primary, causing downtime in -terms of read-write operations. This use case is normally left to development -environments. - -In terms of recovery, the integration with Velero supports snapshot recovery -only, for now. No Point-in-Time Recovery (PITR) is available at the moment with the -Velero add-on, and RPO is determined by the frequency of the snapshots in your -Velero environment. If your organization relies on Velero, this usually is -acceptable, but if you need PITR we recommend you look at the native continuous -backup method on object stores. - -### Backup - -By design, {{name.ln}} offloads as much of the backup -functionality to Velero as possible, with the only requirement to make -available the previously mentioned backup hooks. Since EDB Postgres for -Kubernetes transparently sets all the needed configurations, and the rest is -standard Velero, using Velero to backup a Postgres cluster is as -straightforward as it would be for any other object. For example: - -```bash -velero backup create mybackup \ - --include-namespaces mynamespace \ - -n velero-install-namespace -``` - -This command will create a standard Velero backup using the configured object -storage and the configured Snapshot API. - -!!!info Important -By default, the Velero add-on exclude only a few resources from the backup -operation, namely pods and PVCs of the instances that have not been selected -(as you recall, the operator tries to backup the PVCs of the first replica). -However, you can use the options for the `velero backup` command to fine tune -the resources you want to be part of your backup. -!!! - -### Restore - -As with backup, the recovery process is a standard Velero procedure. The -command to restore from a backup created with the above parameters would be: - -```bash -velero create restore myrestore \ - --from-backup mybackup \ - -n velero-install-namespace -``` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/applications.mdx b/product_docs/docs/postgres_for_kubernetes/preview/applications.mdx deleted file mode 100644 index 97d4b98a318..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/applications.mdx +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: 'Connecting from an application' -originalFilePath: 'src/applications.md' ---- - - - -Applications are supposed to work with the services created by {{name.ln}} -in the same Kubernetes cluster. - -For more information on services and how to manage them, please refer to the -["Service management"](service_management.md) section. - -!!!tip Hint -It is highly recommended using those services in your applications, -and avoiding connecting directly to a specific PostgreSQL instance, as the latter -can change during the cluster lifetime. -!!! - -You can use these services in your applications through: - -- DNS resolution -- environment variables - -For the credentials to connect to PostgreSQL, you can -use the secrets generated by the operator. - -!!!note Connection Pooling -Please refer to the ["Connection Pooling" section](connection_pooling.md) for -information about how to take advantage of PgBouncer as a connection pooler, -and create an access layer between your applications and the PostgreSQL clusters. -!!! - -### DNS resolution - -You can use the Kubernetes DNS service to point to a given server. -The Kubernetes DNS service is required by the operator. -You can do that by using the name of the service if the application is -deployed in the same namespace as the PostgreSQL cluster. -In case the PostgreSQL cluster resides in a different namespace, you can use the -full qualifier: `service-name.namespace-name`. - -DNS is the preferred and recommended discovery method. - -### Environment variables - -If you deploy your application in the same namespace that contains the -PostgreSQL cluster, you can also use environment variables to connect to the database. - -For example, suppose that your PostgreSQL cluster is called `pg-database`, -you can use the following environment variables in your applications: - -- `PG_DATABASE_R_SERVICE_HOST`: the IP address of the service - pointing to all the PostgreSQL instances for read-only workloads - -- `PG_DATABASE_RO_SERVICE_HOST`: the IP address of the - service pointing to all hot-standby replicas of the cluster - -- `PG_DATABASE_RW_SERVICE_HOST`: the IP address of the - service pointing to the *primary* instance of the cluster - -### Secrets - -The PostgreSQL operator will generate up to two `basic-auth` type secrets for -every PostgreSQL cluster it deploys: - -- `[cluster name]-app` (unless you have provided an existing secret through `.spec.bootstrap.initdb.secret.name`) -- `[cluster name]-superuser` (if `.spec.enableSuperuserAccess` is set to `true` - and you have not specified a different secret using `.spec.superuserSecret`) - -Each secret contain the following: - -- username -- password -- hostname to the RW service -- port number -- database name -- a working [`.pgpass file`](https://www.postgresql.org/docs/current/libpq-pgpass.html) -- [uri](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING) -- [jdbc-uri](https://jdbc.postgresql.org/documentation/use/#connecting-to-the-database) -- [fqdn-uri](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING) -- [fqdn-jdbc-uri](https://jdbc.postgresql.org/documentation/use/#connecting-to-the-database) - -The FQDN to be used in the URIs is calculated using the Kubernetes cluster -domain specified in the `KUBERNETES_CLUSTER_DOMAIN` configuration parameter. -See [the operator configuration documentation](operator_conf.md) for more information -about that. - -The `-app` credentials are the ones that should be used by applications -connecting to the PostgreSQL cluster, and correspond to the user *owning* the -database. - -The `-superuser` ones are supposed to be used only for administrative purposes, -and correspond to the `postgres` user. - -!!!info Important -Superuser access over the network is disabled by default. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/architecture.mdx b/product_docs/docs/postgres_for_kubernetes/preview/architecture.mdx deleted file mode 100644 index 1b8fea5e7b3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/architecture.mdx +++ /dev/null @@ -1,450 +0,0 @@ ---- -title: 'Architecture' -originalFilePath: 'src/architecture.md' ---- - - - -!!!tip Hint -For a deeper understanding, we recommend reading our article on the CNCF -blog post titled ["Recommended Architectures for PostgreSQL in Kubernetes"](https://www.cncf.io/blog/2023/09/29/recommended-architectures-for-postgresql-in-kubernetes/), -which provides valuable insights into best practices and design -considerations for PostgreSQL deployments in Kubernetes. -!!! - -This documentation page provides an overview of the key architectural -considerations for implementing a robust business continuity strategy when -deploying PostgreSQL in Kubernetes. These considerations include: - -- **[Deployments in *stretched*](#multi-availability-zone-kubernetes-clusters) - vs. [*non-stretched* clusters](#single-availability-zone-kubernetes-clusters)**: - Evaluating the differences between deploying in stretched clusters (across 3 - or more availability zones) versus non-stretched clusters (within a single - availability zone). -- [**Reservation of `postgres` worker nodes**](#reserving-nodes-for-postgresql-workloads): Isolating PostgreSQL workloads by - dedicating specific worker nodes to `postgres` tasks, ensuring optimal - performance and minimizing interference from other workloads. -- [**PostgreSQL architectures within a single Kubernetes cluster**](#postgresql-architecture): - Designing effective PostgreSQL deployments within a single Kubernetes cluster - to meet high availability and performance requirements. -- [**PostgreSQL architectures across Kubernetes clusters for disaster recovery**](#deployments-across-kubernetes-clusters): - Planning and implementing PostgreSQL architectures that span multiple - Kubernetes clusters to provide comprehensive disaster recovery capabilities. - -## Synchronizing the state - -PostgreSQL is a database management system and, as such, it needs to be treated -as a **stateful workload** in Kubernetes. While stateless applications -mainly use traffic redirection to achieve High Availability (HA) and -Disaster Recovery (DR), in the case of a database, state must be replicated in -multiple locations, preferably in a continuous and instantaneous way, by -adopting either of the following two strategies: - -- *storage-level replication*, normally persistent volumes -- *application-level replication*, in this specific case PostgreSQL - -{{name.ln}} relies on application-level replication, for a simple reason: the -PostgreSQL database management system comes with robust and reliable -built-in **physical replication** capabilities based on **Write Ahead Log (WAL) -shipping**, which have been used in production by millions of users all over -the world for over a decade. - -PostgreSQL supports both asynchronous and synchronous streaming replication -over the network, as well as asynchronous file-based log shipping (normally -used as a fallback option, for example, to store WAL files in an object store). -Replicas are usually called *standby servers* and can also be used for -read-only workloads, thanks to the *Hot Standby* feature. - -!!!info Important -**We recommend against storage-level replication with PostgreSQL**, although -{{name.ln}} allows you to adopt that strategy. For more information, please refer -to the talk given by Chris Milsted and Gabriele Bartolini at KubeCon NA 2022 entitled -["Data On Kubernetes, Deploying And Running PostgreSQL And Patterns For Databases In a Kubernetes Cluster"](https://www.youtube.com/watch?v=99uSJXkKpeI&ab_channel=CNCF%5BCloudNativeComputingFoundation%5D) -where this topic was covered in detail. -!!! - -## Kubernetes architecture - -Kubernetes natively provides the possibility to span separate physical -locations - also known as data centers, failure zones, or more frequently -**availability zones** - connected to each other via redundant, low-latency, -private network connectivity. - -Being a distributed system, the recommended minimum number of availability -zones for a Kubernetes cluster is three (3), in order to make the control -plane resilient to the failure of a single zone. -For details, please refer to -["Running in multiple zones"](https://kubernetes.io/docs/setup/best-practices/multiple-zones/). -This means that **each data center is active at any time** and can run workloads -simultaneously. - -!!!note -Most of the public Cloud Providers' managed Kubernetes services already -provide 3 or more availability zones in each region. -!!! - -### Multi-availability zone Kubernetes clusters - -The multi-availability zone Kubernetes architecture with three (3) or more -zones is the one that we recommend for PostgreSQL usage. -This scenario is typical of Kubernetes services managed by Cloud Providers. - -![Kubernetes cluster spanning over 3 independent data centers](./images/k8s-architecture-3-az.png) - -Such an architecture enables the {{name.ln}} operator to control the full -lifecycle of a `Cluster` resource across the zones within a single Kubernetes -cluster, by treating all the availability zones as active: this includes, among -other operations, -[scheduling](scheduling.md) the workloads in a declarative manner (based on -affinity rules, tolerations and node selectors), automated failover, -self-healing, and updates. All will work seamlessly across the zones in a single -Kubernetes cluster. - -Please refer to the ["PostgreSQL architecture"](#postgresql-architecture) -section below for details on how you can design your PostgreSQL clusters within -the same Kubernetes cluster through shared-nothing deployments at the storage, -worker node, and availability zone levels. - -Additionally, you can leverage [Kubernetes clusters](#deployments-across-kubernetes-clusters) -to deploy distributed PostgreSQL topologies hosting "passive" -[PostgreSQL replica clusters](replica_cluster.md) in different regions and -managing them via declarative configuration. This setup is ideal for disaster -recovery (DR), read-only operations, or cross-region availability. - -!!!info Important -Each operator deployment can only manage operations within its local -Kubernetes cluster. For operations across Kubernetes clusters, such as -controlled switchover or unexpected failover, coordination must be handled -manually (through GitOps, for example) or by using a higher-level cluster -management tool. -!!! - -![Example of a multiple Kubernetes cluster architecture distributed over 3 regions each with 3 independent data centers](./images/k8s-architecture-multi.png) - -### Single availability zone Kubernetes clusters - -If your Kubernetes cluster has only one availability zone, {{name.ln}} still -provides you with a lot of features to improve HA and DR outcomes for your -PostgreSQL databases, pushing the single point of failure (SPoF) to the level -of the zone as much as possible - i.e. the zone must have an outage before your -{{name.ln}} clusters suffer a failure. - -This scenario is typical of self-managed on-premise Kubernetes clusters, where -only one data center is available. - -Single availability zone Kubernetes clusters are the only viable option when -only **two data centers** are available within reach of a low-latency -connection (typically in the same metropolitan area). Having only two zones -prevents the creation of a multi-availability zone Kubernetes cluster, which -requires a minimum of three zones. As a result, users must create two separate -Kubernetes clusters in an active/passive configuration, with the second cluster -primarily used for Disaster Recovery (see -the [replica cluster feature](replica_cluster.md)). - -![Example of a Kubernetes architecture with only 2 data centers](./images/k8s-architecture-2-az.png) - -!!!tip Hint -If you are at an early stage of your Kubernetes journey, please share this -document with your infrastructure team. The two data centers setup might -be simply the result of a "lift-and-shift" transition to Kubernetes -from a traditional bare-metal or VM based infrastructure, and the benefits -that Kubernetes offers in a 3+ zone scenario might not have been known, -or addressed at the time the infrastructure architecture was designed. -Ultimately, a third physical location connected to the other two might -represent a valid option to consider for organization, as it reduces the -overall costs of the infrastructure by moving the day-to-day complexity -from the application level down to the physical infrastructure level. -!!! - -Please refer to the ["PostgreSQL architecture"](#postgresql-architecture) -section below for details on how you can design your PostgreSQL clusters within -your single availability zone Kubernetes cluster through shared-nothing -deployments at the storage and worker node levels only. For HA, in such a -scenario it becomes even more important that the PostgreSQL instances be -located on different worker nodes and do not share the same storage. - -For DR, you can push the SPoF above the single zone, by using additional -[Kubernetes clusters](#deployments-across-kubernetes-clusters) to define a -distributed topology hosting "passive" [PostgreSQL replica clusters](replica_cluster.md). -As with other Kubernetes workloads in this scenario, promotion of a Kubernetes -cluster as primary must be done manually. - -Through the [replica cluster feature](replica_cluster.md), you can define a -distributed PostgreSQL topology and coordinate a controlled switchover between -data centers by first demoting the primary cluster and then promoting the -replica cluster, without the need to re-clone the former primary. While failover -is now fully declarative, automated failover across Kubernetes clusters is not -within {{name.ln}}' scope, as the operator can only function within a single -Kubernetes cluster. - -!!!info Important -{{name.ln}} provides all the necessary primitives and probes to -coordinate PostgreSQL active/passive topologies across different Kubernetes -clusters through a higher-level operator or management tool. -!!! - -### Reserving nodes for PostgreSQL workloads - -Whether you're operating in a multi-availability zone environment or, more -critically, within a single availability zone, we strongly recommend isolating -PostgreSQL workloads by dedicating specific worker nodes exclusively to -`postgres` in production. A Kubernetes worker node dedicated to running -PostgreSQL workloads is referred to as a **Postgres node** or `postgres` node. -This approach ensures optimal performance and resource allocation for your -database operations. - -!!!tip Hint -As a general rule of thumb, deploy Postgres nodes in multiples of -three—ideally with one node per availability zone. Three nodes is -an optimal number because it ensures that a PostgreSQL cluster with three -instances (one primary and two standby replicas) is distributed across -different nodes, enhancing fault tolerance and availability. -!!! - -In Kubernetes, this can be achieved using node labels and taints in a -declarative manner, aligning with Infrastructure as Code (IaC) practices: -labels ensure that a node is capable of running `postgres` workloads, while -taints help prevent any non-`postgres` workloads from being scheduled on that -node. - -!!!info Important -This methodology is the most straightforward way to ensure that PostgreSQL -workloads are isolated from other workloads in terms of both computing -resources and, when using locally attached disks, storage. While different -PostgreSQL clusters may share the same node, you can take this a step further -by using labels and taints to ensure that a node is dedicated to a single -instance of a specific `Cluster`. -!!! - -#### Proposed node label - -{{name.ln}} recommends using the `node-role.kubernetes.io/postgres` label. -Since this is a reserved label (`*.kubernetes.io`), it can only be applied -after a worker node is created. - -To assign the `postgres` label to a node, use the following command: - -```sh -kubectl label node node-role.kubernetes.io/postgres= -``` - -To ensure that a `Cluster` resource is scheduled on a `postgres` node, you must -correctly configure the `.spec.affinity.nodeSelector` stanza in your manifests. -Here’s an example: - -```yaml -spec: - # - affinity: - # - nodeSelector: - node-role.kubernetes.io/postgres: "" -``` - -#### Proposed node taint - -{{name.ln}} recommends using the `node-role.kubernetes.io/postgres` taint. - -To assign the `postgres` taint to a node, use the following command: - -```sh -kubectl taint node node-role.kubernetes.io/postgres=:NoSchedule -``` - -To ensure that a `Cluster` resource is scheduled on a node with a `postgres` taint, you must correctly configure the `.spec.affinity.tolerations` stanza in your manifests. -Here’s an example: - -```yaml -spec: - # - affinity: - # - tolerations: - - key: node-role.kubernetes.io/postgres - operator: Exists - effect: NoSchedule -``` - -## PostgreSQL architecture - -{{name.ln}} supports clusters based on asynchronous and synchronous -streaming replication to manage multiple hot standby replicas within the same -Kubernetes cluster, with the following specifications: - -- One primary, with optional multiple hot standby replicas for HA - -- Available services for applications: - - `-rw`: applications connect only to the primary instance of the cluster - - `-ro`: applications connect only to hot standby replicas for - read-only-workloads (optional) - - `-r`: applications connect to any of the instances for read-only - workloads (optional) - -- Shared-nothing architecture recommended for better resilience of the PostgreSQL cluster: - - PostgreSQL instances should reside on different Kubernetes worker nodes - and share only the network - as a result, instances should not share - the storage and preferably use local volumes attached to the node they - run on - - PostgreSQL instances should reside in different availability zones - within the same Kubernetes cluster / region - -!!!info Important -You can configure the above services through the `managed.services` section -in the `Cluster` configuration. This can be done by reducing the number of -services and selecting the type (default is `ClusterIP`). For more details, -please refer to the ["Service Management" section](service_management.md) -below. -!!! - -The below diagram provides a simplistic view of the recommended shared-nothing -architecture for a PostgreSQL cluster spanning across 3 different availability -zones, running on separate nodes, each with dedicated local storage for -PostgreSQL data. - -![Bird-eye view of the recommended shared nothing architecture for PostgreSQL in Kubernetes](./images/k8s-pg-architecture.png) - -{{name.ln}} automatically takes care of updating the above services if -the topology of the cluster changes. For example, in case of failover, it -automatically updates the `-rw` service to point to the promoted primary, -making sure that traffic from the applications is seamlessly redirected. - -!!!note Replication -Please refer to the ["Replication" section](replication.md) for more -information about how {{name.ln}} relies on PostgreSQL replication, -including synchronous settings. -!!! - -!!!note Connecting from an application -Please refer to the ["Connecting from an application" section](applications.md) for -information about how to connect to {{name.ln}} from a stateless -application within the same Kubernetes cluster. -!!! - -!!!note Connection Pooling -Please refer to the ["Connection Pooling" section](connection_pooling.md) for -information about how to take advantage of PgBouncer as a connection pooler, -and create an access layer between your applications and the PostgreSQL clusters. -!!! - -### Read-write workloads - -Applications can decide to connect to the PostgreSQL instance elected as -*current primary* by the Kubernetes operator, as depicted in the following -diagram: - -![Applications writing to the single primary](./images/architecture-rw.png) - -Applications can use the `-rw` suffix service. - -In case of temporary or permanent unavailability of the primary, for High -Availability purposes {{name.ln}} will trigger a failover, pointing the `-rw` -service to another instance of the cluster. - -### Read-only workloads - -!!!info Important -Applications must be aware of the limitations that -[Hot Standby](https://www.postgresql.org/docs/current/hot-standby.html) -presents and familiar with the way PostgreSQL operates when dealing with -these workloads. -!!! - -Applications can access hot standby replicas through the `-ro` service made available -by the operator. This service enables the application to offload read-only queries from the -primary node. - -The following diagram shows the architecture: - -![Applications reading from hot standby replicas in round robin](./images/architecture-read-only.png) - -Applications can also access any PostgreSQL instance through the -`-r` service. - -## Deployments across Kubernetes clusters - -!!!info -{{name.ln}} supports deploying PostgreSQL across multiple Kubernetes -clusters through a feature that allows you to define a distributed PostgreSQL -topology using replica clusters, as described in this section. -!!! - -In a distributed PostgreSQL cluster there can only be a single PostgreSQL -instance acting as a primary at all times. This means that applications can -only write inside a single Kubernetes cluster, at any time. - -However, for business continuity objectives it is fundamental to: - -- reduce global **recovery point objectives** ([RPO](before_you_start.md#postgresql-terminology)) - by storing PostgreSQL backup data in multiple locations, regions and possibly - using different providers (Disaster Recovery) -- reduce global **recovery time objectives** ([RTO](before_you_start.md#postgresql-terminology)) - by taking advantage of PostgreSQL replication beyond the primary Kubernetes - cluster (High Availability) - -In order to address the above concerns, {{name.ln}} introduces the concept of -a PostgreSQL Topology that is distributed across different Kubernetes clusters -and is made up of a primary PostgreSQL cluster and one or more PostgreSQL -replica clusters. -This feature is called **distributed PostgreSQL topology with replica clusters**, -and it enables multi-cluster deployments in private, public, hybrid, and -multi-cloud contexts. - -A replica cluster is a separate `Cluster` resource that is in continuous -recovery, replicating from another source, either via WAL shipping from a WAL -archive or via streaming replication from a primary or a standby (cascading). - -The diagram below depicts a PostgreSQL cluster spanning over two different -Kubernetes clusters, where the primary cluster is in the first Kubernetes -cluster and the replica cluster is in the second. The second Kubernetes cluster -acts as the company's disaster recovery cluster, ready to be activated in case -of disaster and unavailability of the first one. - -![An example of multi-cluster deployment with a primary and a replica cluster](./images/multi-cluster.png) - -A replica cluster can have the same architecture as the primary cluster. -Instead of a primary instance, a replica cluster has a **designated primary** -instance, which is a standby server with an arbitrary number of cascading -standby servers in streaming replication (symmetric architecture). - -The designated primary can be promoted at any time, transforming the replica -cluster into a primary cluster capable of accepting write connections. -This is typically triggered by: - -- **Human decision:** You choose to make the other PostgreSQL cluster (or the - entire Kubernetes cluster) the primary. To avoid data loss and ensure that - the former primary can follow without being re-cloned (especially with large - data sets), you first demote the current primary, then promote the designated - primary using the API provided by {{name.ln}}. -- **Unexpected failure:** If the entire Kubernetes cluster fails, you might - experience data loss, but you need to fail over to the other Kubernetes - cluster by promoting the PostgreSQL replica cluster. - -!!!warning -{{name.ln}} cannot perform any cross-cluster automated failover, as it -does not have authority beyond a single Kubernetes cluster. Such operations -must be performed manually or delegated to a multi-cluster/federated -cluster-aware authority. -!!! - -!!!info Important -{{name.ln}} allows you to control the distributed topology via -declarative configuration, enabling you to automate these procedures as part of -your Infrastructure as Code (IaC) process, including GitOps. -!!! - -In the example above, the designated primary receives WAL updates via streaming -replication (`primary_conninfo`). As a fallback, it can retrieve WAL segments -from an object store using file-based WAL shipping—for instance, with the -Barman Cloud plugin through `restore_command` and `barman-cloud-wal-restore`. - -{{name.ln}} allows you to define topologies with multiple replica clusters. -You can also define replica clusters with a lower number of replicas, and then -increase this number when the cluster is promoted to primary. - -!!!note Replica clusters -Please refer to the ["Replica Clusters" section](replica_cluster.md) for -more detailed information on how physical replica clusters operate and how to -define a distributed topology with read-only clusters across different -Kubernetes clusters. This approach can significantly enhance your global -disaster recovery and high availability (HA) strategy. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/backup.mdx b/product_docs/docs/postgres_for_kubernetes/preview/backup.mdx deleted file mode 100644 index d9e9914fb09..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/backup.mdx +++ /dev/null @@ -1,509 +0,0 @@ ---- -title: 'Backup' -originalFilePath: 'src/backup.md' ---- - - - -!!!info -This section covers **physical backups** in PostgreSQL. -While PostgreSQL also supports logical backups using the `pg_dump` utility, -these are **not suitable for business continuity** and are **not managed** by -{{name.ln}}. If you still wish to use `pg_dump`, refer to the -[*Troubleshooting / Emergency backup* section](troubleshooting.md#emergency-backup) -for guidance. -!!! - -!!!info Important -Starting with version 1.26, native backup and recovery capabilities are -being **progressively phased out** of the core operator and moved to official -CNPG-I plugins. This transition aligns with {{name.ln}}' shift towards a -**backup-agnostic architecture**, enabled by its extensible -interface—**CNPG-I**—which standardizes the management of **WAL archiving**, -**physical base backups**, and corresponding **recovery processes**. -!!! - -{{name.ln}} currently supports **physical backups of PostgreSQL clusters** in -two main ways: - -- **Via [CNPG-I](https://github.com/cloudnative-pg/cnpg-i/) plugins**: the - {{name.ln}} Community officially supports the [**Barman Cloud Plugin**](https://cloudnative-pg.io/plugin-barman-cloud/) - for integration with object storage services. - -- **Natively**, with support for: - - - [Object storage via Barman Cloud](backup_barmanobjectstore.md) - *(although deprecated from 1.26 in favor of the Barman Cloud Plugin)* - - [Kubernetes Volume Snapshots](backup_volumesnapshot.md), if - supported by the underlying storage class - -Before selecting a backup strategy with {{name.ln}}, it's important to -familiarize yourself with the foundational concepts covered in the ["Main Concepts"](#main-concepts) -section. These include WAL archiving, hot and cold backups, performing backups -from a standby, and more. - -## Main Concepts - -PostgreSQL natively provides first class backup and recovery capabilities based -on file system level (physical) copy. These have been successfully used for -more than 15 years in mission critical production databases, helping -organizations all over the world achieve their disaster recovery goals with -Postgres. - -In {{name.ln}}, the backup infrastructure for each PostgreSQL cluster is made -up of the following resources: - -- **WAL archive**: a location containing the WAL files (transactional logs) - that are continuously written by Postgres and archived for data durability -- **Physical base backups**: a copy of all the files that PostgreSQL uses to - store the data in the database (primarily the `PGDATA` and any tablespace) - -CNPG-I provides a generic and extensible interface for managing WAL archiving -(both archive and restore operations), as well as the base backup and -corresponding restore processes. - -### WAL archive - -The WAL archive in PostgreSQL is at the heart of **continuous backup**, and it -is fundamental for the following reasons: - -- **Hot backups**: the possibility to take physical base backups from any - instance in the Postgres cluster (either primary or standby) without shutting - down the server; they are also known as online backups -- **Point in Time recovery** (PITR): the possibility to recover at any point in - time from the first available base backup in your system - -!!!warning -WAL archive alone is useless. Without a physical base backup, you cannot -restore a PostgreSQL cluster. -!!! - -In general, the presence of a WAL archive enhances the resilience of a -PostgreSQL cluster, allowing each instance to fetch any required WAL file from -the archive if needed (normally the WAL archive has higher retention periods -than any Postgres instance that normally recycles those files). - -This use case can also be extended to [replica clusters](replica_cluster.md), -as they can simply rely on the WAL archive to synchronize across long -distances, extending disaster recovery goals across different regions. - -When you [configure a WAL archive](wal_archiving.md), {{name.ln}} provides -out-of-the-box an [RPO](before_you_start.md#postgresql-terminology) ≤ 5 minutes for disaster -recovery, even across regions. - -!!!info Important -Our recommendation is to always setup the WAL archive in production. -There are known use cases — normally involving staging and development -environments — where none of the above benefits are needed and the WAL -archive is not necessary. RPO in this case can be any value, such as -24 hours (daily backups) or infinite (no backup at all). -!!! - -### Cold and Hot backups - -Hot backups have already been defined in the previous section. They require the -presence of a WAL archive, and they are the norm in any modern database -management system. - -**Cold backups**, also known as offline backups, are instead physical base backups -taken when the PostgreSQL instance (standby or primary) is shut down. They are -consistent per definition, and they represent a snapshot of the database at the -time it was shut down. - -As a result, PostgreSQL instances can be restarted from a cold backup without -the need of a WAL archive, even though they can take advantage of it, if -available (with all the benefits on the recovery side highlighted in the -previous section). - -In those situations with a higher RPO (for example, 1 hour or 24 hours), and -shorter retention periods, cold backups represent a viable option to be considered -for your disaster recovery plans. - -## Comparing Available Backup Options: Object Stores vs Volume Snapshots - -{{name.ln}} currently supports two main approaches for physical backups: - -- **Object store–based backups**, via the [**Barman Cloud - Plugin**](https://cloudnative-pg.io/plugin-barman-cloud/) or the - [**deprecated native integration**](backup_barmanobjectstore.md) -- [**Volume Snapshots**](backup_volumesnapshot.md), using the - Kubernetes CSI interface and supported storage classes - -!!!info Important -CNPG-I is designed to enable third parties to build and integrate their own -backup plugins. Over time, we expect the ecosystem of supported backup -solutions to grow. -!!! - -### Object Store–Based Backups - -Backups to an object store (e.g. AWS S3, Azure Blob, GCS): - -- Always require WAL archiving -- Support hot backups only -- Do not support incremental or differential copies -- Support retention policies - -### Volume Snapshots - -Native volume snapshots: - -- Do not require WAL archiving, though its use is still strongly - recommended in production -- Support incremental and differential copies, depending on the - capabilities of the underlying storage class -- Support both hot and cold backups -- Do not support retention policies - -### Choosing Between the Two - -The best approach depends on your environment and operational requirements. -Consider the following factors: - -- **Object store availability**: Ensure your Kubernetes cluster can access a - reliable object storage solution, including a stable networking layer. -- **Storage class capabilities**: Confirm that your storage class supports CSI - volume snapshots with incremental/differential features. -- **Database size**: For very large databases (VLDBs), **volume snapshots are - generally preferred** as they enable faster recovery due to copy-on-write - technology—this significantly improves your - [Recovery Time Objective (RTO)](before_you_start.md#postgresql-terminology). -- **Data mobility**: Object store–based backups may offer greater flexibility - for replicating or storing backups across regions or environments. -- **Operational familiarity**: Choose the method that aligns best with your - team's experience and confidence in managing storage. - -### Comparison Summary - -| Feature | Object Store | Volume Snapshots | -| --------------------------------- | :----------: | :------------------: | -| **WAL archiving** | Required | Recommended^1^ | -| **Cold backup** | ❌ | ✅ | -| **Hot backup** | ✅ | ✅ | -| **Incremental copy** | ❌ | ✅^2^ | -| **Differential copy** | ❌ | ✅^2^ | -| **Backup from a standby** | ✅ | ✅ | -| **Snapshot recovery** | ❌^3^ | ✅ | -| **Retention policies** | ✅ | ❌ | -| **Point-in-Time Recovery (PITR)** | ✅ | Requires WAL archive | -| **Underlying technology** | Barman Cloud | Kubernetes API | - -* * * - -> **Notes:** -> -> 1. WAL archiving must currently use an object store through a plugin (or the -> deprecated native one). -> 2. Availability of incremental and differential copies depends on the -> capabilities of the storage class used for PostgreSQL volumes. -> 3. Snapshot recovery can be emulated by using the -> `bootstrap.recovery.recoveryTarget.targetImmediate` option. - -## Scheduled Backups - -Scheduled backups are the recommended way to implement a reliable backup -strategy in {{name.ln}}. They are defined using the `ScheduledBackup` custom -resource. - -!!!info -For a complete list of configuration options, refer to the -[`ScheduledBackupSpec`](pg4k.v1.md#scheduledbackupspec) -in the API reference. -!!! - -### Cron Schedule - -The `schedule` field defines **when** the backup should occur, using a -*six-field cron expression* that includes seconds. This format follows the -[Go `cron` package specification](https://pkg.go.dev/github.com/robfig/cron#hdr-CRON_Expression_Format). - -!!!warning -This format differs from the traditional Unix/Linux `crontab`—it includes a -**seconds** field as the first entry. -!!! - -Example of a daily scheduled backup: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ScheduledBackup -metadata: - name: backup-example -spec: - schedule: "0 0 0 * * *" # At midnight every day - backupOwnerReference: self - cluster: - name: pg-backup - # method: plugin, volumeSnapshot, or barmanObjectStore (default) -``` - -The schedule `"0 0 0 * * *"` triggers a backup every day at midnight -(00:00:00). In Kubernetes CronJobs, the equivalent expression would be `0 0 * * *`, -since seconds are not supported. - -!!!warning - -The `spec.cluster` field is immutable after creation. To schedule backups -for a different `Cluster`, create a new `ScheduledBackup` resource instead -of updating an existing one. -!!! - -### Backup Frequency and RTO - -!!!tip Hint -The frequency of your backups directly impacts your **Recovery Time Objective** -([RTO](before_you_start.md#postgresql-terminology)). -!!! - -To optimize your disaster recovery strategy based on continuous backup: - -- Regularly test restoring from your backups. -- Measure the time required for a full recovery. -- Account for the size of base backups and the number of WAL files that must be - retrieved and replayed. - -In most cases, a **weekly base backup** is sufficient. It is rare to schedule -full backups more frequently than once per day. - -### Immediate Backup - -To trigger a backup immediately when the `ScheduledBackup` is created: - -```yaml -spec: - immediate: true -``` - -### Pause Scheduled Backups - -To temporarily stop scheduled backups from running: - -```yaml -spec: - suspend: true -``` - -### Backup Owner Reference (`.spec.backupOwnerReference`) - -Controls which Kubernetes object is set as the owner of the backup resource: - -- `none`: No owner reference (legacy behavior) -- `self`: The `ScheduledBackup` object becomes the owner -- `cluster`: The PostgreSQL cluster becomes the owner - -## On-Demand Backups - -On-demand backups allow you to manually trigger a backup operation at any time -by creating a `Backup` resource. - -!!!info -For a full list of available options, see the -[`BackupSpec`](pg4k.v1.md#backupspec) in the -API reference. -!!! - -### Example: Requesting an On-Demand Backup - -To start an on-demand backup, apply a `Backup` request custom resource like the -following: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Backup -metadata: - name: backup-example -spec: - method: barmanObjectStore - cluster: - name: pg-backup -``` - -In this example, the operator will orchestrate the backup process using the -`barman-cloud-backup` tool and store the backup in the configured object store. - -### Monitoring Backup Progress - -You can check the status of the backup using: - -```bash -kubectl describe backup backup-example -``` - -While the backup is in progress, you'll see output similar to: - -```text -Name: backup-example -Namespace: default -... -Spec: - Cluster: - Name: pg-backup -Status: - Phase: running - Started At: 2020-10-26T13:57:40Z -Events: -``` - -Once the backup has successfully completed, the `phase` will be set to -`completed`, and the output will include additional metadata: - -```text -Name: backup-example -Namespace: default -... -Status: - Backup Id: 20201026T135740 - Destination Path: s3://backups/ - Endpoint URL: http://minio:9000 - Phase: completed - S3 Credentials: - Access Key Id: - Name: minio - Key: ACCESS_KEY_ID - Secret Access Key: - Name: minio - Key: ACCESS_SECRET_KEY - Server Name: pg-backup - Started At: 2020-10-26T13:57:40Z - Stopped At: 2020-10-26T13:57:44Z -``` - -* * * - -!!!info Important -On-demand backups do **not** include Kubernetes secrets for the PostgreSQL -superuser or application user. You should ensure these secrets are included in -your broader Kubernetes cluster backup strategy. -!!! - -## Backup Methods - -{{name.ln}} currently supports the following backup methods for scheduled -and on-demand backups: - -- `plugin` – Uses a CNPG-I plugin (requires `.spec.pluginConfiguration`) -- `volumeSnapshot` – Uses native [Kubernetes volume snapshots](backup_volumesnapshot.md#how-to-configure-volume-snapshot-backups) -- `barmanObjectStore` – Uses [Barman Cloud for object storage](backup_barmanobjectstore.md) - *(deprecated starting with v1.26 in favor of the - [Barman Cloud Plugin](https://cloudnative-pg.io/plugin-barman-cloud/), - but still the default for backward compatibility)* - -Specify the method using the `.spec.method` field (defaults to -`barmanObjectStore`). - -If your cluster is configured to support volume snapshots, you can enable -scheduled snapshot backups like this: - -```yaml -spec: - method: volumeSnapshot -``` - -To use the Barman Cloud Plugin as the backup method, set `method: plugin` and -configure the plugin accordingly. You can find an example in the -["Performing a Base Backup" section of the plugin documentation](https://cloudnative-pg.io/plugin-barman-cloud/docs/usage/#performing-a-base-backup) - -## Backup from a Standby - -Taking a base backup involves reading the entire on-disk data set of a -PostgreSQL instance, which can introduce I/O contention and impact the -performance of the active workload. - -To reduce this impact, **{{name.ln}} supports taking backups from a standby -instance**, leveraging PostgreSQL’s built-in capability to perform backups from -read-only replicas. - -By default, backups are performed on the **most up-to-date replica** in the -cluster. If no replicas are available, the backup will fall back to the -**primary instance**. - -!!!note -The examples in this section are focused on backup target selection and do not -take the backup method (`spec.method`) into account, as it is not relevant to -the scope being discussed. -!!! - -### How It Works - -When `prefer-standby` is the target (the default behavior), {{name.ln}} will -attempt to: - -1. Identify the most synchronized standby node. -2. Run the backup process on that standby. -3. Fall back to the primary if no standbys are available. - -This strategy minimizes interference with the primary’s workload. - -!!!warning -Although the standby might not always be up to date with the primary, -in the time continuum from the first available backup to the last -archived WAL this is normally irrelevant. The base backup indeed -represents the starting point from which to begin a recovery operation, -including PITR. Similarly to what happens with -[`pg_basebackup`](https://www.postgresql.org/docs/current/app-pgbasebackup.html), -when backing up from an online standby we do not force a switch of the WAL on the -primary. This might produce unexpected results in the short term (before -`archive_timeout` kicks in) in deployments with low write activity. -!!! - -### Forcing Backup on the Primary - -To always run backups on the primary instance, explicitly set the backup target -to `primary` in the cluster configuration: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - [...] -spec: - backup: - target: "primary" -``` - -!!!warning -Be cautious when using `primary` as the target for **cold backups using -volume snapshots**, as this will require shutting down the primary instance -temporarily—interrupting all write operations. The same caution applies to -single-instance clusters, even if you haven't explicitly set the target. -!!! - -### Overriding the Cluster-Wide Target - -You can override the cluster-level target on a per-backup basis, using either -`Backup` or `ScheduledBackup` resources. Here's an example of an on-demand -backup: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Backup -metadata: - [...] -spec: - cluster: - name: [...] - target: "primary" -``` - -In this example, even if the cluster’s default target is `prefer-standby`, the -backup will be taken from the primary instance. - -## Retention Policies - -{{name.ln}} is evolving toward a **backup-agnostic architecture**, where -backup responsibilities are delegated to external **CNPG-I plugins**. These -plugins are expected to offer advanced and customizable data protection -features, including sophisticated retention management, that go beyond the -built-in capabilities and scope of {{name.ln}}. - -As part of this transition, the `spec.backup.retentionPolicy` field in the -`Cluster` resource is **deprecated** and will be removed in a future release. - -For more details on available retention features, refer to your chosen plugin’s documentation. -For example: ["Retention Policies" with Barman Cloud Plugin](https://cloudnative-pg.io/plugin-barman-cloud/docs/retention/). - -!!!info Important -Users are encouraged to rely on the retention mechanisms provided by the -backup plugin they are using. This ensures better flexibility and consistency -with the backup method in use. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/backup_barmanobjectstore.mdx b/product_docs/docs/postgres_for_kubernetes/preview/backup_barmanobjectstore.mdx deleted file mode 100644 index 1aa167ba06b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/backup_barmanobjectstore.mdx +++ /dev/null @@ -1,359 +0,0 @@ ---- -title: 'Appendix B - Backup on object stores' -originalFilePath: 'src/appendixes/backup_barmanobjectstore.md' ---- - - - -!!!warning -As of {{name.ln}} 1.26, **native Barman Cloud support is deprecated** in -favor of the **Barman Cloud Plugin**. This page has been moved to the appendix -for reference purposes. While the native integration remains functional for -now, we strongly recommend beginning a gradual migration to the plugin-based -interface after appropriate testing. For guidance, see -[Migrating from Built-in {{name.ln}} Backup](https://cloudnative-pg.io/plugin-barman-cloud/docs/migration/). -!!! - -{{name.ln}} natively supports **online/hot backup** of PostgreSQL -clusters through continuous physical backup and WAL archiving on an object -store. This means that the database is always up (no downtime required) -and that Point In Time Recovery is available. - -The operator can orchestrate a continuous backup infrastructure -that is based on the [Barman Cloud](https://pgbarman.org) tool. Instead -of using the classical architecture with a Barman server, which -backs up many PostgreSQL instances, the operator relies on the -`barman-cloud-wal-archive`, `barman-cloud-check-wal-archive`, -`barman-cloud-backup`, `barman-cloud-backup-list`, and -`barman-cloud-backup-delete` tools. As a result, base backups will -be *tarballs*. Both base backups and WAL files can be compressed -and encrypted. - -For this, it is required to use an image with `barman-cli-cloud` included. -You can use the image `docker.enterprisedb.com/k8s/postgresql` for this scope, -as it is composed of a community PostgreSQL image and the latest -`barman-cli-cloud` package. - -!!!info Important -Always ensure that you are running the latest version of the operands -in your system to take advantage of the improvements introduced in -Barman cloud (as well as improve the security aspects of your cluster). -!!! - -!!!warning Changes in Barman Cloud 3.16+ and Bucket Creation -Starting with Barman Cloud 3.16, most Barman Cloud commands no longer -automatically create the target bucket, assuming it already exists. Only the -`barman-cloud-check-wal-archive` command creates the bucket now. Whenever this -is not the first operation run on an empty bucket, {{name.ln}} will throw an -error. As a result, to ensure reliable, future-proof operations and avoid -potential issues, we strongly recommend that you create and configure your -object store bucket *before* creating a `Cluster` resource that references it. -!!! - -A backup is performed from a primary or a designated primary instance in a -`Cluster` (please refer to -[replica clusters](replica_cluster.md) -for more information about designated primary instances), or alternatively -on a [standby](backup.md#backup-from-a-standby). - -## Common object stores - -If you are looking for a specific object store such as -[AWS S3](object_stores.md#aws-s3), -[Microsoft Azure Blob Storage](object_stores.md#azure-blob-storage), -[Google Cloud Storage](object_stores.md#google-cloud-storage), or a compatible -provider, please refer to [Appendix C - Common object stores for backups](object_stores.md). - -## WAL archiving - -WAL archiving is the process that feeds a [WAL archive](backup.md#wal-archive) -in {{name.ln}}. - -The WAL archive is defined in the `.spec.backup.barmanObjectStore` stanza of -a `Cluster` resource. - -!!!info -Please refer to [`BarmanObjectStoreConfiguration`](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration) -in the barman-cloud API for a full list of options. -!!! - -If required, you can choose to compress WAL files as soon as they -are uploaded and/or encrypt them: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - [...] - wal: - compression: gzip - encryption: AES256 -``` - -You can configure the encryption directly in your bucket, and the operator -will use it unless you override it in the cluster configuration. - -PostgreSQL implements a sequential archiving scheme, where the -`archive_command` will be executed sequentially for every WAL -segment to be archived. - -!!!info Important -By default, {{name.ln}} sets `archive_timeout` to `5min`, ensuring -that WAL files, even in case of low workloads, are closed and archived -at least every 5 minutes, providing a deterministic time-based value for -your Recovery Point Objective ([RPO](before_you_start.md#postgresql-terminology)). Even though you change the value -of the [`archive_timeout` setting in the PostgreSQL configuration](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-ARCHIVE-TIMEOUT), -our experience suggests that the default value set by the operator is -suitable for most use cases. -!!! - -When the bandwidth between the PostgreSQL instance and the object -store allows archiving more than one WAL file in parallel, you -can use the parallel WAL archiving feature of the instance manager -like in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - [...] - wal: - compression: gzip - maxParallel: 8 - encryption: AES256 -``` - -In the previous example, the instance manager optimizes the WAL -archiving process by archiving in parallel at most eight ready -WALs, including the one requested by PostgreSQL. - -When PostgreSQL will request the archiving of a WAL that has -already been archived by the instance manager as an optimization, -that archival request will be just dismissed with a positive status. - -## Retention policies - -{{name.ln}} can manage the automated deletion of backup files from -the backup object store, using **retention policies** based on the recovery -window. - -Internally, the retention policy feature uses `barman-cloud-backup-delete` -with `--retention-policy “RECOVERY WINDOW OF {{ retention policy value }} {{ retention policy unit }}”`. - -For example, you can define your backups with a retention policy of 30 days as -follows: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - destinationPath: "" - s3Credentials: - accessKeyId: - name: aws-creds - key: ACCESS_KEY_ID - secretAccessKey: - name: aws-creds - key: ACCESS_SECRET_KEY - retentionPolicy: "30d" -``` - -!!!note There's more ... -The **recovery window retention policy** is focused on the concept of -*Point of Recoverability* (`PoR`), a moving point in time determined by -`current time - recovery window`. The *first valid backup* is the first -available backup before `PoR` (in reverse chronological order). -{{name.ln}} must ensure that we can recover the cluster at -any point in time between `PoR` and the latest successfully archived WAL -file, starting from the first valid backup. Base backups that are older -than the first valid backup will be marked as *obsolete* and permanently -removed after the next backup is completed. -!!! - -## Compression algorithms - -{{name.ln}} by default archives backups and WAL files in an -uncompressed fashion. However, it also supports the following compression -algorithms via `barman-cloud-backup` (for backups) and -`barman-cloud-wal-archive` (for WAL files): - -- bzip2 -- gzip -- lz4 -- snappy -- xz -- zstd - -The compression settings for backups and WALs are independent. See the -[DataBackupConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#DataBackupConfiguration) and -[WALBackupConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#WalBackupConfiguration) sections in -the barman-cloud API reference. - -It is important to note that archival time, restore time, and size change -between the algorithms, so the compression algorithm should be chosen according -to your use case. - -The Barman team has performed an evaluation of the performance of the supported -algorithms for Barman Cloud. The following table summarizes a scenario where a -backup is taken on a local MinIO deployment. The Barman GitHub project includes -a [deeper analysis](https://github.com/EnterpriseDB/barman/issues/344#issuecomment-992547396). - -| Compression | Backup Time (ms) | Restore Time (ms) | Uncompressed size (MB) | Compressed size (MB) | Approx ratio | -| ----------- | ---------------- | ----------------- | ---------------------- | -------------------- | ------------ | -| None | 10927 | 7553 | 395 | 395 | 1:1 | -| bzip2 | 25404 | 13886 | 395 | 67 | 5.9:1 | -| gzip | 116281 | 3077 | 395 | 91 | 4.3:1 | -| snappy | 8134 | 8341 | 395 | 166 | 2.4:1 | - -## Tagging of backup objects - -Barman 2.18 introduces support for tagging backup resources when saving them in -object stores via `barman-cloud-backup` and `barman-cloud-wal-archive`. As a -result, if your PostgreSQL container image includes Barman with version 2.18 or -higher, {{name.ln}} enables you to specify tags as key-value pairs -for backup objects, namely base backups, WAL files and history files. - -You can use two properties in the `.spec.backup.barmanObjectStore` definition: - -- `tags`: key-value pair tags to be added to backup objects and archived WAL - file in the backup object store -- `historyTags`: key-value pair tags to be added to archived history files in - the backup object store - -The excerpt of a YAML manifest below provides an example of usage of this -feature: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - [...] - tags: - backupRetentionPolicy: "expire" - historyTags: - backupRetentionPolicy: "keep" -``` - -## Extra options for the backup and WAL commands - -You can append additional options to the `barman-cloud-backup` and `barman-cloud-wal-archive` commands by using -the `additionalCommandArgs` property in the -`.spec.backup.barmanObjectStore.data` and `.spec.backup.barmanObjectStore.wal` sections respectively. -These properties are lists of strings that will be appended to the -`barman-cloud-backup` and `barman-cloud-wal-archive` commands. - -For example, you can use the `--read-timeout=60` to customize the connection -reading timeout. - -For additional options supported by `barman-cloud-backup` and `barman-cloud-wal-archive` commands you can refer to the -official barman documentation [here](https://www.pgbarman.org/documentation/). - -If an option provided in `additionalCommandArgs` is already present in the -declared options in its section (`.spec.backup.barmanObjectStore.data` or `.spec.backup.barmanObjectStore.wal`), the extra option will be -ignored. - -The following is an example of how to use this property: - -For backups: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - [...] - data: - additionalCommandArgs: - - "--min-chunk-size=5MB" - - "--read-timeout=60" -``` - -For WAL files: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - [...] - wal: - additionalCommandArgs: - - "--max-concurrency=1" - - "--read-timeout=60" -``` - -## Recovery from an object store - -You can recover from a backup created by Barman Cloud and stored on a supported -object store. After you define the external cluster, including all the required -configuration in the `barmanObjectStore` section, you need to reference it in -the `.spec.recovery.source` option. - -This example defines a recovery object store in a blob container in Azure: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - [...] - - superuserSecret: - name: superuser-secret - - bootstrap: - recovery: - source: clusterBackup - - externalClusters: - - name: clusterBackup - barmanObjectStore: - destinationPath: https://STORAGEACCOUNTNAME.blob.core.windows.net/CONTAINERNAME/ - azureCredentials: - storageAccount: - name: recovery-object-store-secret - key: storage_account_name - storageKey: - name: recovery-object-store-secret - key: storage_account_key - wal: - maxParallel: 8 -``` - -The previous example assumes that the application database and its owning user -are named `app` by default. If the PostgreSQL cluster being restored uses -different names, you must specify these names before exiting the recovery phase, -as documented in ["Configure the application database"](recovery.md#configure-the-application-database). - -!!!info Important -By default, the `recovery` method strictly uses the `name` of the -cluster in the `externalClusters` section as the name of the main folder -of the backup data within the object store. This name is normally reserved -for the name of the server. You can specify a different folder name -using the `barmanObjectStore.serverName` property. -!!! - -!!!note -This example takes advantage of the parallel WAL restore feature, -dedicating up to 8 jobs to concurrently fetch the required WAL files from the -archive. This feature can appreciably reduce the recovery time. Make sure that -you plan ahead for this scenario and correctly tune the value of this parameter -for your environment. It will make a difference when you need it, and you will. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/backup_recovery.mdx b/product_docs/docs/postgres_for_kubernetes/preview/backup_recovery.mdx deleted file mode 100644 index b90f8c8a302..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/backup_recovery.mdx +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: 'Backup and Recovery' -originalFilePath: 'src/backup_recovery.md' ---- - - - -[Backup](backup.md) and [recovery](recovery.md) are in two separate sections. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/backup_volumesnapshot.mdx b/product_docs/docs/postgres_for_kubernetes/preview/backup_volumesnapshot.mdx deleted file mode 100644 index aa7fcd36f4e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/backup_volumesnapshot.mdx +++ /dev/null @@ -1,414 +0,0 @@ ---- -title: 'Appendix A - Backup on volume snapshots' -originalFilePath: 'src/appendixes/backup_volumesnapshot.md' ---- - - - -!!!info Important -Please refer to the official Kubernetes documentation for a list of all -the supported [Container Storage Interface (CSI) drivers](https://kubernetes-csi.github.io/docs/drivers.html) -that provide snapshotting capabilities. -!!! - -{{name.ln}} is one of the first known cases of database operators that -directly leverages the Kubernetes native Volume Snapshot API for both -backup and recovery operations, in an entirely declarative way. - -## About standard Volume Snapshots - -Volume snapshotting was first introduced in -[Kubernetes 1.12 (2018) as alpha](https://kubernetes.io/blog/2018/10/09/introducing-volume-snapshot-alpha-for-kubernetes/), -promoted to [beta in 1.17 (2019)](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/), -and [moved to GA in 1.20 (2020)](https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/). -It’s now stable, widely available, and standard, providing 3 custom resource -definitions: `VolumeSnapshot`, `VolumeSnapshotContent` and -`VolumeSnapshotClass`. - -This Kubernetes feature defines a generic interface for: - -- the creation of a new volume snapshot, starting from a PVC -- the deletion of an existing snapshot -- the creation of a new volume from a snapshot - -Kubernetes delegates the actual implementation to the underlying CSI drivers -(not all of them support volume snapshots). Normally, storage classes that -provide volume snapshotting support **incremental and differential block level -backup in a transparent way for the application**, which can delegate the -complexity and the independent management down the stack, including -cross-cluster availability of the snapshots. - -## Requirements - -For Volume Snapshots to work with a {{name.ln}} cluster, you need to ensure -that each storage class used to dynamically provision the PostgreSQL volumes -(namely, `storage` and `walStorage` sections) support volume snapshots. - -Given that instructions vary from storage class to storage class, please -refer to the documentation of the specific storage class and related CSI -drivers you have deployed in your Kubernetes system. - -Normally, it is the [`VolumeSnapshotClass`](https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes/) -that is responsible to ensure that snapshots can be taken from persistent -volumes of a given storage class, and managed as `VolumeSnapshot` and -`VolumeSnapshotContent` resources. - -!!!info Important -It is your responsibility to verify with the third party vendor -that volume snapshots are supported. {{name.ln}} only interacts -with the Kubernetes API on this matter, and we cannot support issues -at the storage level for each specific CSI driver. -!!! - -## How to configure Volume Snapshot backups - -{{name.ln}} allows you to configure a given Postgres cluster for Volume -Snapshot backups through the `backup.volumeSnapshot` stanza. - -!!!info -Please refer to [`VolumeSnapshotConfiguration`](pg4k.v1.md#volumesnapshotconfiguration) -in the API reference for a full list of options. -!!! - -A generic example with volume snapshots (assuming that PGDATA and WALs share -the same storage class) is the following: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: snapshot-cluster -spec: - instances: 3 - - storage: - storageClass: @STORAGE_CLASS@ - size: 10Gi - walStorage: - storageClass: @STORAGE_CLASS@ - size: 10Gi - - backup: - # Volume snapshot backups - volumeSnapshot: - className: @VOLUME_SNAPSHOT_CLASS_NAME@ - - plugins: - - name: barman-cloud.cloudnative-pg.io - isWALArchiver: true - parameters: - barmanObjectName: @OBJECTSTORE_NAME@ -``` - -As you can see, the `backup` section contains both the `volumeSnapshot` stanza -(controlling physical base backups on volume snapshots) and the -`plugins` one (controlling the [WAL archive](wal_archiving.md)). - -!!!info -Once you have defined the `plugin`, you can decide to use -both volume snapshot and plugin backup strategies simultaneously -to take physical backups. -!!! - -The `volumeSnapshot.className` option allows you to reference the default -`VolumeSnapshotClass` object used for all the storage volumes you have -defined in your PostgreSQL cluster. - -!!!info -In case you are using a different storage class for `PGDATA` and -WAL files, you can specify a separate `VolumeSnapshotClass` for -that volume through the `walClassName` option (which defaults to -the same value as `className`). -!!! - -Once a cluster is defined for volume snapshot backups, you need to define -a `ScheduledBackup` resource that requests such backups on a periodic basis. - -## Hot and cold backups - -!!!warning -As noted in the [backup document](backup.md), a cold snapshot explicitly -set to target the primary will result in the primary being fenced for -the duration of the backup, making the cluster read-only during this -period. For safety, in a cluster already containing fenced instances, a cold -snapshot is rejected. -!!! - -By default, {{name.ln}} requests an online/hot backup on volume snapshots, using the -[PostgreSQL defaults of the low-level API for base backups](https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP): - -- it doesn't request an immediate checkpoint when starting the backup procedure -- it waits for the WAL archiver to archive the last segment of the backup when - terminating the backup procedure - -!!!info Important -The default values are suitable for most production environments. Hot -backups are consistent and can be used to perform snapshot recovery, as we -ensure WAL retention from the start of the backup through a temporary -replication slot. However, our recommendation is to rely on cold backups for -that purpose. -!!! - -You can explicitly change the default behavior through the following options in -the `.spec.backup.volumeSnapshot` stanza of the `Cluster` resource: - -- `online`: accepting `true` (default) or `false` as a value -- `onlineConfiguration.immediateCheckpoint`: whether you want to request an - immediate checkpoint before you start the backup procedure or not; - technically, it corresponds to the `fast` argument you pass to the - `pg_backup_start`/`pg_start_backup()` function in PostgreSQL, accepting - `true` (default) or `false` -- `onlineConfiguration.waitForArchive`: whether you want to wait for the - archiver to process the last segment of the backup or not; technically, it - corresponds to the `wait_for_archive` argument you pass to the - `pg_backup_stop`/`pg_stop_backup()` function in PostgreSQL, accepting `true` - (default) or `false` - -If you want to change the default behavior of your Postgres cluster to take -cold backups by default, all you need to do is add the `online: false` option -to your manifest, as follows: - -```yaml - # ... - backup: - volumeSnapshot: - online: false - # ... -``` - -If you are instead requesting an immediate checkpoint as the default behavior, -you can add this section: - -```yaml - # ... - backup: - volumeSnapshot: - online: true - onlineConfiguration: - immediateCheckpoint: true - # ... -``` - -### Overriding the default behavior - -You can change the default behavior defined in the cluster resource by setting -different values for `online` and, if needed, `onlineConfiguration` in the `Backup` or `ScheduledBackup` objects. - -For example, in case you want to issue an on-demand cold backup, you can -create a `Backup` object with `.spec.online: false`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Backup -metadata: - name: snapshot-cluster-cold-backup-example -spec: - cluster: - name: snapshot-cluster - method: volumeSnapshot - online: false -``` - -Similarly, for the ScheduledBackup: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ScheduledBackup -metadata: - name: snapshot-cluster-cold-backup-example -spec: - schedule: "0 0 0 * * *" - backupOwnerReference: self - cluster: - name: snapshot-cluster - method: volumeSnapshot - online: false -``` - -## Persistence of volume snapshot objects - -By default, `VolumeSnapshot` objects created by {{name.ln}} are retained after -deleting the `Backup` object that originated them, or the `Cluster` they refer to. -Such behavior is controlled by the `.spec.backup.volumeSnapshot.snapshotOwnerReference` -option which accepts the following values: - -- `none`: no ownership is set, meaning that `VolumeSnapshot` objects persist - after the `Backup` and/or the `Cluster` resources are removed -- `backup`: the `VolumeSnapshot` object is owned by the `Backup` resource that - originated it, and when the backup object is removed, the volume snapshot is - also removed -- `cluster`: the `VolumeSnapshot` object is owned by the `Cluster` resource that - is backed up, and when the Postgres cluster is removed, the volume snapshot is - also removed - -In case a `VolumeSnapshot` is deleted, the `deletionPolicy` specified in the -`VolumeSnapshotContent` is evaluated: - -- if set to `Retain`, the `VolumeSnapshotContent` object is kept -- if set to `Delete`, the `VolumeSnapshotContent` object is removed as well - -!!!warning -`VolumeSnapshotContent` objects do not keep all the information regarding the -backup and the cluster they refer to (like the annotations and labels that -are contained in the `VolumeSnapshot` object). Although possible, restoring -from just this kind of object might not be straightforward. For this reason, -our recommendation is to always backup the `VolumeSnapshot` definitions, -even using a Kubernetes level data protection solution. -!!! - -The value in `VolumeSnapshotContent` is determined by the `deletionPolicy` set -in the corresponding `VolumeSnapshotClass` definition, which is -referenced in the `.spec.backup.volumeSnapshot.className` option. - -Please refer to the [Kubernetes documentation on Volume Snapshot Classes](https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes/) -for details on this standard behavior. - -## Backup Volume Snapshot Deadlines - -{{name.ln}} supports backups using the volume snapshot method. In some -environments, volume snapshots may encounter temporary issues that can be -retried. - -The `backup.k8s.enterprisedb.io/volumeSnapshotDeadline` annotation defines how long -{{name.ln}} should continue retrying recoverable errors before marking the -backup as failed. - -You can add the `backup.k8s.enterprisedb.io/volumeSnapshotDeadline` annotation to both -`Backup` and `ScheduledBackup` resources. For `ScheduledBackup` resources, this -annotation is automatically inherited by any `Backup` resources created from -the schedule. - -If not specified, the default retry deadline is **10 minutes**. - -### Error Handling - -When a retryable error occurs during a volume snapshot operation: - -1. {{name.ln}} records the time of the first error. -2. The system retries the operation every **10 seconds**. -3. If the error persists beyond the specified deadline (or the default 10 - minutes), the backup is marked as **failed**. - -### Retryable Errors - -{{name.ln}} treats the following types of errors as retryable: - -- **Server timeout errors** (HTTP 408, 429, 500, 502, 503, 504) -- **Conflicts** (optimistic locking errors) -- **Internal errors** -- **Context deadline exceeded errors** -- **Timeout errors from the CSI snapshot controller** - -### Examples - -You can add the annotation to a `ScheduledBackup` resource as follows: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ScheduledBackup -metadata: - name: daily-backup-schedule - annotations: - backup.k8s.enterprisedb.io/volumeSnapshotDeadline: "20" -spec: - schedule: "0 0 * * *" - backupOwnerReference: self - method: volumeSnapshot - # other configuration... -``` - -When you define a `ScheduledBackup` with the annotation, any `Backup` resources -created from this schedule automatically inherit the specified timeout value. - -In the following example, all backups created from the schedule will have a -30-minute timeout for retrying recoverable snapshot errors. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ScheduledBackup -metadata: - name: weekly-backup - annotations: - backup.k8s.enterprisedb.io/volumeSnapshotDeadline: "30" -spec: - schedule: "0 0 * * 0" # Weekly backup on Sunday - method: volumeSnapshot - cluster: - name: my-postgresql-cluster -``` - -Alternatively, you can add the annotation directly to a `Backup` Resource: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Backup -metadata: - name: my-backup - annotations: - backup.k8s.enterprisedb.io/volumeSnapshotDeadline: "15" -spec: - method: volumeSnapshot - # other backup configuration... -``` - -## Example of Volume Snapshot Backup - -The following example shows how to configure volume snapshot base backups on an -EKS cluster on AWS using the `ebs-sc` storage class and the `csi-aws-vsc` -volume snapshot class. - -!!!info Important -If you are interested in testing the example, please read -["Volume Snapshots" for the Amazon Elastic Block Store (EBS) CSI driver](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/tree/master/examples/kubernetes/snapshot) -for detailed instructions on the installation process for the storage class and the snapshot class. -!!! - -The following manifest creates a `Cluster` that is ready to be used for volume -snapshots and that stores the WAL archive in a S3 bucket via IAM role for the -Service Account (IRSA, see [AWS S3](object_stores.md#aws-s3)): - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: hendrix -spec: - instances: 3 - - storage: - storageClass: ebs-sc - size: 10Gi - walStorage: - storageClass: ebs-sc - size: 10Gi - - backup: - volumeSnapshot: - className: csi-aws-vsc - - plugins: - - name: barman-cloud.cloudnative-pg.io - isWALArchiver: true - parameters: - barmanObjectName: @OBJECTSTORE_NAME@ - - serviceAccountTemplate: - metadata: - annotations: - eks.amazonaws.com/role-arn: "@ARN@" ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ScheduledBackup -metadata: - name: hendrix-vs-backup -spec: - cluster: - name: hendrix - method: volumeSnapshot - schedule: '0 0 0 * * *' - backupOwnerReference: cluster - immediate: true -``` - -The last resource defines daily volume snapshot backups at midnight, requesting -one immediately after the cluster is created. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/before_you_start.mdx b/product_docs/docs/postgres_for_kubernetes/preview/before_you_start.mdx deleted file mode 100644 index 6e22af47e7b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/before_you_start.mdx +++ /dev/null @@ -1,163 +0,0 @@ ---- -title: 'Before you start' -originalFilePath: 'src/before_you_start.md' ---- - - - -Before we get started, it is essential to go over some terminology that is -specific to Kubernetes and PostgreSQL. - -## Kubernetes terminology - -[Node](https://kubernetes.io/docs/concepts/architecture/nodes/) -: A *node* is a worker machine in Kubernetes, either virtual or physical, where - all services necessary to run pods are managed by the control plane node(s). - -[Postgres Node](architecture.md#reserving-nodes-for-postgresql-workloads) -: A *Postgres node* is a Kubernetes worker node dedicated to running PostgreSQL - workloads. This is achieved by applying the `node-role.kubernetes.io` label and - taint, as [proposed by {{name.ln}}](architecture.md#reserving-nodes-for-postgresql-workloads). - It is also referred to as a `postgres` node. - -[Pod](https://kubernetes.io/docs/concepts/workloads/pods/pod/) -: A *pod* is the smallest computing unit that can be deployed in a Kubernetes - cluster and is composed of one or more containers that share network and - storage. - -[Service](https://kubernetes.io/docs/concepts/services-networking/service/) -: A *service* is an abstraction that exposes as a network service an - application that runs on a group of pods and standardizes important features - such as service discovery across applications, load balancing, failover, and so - on. - -[Secret](https://kubernetes.io/docs/concepts/configuration/secret/) -: A *secret* is an object that is designed to store small amounts of sensitive - data such as passwords, access keys, or tokens, and use them in pods. - -[Storage Class](https://kubernetes.io/docs/concepts/storage/storage-classes/) -: A *storage class* allows an administrator to define the classes of storage in - a cluster, including provisioner (such as AWS EBS), reclaim policies, mount - options, volume expansion, and so on. - -[Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) -: A *persistent volume* (PV) is a resource in a Kubernetes cluster that - represents storage that has been either manually provisioned by an - administrator or dynamically provisioned by a *storage class* controller. A PV - is associated with a pod using a *persistent volume claim* and its lifecycle is - independent of any pod that uses it. Normally, a PV is a network volume, - especially in the public cloud. A [*local persistent volume* - (LPV)](https://kubernetes.io/docs/concepts/storage/volumes/#local) is a - persistent volume that exists only on the particular node where the pod that - uses it is running. - -[Persistent Volume Claim](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) -: A *persistent volume claim* (PVC) represents a request for storage, which - might include size, access mode, or a particular storage class. Similar to how - a pod consumes node resources, a PVC consumes the resources of a PV. - -[Namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) -: A *namespace* is a logical and isolated subset of a Kubernetes cluster and - can be seen as a *virtual cluster* within the wider physical cluster. - Namespaces allow administrators to create separated environments based on - projects, departments, teams, and so on. - -[RBAC](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) -: *Role Based Access Control* (RBAC), also known as *role-based security*, is a - method used in computer systems security to restrict access to the network and - resources of a system to authorized users only. Kubernetes has a native API to - control roles at the namespace and cluster level and associate them with - specific resources and individuals. - -[CRD](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) -: A *custom resource definition* (CRD) is an extension of the Kubernetes API - and allows developers to create new data types and objects, *called custom - resources*. - -[Operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) -: An *operator* is a custom resource that automates those steps that are - normally performed by a human operator when managing one or more applications - or given services. An operator assists Kubernetes in making sure that the - resource's defined state always matches the observed one. - -[`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/) -: `kubectl` is the command-line tool used to manage a Kubernetes cluster. - -{{name.ln}} requires a Kubernetes version supported by the community. Please refer to the -["Supported releases"](https://www.enterprisedb.com/resources/platform-compatibility#pgk8s) page for details. - -## PostgreSQL terminology - -Instance -: A Postgres server process running and listening on a pair "IP address(es)" - and "TCP port" (usually 5432). - -Primary -: A PostgreSQL instance that can accept both read and write operations. - -Replica -: A PostgreSQL instance replicating from the only primary instance in a - cluster and is kept updated by reading a stream of Write-Ahead Log (WAL) - records. A replica is also known as *standby* or *secondary* server. PostgreSQL - relies on physical streaming replication (async/sync) and file-based log - shipping (async). - -Hot Standby -: PostgreSQL feature that allows a *replica* to accept read-only workloads. - -Cluster -: To be intended as High Availability (HA) Cluster: a set of PostgreSQL - instances made up by a single primary and an optional arbitrary number of - replicas. - -Replica Cluster -: A {{name.ln}} `Cluster` that is in continuous recovery mode from a selected - PostgreSQL cluster, normally residing outside the Kubernetes cluster. It is a - feature that enables multi-cluster deployments in private, public, hybrid, and - multi-cloud contexts. - -Designated Primary -: A PostgreSQL standby instance in a replica cluster that is in continuous - recovery from another PostgreSQL cluster and that is designated to become - primary in case the replica cluster becomes primary. - -Superuser -: In PostgreSQL a *superuser* is any role with both `LOGIN` and `SUPERUSER` - privileges. For security reasons, {{name.ln}} performs administrative tasks - by connecting to the `postgres` database as the `postgres` user via `peer` - authentication over the local Unix Domain Socket. - -[WAL](https://www.postgresql.org/docs/current/wal-intro.html) -: Write-Ahead Logging (WAL) is a standard method for ensuring data integrity in - database management systems. - -PVC group -: A PVC group in {{name.ln}}' terminology is a group of related PVCs - belonging to the same PostgreSQL instance, namely the main volume containing - the PGDATA (`storage`) and the volume for WALs (`walStorage`). - -RTO -: Acronym for "recovery time objective", the amount of time a system can be - unavailable without adversely impacting the application. - -RPO -: Acronym for "recovery point objective", a calculation of the level of - acceptable data loss following a disaster recovery scenario. - -## Cloud terminology - -Region -: A *region* in the Cloud is an isolated and independent geographic area - organized in *availability zones*. Zones within a region have very little - round-trip network latency. - -Zone -: An *availability zone* in the Cloud (also known as *zone*) is an area in a - region where resources can be deployed. Usually, an availability zone - corresponds to a data center or an isolated building of the same data center. - -## What to do next - -Now that you have familiarized with the terminology, you can decide to -[test {{name.ln}} on your laptop using a local cluster](quickstart.md) before -deploying the operator in your selected cloud environment. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/benchmarking.mdx b/product_docs/docs/postgres_for_kubernetes/preview/benchmarking.mdx deleted file mode 100644 index 764e6d10f43..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/benchmarking.mdx +++ /dev/null @@ -1,213 +0,0 @@ ---- -title: 'Benchmarking' -originalFilePath: 'src/benchmarking.md' ---- - - - -The CNP kubectl plugin provides an easy way for benchmarking a PostgreSQL deployment in Kubernetes using {{name.ln}}. - -Benchmarking is focused on two aspects: - -- the **database**, by relying on [pgbench](https://www.postgresql.org/docs/current/pgbench.html) -- the **storage**, by relying on [fio](https://fio.readthedocs.io/en/latest/fio_doc.html) - -!!!info IMPORTANT -`pgbench` and `fio` must be run in a staging or pre-production environment. -Do not use these plugins in a production environment, as it might have -catastrophic consequences on your databases and the other -workloads/applications that run in the same shared environment. -!!! - -### pgbench - -The `kubectl` CNP plugin command `pgbench` executes a user-defined `pgbench` job -against an existing Postgres Cluster. - -Through the `--dry-run` flag you can generate the manifest of the job for later -modification/execution. - -A common command structure with `pgbench` is the following: - -```shell -kubectl cnp pgbench \ - -n \ - --job-name \ - --db-name \ - -- -``` - -!!!info IMPORTANT -Please refer to the [`pgbench` documentation](https://www.postgresql.org/docs/current/pgbench.html) -for information about the specific options to be used in your jobs. -!!! - -This example creates a job called `pgbench-init` that initializes for `pgbench` -OLTP-like purposes the `app` database in a `Cluster` named `cluster-example`, -using a scale factor of 1000: - -```shell -kubectl cnp pgbench \ - --job-name pgbench-init \ - cluster-example \ - -- --initialize --scale 1000 -``` - -!!!note -This will generate a database with 100000000 records, taking approximately 13GB -of space on disk. -!!! - -You can see the progress of the job with: - -```shell -kubectl logs jobs/pgbench-run -``` - -The following example creates a job called `pgbench-run` executing `pgbench` -against the previously initialized database for 30 seconds, using a single -connection: - -```shell -kubectl cnp pgbench \ - --job-name pgbench-run \ - cluster-example \ - -- --time 30 --client 1 --jobs 1 -``` - -The next example runs `pgbench` against an existing database by using the -`--db-name` flag and the `pgbench` namespace: - -```shell -kubectl cnp pgbench \ - --db-name pgbench \ - --job-name pgbench-job \ - cluster-example \ - -- --time 30 --client 1 --jobs 1 -``` - -By default, jobs do not expire. You can enable automatic deletion with the -`--ttl` flag. The job will be deleted after the specified duration (in seconds). - -```shell -kubectl cnp pgbench \ - --job-name pgbench-run \ - --ttl 600 \ - cluster-example \ - -- --time 30 --client 1 --jobs 1 -``` - -If you want to run a `pgbench` job on a specific worker node, you can use -the `--node-selector` option. Suppose you want to run the previous -initialization job on a node having the `workload=pgbench` label, you can run: - -```shell -kubectl cnp pgbench \ - --db-name pgbench \ - --job-name pgbench-init \ - --node-selector workload=pgbench \ - cluster-example \ - -- --initialize --scale 1000 -``` - -The job status can be fetched by running: - -``` -kubectl get job/pgbench-job -n - -NAME COMPLETIONS DURATION AGE -job-name 1/1 15s 41s -``` - -Once the job is completed the results can be gathered by executing: - -``` -kubectl logs job/pgbench-job -n -``` - -### fio - -The kubectl CNP plugin command `fio` executes a fio job with default values -and read operations. -Through the `--dry-run` flag you can generate the manifest of the job for later -modification/execution. - -!!!note -The kubectl plugin command `fio` will create a deployment with predefined -fio job values using a ConfigMap. If you want to provide custom job values, we -recommend generating a manifest using the `--dry-run` flag and providing your -custom job values in the generated ConfigMap. -!!! - -Example of default usage: - -```shell -kubectl cnp fio -``` - -Example with custom values: - -```shell -kubectl cnp fio \ - -n \ - --storageClass \ - --pvcSize -``` - -Example of how to run the `fio` command against a `StorageClass` named -`standard` and `pvcSize: 2Gi` in the `fio` namespace: - -```shell -kubectl cnp fio fio-job \ - -n fio \ - --storageClass standard \ - --pvcSize 2Gi -``` - -The deployment status can be fetched by running: - -```shell -kubectl get deployment/fio-job -n fio - -NAME READY UP-TO-DATE AVAILABLE AGE -fio-job 1/1 1 1 14s - -``` - -After running kubectl plugin command `fio`. - -It will: - -1. Create a PVC -2. Create a ConfigMap representing the configuration of a fio job -3. Create a fio deployment composed by a single Pod, which will run fio on - the PVC, create graphs after completing the benchmark and start serving the - generated files with a webserver. We use the - [`fio-tools`](https://github.com/wallnerryan/fio-tools) image for that. - -The Pod created by the deployment will be ready when it starts serving the -results. You can forward the port of the pod created by the deployment - -``` -kubectl port-forward -n deployment/ 8000 -``` - -and then use a browser and connect to `http://localhost:8000/` to get the data. - -The default 8k block size has been chosen to emulate a PostgreSQL workload. -Disks that cap the amount of available IOPS can show very different throughput -values when changing this parameter. - -Below is an example diagram of sequential writes on a local disk -mounted on a dedicated Kubernetes node -(1 hour benchmark): - -![Sequential writes bandwidth](images/write_bw.1-2Draw.png) - -After all testing is done, fio deployment and resources can be deleted by: - -```shell -kubectl cnp fio --dry-run | kubectl delete -f - -``` - -make sure use the same name which was used to create the fio deployment and add namespace if applicable. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/bootstrap.mdx b/product_docs/docs/postgres_for_kubernetes/preview/bootstrap.mdx deleted file mode 100644 index 8112f82c19c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/bootstrap.mdx +++ /dev/null @@ -1,819 +0,0 @@ ---- -title: 'Bootstrap' -originalFilePath: 'src/bootstrap.md' ---- - - - -!!!note -When referring to "PostgreSQL cluster" in this section, the same -concepts apply to both PostgreSQL and EDB Postgres Advanced Server, unless -differently stated. -!!! - -This section describes the options available to create a new -PostgreSQL cluster and the design rationale behind them. -There are primarily two ways to bootstrap a new cluster: - -- from scratch (`initdb`) -- from an existing PostgreSQL cluster, either directly (`pg_basebackup`) - or indirectly through a physical base backup (`recovery`) - -The `initdb` bootstrap also provides the option to import one or more -databases from an existing PostgreSQL cluster, even if it's outside -Kubernetes or running a different major version of PostgreSQL. -For more detailed information about this feature, please refer to the -["Importing Postgres databases"](database_import.md) section. - -!!!info Important -Bootstrapping from an existing cluster enables the creation of a -**replica cluster**—an independent PostgreSQL cluster that remains in -continuous recovery, stays synchronized with the source cluster, and -accepts read-only connections. -For more details, refer to the [Replica Cluster section](replica_cluster.md). -!!! - -!!!warning -{{name.ln}} requires both the `postgres` user and database to -always exist. Using the local Unix Domain Socket, it needs to connect -as the `postgres` user to the `postgres` database via `peer` authentication in -order to perform administrative tasks on the cluster. -**DO NOT DELETE** the `postgres` user or the `postgres` database!!! -!!! - -!!!info -{{name.ln}} is gradually introducing support for -[Kubernetes' native `VolumeSnapshot` API](https://github.com/cloudnative-pg/cloudnative-pg/issues/2081) -for both incremental and differential copy in backup and recovery -operations - if supported by the underlying storage classes. -Please see ["Recovery from Volume Snapshot objects"](recovery.md#recovery-from-volumesnapshot-objects) -for details. -!!! - -## The `bootstrap` section - -The *bootstrap* method can be defined in the `bootstrap` section of the cluster -specification. {{name.ln}} currently supports the following bootstrap methods: - -- `initdb`: initialize a new PostgreSQL cluster (default) -- `recovery`: create a PostgreSQL cluster by restoring from a base backup of an - existing cluster and, if needed, replaying all the available WAL files or up to - a given *point in time* -- `pg_basebackup`: create a PostgreSQL cluster by cloning an existing one of - the same major version using `pg_basebackup` through the streaming - replication protocol. This method is particularly useful for migrating - databases to {{name.ln}}, although meeting all requirements can be - challenging. Be sure to review the warnings in the - [`pg_basebackup` subsection](#bootstrap-from-a-live-cluster-pg_basebackup) - carefully. - -Only one bootstrap method can be specified in the manifest. -Attempting to define multiple bootstrap methods will result in validation errors. - -In contrast to the `initdb` method, both `recovery` and `pg_basebackup` -create a new cluster based on another one (either offline or online) and can be -used to spin up replica clusters. They both rely on the definition of external -clusters. -Refer to the [replica cluster section](replica_cluster.md) for more information. - -Given the amount of possible backup methods and combinations of backup -storage that the {{name.ln}} operator provides for `recovery`, please refer to -the dedicated ["Recovery" section](recovery.md) for guidance on each method. - -!!!note API reference -Please refer to the ["API reference for the `bootstrap` section](pg4k.v1.md#bootstrapconfiguration) -for more information. -!!! - -## The `externalClusters` section - -The `externalClusters` section of the cluster manifest can be used to configure -access to one or more PostgreSQL clusters as *sources*. -The primary use cases include: - -1. **Importing Databases:** Specify an external source to be utilized during - the [importation of databases](database_import.md) via logical backup and - restore, as part of the `initdb` bootstrap method. -2. **Cross-Region Replication:** Define a cross-region PostgreSQL cluster - employing physical replication, capable of extending across distinct Kubernetes - clusters or traditional VM/bare-metal environments. -3. **Recovery from Physical Base Backup:** Recover, fully or at a - given Point-In-Time, a PostgreSQL cluster by referencing a physical base - backup. - -!!!info -Ongoing development will extend the functionality of `externalClusters` to -accommodate additional use cases, such as logical replication and foreign -servers in future releases. -!!! - -As far as bootstrapping is concerned, `externalClusters` can be used -to define the source PostgreSQL cluster for either the `pg_basebackup` -method or the `recovery` one. An external cluster needs to have: - -- a name that identifies the external cluster, to be used as a reference via the - `source` option -- at least one of the following: - - - information about streaming connection - - information about the **recovery object store**, which is a Barman Cloud - compatible object store that contains: - - the WAL archive (required for Point In Time Recovery) - - the catalog of physical base backups for the Postgres cluster - -!!!note -A recovery object store is normally an AWS S3, Azure Blob Storage, -or Google Cloud Storage source that is managed by Barman Cloud. -!!! - -When only the streaming connection is defined, the source can be used for the -`pg_basebackup` method. When only the recovery object store is defined, the -source can be used for the `recovery` method. When both are defined, any of -the two bootstrap methods can be chosen. The following table summarizes your -options: - -| Content of externalClusters | pg_basebackup | recovery | -| :-------------------------- | :-----------: | :------: | -| Only streaming | ✓ | | -| Only object store | | ✓ | -| Streaming and object store | ✓ | ✓ | - -Furthermore, in case of `pg_basebackup` or full `recovery` point in time, the -cluster is eligible for replica cluster mode. This means that the cluster is -continuously fed from the source, either via streaming, via WAL shipping -through the PostgreSQL's `restore_command`, or any of the two. - -!!!note API reference -Please refer to the ["API reference for the `externalClusters` section](pg4k.v1.md#externalcluster) -for more information. -!!! - -### Password files - -Whenever a password is supplied within an `externalClusters` entry, -{{name.ln}} autonomously manages a [PostgreSQL password file](https://www.postgresql.org/docs/current/libpq-pgpass.html) -for it, residing at `/controller/external/NAME/pgpass` in each instance. - -This approach enables {{name.ln}} to securely establish connections with an -external server without exposing any passwords in the connection string. -Instead, the connection safely references the aforementioned file through the -`passfile` connection parameter. - -## Bootstrap an empty cluster (`initdb`) - -The `initdb` bootstrap method is used to create a new PostgreSQL cluster from -scratch. It is the default one unless specified differently. - -The following example contains the full structure of the `initdb` -configuration: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb -spec: - instances: 3 - - bootstrap: - initdb: - database: app - owner: app - secret: - name: app-secret - - storage: - size: 1Gi -``` - -The above example of bootstrap will: - -1. create a new `PGDATA` folder using PostgreSQL's native `initdb` command -2. create an *unprivileged* user named `app` -3. set the password of the latter (`app`) using the one in the `app-secret` - secret (make sure that `username` matches the same name of the `owner`) -4. create a database called `app` owned by the `app` user. - -Thanks to the *convention over configuration paradigm*, you can let the -operator choose a default database name (`app`) and a default application -user name (same as the database name), as well as randomly generate a -secure password for both the superuser and the application user in -PostgreSQL. - -Alternatively, you can generate your password, store it as a secret, -and use it in the PostgreSQL cluster - as described in the above example. - -The supplied secret must comply with the specifications of the -[`kubernetes.io/basic-auth` type](https://kubernetes.io/docs/concepts/configuration/secret/#basic-authentication-secret). -As a result, the `username` in the secret must match the one of the `owner` -(for the application secret) and `postgres` for the superuser one. - -The following is an example of a `basic-auth` secret: - -```yaml -apiVersion: v1 -data: - username: YXBw - password: cGFzc3dvcmQ= -kind: Secret -metadata: - name: app-secret -type: kubernetes.io/basic-auth -``` - -The application database is the one that should be used to store application -data. Applications should connect to the cluster with the user that owns -the application database. - -!!!info Important -If you need to create additional users, please refer to -["Declarative database role management"](declarative_role_management.md). -!!! - -In case you don't supply any database name, the operator will proceed -by convention and create the `app` database, and adds it to the cluster -definition using a *defaulting webhook*. -The user that owns the database defaults to the database name instead. - -The application user is not used internally by the operator, which instead -relies on the superuser to reconcile the cluster with the desired status. - -### Passing Options to `initdb` - -The PostgreSQL data directory is initialized using the -[`initdb` PostgreSQL command](https://www.postgresql.org/docs/current/app-initdb.html). - -{{name.ln}} enables you to customize the behavior of `initdb` to modify -settings such as default locale configurations and data checksums. - -!!!warning -{{name.ln}} acts only as a direct proxy to `initdb` for locale-related -options, due to the ongoing and significant enhancements in PostgreSQL's locale -support. It is your responsibility to ensure that the correct options are -provided, following the PostgreSQL documentation, and to verify that the -bootstrap process completes successfully. -!!! - -To include custom options in the `initdb` command, you can use the following -parameters: - -builtinLocale -: When `builtinLocale` is set to a value, {{name.ln}} passes it to the - `--builtin-locale` option in `initdb`. This option controls the builtin locale, as - defined in ["Locale Support"](https://www.postgresql.org/docs/current/locale.html) - from the PostgreSQL documentation (default: empty). Note that this option requires - `localeProvider` to be set to `builtin`. Available from PostgreSQL 17. - -dataChecksums -: When `dataChecksums` is set to `true`, {{name.ln}} invokes the `-k` option in - `initdb` to enable checksums on data pages and help detect corruption by the - I/O system - that would otherwise be silent (default: `false`). - -encoding -: When `encoding` set to a value, {{name.ln}} passes it to the `--encoding` - option in `initdb`, which selects the encoding of the template database - (default: `UTF8`). - -icuLocale -: When `icuLocale` is set to a value, {{name.ln}} passes it to the - `--icu-locale` option in `initdb`. This option controls the ICU locale, as - defined in ["Locale Support"](https://www.postgresql.org/docs/current/locale.html) - from the PostgreSQL documentation (default: empty). - Note that this option requires `localeProvider` to be set to `icu`. - Available from PostgreSQL 15. - -icuRules -: When `icuRules` is set to a value, {{name.ln}} passes it to the - `--icu-rules` option in `initdb`. This option controls the ICU locale, as - defined in ["Locale - Support"](https://www.postgresql.org/docs/current/locale.html) from the - PostgreSQL documentation (default: empty). Note that this option requires - `localeProvider` to be set to `icu`. Available from PostgreSQL 16. - -locale -: When `locale` is set to a value, {{name.ln}} passes it to the `--locale` - option in `initdb`. This option controls the locale, as defined in - ["Locale Support"](https://www.postgresql.org/docs/current/locale.html) from - the PostgreSQL documentation. By default, the locale parameter is empty. In - this case, environment variables such as `LANG` are used to determine the - locale. Be aware that these variables can vary between container images, - potentially leading to inconsistent behavior. - -localeCollate -: When `localeCollate` is set to a value, {{name.ln}} passes it to the `--lc-collate` - option in `initdb`. This option controls the collation order (`LC_COLLATE` - subcategory), as defined in ["Locale Support"](https://www.postgresql.org/docs/current/locale.html) - from the PostgreSQL documentation (default: `C`). - -localeCType -: When `localeCType` is set to a value, {{name.ln}} passes it to the `--lc-ctype` option in - `initdb`. This option controls the collation order (`LC_CTYPE` subcategory), as - defined in ["Locale Support"](https://www.postgresql.org/docs/current/locale.html) - from the PostgreSQL documentation (default: `C`). - -localeProvider -: When `localeProvider` is set to a value, {{name.ln}} passes it to the `--locale-provider` -option in `initdb`. This option controls the locale provider, as defined in -["Locale Support"](https://www.postgresql.org/docs/current/locale.html) from the -PostgreSQL documentation (default: empty, which means `libc` for PostgreSQL). -Available from PostgreSQL 15. - -walSegmentSize -: When `walSegmentSize` is set to a value, {{name.ln}} passes it to the `--wal-segsize` - option in `initdb` (default: not set - defined by PostgreSQL as 16 megabytes). - -!!!note -The only two locale options that {{name.ln}} implements during -the `initdb` bootstrap refer to the `LC_COLLATE` and `LC_TYPE` subcategories. -The remaining locale subcategories can be configured directly in the PostgreSQL -configuration, using the `lc_messages`, `lc_monetary`, `lc_numeric`, and -`lc_time` parameters. -!!! - -The following example enables data checksums and sets the default encoding to -`LATIN1`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb -spec: - instances: 3 - - bootstrap: - initdb: - database: app - owner: app - dataChecksums: true - encoding: 'LATIN1' - storage: - size: 1Gi -``` - -!!!warning -{{name.ln}} supports another way to customize the behavior of the -`initdb` invocation, using the `options` subsection. However, given that there -are options that can break the behavior of the operator (such as `--auth` or -`-d`), this technique is deprecated and will be removed from future versions of -the API. -!!! - -### Executing Queries After Initialization - -You can specify a custom list of queries that will be executed once, -immediately after the cluster is created and configured. These queries will be -executed as the *superuser* (`postgres`) against three different databases, in -this specific order: - -1. The `postgres` database (`postInit` section) -2. The `template1` database (`postInitTemplate` section) -3. The application database (`postInitApplication` section) - -For each of these sections, {{name.ln}} provides two ways to specify custom -queries, executed in the following order: - -- As a list of SQL queries in the cluster's definition (`postInitSQL`, - `postInitTemplateSQL`, and `postInitApplicationSQL` stanzas) -- As a list of Secrets and/or ConfigMaps, each containing a SQL script to be - executed (`postInitSQLRefs`, `postInitTemplateSQLRefs`, and - `postInitApplicationSQLRefs` stanzas). Secrets are processed before ConfigMaps. - -Objects in each list will be processed sequentially. - -!!!warning -Use the `postInit`, `postInitTemplate`, and `postInitApplication` options -with extreme care, as queries are run as a superuser and can disrupt the entire -cluster. An error in any of those queries will interrupt the bootstrap phase, -leaving the cluster incomplete and requiring manual intervention. -!!! - -!!!note - -These queries run with the standard `"$user", public` `search_path`, even -though operator-issued connections otherwise pin a fixed `search_path` for -security reasons. -See [Schema resolution and `search_path` hardening](security.md#schema-resolution-and-search_path-hardening) -for details. -Schema-qualify object references if you need them to be independent of the -`search_path`. -!!! - -!!!info Important -Ensure the existence of entries inside the ConfigMaps or Secrets specified -in `postInitSQLRefs`, `postInitTemplateSQLRefs`, and -`postInitApplicationSQLRefs`, otherwise the bootstrap will fail. Errors in any -of those SQL files will prevent the bootstrap phase from completing -successfully. -!!! - -The following example runs a single SQL query as part of the `postInitSQL` -stanza: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb -spec: - instances: 3 - - bootstrap: - initdb: - database: app - owner: app - dataChecksums: true - localeCollate: 'en_US' - localeCType: 'en_US' - postInitSQL: - - CREATE DATABASE angus - storage: - size: 1Gi -``` - -The example below relies on `postInitApplicationSQLRefs` to specify a secret -and a ConfigMap containing the queries to run after the initialization on the -application database: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb -spec: - instances: 3 - - bootstrap: - initdb: - database: app - owner: app - postInitApplicationSQLRefs: - secretRefs: - - name: my-secret - key: secret.sql - configMapRefs: - - name: my-configmap - key: configmap.sql - storage: - size: 1Gi -``` - -!!!note -Within SQL scripts, each SQL statement is executed in a single exec on the -server according to the [PostgreSQL semantics](https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-MULTI-STATEMENT). -Comments can be included, but internal commands like `psql` cannot. -!!! - -### Compatibility Features - -EDB Postgres Advanced Server adds many compatibility features to the -plain community PostgreSQL. You can find more information about that -in the [EDB Postgres Advanced Server](/epas/latest/). - -Those features are already enabled during cluster creation on EPAS and -are not supported on the community PostgreSQL image. To disable them -you can use the `redwood` flag in the `initdb` section -like in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb -spec: - instances: 3 - imageName: - - bootstrap: - initdb: - database: app - owner: app - redwood: false - storage: - size: 1Gi -``` - -## Bootstrap from another cluster - -{{name.ln}} enables bootstrapping a cluster starting from -another one of the same major version. -This operation can be carried out either connecting directly to the source cluster via -streaming replication (`pg_basebackup`), or indirectly via an existing -physical *base backup* (`recovery`). - -The source cluster must be defined in the `externalClusters` section, identified -by `name` (our recommendation is to use the same `name` of the origin cluster). - -!!!info Important -By default the `recovery` method strictly uses the `name` of the -cluster in the `externalClusters` section to locate the main folder -of the backup data within the object store, which is normally reserved -for the name of the server. Backup plugins provide ways to specify a -different one. For example, the Barman Cloud Plugin provides the [`serverName` parameter](https://cloudnative-pg.io/plugin-barman-cloud/docs/parameters/) -(by default assigned to the value of `name` in the external cluster definition). -!!! - -### Bootstrap from a backup (`recovery`) - -Given the variety of backup methods and combinations of backup storage -options provided by the {{name.ln}} operator for `recovery`, please refer -to the dedicated ["Recovery" section](recovery.md) for detailed guidance on -each method. - -### Bootstrap from a live cluster (`pg_basebackup`) - -The `pg_basebackup` bootstrap mode allows you to create a new cluster -(*target*) as an exact physical copy of an existing and **binary-compatible** -PostgreSQL instance (*source*) managed by {{name.ln}}, using a valid -*streaming replication* connection. The source instance can either be a primary -or a standby PostgreSQL server. It’s crucial to thoroughly review the -requirements section below, as the pros and cons of PostgreSQL physical -replication fully apply. - -The primary use cases for this method include: - -- Reporting and business intelligence clusters that need to be regenerated - periodically (daily, weekly) -- Test databases containing live data that require periodic regeneration - (daily, weekly, monthly) and anonymization -- Rapid spin-up of a standalone replica cluster -- Physical migrations of {{name.ln}} clusters to different namespaces or - Kubernetes clusters - -!!!info Important -Avoid using this method, based on physical replication, to migrate an -existing PostgreSQL cluster outside of Kubernetes into {{name.ln}}, unless you -are completely certain that all [requirements](#requirements) are met and -the operation has been -thoroughly tested. The {{name.ln}} community does not endorse this approach -for such use cases, and recommends using logical import instead. It is -exceedingly rare that all requirements for physical replication are met in a -way that seamlessly works with {{name.ln}}. -!!! - -!!!warning -In its current implementation, this method clones the source PostgreSQL -instance, thereby creating a *snapshot*. Once the cloning process has finished, -the new cluster is immediately started. -Refer to ["Current limitations"](#current-limitations) for more details. -!!! - -Similar to the `recovery` bootstrap method, once the cloning operation is -complete, the operator takes full ownership of the target cluster, starting -from the first instance. This includes overriding certain configuration -parameters as required by {{name.ln}}, resetting the superuser password, -creating the `streaming_replica` user, managing replicas, and more. The -resulting cluster operates independently from the source instance. - -!!!info Important -Configuring the network connection between the target and source instances -lies outside the scope of {{name.ln}} documentation, as it depends heavily on -the specific context and environment. -!!! - -The streaming replication client on the target instance, managed transparently -by `pg_basebackup`, can authenticate on the source instance using one of the -following methods: - -1. [Username/password](#usernamepassword-authentication) -2. [TLS client certificate](#tls-certificate-authentication) - -Both authentication methods are detailed below. - -#### Requirements - -The following requirements apply to the `pg_basebackup` bootstrap method: - -- target and source must have the same hardware architecture -- target and source must have the same major PostgreSQL version -- target and source must have the same tablespaces -- source must be configured with enough `max_wal_senders` to grant - access from the target for this one-off operation by providing at least - one *walsender* for the backup plus one for WAL streaming -- the network between source and target must be configured to enable the target - instance to connect to the PostgreSQL port on the source instance -- source must have a role with `REPLICATION LOGIN` privileges and must accept - connections from the target instance for this role in `pg_hba.conf`, preferably - via TLS (see ["About the replication user"](#about-the-replication-user) below) -- target must be able to successfully connect to the source PostgreSQL instance - using a role with `REPLICATION LOGIN` privileges - -!!!note Seealso -For further information, please refer to the -["Planning" section for Warm Standby](https://www.postgresql.org/docs/current/warm-standby.html#STANDBY-PLANNING), -the -[`pg_basebackup` page](https://www.postgresql.org/docs/current/app-pgbasebackup.html) -and the -["High Availability, Load Balancing, and Replication" chapter](https://www.postgresql.org/docs/current/high-availability.html) -in the PostgreSQL documentation. -!!! - -#### About the replication user - -As explained in the requirements section, you need to have a user -with either the `SUPERUSER` or, preferably, just the `REPLICATION` -privilege in the source instance. - -If the source database is created with {{name.ln}}, you -can reuse the `streaming_replica` user and take advantage of client -TLS certificates authentication (which, by default, is the only allowed -connection method for `streaming_replica`). - -For all other cases, including outside Kubernetes, please verify that -you already have a user with the `REPLICATION` privilege, or create -a new one by following the instructions below. - -As `postgres` user on the source system, please run: - -```console -createuser -P --replication streaming_replica -``` - -Enter the password at the prompt and save it for later, as you -will need to add it to a secret in the target instance. - -!!!note -Although the name is not important, we will use `streaming_replica` -for the sake of simplicity. Feel free to change it as you like, -provided you adapt the instructions in the following sections. -!!! - -#### Username/Password authentication - -The first authentication method supported by {{name.ln}} -with the `pg_basebackup` bootstrap is based on username and password matching. - -Make sure you have the following information before you start the procedure: - -- location of the source instance, identified by a hostname or an IP address - and a TCP port -- replication username (`streaming_replica` for simplicity) -- password - -You might need to add a line similar to the following to the `pg_hba.conf` -file on the source PostgreSQL instance: - -``` -# A more restrictive rule for TLS and IP of origin is recommended -host replication streaming_replica all md5 -``` - -The following manifest creates a new PostgreSQL 18.4 cluster, -called `target-db`, using the `pg_basebackup` bootstrap method -to clone an external PostgreSQL cluster defined as `source-db` -(in the `externalClusters` array). As you can see, the `source-db` -definition points to the `source-db.foo.com` host and connects as -the `streaming_replica` user, whose password is stored in the -`password` key of the `source-db-replica-user` secret. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: target-db -spec: - instances: 3 - imageName: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 - - bootstrap: - pg_basebackup: - source: source-db - - storage: - size: 1Gi - - externalClusters: - - name: source-db - connectionParameters: - host: source-db.foo.com - user: streaming_replica - password: - name: source-db-replica-user - key: password -``` - -All the requirements must be met for the clone operation to work, including -the same PostgreSQL version (in our case 18.4). - -#### TLS certificate authentication - -The second authentication method supported by {{name.ln}} -with the `pg_basebackup` bootstrap is based on TLS client certificates. -This is the recommended approach from a security standpoint. - -The following example clones an existing PostgreSQL cluster (`cluster-example`) -in the same Kubernetes cluster. - -!!!note -This example can be easily adapted to cover an instance that resides -outside the Kubernetes cluster. -!!! - -The manifest defines a new PostgreSQL 18.4 cluster called `cluster-clone-tls`, -which is bootstrapped using the `pg_basebackup` method from the `cluster-example` -external cluster. The host is identified by the read/write service -in the same cluster, while the `streaming_replica` user is authenticated -thanks to the provided keys, certificate, and certification authority -information (respectively in the `cluster-example-replication` and -`cluster-example-ca` secrets). - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-clone-tls -spec: - instances: 3 - imageName: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 - - bootstrap: - pg_basebackup: - source: cluster-example - - storage: - size: 1Gi - - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: streaming_replica - sslmode: verify-full - sslKey: - name: cluster-example-replication - key: tls.key - sslCert: - name: cluster-example-replication - key: tls.crt - sslRootCert: - name: cluster-example-ca - key: ca.crt -``` - -#### Configure the application database - -We also support to configure the application database for cluster which bootstrap -from a live cluster, just like the case of `initdb` and `recovery` bootstrap method. -If the new cluster is created as a replica cluster (with replica mode enabled), application -database configuration will be skipped. - -!!!info Important -While the `Cluster` is in recovery mode, no changes to the database, -including the catalog, are permitted. This restriction includes any role -overrides, which are deferred until the `Cluster` transitions to primary. -During the recovery phase, roles remain as defined in the source cluster. -!!! - -The example below configures the `app` database with the owner `app` and -the password stored in the provided secret `app-secret`, following the -bootstrap from a live cluster. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - bootstrap: - pg_basebackup: - database: app - owner: app - secret: - name: app-secret - source: cluster-example -``` - -With the above configuration, the following will happen only **after recovery is -completed**: - -1. If the `app` database does not exist, it will be created. -2. If the `app` user does not exist, it will be created. -3. If the `app` user is not the owner of the `app` database, ownership will be - granted to the `app` user. -4. If the `username` value matches the `owner` value in the secret, the - password for the application user (the `app` user in this case) will be - updated to the `password` value in the secret. - -#### Current limitations - -##### Snapshot copy - -The `pg_basebackup` method takes a snapshot of the source instance in the form of -a PostgreSQL base backup. All transactions written from the start of -the backup to the correct termination of the backup will be streamed to the target -instance using a second connection (see the `--wal-method=stream` option for -`pg_basebackup`). - -Once the backup is completed, the new instance will be started on a new timeline -and diverge from the source. -For this reason, it is advised to stop all write operations to the source database -before migrating to the target database. - -Note that this limitation applies only if the target cluster is not defined as -a replica cluster. - -!!!info Important -Before you attempt a migration, you must test both the procedure -and the applications. In particular, it is fundamental that you run the migration -procedure as many times as needed to systematically measure the downtime of your -applications in production. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/certificates.mdx b/product_docs/docs/postgres_for_kubernetes/preview/certificates.mdx deleted file mode 100644 index aaad7b4ec9a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/certificates.mdx +++ /dev/null @@ -1,375 +0,0 @@ ---- -title: 'Certificates' -originalFilePath: 'src/certificates.md' ---- - - - -{{name.ln}} was designed to natively support TLS certificates. -To set up a cluster, the operator requires: - -- A server certification authority (CA) certificate -- A server TLS certificate signed by the server CA -- A client CA certificate -- A streaming replication client certificate generated by the client CA - -!!!note -You can find all the secrets used by the cluster and their expiration dates -in the cluster's status. -!!! - -{{name.ln}} is very flexible when it comes to TLS certificates. It -primarily operates in two modes: - -1. [**Operator managed**](#operator-managed-mode) – Certificates are internally - managed by the operator in a fully automated way and signed using a CA created - by {{name.ln}}. -2. [**User provided**](#user-provided-certificates-mode) – Certificates are - generated outside the operator and imported in the cluster definition as - secrets. {{name.ln}} integrates itself with [cert-manager](https://cert-manager.io/) - (See [Cert-manager example](#cert-manager-example).) - -You can also choose a hybrid approach, where only part of the certificates is -generated outside CNP. - -!!!note -The operator and instances verify server certificates against the CA only, -disregarding the DNS name. This approach is due to the typical absence of DNS -names in user-provided certificates for the `-rw` service used for -communication within the cluster. -!!! - -!!!note - -Beyond the CA-managed certificates listed above, the operator also uses a -self-signed client certificate, generated in memory, to authenticate to the -instance manager's status port. This certificate is not signed by the client -CA: the instance manager trusts it by pinning its public-key fingerprint. See -[Operator-to-instance authentication](security.md#operator-to-instance-authentication). -!!! - -## Operator-Managed Mode - -By default, the operator automatically generates a single Certificate Authority -(CA) to issue both client and server certificates. These certificates are -managed continuously by the operator, with automatic renewal 7 days before -expiration (within a 90-day validity period). - -!!!info -You can adjust this default behavior by configuring the -`CERTIFICATE_DURATION` and `EXPIRING_CHECK_THRESHOLD` environment variables. -For detailed guidance, refer to the [Operator Configuration](operator_conf.md). -!!! - -!!!info Important -Certificate renewal does not cause any downtime for the PostgreSQL server, -as a simple reload operation is sufficient. However, any user-managed -certificates not controlled by {{name.ln}} must be re-issued following the -renewal process. -!!! - -When generating certificates, the operator assumes that the Kubernetes -cluster's DNS zone is set to `cluster.local` by default. This behavior can be -customized by setting the `KUBERNETES_CLUSTER_DOMAIN` environment variable. A -convenient alternative is to use the [operator's configuration capability](operator_conf.md). - -### Server certificates - -#### Server CA secret - -The operator generates a self-signed CA and stores it in a generic secret -containing the following keys: - -- `ca.crt` – CA certificate used to validate the server certificate, used as - `sslrootcert` in clients' connection strings. -- `ca.key` – The key used to sign the server SSL certificate automatically. - -#### Server TLS secret - -The operator uses the generated self-signed CA to sign a server TLS -certificate. It's stored in a secret of type `kubernetes.io/tls` and configured -to be used as `ssl_cert_file` and `ssl_key_file` by the instances. This -approach enables clients to verify their identity and connect securely. - -#### Server alternative DNS names - -In addition to the default ones, you can specify DNS server alternative names -as part of the generated server TLS secret. - -### Client certificates - -#### Client CA secret - -By default, the same self-signed CA as the server CA is used. The public part -is passed as `ssl_ca_file` to all the instances so it can verify client -certificates it signed. The private key is stored in the same secret and used -to sign client certificates generated by the `kubectl cnp` plugin. - -#### Client `streaming_replica` certificate - -The operator uses the generated self-signed CA to sign a client certificate for -the user `streaming_replica`, storing it in a secret of type -`kubernetes.io/tls`. To allow secure connection to the primary instance, this -certificate is passed as `sslcert` and `sslkey` in the replicas' connection -strings. - -## User-provided certificates mode - -### Server certificates - -If required, you can also provide the two server certificates, generating them -using a separate component such as [cert-manager](https://cert-manager.io/). -To use a custom server TLS certificate for a cluster, you must specify -the following parameters: - -- `serverTLSSecret` – The name of a secret of type `kubernetes.io/tls` - containing the server TLS certificate. It must contain both the standard - `tls.crt` and `tls.key` keys. -- `serverCASecret` – The name of a secret containing the `ca.crt` key. - -!!!note -The operator still creates and manages the two secrets related to client -certificates. -!!! - -!!!note -The operator and instances verify server certificates against the CA only, -disregarding the DNS name. This approach is due to the typical absence of DNS -names in user-provided certificates for the `-rw` service used for -communication within the cluster. -!!! - -!!!note -If you want ConfigMaps and secrets to be reloaded by instances, you can add -a label with the key `k8s.enterprisedb.io/reload` to it. Otherwise you must reload the -instances using the `kubectl cnp reload` subcommand. -!!! - -#### Example - -Given the following files: - -- `server-ca.crt` – The certificate of the CA that signed the server TLS certificate. -- `server.crt`– The certificate of the server TLS certificate. -- `server.key` – The private key of the server TLS certificate. - -Create a secret containing the CA certificate: - -```sh -kubectl create secret generic my-postgresql-server-ca \ - --from-file=ca.crt=./server-ca.crt -``` - -Create a secret with the TLS certificate: - -```sh -kubectl create secret tls my-postgresql-server \ - --cert=./server.crt --key=./server.key -``` - -Create a PostgreSQL cluster referencing those secrets: - -```bash -kubectl apply -f - < - -## Pod-to-Pod Network Security with {{name.ln}} and Cilium - -Kubernetes’ default behavior is to allow traffic between any two Pods in the cluster network. -Cilium provides advanced L3/L4 network security using the `CiliumNetworkPolicy` resource. This -enables fine-grained control over network traffic between Pods within a Kubernetes cluster. It is -especially useful for securing communication between application workloads and backend -services. - -In the following examples, we demonstrate how Cilium can be used to secure a -{{name.ln}} PostgreSQL instance by restricting ingress traffic to only -authorized Pods. - -!!!info Important -Before proceeding, ensure that the `cluster-example` Postgres cluster is up -and running in your environment. -!!! - -## Default Deny Behavior in Cilium - -By default, Cilium does **not** deny all traffic unless explicitly configured -to do so. In contrast to Kubernetes NetworkPolicy, which uses a deny-by-default -model once a policy is present in a namespace, Cilium provides more flexible -control over default deny behavior. - -To enforce a default deny posture with Cilium, you need to explicitly create a -policy that denies all traffic to a set of Pods unless otherwise allowed. This -is commonly achieved by using an **empty `ingress` section** in combination -with `endpointSelector`, or by enabling **`--enable-default-deny`** at the -Cilium agent level for broader enforcement. - -A minimal example of a default deny policy: - -```yaml -apiVersion: cilium.io/v2 -kind: CiliumNetworkPolicy -metadata: - name: default-deny - namespace: default -spec: - description: "Default deny all ingress traffic to all Pods in this namespace" - endpointSelector: {} - ingress: [] -``` - -## Making Cilium Network Policies work with {{name.ln}} Operator - -When working with a network policy, Cilium or not, the first step is to make -sure that the operator can reach the Pods in the target namespace. This is -important because the operator needs to be able to perform checks and actions -on the Pods, and one of those actions requires access to the port `8000` on the -Pods to get the current status of the PostgreSQL instance running inside. - -The following `CiliumNetworkPolicy` allows the operator to access the Pods in -the target `default` namespace: - -```yaml -apiVersion: cilium.io/v2 -kind: CiliumNetworkPolicy -metadata: - name: postgresql-operator-operator-access - namespace: default -spec: - description: "Allow {{name.ln}} operator access to any pod in the target namespace" - endpointSelector: {} - ingress: - - fromEndpoints: - - matchLabels: - io.kubernetes.pod.namespace: postgresql-operator-system - toPorts: - - ports: - - port: "8000" - protocol: TCP -``` - -!!!info Important -The `postgresql-operator-system` namespace is the default namespace for the operator when -using the YAML manifests. If the operator was installed using a different -process (Helm, OLM, etc.), the namespace may be different. Make sure to adjust -the namespace properly. -!!! - -## Allowing access between cluster Pods - -Since the default policy is "deny all", we need to explicitly allow access -between the cluster Pods in the same namespace. We will improve our previous -policy by adding the required ingress rule: - -```yaml -apiVersion: cilium.io/v2 -kind: CiliumNetworkPolicy -metadata: - name: cnp-cluster-internal-access - namespace: default -spec: - description: "Allow {{name.ln}} operator access and connection between pods in the same namespace" - endpointSelector: {} - ingress: - - fromEndpoints: - - matchLabels: - io.kubernetes.pod.namespace: postgresql-operator-system - - matchLabels: - io.kubernetes.pod.namespace: default - k8s.enterprisedb.io/cluster: cluster-example - toPorts: - - ports: - - port: "8000" - protocol: TCP - - port: "5432" - protocol: TCP -``` - -The policy allows access from `postgresql-operator-system` Pods and from `default` namespace -Pods that also belong to `cluster-example`. The `matchLabels` selector requires -Pods to have the complete set of listed labels. Missing even one label means -the Pod will not match. - -## Restricting Access to PostgreSQL with Cilium - -In this example, we define a `CiliumNetworkPolicy` that allows only Pods -labeled `role=backend` in the `default` namespace to connect to a PostgreSQL -cluster named `cluster-example`. All other ingress traffic is blocked by -default. - -```yaml -apiVersion: cilium.io/v2 -kind: CiliumNetworkPolicy -metadata: - name: postgres-access-backend-label - namespace: default -spec: - description: "Allow PostgreSQL access on port 5432 from Pods with role=backend" - endpointSelector: - matchLabels: - k8s.enterprisedb.io/cluster: cluster-example - ingress: - - fromEndpoints: - - matchLabels: - role: backend - toPorts: - - ports: - - port: "5432" - protocol: TCP -``` - -This `CiliumNetworkPolicy` ensures that only Pods labeled with `role=backend` -can access the PostgreSQL instance managed by {{name.ln}} via port 5432 in -the `default` namespace. - -In the following policy, we demonstrate how to allow ingress traffic to port -5432 of a PostgreSQL cluster named `cluster-example`, only from Pods with the -label `role=backend` in any namespace. - -```yaml -apiVersion: cilium.io/v2 -kind: CiliumNetworkPolicy -metadata: - name: postgres-access-backend-any-ns - namespace: default -spec: - description: "Allow PostgreSQL access on port 5432 from Pods with role=backend in any namespace" - endpointSelector: - matchLabels: - k8s.enterprisedb.io/cluster: cluster-example - ingress: - - fromEndpoints: - - labelSelector: - matchLabels: - role: backend - matchExpressions: - - key: io.kubernetes.pod.namespace - operator: Exists - toPorts: - - ports: - - port: "5432" - protocol: TCP -``` - -The following example allows ingress traffic to port 5432 of the -`cluster-example` cluster (located in the `default` namespace) from any Pods in -the `backend` namespace. - -```yaml -apiVersion: cilium.io/v2 -kind: CiliumNetworkPolicy -metadata: - name: postgres-access-backend-namespace - namespace: default -spec: - description: "Allow PostgreSQL access on port 5432 from any Pods in the backend namespace" - endpointSelector: - matchLabels: - k8s.enterprisedb.io/cluster: cluster-example - ingress: - - fromEndpoints: - - matchLabels: - io.kubernetes.pod.namespace: backend - toPorts: - - ports: - - port: "5432" - protocol: TCP -``` - -Using Cilium’s L3/L4 policy model, we define a `CiliumNetworkPolicy` that -explicitly allows ingress traffic to cluster Pods only from application Pods in -the `backend` namespace. All other traffic is implicitly denied unless -explicitly permitted by additional policies. - -The following example allows ingress traffic to port 5432 of the -`cluster-example` cluster (located in the `default` namespace) from any source -within the Kubernetes cluster. - -```yaml -apiVersion: cilium.io/v2 -kind: CiliumNetworkPolicy -metadata: - name: postgres-access-cluster-wide - namespace: default -spec: - description: "Allow ingress traffic to port 5432 of the cluster-example from any pods within the Kubernetes cluster" - endpointSelector: - matchLabels: - k8s.enterprisedb.io/cluster: cluster-example - ingress: - - fromEntities: - - cluster - toPorts: - - ports: - - port: "5432" - protocol: TCP -``` - -You may consider using [editor.networkpolicy.io](https://editor.networkpolicy.io/), -a visual and interactive tool that simplifies the creation and validation of -Cilium Network Policies. It’s especially helpful for avoiding misconfigurations -and understanding traffic rules more clearly by presenting in a visual way. - -With these policies, you've established baseline access controls for -PostgreSQL. You can layer additional egress or audit rules using Cilium's -policy language or extend to L7 enforcement with Envoy. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/cncf-projects/external-secrets.mdx b/product_docs/docs/postgres_for_kubernetes/preview/cncf-projects/external-secrets.mdx deleted file mode 100644 index 4012167c838..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/cncf-projects/external-secrets.mdx +++ /dev/null @@ -1,271 +0,0 @@ ---- -title: 'External Secrets' -originalFilePath: 'src/cncf-projects/external-secrets.md' ---- - -[External Secrets](https://external-secrets.io/latest/) is a CNCF Sandbox -project, accepted in 2022 under the sponsorship of TAG Security. - -## About - -The **External Secrets Operator (ESO)** is a Kubernetes operator that enhances -secret management by decoupling the storage of secrets from Kubernetes itself. -It enables seamless synchronization between external secret management systems -and native Kubernetes `Secret` resources. - -ESO supports a wide range of backends, including: - -- [HashiCorp Vault](https://www.vaultproject.io/) -- [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) -- [Google Secret Manager](https://cloud.google.com/secret-manager) -- [Azure Key Vault](https://azure.microsoft.com/en-us/services/key-vault/) -- [IBM Cloud Secrets Manager](https://www.ibm.com/cloud/secrets-manager) - -…and many more. For a full and up-to-date list of supported providers, refer to -the [official External Secrets documentation](https://external-secrets.io/latest/). - -## Integration with PostgreSQL and {{name.ln}} - -When it comes to PostgreSQL databases, External Secrets integrates seamlessly -with {{name.ln}} in two major use cases: - -- **Automated password management:** ESO can handle the automatic generation - and rotation of database user passwords stored in Kubernetes `Secret` - resources, ensuring that applications running inside the cluster always have - access to up-to-date credentials. - -- **Cross-platform secret access:** It enables transparent synchronization of - those passwords with an external Key Management Service (KMS) via a - `SecretStore` resources. This allows applications and developers outside the - Kubernetes cluster—who may not have access to Kubernetes secrets—to retrieve - the database credentials directly from the external KMS. - -## Example: Automated Password Management with External Secrets - -Let’s walk through how to automatically rotate the password of the `app` user -every 24 hours in the `cluster-example` Postgres cluster from the -[quickstart guide](../quickstart.md#part-3-deploy-a-postgresql-cluster). - -!!!info Important -Before proceeding, ensure that the `cluster-example` Postgres cluster is up -and running in your environment. -!!! - -By default, {{name.ln}} generates and manages a Kubernetes `Secret` named -`cluster-example-app`, which contains the credentials for the `app` user in the -`cluster-example` cluster. You can read more about this in the -[“Connecting from an application” section](../applications.mdx#secrets). - -With External Secrets, the goal is to: - -1. Define a `Password` generator that specifies how to generate the password. -2. Create an `ExternalSecret` resource that keeps the `cluster-example-app` - secret in sync by updating only the `password` and `pgpass` fields. - -### Creating the Password Generator - -The following example creates a -[`Password` generator](https://external-secrets.io/main/api/generator/password/) -resource named `pg-password-generator` in the `default` namespace. You can -customize the name and properties to suit your needs: - -```yaml -apiVersion: generators.external-secrets.io/v1alpha1 -kind: Password -metadata: - name: pg-password-generator -spec: - length: 42 - digits: 5 - symbols: 5 - symbolCharacters: "-_$@" - noUpper: false - allowRepeat: true -``` - -This specification defines the characteristics of the generated password, -including its length and the inclusion of digits, symbols, and uppercase -letters. - -### Creating the External Secret - -The example below creates an `ExternalSecret` resource named -`cluster-example-app-secret`, which refreshes the password every 24 hours. It -uses a `Merge` policy to update only the specified fields (`password`, `pgpass`, -`jdbc-uri` and `uri`) in the `cluster-example-app` secret. - -```yaml -apiVersion: external-secrets.io/v1 -kind: ExternalSecret -metadata: - name: cluster-example-app-secret -spec: - refreshInterval: "24h" - target: - name: cluster-example-app - creationPolicy: Merge - template: - metadata: - labels: - k8s.enterprisedb.io/reload: "true" - data: - password: "{{ .password }}" - pgpass: "cluster-example-rw:5432:app:app:{{ .password }}" - jdbc-uri: "jdbc:postgresql://cluster-example-rw.default:5432/app?password={{ .password }}&user=app" - uri: "postgresql://app:{{ .password }}@cluster-example-rw.default:5432/app" - dataFrom: - - sourceRef: - generatorRef: - apiVersion: generators.external-secrets.io/v1alpha1 - kind: Password - name: pg-password-generator -``` - -The label `k8s.enterprisedb.io/reload: "true"` ensures that {{name.ln}} triggers a reload -of the user password in the database when the secret changes. - -### Verifying the Configuration - -To check that the `ExternalSecret` is correctly synchronizing: - -```sh -kubectl get es cluster-example-app-secret -``` - -To observe the password being refreshed in real time, temporarily reduce the -`refreshInterval` to `30s` and run the following command repeatedly: - -```sh -kubectl get secret cluster-example-app \ - -o jsonpath="{.data.password}" | base64 -d -``` - -You should see the password change every 30 seconds, confirming that the -rotation is working correctly. - -### There's More - -While the example above focuses on the default `cluster-example-app` secret -created by {{name.ln}}, the same approach can be extended to manage any -custom secrets or PostgreSQL users you create to regularly rotate their -password. - -## Example: Integration with an External KMS - -One of the most widely used Key Management Service (KMS) providers in the CNCF -ecosystem is [HashiCorp Vault](https://www.vaultproject.io/). Although Vault is -licensed under the Business Source License (BUSL), a fully compatible and -actively maintained open source alternative is available: [OpenBao](https://openbao.org/). -OpenBao supports all the same interfaces as HashiCorp Vault, making it a true -drop-in replacement. - -In this example, we'll demonstrate how to integrate {{name.ln}}, -External Secrets Operator, and HashiCorp Vault to automatically rotate -a PostgreSQL password and securely store it in Vault. - -!!!info Important -This example assumes that HashiCorp Vault is already installed and properly -configured in your environment, and that your team has the necessary expertise -to operate it. There are various ways to deploy Vault, and detailing them is -outside the scope of {{name.ln}}. While it's possible to run Vault inside -Kubernetes, it is more commonly deployed externally. For detailed instructions, -consult the [HashiCorp Vault documentation](https://www.vaultproject.io/docs). -!!! - -Continuing from the previous example, we will now create the necessary -`SecretStore` and `PushSecret` resources to complete the integration with -Vault. - -### Creating the `SecretStore` - -In this example, we assume that HashiCorp Vault is accessible from within the -namespace at `http://vault.vault.svc:8200`, and that a Kubernetes `Secret` -named `vault-token` exists in the same namespace, containing the token used to -authenticate with Vault. - -```yaml -apiVersion: external-secrets.io/v1 -kind: SecretStore -metadata: - name: vault-backend -spec: - provider: - vault: - server: "http://vault.vault.svc:8200" - path: "secrets" - # Specifies the Vault KV secret engine version ("v1" or "v2"). - # Defaults to "v2" if not set. - version: "v2" - auth: - # References a Kubernetes Secret that contains the Vault token. - # See: https://www.vaultproject.io/docs/auth/token - tokenSecretRef: - name: "vault-token" - key: "token" ---- -apiVersion: v1 -kind: Secret -metadata: - name: vault-token -data: - token: aHZzLioqKioqKio= # hvs.******* -``` - -This configuration creates a `SecretStore` resource named `vault-backend`. - -!!!info Important -This example uses basic token-based authentication, which is suitable for -testing API, and CLI use cases. While it is the default method enabled in -Vault, it is not recommended for production environments. For production, -consider using more secure authentication methods. -Refer to the [External Secrets Operator documentation](https://external-secrets.io/latest/provider/hashicorp-vault/) -for a full list of supported authentication mechanisms. -!!! - -!!!info -HashiCorp Vault must have a KV secrets engine enabled at the `secrets` path -with version `v2`. If your Vault instance uses a different path or -version, be sure to update the `path` and `version` fields accordingly. -!!! - -### Creating the `PushSecret` - -The `PushSecret` resource is used to push a Kubernetes `Secret` to HashiCorp -Vault. In this simplified example, we'll push the credentials for the `app` -user of the sample cluster `cluster-example`. - -For more details on configuring `PushSecret`, refer to the -[External Secrets Operator documentation](https://external-secrets.io/latest/api/pushsecret/). - -```yaml -apiVersion: external-secrets.io/v1alpha1 -kind: PushSecret -metadata: - name: pushsecret-example -spec: - deletionPolicy: Delete - refreshInterval: 24h - secretStoreRefs: - - name: vault-backend - kind: SecretStore - selector: - secret: - name: cluster-example-app - data: - - match: - remoteRef: - remoteKey: cluster-example-app -``` - -In this example, the `PushSecret` resource instructs the External Secrets -Operator to push the Kubernetes `Secret` named `cluster-example-app` to -HashiCorp Vault (from the previous example). The `remoteKey` defines the name -under which the secret will be stored in Vault, using the `SecretStore` named -`vault-backend`. - -### Verifying the Configuration - -To verify that the `PushSecret` is functioning correctly, navigate to the -HashiCorp Vault UI. In the `kv` secrets engine at the path `secrets`, you -should find a secret named `cluster-example-app`, corresponding to the -`remoteKey` defined above. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/cncf-projects/index.mdx b/product_docs/docs/postgres_for_kubernetes/preview/cncf-projects/index.mdx deleted file mode 100644 index b02c028f676..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/cncf-projects/index.mdx +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: CNCF Projects Integrations -indexCards: simple -navigation: -- external-secrets -- cilium ---- diff --git a/product_docs/docs/postgres_for_kubernetes/preview/cnpg_i.mdx b/product_docs/docs/postgres_for_kubernetes/preview/cnpg_i.mdx deleted file mode 100644 index b4b717f4586..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/cnpg_i.mdx +++ /dev/null @@ -1,243 +0,0 @@ ---- -title: 'CNPG-I' -originalFilePath: 'src/cnpg_i.md' ---- - - - -The **CloudNativePG Interface** ([CNPG-I](https://github.com/cloudnative-pg/cnpg-i)) -is a standard way to extend and customize {{name.ln}} without modifying its -core codebase. - -## Why CNPG-I? - -{{name.ln}} supports a wide range of use cases, but sometimes its built-in -functionality isn’t enough, or adding certain features directly to the main -project isn’t practical. - -Before CNPG-I, users had two main options: - -- Fork the project to add custom behavior, or -- Extend the upstream codebase by writing custom components on top of it. - -Both approaches created maintenance overhead, slowed upgrades, and delayed delivery of critical features. - -CNPG-I solves these problems by providing a stable, gRPC-based integration -point for extending {{name.ln}} at key points in a cluster’s lifecycle —such -as backups, recovery, and sub-resource reconciliation— without disrupting the -core project. - -CNPG-I can extend: - -- The operator, and/or -- The instance manager running inside PostgreSQL pods. - -## Registering a plugin - -CNPG-I is inspired by the Kubernetes -[Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/). -The operator communicates with registered plugins using **gRPC**, following the -[CNPG-I protocol](https://github.com/cloudnative-pg/cnpg-i/blob/main/docs/protocol.md). - -You can register plugins in one of two ways: - -- Sidecar container – run the plugin inside the operator’s Deployment -- Standalone Deployment – run the plugin as a separate workload in the same - namespace - -In both cases, the plugin must be packaged as a container image. - -### Sidecar Container - -Sidecar plugins are discovered once at operator startup. - -The plugin must expose its gRPC server via a **Unix -domain socket**. This socket must be placed in a directory shared with the -operator container, mounted at the path set in `PLUGIN_SOCKET_DIR` (default: -`/plugin`). - -Example: - -```yaml -apiVersion: apps/v1 -kind: Deployment -metadata: - name: controller-manager -spec: - template: - spec: - containers: - - image: cloudnative-pg:latest - [...] - name: manager - volumeMounts: - - mountPath: /plugins - name: cnpg-i-plugins - - - image: cnpg-i-plugin-example:latest - name: cnpg-i-plugin-example - volumeMounts: - - mountPath: /plugins - name: cnpg-i-plugins - volumes: - - name: cnpg-i-plugins - emptyDir: {} -``` - -### Standalone Deployment (recommended) - -Running a plugin as its own Deployment decouples its lifecycle from the -operator’s and allows independent scaling. In this setup, the plugin exposes a -TCP gRPC endpoint behind a Service, with **mTLS** for secure communication. -Standalone plugins are discovered dynamically by watching for Services with the -required labels and annotations — no operator restart is needed. - -When a standalone plugin's pods are rolled (for example, after upgrading its -image), the operator detects the change through the EndpointSlices backing the -plugin Service and reconciles every cluster using that plugin, so they start -interacting with the new pods promptly instead of waiting for the periodic -resync. - -Example Deployment: - -```yaml -apiVersion: apps/v1 -kind: Deployment -metadata: - name: cnpg-i-plugin-example -spec: - template: - [...] - spec: - containers: - - name: cnpg-i-plugin-example - image: cnpg-i-plugin-example:latest - ports: - - containerPort: 9090 - protocol: TCP -``` - -The related Service for the plugin must include: - -- The label `k8s.enterprisedb.io/plugin: ` — required for {{name.ln}} to - discover the plugin -- The annotation `k8s.enterprisedb.io/pluginPort: ` — specifies the port where the - plugin’s gRPC server is exposed - -Example Service: - -```yaml -apiVersion: v1 -kind: Service -metadata: - annotations: - k8s.enterprisedb.io/pluginPort: "9090" - labels: - k8s.enterprisedb.io/pluginName: cnpg-i-plugin-example.my-org.io - name: cnpg-i-plugin-example -spec: - ports: - - port: 9090 - protocol: TCP - targetPort: 9090 - selector: - app: cnpg-i-plugin-example -``` - -### Configuring TLS Certificates - -When a plugin runs as a `Deployment`, communication with {{name.ln}} happens -over the network. To secure it, **mTLS is enforced**, requiring TLS -certificates for both sides. - -Certificates must be stored as [Kubernetes TLS Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#tls-secrets) -and referenced in the plugin’s Service annotations -(`k8s.enterprisedb.io/pluginClientSecret` and `k8s.enterprisedb.io/pluginServerSecret`): - -```yaml -apiVersion: v1 -kind: Service -metadata: - annotations: - k8s.enterprisedb.io/pluginClientSecret: cnpg-i-plugin-example-client-tls - k8s.enterprisedb.io/pluginServerSecret: cnpg-i-plugin-example-server-tls - k8s.enterprisedb.io/pluginPort: "9090" - name: barman-cloud - namespace: postgresql-operator-system -spec: - [...] -``` - -!!!note -You can provide your own certificate bundles, but the recommended method is -to use [Cert-manager](https://cert-manager.io). -!!! - -#### Customizing the Certificate DNS Name - -By default, {{name.ln}} uses the Service name as the server name for TLS -verification when connecting to the plugin. If your environment requires the -certificate to have a different DNS name (e.g., `barman-cloud.svc`), you can -customize it using the `k8s.enterprisedb.io/pluginServerName` annotation: - -```yaml -apiVersion: v1 -kind: Service -metadata: - annotations: - k8s.enterprisedb.io/pluginClientSecret: cnpg-i-plugin-example-client-tls - k8s.enterprisedb.io/pluginServerSecret: cnpg-i-plugin-example-server-tls - k8s.enterprisedb.io/pluginPort: "9090" - k8s.enterprisedb.io/pluginServerName: barman-cloud.svc - name: barman-cloud - namespace: postgresql-operator-system -spec: - [...] -``` - -This allows the operator to verify the plugin's certificate against the -specified DNS name instead of the default Service name. The server certificate -must include this DNS name in its Subject Alternative Names (SAN). - -## Using a plugin - -To enable a plugin, configure the `.spec.plugins` section in your `Cluster` -resource. Refer to the {{name.ln}} API Reference for the full -[PluginConfiguration](https://cloudnative-pg.io/docs/devel/cloudnative-pg.v1/#pluginconfiguration) -specification. - -Example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-with-plugins -spec: - instances: 1 - storage: - size: 1Gi - plugins: - - name: cnpg-i-plugin-example.my-org.io - enabled: true - parameters: - key1: value1 - key2: value2 -``` - -Each plugin may have its own parameters—check the plugin’s documentation for -details. The `name` field in `spec.plugins` depends on how the plugin is -deployed: - -- Sidecar container: use the Unix socket file name -- Deployment: use the value from the Service’s `k8s.enterprisedb.io/pluginName` label - -## Community plugins - -The CNPG-I protocol has quickly become a proven and reliable pattern for -extending {{name.ln}} while keeping the core project maintainable. -Over time, the community has built and shared plugins that address real-world -needs and serve as examples for developers. - -For a complete and up-to-date list of plugins built with CNPG-I, please refer to the -[CNPG-I GitHub page](https://github.com/cloudnative-pg/cnpg-i?tab=readme-ov-file#projects-built-with-cnpg-i). diff --git a/product_docs/docs/postgres_for_kubernetes/preview/connection_pooling.mdx b/product_docs/docs/postgres_for_kubernetes/preview/connection_pooling.mdx deleted file mode 100644 index 5f34f7a8db9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/connection_pooling.mdx +++ /dev/null @@ -1,930 +0,0 @@ ---- -title: 'Connection Pooling' -originalFilePath: 'src/connection_pooling.md' ---- - - - -{{name.ln}} provides native support for connection pooling with -[PgBouncer](https://www.pgbouncer.org/), one of the most popular open source -connection poolers for PostgreSQL, through the `Pooler` custom resource definition (CRD). - -In brief, a pooler in {{name.ln}} is a deployment of PgBouncer pods that sits -between your applications and a PostgreSQL service, for example, the `rw` -service. It creates a separate, scalable, configurable, and highly available -database access layer. - -!!!warning -{{name.ln}} requires the `auth_dbname` feature in PgBouncer. -Make sure to use a PgBouncer container image version **1.19 or higher**. -!!! - -## Architecture - -The following diagram highlights how introducing a database access layer based -on PgBouncer changes the architecture of {{name.ln}}. Instead of directly -connecting to the PostgreSQL primary service, applications can connect to the -equivalent service for PgBouncer. This ability enables reuse of existing -connections for faster performance and better resource management on the -PostgreSQL side. - -![Applications writing to the single primary via PgBouncer](./images/pgbouncer-architecture-rw.png) - -## Quick start - -This example helps to show how {{name.ln}} implements a PgBouncer -pooler: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-example-rw -spec: - cluster: - name: cluster-example - - instances: 3 - type: rw - pgbouncer: - poolMode: session - parameters: - max_client_conn: "1000" - default_pool_size: "10" -``` - -!!!info Important -The pooler name can't be the same as any cluster name in the same namespace. -!!! - -!!!warning - -The `spec.cluster` field is immutable after creation. To point a pooler at -a different `Cluster`, create a new `Pooler` resource instead of updating -an existing one. -!!! - -This example creates a `Pooler` resource called `pooler-example-rw` -that's strictly associated with the Postgres `Cluster` resource called -`cluster-example`. It points to the primary, identified by the read/write -service (`rw`, therefore `cluster-example-rw`). - -The `Pooler` resource must live in the same namespace as the Postgres cluster. -It consists of a Kubernetes deployment of 3 pods running the -[latest stable image of PgBouncer](https://docker.enterprisedb.com/k8s/pgbouncer), -configured with the [`session` pooling mode](https://www.pgbouncer.org/config.html#pool-mode) -and accepting up to 1000 connections each. The default pool size is 10 -user/database pairs toward PostgreSQL. - -!!!info Important -The `Pooler` resource sets only the `*` fallback database in PgBouncer. This setting means that -that all parameters in the connection strings passed from the client are -relayed to the PostgreSQL server. For details, see ["Section \[databases\]" -in the PgBouncer documentation](https://www.pgbouncer.org/config.html#section-databases). -!!! - -{{name.ln}} also creates a secret with the same name as the pooler containing -the configuration files used with PgBouncer. - -!!!note API reference -For details, see [`PgBouncerSpec`](pg4k.v1.md#pgbouncerspec) -in the API reference. -!!! - -## Pooler resource lifecycle - -`Pooler` resources are not managed automatically by the operator. You create -them manually when needed, and you can deploy multiple poolers for the same -PostgreSQL cluster. - -The key point to understand is that the lifecycles of the `Cluster` and -`Pooler` resources are independent. Deleting a cluster does not automatically -remove its poolers, and deleting a pooler does not affect the cluster. - -!!!info -Once you are familiar with how poolers work, you have complete flexibility -in designing your architecture. You can run clusters without poolers, clusters -with a single pooler, or clusters with multiple poolers (for example, one per -application). -!!! - -!!!info Important -When the operator itself is upgraded, pooler pods will also undergo a -rolling upgrade. This ensures that the instance manager inside the pooler -pods is upgraded consistently. -!!! - -## Security - -Any PgBouncer pooler is transparently integrated with {{name.ln}} support for -in-transit encryption by way of TLS connections, both on the client -(application) and server (PostgreSQL) side of the pool. - -Containers run as the `pgbouncer` system user, and access to the `pgbouncer` -administration database is allowed only by way of local connections, through -peer authentication. - -### Certificates - -By default, a PgBouncer pooler reuses the same certificates as the PostgreSQL -cluster. It relies on TLS client certificate authentication to connect to the -PostgreSQL server and run the `auth_query` used for client password -authentication (see ["Authentication"](#authentication)). - -Supplying your own secrets disables the built-in integration. From that point, -you gain complete control (and responsibility) for managing authentication. -Supported secret formats are: - -1. Basic Auth -2. TLS -3. Opaque - -For Opaque secrets, the `Pooler` resource expects the following keys: - -- `tls.crt` -- `tls.key` - -In practice, this means you can treat an Opaque secret as a TLS secret, -starting from the same structure. - -## Authentication - -### Default authentication method - -By default, {{name.ln}} natively supports password-based authentication for -PgBouncer clients connecting to the PostgreSQL database. - -This built-in mechanism leverages PgBouncer’s `auth_dbname` (introduced in -version 1.19), together with the `auth_user` and `auth_query` options. - -!!!info Important -If you provide your own certificate secrets, the built-in integration is -disabled. In that case, you are fully responsible for configuring and -managing PgBouncer authentication. -!!! - -The built-in integration performs the following tasks: - -- Creates a dedicated user called `cnp_pooler_pgbouncer` in the PostgreSQL - server -- Creates the lookup function in the `postgres` database and grants execution - privileges to `cnp_pooler_pgbouncer` (following PoLA principles) -- Issues a TLS certificate for this user -- Configures PgBouncer to use `cnp_pooler_pgbouncer` as the `auth_user` and - `postgres` as the `auth_dbname` -- Configures PgBouncer to authenticate `cnp_pooler_pgbouncer` against - PostgreSQL using the issued TLS certificate -- Cleans up all of the above automatically when no poolers are associated with - the cluster - -#### SQL instructions - -As part of the built-in integration, {{name.ln}} automatically executes a set -of SQL statements during reconciliation. These statements are run by the -instance manager using the `postgres` user against the `postgres` database. - -Role creation: - -```sql -CREATE ROLE cnp_pooler_pgbouncer WITH LOGIN; -``` - -Grant access to the `postgres` database: - -```sql -GRANT CONNECT ON DATABASE postgres TO cnp_pooler_pgbouncer; -``` - -Create the lookup function for password verification. This function is created -in the `postgres` database with `SECURITY DEFINER` privileges and is used by -PgBouncer’s `auth_query` option. Because it runs as the function owner, its -`search_path` is pinned to `pg_catalog, pg_temp` so that the function body -cannot resolve operators or objects through a caller- or -tenant-controlled `search_path`: - -```sql -CREATE OR REPLACE FUNCTION public.user_search(uname TEXT) - RETURNS TABLE (usename name, passwd text) - LANGUAGE sql SECURITY DEFINER - SET search_path = pg_catalog, pg_temp AS - 'SELECT usename, passwd FROM pg_catalog.pg_shadow WHERE usename=$1;'; -``` - -!!!note - -Clusters created with an earlier version of {{name.ln}} carry a -`user_search` function without the pinned `search_path`. The operator -recreates the function with the `SET search_path` clause automatically -during reconciliation when the cluster is upgraded. -!!! - -Restrict and grant permissions on the lookup function: - -```sql -REVOKE ALL ON FUNCTION public.user_search(text) - FROM public; - -GRANT EXECUTE ON FUNCTION public.user_search(text) - TO cnp_pooler_pgbouncer; -``` - -### Custom authentication method - -Providing your own certificate secrets disables the built-in integration. - -This gives you the flexibility — and responsibility — to manage the -authentication process yourself. You can follow the instructions above to -replicate similar behavior to the default setup. - -## Pod templates - -The `Pooler` resource allows you to customize the underlying pods via the -`template` section. This provides full access to the Kubernetes `PodSpec` for -advanced configurations like scheduling constraints, custom security contexts, -or resource overrides. - -For a complete list of supported fields, see the -[`PoolerSpec`](pg4k.v1.md#poolerspec) API reference. - -### Key requirements - -- **The `pgbouncer` container name:** When overriding container settings (like - images or resources), the name of the container **must** be set to - `pgbouncer`. The operator looks for this specific name to manage the - PgBouncer process. - -- **Mandatory `containers` field:** Since `template` follows the standard - Kubernetes `PodSpec` schema, the `containers` field is mandatory. - -- If you aren't modifying container-level settings, you must set it to an empty - array: `containers: []`. - -- If the `containers` field is missing, the API server will throw a - `ValidationError`. - -### Examples - -#### High availability with pod anti-affinity - -This configuration uses `podAntiAffinity` to ensure that PgBouncer pods are -distributed across different nodes, preventing a single node failure from -taking down the entire pool. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-example-rw -spec: - cluster: - name: cluster-example - instances: 3 - type: rw - - template: - metadata: - labels: - app: pooler - spec: - containers: [] - affinity: - podAntiAffinity: - requiredDuringSchedulingIgnoredDuringExecution: - - labelSelector: - matchExpressions: - - key: app - operator: In - values: - - pooler - topologyKey: "kubernetes.io/hostname" -``` - -#### Resource limits - -You can define resource requests and limits by adding a container named -`pgbouncer` to the `template` section: - -```yaml -# ... - template: - metadata: - # ... - spec: - containers: - # This name MUST be "pgbouncer" - - name: pgbouncer - resources: - requests: - cpu: "0.1" - memory: 100Mi - limits: - cpu: "0.5" - memory: 500Mi -``` - -## PgBouncer image - -By default, {{name.ln}} deploys the -[latest stable PgBouncer image](https://docker.enterprisedb.com/k8s/pgbouncer) -the operator was built against. You can override that default in three ways. -When more than one is set, the sources are evaluated top-down — the first -match in the list below is used; if none match, the operator's built-in -default applies: - -1. An explicit image set on the `pgbouncer` container inside - `spec.template.spec.containers` (escape hatch — see - [Pod-template override](#pod-template-override) below). -2. `spec.pgbouncer.image` — an image reference set directly on the `Pooler`. -3. `spec.pgbouncer.imageCatalogRef` — a reference to an entry in an - `ImageCatalog` or `ClusterImageCatalog`. - -`spec.pgbouncer.image` and `spec.pgbouncer.imageCatalogRef` are mutually -exclusive — set at most one. - -!!!warning Policy gating - -If you enforce admission policies that restrict which PgBouncer images -may run, those policies **must gate all three** image sources: -`spec.pgbouncer.image`, `spec.pgbouncer.imageCatalogRef`, and the -`image` field on a `pgbouncer` container inside -`spec.template.spec.containers`. A policy that covers only the first -two leaves the pod-template override as an unguarded escape hatch. -The same consideration applies to `Cluster.spec.imageName` and -`Cluster.spec.imageCatalogRef`. -!!! - -### Setting an explicit image - -Use `spec.pgbouncer.image` to pin a specific PgBouncer version or pull from -a private registry: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-example-rw -spec: - cluster: - name: cluster-example - instances: 3 - type: rw - pgbouncer: - poolMode: session - image: docker.enterprisedb.com/k8s/pgbouncer:1.25.1-ubi9 -``` - -### Using an image catalog - -The `Pooler` resource can manage the PgBouncer container image centrally via -an `ImageCatalog` or `ClusterImageCatalog`, following the same pattern as -`Cluster` resources (see [Image Catalog](image_catalog.md)). The catalog -entry is selected by the `key` defined in the catalog's `componentImages` -list. - -Reference a catalog entry with `spec.pgbouncer.imageCatalogRef`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-example-rw -spec: - cluster: - name: cluster-example - instances: 3 - type: rw - pgbouncer: - poolMode: session - imageCatalogRef: - apiGroup: postgresql.k8s.enterprisedb.io - kind: ImageCatalog - name: my-catalog - key: pgbouncer -``` - -To use a cluster-wide catalog instead, set `kind: ClusterImageCatalog` and -point `name` at the corresponding resource — the rest of the spec is -identical. - -When a catalog entry is updated, the operator automatically reconciles all -poolers referencing it and rolls out the new image without any change to the -`Pooler` spec. - -### Pod-template override - -The pod template can also carry an `image` on the `pgbouncer` container, in -which case it overrides every other source (including `spec.pgbouncer.image` -and `spec.pgbouncer.imageCatalogRef`). Treat this as an **escape hatch** — -use it only when you need to customize other container-level settings -(resources, environment, security context) and happen to want to pin the -image in the same place. For routine image changes, prefer -`spec.pgbouncer.image` or an image catalog: those fields are validated, -mutually exclusive, and visible to admission policies that gate the -PgBouncer image (see [Pod templates](#pod-templates) for the broader -template mechanics): - -```yaml -# ... - template: - spec: - containers: - - name: pgbouncer - image: my-pgbouncer:latest -``` - -### Monitoring the resolved image - -The operator stores the resolved image in `status.image` and reflects the -outcome in `status.phase`, one of `active`, `paused`, `inactive`, or -`failed`. On `failed`, `status.phaseReason` describes the cause (for -example, if the catalog or key does not exist). You can inspect the -current state with: - -```shell -kubectl get pooler pooler-example-rw -o jsonpath='{.status.image}' -``` - -!!!note API reference - -For details, see [`PgBouncerSpec`](pg4k.v1.md#pgbouncerspec) -in the API reference. -!!! - -## Service Template - -Sometimes, your pooler will require some different labels, annotations, or -even a different Service type. You can achieve that by using the -`serviceTemplate` field: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-example-rw -spec: - cluster: - name: cluster-example - instances: 3 - type: rw - serviceTemplate: - metadata: - labels: - app: pooler - spec: - type: LoadBalancer - pgbouncer: - poolMode: session - parameters: - max_client_conn: "1000" - default_pool_size: "10" -``` - -The operator by default adds a `ServicePort` with the following data: - -``` - ports: - - name: pgbouncer - port: 5432 - protocol: TCP - targetPort: pgbouncer -``` - -!!!warning -Specifying a `ServicePort` with the name `pgbouncer` or the port `5432` will prevent the default `ServicePort` from being added. -This because `ServicePort` entries with the same `name` or `port` are not allowed on Kubernetes and result in errors. -!!! - -## High availability (HA) - -Because of Kubernetes' deployments, you can configure your pooler to run on a -single instance or over multiple pods. The exposed service makes sure that your -clients are randomly distributed over the available pods running PgBouncer, -which then manages and reuses connections toward the underlying server (if -using the `rw` service) or servers (if using the `ro` service with multiple -replicas). - -!!!warning -If your infrastructure spans multiple availability zones with high latency -across them, be aware of network hops. Consider, for example, the case of your -application running in zone 2, connecting to PgBouncer running in zone 3, and -pointing to the PostgreSQL primary in zone 1. -!!! - -## PgBouncer configuration options - -The operator manages most of the [configuration options for PgBouncer](https://www.pgbouncer.org/config.html), -allowing you to modify only a subset of them. - -!!!warning - -The operator passes these settings directly to PgBouncer without validation. -To prevent configuration errors or crash loops, ensure each parameter is -supported by your specific PgBouncer image version. -!!! - -These are the PgBouncer options you can customize, with links to the PgBouncer -documentation for each parameter. Unless stated otherwise, the default values -are the ones directly set by PgBouncer. - -- [`auth_type`](https://www.pgbouncer.org/config.html#auth_type) -- [`application_name_add_host`](https://www.pgbouncer.org/config.html#application_name_add_host) -- [`autodb_idle_timeout`](https://www.pgbouncer.org/config.html#autodb_idle_timeout) -- [`cancel_wait_timeout`](https://www.pgbouncer.org/config.html#cancel_wait_timeout) -- [`client_idle_timeout`](https://www.pgbouncer.org/config.html#client_idle_timeout) -- [`client_login_timeout`](https://www.pgbouncer.org/config.html#client_login_timeout) -- [`client_tls_ciphers`](https://www.pgbouncer.org/config.html#client_tls_ciphers) -- [`client_tls_sslmode`](https://www.pgbouncer.org/config.html#client_tls_sslmode) -- [`client_tls13_ciphers`](https://www.pgbouncer.org/config.html#client_tls13_ciphers) (1.25+) -- [`default_pool_size`](https://www.pgbouncer.org/config.html#default_pool_size) -- [`disable_pqexec`](https://www.pgbouncer.org/config.html#disable_pqexec) -- [`dns_max_ttl`](https://www.pgbouncer.org/config.html#dns_max_ttl) -- [`dns_nxdomain_ttl`](https://www.pgbouncer.org/config.html#dns_nxdomain_ttl) -- [`idle_transaction_timeout`](https://www.pgbouncer.org/config.html#idle_transaction_timeout) -- [`ignore_startup_parameters`](https://www.pgbouncer.org/config.html#ignore_startup_parameters): - to be appended to `extra_float_digits,options` - required by {{name.ln}} -- [`listen_backlog`](https://www.pgbouncer.org/config.html#listen_backlog) -- [`log_connections`](https://www.pgbouncer.org/config.html#log_connections) -- [`log_disconnections`](https://www.pgbouncer.org/config.html#log_disconnections) -- [`log_pooler_errors`](https://www.pgbouncer.org/config.html#log_pooler_errors) -- [`log_stats`](https://www.pgbouncer.org/config.html#log_stats): by default - disabled (`0`), given that statistics are already collected by the Prometheus - export as described in the ["Monitoring"](#monitoring) section below -- [`max_client_conn`](https://www.pgbouncer.org/config.html#max_client_conn) -- [`max_db_connections`](https://www.pgbouncer.org/config.html#max_db_connections) -- [`max_packet_size`](https://www.pgbouncer.org/config.html#max_packet_size) -- [`max_prepared_statements`](https://www.pgbouncer.org/config.html#max_prepared_statements) -- [`max_user_connections`](https://www.pgbouncer.org/config.html#max_user_connections) -- [`min_pool_size`](https://www.pgbouncer.org/config.html#min_pool_size) -- [`pkt_buf`](https://www.pgbouncer.org/config.html#pkt_buf) -- [`query_timeout`](https://www.pgbouncer.org/config.html#query_timeout) -- [`query_wait_timeout`](https://www.pgbouncer.org/config.html#query_wait_timeout) -- [`reserve_pool_size`](https://www.pgbouncer.org/config.html#reserve_pool_size) -- [`reserve_pool_timeout`](https://www.pgbouncer.org/config.html#reserve_pool_timeout) -- [`sbuf_loopcnt`](https://www.pgbouncer.org/config.html#sbuf_loopcnt) -- [`server_check_delay`](https://www.pgbouncer.org/config.html#server_check_delay) -- [`server_check_query`](https://www.pgbouncer.org/config.html#server_check_query) -- [`server_connect_timeout`](https://www.pgbouncer.org/config.html#server_connect_timeout) -- [`server_fast_close`](https://www.pgbouncer.org/config.html#server_fast_close) -- [`server_idle_timeout`](https://www.pgbouncer.org/config.html#server_idle_timeout) -- [`server_lifetime`](https://www.pgbouncer.org/config.html#server_lifetime) -- [`server_login_retry`](https://www.pgbouncer.org/config.html#server_login_retry) -- [`server_reset_query`](https://www.pgbouncer.org/config.html#server_reset_query) -- [`server_reset_query_always`](https://www.pgbouncer.org/config.html#server_reset_query_always) -- [`server_round_robin`](https://www.pgbouncer.org/config.html#server_round_robin) -- [`server_tls_ciphers`](https://www.pgbouncer.org/config.html#server_tls_ciphers) -- [`server_tls13_ciphers`](https://www.pgbouncer.org/config.html#server_tls13_ciphers) (1.25+) -- [`server_tls_protocols`](https://www.pgbouncer.org/config.html#server_tls_protocols) -- [`server_tls_sslmode`](https://www.pgbouncer.org/config.html#server_tls_sslmode) -- [`stats_period`](https://www.pgbouncer.org/config.html#stats_period) -- [`suspend_timeout`](https://www.pgbouncer.org/config.html#suspend_timeout) -- [`tcp_defer_accept`](https://www.pgbouncer.org/config.html#tcp_defer_accept) -- [`tcp_keepalive`](https://www.pgbouncer.org/config.html#tcp_keepalive) -- [`tcp_keepcnt`](https://www.pgbouncer.org/config.html#tcp_keepcnt) -- [`tcp_keepidle`](https://www.pgbouncer.org/config.html#tcp_keepidle) -- [`tcp_keepintvl`](https://www.pgbouncer.org/config.html#tcp_keepintvl) -- [`tcp_user_timeout`](https://www.pgbouncer.org/config.html#tcp_user_timeout) -- [`tcp_socket_buffer`](https://www.pgbouncer.org/config.html#tcp_socket_buffer) -- [`track_extra_parameters`](https://www.pgbouncer.org/config.html#track_extra_parameters) -- [`verbose`](https://www.pgbouncer.org/config.html#verbose) - -Customizations of the PgBouncer configuration are written declaratively in the -`.spec.pgbouncer.parameters` map. - -The operator reacts to the changes in the pooler specification, and every -PgBouncer instance reloads the updated configuration without disrupting the -service. - -!!!warning -Every PgBouncer pod has the same configuration, aligned -with the parameters in the specification. A mistake in these -parameters might disrupt the operability of the whole pooler. -The operator doesn't validate the value of any option. -!!! - -## Monitoring - -The PgBouncer implementation of the `Pooler` comes with a default -Prometheus exporter. It makes available several -metrics having the `cnp_pgbouncer_` prefix by running: - -- `SHOW LISTS` (prefix: `cnp_pgbouncer_lists`) -- `SHOW POOLS` (prefix: `cnp_pgbouncer_pools`) -- `SHOW STATS` (prefix: `cnp_pgbouncer_stats`) - -Like the {{name.ln}} instance, the exporter runs on port -`9127` of each pod running PgBouncer and also provides metrics related to the -Go runtime (with the prefix `go_*`). - -!!!info -You can inspect the exported metrics on a pod running PgBouncer. For instructions, see -[How to inspect the exported metrics](monitoring.md#how-to-inspect-the-exported-metrics). -Make sure that you use the correct IP and the `9127` port. -!!! - -This example shows the output for `cnp_pgbouncer` metrics: - -```text -# HELP cnp_pgbouncer_collection_duration_seconds Collection time duration in seconds -# TYPE cnp_pgbouncer_collection_duration_seconds gauge -cnp_pgbouncer_collection_duration_seconds{collector="Collect.up"} 0.002338805 -# HELP cnp_pgbouncer_collection_errors_total Total errors occurred accessing PostgreSQL for metrics. -# TYPE cnp_pgbouncer_collection_errors_total counter -cnp_pgbouncer_collection_errors_total{collector="sql: Scan error on column index 16, name \"load_balance_hosts\": converting NULL to int is unsupported"} 5 -# HELP cnp_pgbouncer_collections_total Total number of times PostgreSQL was accessed for metrics. -# TYPE cnp_pgbouncer_collections_total counter -cnp_pgbouncer_collections_total 5 -# HELP cnp_pgbouncer_last_collection_error 1 if the last collection ended with error, 0 otherwise. -# TYPE cnp_pgbouncer_last_collection_error gauge -cnp_pgbouncer_last_collection_error 0 -# HELP cnp_pgbouncer_lists_databases Count of databases. -# TYPE cnp_pgbouncer_lists_databases gauge -cnp_pgbouncer_lists_databases 1 -# HELP cnp_pgbouncer_lists_dns_names Count of DNS names in the cache. -# TYPE cnp_pgbouncer_lists_dns_names gauge -cnp_pgbouncer_lists_dns_names 0 -# HELP cnp_pgbouncer_lists_dns_pending Not used. -# TYPE cnp_pgbouncer_lists_dns_pending gauge -cnp_pgbouncer_lists_dns_pending 0 -# HELP cnp_pgbouncer_lists_dns_queries Count of in-flight DNS queries. -# TYPE cnp_pgbouncer_lists_dns_queries gauge -cnp_pgbouncer_lists_dns_queries 0 -# HELP cnp_pgbouncer_lists_dns_zones Count of DNS zones in the cache. -# TYPE cnp_pgbouncer_lists_dns_zones gauge -cnp_pgbouncer_lists_dns_zones 0 -# HELP cnp_pgbouncer_lists_free_clients Count of free clients. -# TYPE cnp_pgbouncer_lists_free_clients gauge -cnp_pgbouncer_lists_free_clients 49 -# HELP cnp_pgbouncer_lists_free_servers Count of free servers. -# TYPE cnp_pgbouncer_lists_free_servers gauge -cnp_pgbouncer_lists_free_servers 0 -# HELP cnp_pgbouncer_lists_login_clients Count of clients in login state. -# TYPE cnp_pgbouncer_lists_login_clients gauge -cnp_pgbouncer_lists_login_clients 0 -# HELP cnp_pgbouncer_lists_pools Count of pools. -# TYPE cnp_pgbouncer_lists_pools gauge -cnp_pgbouncer_lists_pools 1 -# HELP cnp_pgbouncer_lists_used_clients Count of used clients. -# TYPE cnp_pgbouncer_lists_used_clients gauge -cnp_pgbouncer_lists_used_clients 1 -# HELP cnp_pgbouncer_lists_used_servers Count of used servers. -# TYPE cnp_pgbouncer_lists_used_servers gauge -cnp_pgbouncer_lists_used_servers 0 -# HELP cnp_pgbouncer_lists_users Count of users. -# TYPE cnp_pgbouncer_lists_users gauge -cnp_pgbouncer_lists_users 2 -# HELP cnp_pgbouncer_pools_cl_active Client connections that are linked to server connection and can process queries. -# TYPE cnp_pgbouncer_pools_cl_active gauge -cnp_pgbouncer_pools_cl_active{database="pgbouncer",user="pgbouncer"} 1 -# HELP cnp_pgbouncer_pools_cl_active_cancel_req Client connections that have forwarded query cancellations to the server and are waiting for the server response. -# TYPE cnp_pgbouncer_pools_cl_active_cancel_req gauge -cnp_pgbouncer_pools_cl_active_cancel_req{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_cl_cancel_req Client connections that have not forwarded query cancellations to the server yet. -# TYPE cnp_pgbouncer_pools_cl_cancel_req gauge -cnp_pgbouncer_pools_cl_cancel_req{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_cl_waiting Client connections that have sent queries but have not yet got a server connection. -# TYPE cnp_pgbouncer_pools_cl_waiting gauge -cnp_pgbouncer_pools_cl_waiting{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_cl_waiting_cancel_req Client connections that have not forwarded query cancellations to the server yet. -# TYPE cnp_pgbouncer_pools_cl_waiting_cancel_req gauge -cnp_pgbouncer_pools_cl_waiting_cancel_req{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_load_balance_hosts Number of hosts not load balancing between hosts -# TYPE cnp_pgbouncer_pools_load_balance_hosts gauge -cnp_pgbouncer_pools_load_balance_hosts{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_maxwait How long the first (oldest) client in the queue has waited, in seconds. If this starts increasing, then the current pool of servers does not handle requests quickly enough. The reason may be either an overloaded server or just too small of a pool_size setting. -# TYPE cnp_pgbouncer_pools_maxwait gauge -cnp_pgbouncer_pools_maxwait{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_maxwait_us Microsecond part of the maximum waiting time. -# TYPE cnp_pgbouncer_pools_maxwait_us gauge -cnp_pgbouncer_pools_maxwait_us{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_pool_mode The pooling mode in use. 1 for session, 2 for transaction, 3 for statement, -1 if unknown -# TYPE cnp_pgbouncer_pools_pool_mode gauge -cnp_pgbouncer_pools_pool_mode{database="pgbouncer",user="pgbouncer"} 3 -# HELP cnp_pgbouncer_pools_sv_active Server connections that are linked to a client. -# TYPE cnp_pgbouncer_pools_sv_active gauge -cnp_pgbouncer_pools_sv_active{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_sv_active_cancel Server connections that are currently forwarding a cancel request -# TYPE cnp_pgbouncer_pools_sv_active_cancel gauge -cnp_pgbouncer_pools_sv_active_cancel{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_sv_idle Server connections that are unused and immediately usable for client queries. -# TYPE cnp_pgbouncer_pools_sv_idle gauge -cnp_pgbouncer_pools_sv_idle{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_sv_login Server connections currently in the process of logging in. -# TYPE cnp_pgbouncer_pools_sv_login gauge -cnp_pgbouncer_pools_sv_login{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_sv_tested Server connections that are currently running either server_reset_query or server_check_query. -# TYPE cnp_pgbouncer_pools_sv_tested gauge -cnp_pgbouncer_pools_sv_tested{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_sv_used Server connections that have been idle for more than server_check_delay, so they need server_check_query to run on them before they can be used again. -# TYPE cnp_pgbouncer_pools_sv_used gauge -cnp_pgbouncer_pools_sv_used{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_pools_sv_wait_cancels Servers that normally could become idle, but are waiting to do so until all in-flight cancel requests have completed that were sent to cancel a query on this server. -# TYPE cnp_pgbouncer_pools_sv_wait_cancels gauge -cnp_pgbouncer_pools_sv_wait_cancels{database="pgbouncer",user="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_bind_count Average number of prepared statements readied for execution by clients and forwarded to PostgreSQL by pgbouncer. -# TYPE cnp_pgbouncer_stats_avg_bind_count gauge -cnp_pgbouncer_stats_avg_bind_count{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_client_parse_count Average number of prepared statements created by clients. -# TYPE cnp_pgbouncer_stats_avg_client_parse_count gauge -cnp_pgbouncer_stats_avg_client_parse_count{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_query_count Average queries per second in last stat period. -# TYPE cnp_pgbouncer_stats_avg_query_count gauge -cnp_pgbouncer_stats_avg_query_count{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_query_time Average query duration, in microseconds. -# TYPE cnp_pgbouncer_stats_avg_query_time gauge -cnp_pgbouncer_stats_avg_query_time{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_recv Average received (from clients) bytes per second. -# TYPE cnp_pgbouncer_stats_avg_recv gauge -cnp_pgbouncer_stats_avg_recv{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_sent Average sent (to clients) bytes per second. -# TYPE cnp_pgbouncer_stats_avg_sent gauge -cnp_pgbouncer_stats_avg_sent{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_server_parse_count Average number of prepared statements created by pgbouncer on a server. -# TYPE cnp_pgbouncer_stats_avg_server_parse_count gauge -cnp_pgbouncer_stats_avg_server_parse_count{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_wait_time Time spent by clients waiting for a server, in microseconds (average per second). -# TYPE cnp_pgbouncer_stats_avg_wait_time gauge -cnp_pgbouncer_stats_avg_wait_time{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_xact_count Average transactions per second in last stat period. -# TYPE cnp_pgbouncer_stats_avg_xact_count gauge -cnp_pgbouncer_stats_avg_xact_count{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_avg_xact_time Average transaction duration, in microseconds. -# TYPE cnp_pgbouncer_stats_avg_xact_time gauge -cnp_pgbouncer_stats_avg_xact_time{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_total_bind_count Total number of prepared statements readied for execution by clients and forwarded to PostgreSQL by pgbouncer -# TYPE cnp_pgbouncer_stats_total_bind_count gauge -cnp_pgbouncer_stats_total_bind_count{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_total_client_parse_count Total number of prepared statements created by clients. -# TYPE cnp_pgbouncer_stats_total_client_parse_count gauge -cnp_pgbouncer_stats_total_client_parse_count{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_total_query_count Total number of SQL queries pooled by pgbouncer. -# TYPE cnp_pgbouncer_stats_total_query_count gauge -cnp_pgbouncer_stats_total_query_count{database="pgbouncer"} 15 -# HELP cnp_pgbouncer_stats_total_query_time Total number of microseconds spent by pgbouncer when actively connected to PostgreSQL, executing queries. -# TYPE cnp_pgbouncer_stats_total_query_time gauge -cnp_pgbouncer_stats_total_query_time{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_total_received Total volume in bytes of network traffic received by pgbouncer. -# TYPE cnp_pgbouncer_stats_total_received gauge -cnp_pgbouncer_stats_total_received{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_total_sent Total volume in bytes of network traffic sent by pgbouncer. -# TYPE cnp_pgbouncer_stats_total_sent gauge -cnp_pgbouncer_stats_total_sent{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_total_server_parse_count Total number of prepared statements created by pgbouncer on a server. -# TYPE cnp_pgbouncer_stats_total_server_parse_count gauge -cnp_pgbouncer_stats_total_server_parse_count{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_total_wait_time Time spent by clients waiting for a server, in microseconds. -# TYPE cnp_pgbouncer_stats_total_wait_time gauge -cnp_pgbouncer_stats_total_wait_time{database="pgbouncer"} 0 -# HELP cnp_pgbouncer_stats_total_xact_count Total number of SQL transactions pooled by pgbouncer. -# TYPE cnp_pgbouncer_stats_total_xact_count gauge -cnp_pgbouncer_stats_total_xact_count{database="pgbouncer"} 15 -# HELP cnp_pgbouncer_stats_total_xact_time Total number of microseconds spent by pgbouncer when connected to PostgreSQL in a transaction, either idle in transaction or executing queries. -# TYPE cnp_pgbouncer_stats_total_xact_time gauge -cnp_pgbouncer_stats_total_xact_time{database="pgbouncer"} 0 -``` - -!!!info -For a better understanding of the metrics please refer to the PgBouncer documentation. -!!! - -As for clusters, a specific pooler can be monitored using the -[Prometheus operator's](https://github.com/prometheus-operator/prometheus-operator) -[`PodMonitor` resource](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api-reference/api.md#monitoring.coreos.com/v1.PodMonitor). - -You can deploy a `PodMonitor` for a specific pooler using the following basic example, and change it as needed: - -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: PodMonitor -metadata: - name: -spec: - selector: - matchLabels: - k8s.enterprisedb.io/poolerName: - podMetricsEndpoints: - - port: metrics -``` - -### TLS for the Metrics Endpoint - -Set `.spec.monitoring.tls.enabled: true` to serve the metrics endpoint over -HTTPS. By default, the cluster's server certificate is being used. -The certificate is reloaded on every TLS handshake, so rotations are -picked up without restarting the pod. - -```yaml -spec: - monitoring: - tls: - enabled: true -``` - -When `.spec.pgbouncer.clientTLSSecret` is set, the metrics server presents -that certificate instead. - -```yaml -spec: - pgbouncer: - clientTLSSecret: - name: - monitoring: - tls: - enabled: true -``` - -The generated `PodMonitor` scrapes with `insecureSkipVerify=true` because -Prometheus scrapes pods by IP and the certificate's SANs do not generally -cover the pod IP. - -If you need strict verification, set `.spec.monitoring.enablePodMonitor: false` -and manage the `PodMonitor` yourself: the operator-generated one is hardcoded -to `insecureSkipVerify=true` and overwrites its spec on every reconcile, so a -manual patch on the generated `PodMonitor` would not survive. - -### Deprecation of Automatic `PodMonitor` Creation - -!!!warning Feature Deprecation Notice -The `.spec.monitoring.enablePodMonitor` field in the `Pooler` resource is -now deprecated and will be removed in a future version of the operator. -!!! - -If you are currently using this feature, we strongly recommend you either -remove or set `.spec.monitoring.enablePodMonitor` to `false` and manually -create a `PodMonitor` resource for your pooler as described above. -This change ensures that you have complete ownership of your monitoring -configuration, preventing it from being managed or overwritten by the operator. - -## Logging - -Logs are directly sent to standard output, in JSON format, like in the -following example: - -```json -{ - "level": "info", - "ts": SECONDS.MICROSECONDS, - "msg": "record", - "pipe": "stderr", - "record": { - "timestamp": "YYYY-MM-DD HH:MM:SS.MS UTC", - "pid": "", - "level": "LOG", - "msg": "kernel file descriptor limit: 1048576 (hard: 1048576); max_client_conn: 100, max expected fd use: 112" - } -} -``` - -## Pausing connections - -The `Pooler` specification allows you to take advantage of PgBouncer's `PAUSE` -and `RESUME` commands, using only declarative configuration. You can do this -using the `paused` option, which by default is set to `false`. When set to -`true`, the operator internally invokes the `PAUSE` command in PgBouncer, -which: - -1. Closes all active connections toward the PostgreSQL server, after waiting - for the queries to complete -2. Pauses any new connection coming from the client - -When the `paused` option is reset to `false`, the operator invokes the -`RESUME` command in PgBouncer, reopening the taps toward the PostgreSQL -service defined in the `Pooler` resource. - -!!!note PAUSE -For more information, see -[`PAUSE` in the PgBouncer documentation](https://www.pgbouncer.org/usage.html#pause-db). -!!! - -!!!info Important -In future versions, the switchover operation will be fully integrated -with the PgBouncer pooler and take advantage of the `PAUSE`/`RESUME` -features to reduce the perceived downtime by client applications. -Currently, you can achieve the same results by setting the `paused` -attribute to `true`, issuing the switchover command through the -[`cnp` plugin](kubectl-plugin.md#promote), and then restoring the `paused` -attribute to `false`. -!!! - -## Limitations - -### Single PostgreSQL cluster - -The current implementation of the pooler is designed to work as part of a -specific {{name.ln}} cluster (a service). It isn't currently possible to -create a pooler that spans multiple clusters. - -### Controlled configurability - -{{name.ln}} transparently manages several configuration options that are used -for the PgBouncer layer to communicate with PostgreSQL. Such options aren't -configurable from outside and include TLS certificates, authentication -settings, the `databases` section, and the `users` section. Also, considering -the specific use case for the single PostgreSQL cluster, the adopted criteria -is to explicitly list the options that can be configured by users. - -!!!note -The adopted solution likely addresses the majority of -use cases. It leaves room for the future implementation of a separate -operator for PgBouncer to complete the gamma with more advanced and customized -scenarios. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/container_images.mdx b/product_docs/docs/postgres_for_kubernetes/preview/container_images.mdx deleted file mode 100644 index 9b952921b57..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/container_images.mdx +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: 'Container Image Requirements' -originalFilePath: 'src/container_images.md' ---- - - - -The {{name.ln}} operator for Kubernetes is designed to work with any -compatible PostgreSQL container image that meets the following requirements: - -- PostgreSQL executables must be available in the system path: - - `initdb` - - `postgres` - - `pg_ctl` - - `pg_controldata` - - `pg_basebackup` -- Proper locale settings configured - -Optional Components: - -- [PGAudit](https://www.pgaudit.org/) extension (only required if audit logging - is needed) -- `du` (used for `kubectl cnp status`) - -!!!info Important -Only [PostgreSQL versions officially supported by PGDG](https://postgresql.org/) are allowed. -!!! - -!!!info -Barman Cloud executables are no longer required in {{name.ln}}. The -recommended approach is to use the dedicated [Barman Cloud Plugin](https://github.com/cloudnative-pg/plugin-barman-cloud). -!!! - -No entry point or command is required in the image definition. {{name.ln}} -automatically overrides it with its instance manager. - -!!!warning -{{name.ln}} only supports **Primary with multiple/optional Hot Standby -Servers architecture** for PostgreSQL application container images. -!!! - -## Image Tag Requirements - -To ensure the operator makes informed decisions, it must accurately detect the -PostgreSQL major version. This detection can occur in two ways: - -1. Utilizing the `major` field of the `imageCatalogRef`, if defined. -2. Auto-detecting the major version from the image tag of the `imageName` if - not explicitly specified. - -For auto-detection to work, the image tag must adhere to a specific format. It -should commence with a valid PostgreSQL major version number (e.g., 15.6 or -16), optionally followed by a dot and the patch level. - -Following this, the tag can include any character combination valid and -accepted in a Docker tag, preceded by a dot, an underscore, or a minus sign. - -Examples of accepted image tags: - -- `12.1` -- `13.3.2.1-1` -- `13.4` -- `14` -- `15.5-10` -- `16.0` - -!!!warning -`latest` is not considered a valid tag for the image. -!!! - -!!!note -Image tag requirements do not apply for images defined in a catalog. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/controller.mdx b/product_docs/docs/postgres_for_kubernetes/preview/controller.mdx deleted file mode 100644 index 6d33d7e139b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/controller.mdx +++ /dev/null @@ -1,128 +0,0 @@ ---- -title: 'Custom Pod Controller' -originalFilePath: 'src/controller.md' ---- - - - -Kubernetes uses the -[Controller pattern](https://kubernetes.io/docs/concepts/architecture/controller/) -to align the current cluster state with the desired one. - -Stateful applications are usually managed with the -[`StatefulSet`](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/) -controller, which creates and reconciles a set of Pods built from the same -specification, and assigns them a sticky identity. - -{{name.ln}} implements its own custom controller to manage PostgreSQL -instances, instead of relying on the `StatefulSet` controller. -While bringing more complexity to the implementation, this design choice -provides the operator with more flexibility on how we manage the cluster, -while being transparent on the topology of PostgreSQL clusters. - -Like many choices in the design realm, different ones lead to other -compromises. The following sections discuss a few points where we believe -this design choice has made the implementation of {{name.ln}} -more reliable, and easier to understand. - -## PVC resizing - -This is a well known limitation of `StatefulSet`: it does not support resizing -PVCs. This is inconvenient for a database. Resizing volumes requires -convoluted workarounds. - -In contrast, {{name.ln}} leverages the configured storage class to -manage the underlying PVCs directly, and can handle PVC resizing if -the storage class supports it. - -## Primary Instances versus Replicas - -The `StatefulSet` controller is designed to create a set of Pods -from just one template. Given that we use one `Pod` per PostgreSQL instance, -we have two kinds of Pods: - -1. primary instance (only one) -2. replicas (multiple, optional) - -This difference is relevant when deciding the correct deployment strategy to -execute for a given operation. - -Some operations should be performed on the replicas first, -and then on the primary, but only after an updated replica is promoted -as the new primary. -For example, when you want to apply a different PostgreSQL image version, -or when you increase configuration parameters like `max_connections` (which are -[treated specially by PostgreSQL because {{name.ln}} uses hot standby -replicas](https://www.postgresql.org/docs/current/hot-standby.html)). - -While doing that, {{name.ln}} considers the PostgreSQL instance's -role - and not just its serial number. - -Sometimes the operator needs to follow the opposite process: work on the -primary first and then on the replicas. For example, when you -lower `max_connections`. In that case, {{name.ln}} will: - -- apply the new setting to the primary instance -- restart it -- apply the new setting on the replicas - -The `StatefulSet` controller, being application-independent, can't -incorporate this behavior, which is specific to PostgreSQL's native -replication technology. - -## Coherence of PVCs - -PostgreSQL instances can be configured to work with multiple PVCs: this is how -WAL storage can be separated from `PGDATA`. - -The two data stores need to be coherent from the PostgreSQL point of view, -as they're used simultaneously. If you delete the PVC corresponding to -the WAL storage of an instance, the PVC where `PGDATA` is stored will not be -usable anymore. - -This behavior is specific to PostgreSQL and is not implemented in the -`StatefulSet` controller - the latter not being application specific. - -After the user dropped a PVC, a `StatefulSet` would just recreate it, leading -to a corrupted PostgreSQL instance. - -{{name.ln}} would instead classify the remaining PVC as unusable, and -start creating a new pair of PVCs for another instance to join the cluster -correctly. - -## Local storage, remote storage, and database size - -Sometimes you need to take down a Kubernetes node to do an upgrade. -After the upgrade, depending on your upgrade strategy, the updated node -could go up again, or a new node could replace it. - -Supposing the unavailable node was hosting a PostgreSQL instance, -depending on your database size and your cloud infrastructure, you -may prefer to choose one of the following actions: - -1. drop the PVC and the Pod residing on the downed node; - create a new PVC cloning the data from another PVC; - after that, schedule a Pod for it - -2. drop the Pod, schedule the Pod in a different node, and mount - the PVC from there - -3. leave the Pod and the PVC as they are, and wait for the node to - be back up. - -The first solution is practical when your database size permits, allowing -you to immediately bring back the desired number of replicas. - -The second solution is only feasible when you're not using the storage of the -local node, and re-mounting the PVC in another host is possible in a reasonable -amount of time (which only you and your organization know). - -The third solution is appropriate when the database is big and uses local -node storage for maximum performance and data durability. - -The {{name.ln}} controller implements all these strategies so that the -user can select the preferred behavior at the cluster level (read the -["Kubernetes upgrade"](kubernetes_upgrade.md) section for details). - -Being generic, the `StatefulSet` doesn't allow this level of -customization. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/css/override.css b/product_docs/docs/postgres_for_kubernetes/preview/css/override.css deleted file mode 100644 index f7389b7b398..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/css/override.css +++ /dev/null @@ -1,3 +0,0 @@ -.wy-table-responsive table td, .wy-table-responsive table th { - white-space: normal; -} diff --git a/product_docs/docs/postgres_for_kubernetes/preview/database_import.mdx b/product_docs/docs/postgres_for_kubernetes/preview/database_import.mdx deleted file mode 100644 index ff8fa24e849..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/database_import.mdx +++ /dev/null @@ -1,500 +0,0 @@ ---- -title: 'Importing Postgres databases' -originalFilePath: 'src/database_import.md' ---- - - - -This section describes how to import one or more existing PostgreSQL -databases inside a brand new {{name.ln}} cluster. - -The import operation is based on the concept of online logical backups in PostgreSQL, -and relies on `pg_dump` via a network connection to the origin host, and `pg_restore`. -Thanks to native Multi-Version Concurrency Control (MVCC) and snapshots, -PostgreSQL enables taking consistent backups over the network, in a concurrent -manner, without stopping any write activity. - -Logical backups are also the most common, flexible and reliable technique to -perform major upgrades of PostgreSQL versions. - -As a result, the instructions in this section are suitable for both: - -- importing one or more databases from an existing PostgreSQL instance, even - outside Kubernetes -- importing the database from any PostgreSQL version to one that is either the - same or newer, enabling *major upgrades* of PostgreSQL (e.g. from version 14.x - to version 18.x) - -!!!warning -When performing major upgrades of PostgreSQL you are responsible for making -sure that applications are compatible with the new version and that the -upgrade path of the objects contained in the database (including extensions) is -feasible. -!!! - -In both cases, the operation is performed on a consistent **snapshot** of the -origin database. - -!!!info Important -For this reason we suggest to stop write operations on the source before -the final import in the `Cluster` resource, as changes done to the source -database after the start of the backup will not be in the destination cluster - -hence why this feature is referred to as "offline import" or "offline major -upgrade". -!!! - -## How it works - -Conceptually, the import requires you to create a new cluster from scratch -(*destination cluster*), using the [`initdb` bootstrap method](bootstrap.md), -and then complete the `initdb.import` subsection to import objects from an -existing Postgres cluster (*source cluster*). As per PostgreSQL recommendation, -we suggest that the PostgreSQL major version of the *destination cluster* is -greater or equal than the one of the *source cluster*. - -{{name.ln}} provides two main ways to import objects from the source cluster -into the destination cluster: - -- **microservice approach**: the destination cluster is designed to host a - single application database owned by the specified application user, as - recommended by the {{name.ln}} project - -- **monolith approach**: the destination cluster is designed to host multiple - databases and different users, imported from the source cluster - -The first import method is available via the `microservice` type, the -second via the `monolith` type. - -!!!warning -It is your responsibility to ensure that the destination cluster can -access the source cluster with a superuser or a user having enough -privileges to take a logical backup with `pg_dump`. Please refer to the -[PostgreSQL documentation on `pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html) -for further information. -!!! - -## The `microservice` type - -With the microservice approach, you can specify a single database you want to -import from the source cluster into the destination cluster. The operation is -performed in 4 steps: - -- `initdb` bootstrap of the new cluster -- export of the selected database (in `initdb.import.databases`) using - `pg_dump -Fd` -- import of the database using `pg_restore --no-acl --no-owner` into the - `initdb.database` (application database) owned by the `initdb.owner` user -- cleanup of the database dump file -- optional execution of the user defined SQL queries in the application - database via the `postImportApplicationSQL` parameter -- execution of `ANALYZE VERBOSE` on the imported database - -In the figure below, a single PostgreSQL cluster containing *N* databases is -imported into separate {{name.ln}} clusters, with each cluster using a -microservice import for one of the *N* source databases. - -![Example of microservice import type](./images/microservice-import.png) - -For example, the YAML below creates a new 3 instance PostgreSQL cluster (latest -available major version at the time the operator was released) called -`cluster-microservice` that imports the `angus` database from the -`cluster-pg96` cluster (with the unsupported PostgreSQL 9.6), by connecting to -the `postgres` database using the `postgres` user, via the password stored in -the `cluster-pg96-superuser` secret. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-microservice -spec: - instances: 3 - - bootstrap: - initdb: - import: - type: microservice - databases: - - angus - source: - externalCluster: cluster-pg96 - #postImportApplicationSQL: - #- | - # INSERT YOUR SQL QUERIES HERE - storage: - size: 1Gi - externalClusters: - - name: cluster-pg96 - connectionParameters: - # Use the correct IP or host name for the source database - host: pg96.local - user: postgres - dbname: postgres - password: - name: cluster-pg96-superuser - key: password -``` - -!!!warning -The example above deliberately uses a source database running a version of -PostgreSQL that is not supported anymore by the Community, and consequently by -{{name.ln}}. -Data export from the source instance is performed using the version of -`pg_dump` in the destination cluster, which must be a supported one, and -equal or greater than the source one. -Based on our experience, this way of exporting data should work on older -and unsupported versions of Postgres too, giving you the chance to move your -legacy data to a better system, inside Kubernetes. -This is the main reason why we used 9.6 in the examples of this section. -We'd be interested to hear from you, should you experience any issues in this area. -!!! - -There are a few things you need to be aware of when using the `microservice` type: - -- It requires an `externalCluster` that points to an existing PostgreSQL - instance containing the data to import (for more information, please refer to - ["The `externalClusters` section"](bootstrap.md#the-externalclusters-section)) -- Traffic must be allowed between the Kubernetes cluster and the - `externalCluster` during the operation -- Connection to the source database must be granted with the specified user - that needs to run `pg_dump` and read roles information (*superuser* is OK) -- Currently, the `pg_dump -Fd` result is stored temporarily inside the `dumps` - folder in the `PGDATA` volume, so there should be enough available space to - temporarily contain the dump result on the assigned node, as well as the - restored data and indexes. Once the import operation is completed, this - folder is automatically deleted by the operator. -- Only one database can be specified inside the `initdb.import.databases` array -- Roles are not imported - and as such they cannot be specified inside `initdb.import.roles` - -!!!tip Hint -The microservice approach adheres to {{name.ln}} conventions and defaults -for the destination cluster. If you do not set `initdb.database` or -`initdb.owner` for the destination cluster, both parameters will default to -`app`. -!!! - -## The `monolith` type - -With the monolith approach, you can specify a set of roles and databases you -want to import from the source cluster into the destination cluster. -The operation is performed in the following steps: - -- `initdb` bootstrap of the new cluster -- export and import of the selected roles -- export of the selected databases (in `initdb.import.databases`), one at a time, - using `pg_dump -Fd` -- create each of the selected databases and import data using `pg_restore` -- run `ANALYZE` on each imported database -- cleanup of the database dump files - -![Example of monolith import type](./images/monolith-import.png) - -For example, the YAML below creates a new 3 instance PostgreSQL cluster (latest -available major version at the time the operator was released) called -`cluster-monolith` that imports the `accountant` and the `bank_user` roles, -as well as the `accounting`, `banking`, `resort` databases from the -`cluster-pg96` cluster (with the unsupported PostgreSQL 9.6), by connecting to -the `postgres` database using the `postgres` user, via the password stored in -the `cluster-pg96-superuser` secret. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-monolith -spec: - instances: 3 - bootstrap: - initdb: - import: - type: monolith - databases: - - accounting - - banking - - resort - roles: - - accountant - - bank_user - source: - externalCluster: cluster-pg96 - storage: - size: 1Gi - externalClusters: - - name: cluster-pg96 - connectionParameters: - # Use the correct IP or host name for the source database - host: pg96.local - user: postgres - dbname: postgres - sslmode: require - password: - name: cluster-pg96-superuser - key: password -``` - -There are a few things you need to be aware of when using the `monolith` type: - -- It requires an `externalCluster` that points to an existing PostgreSQL - instance containing the data to import (for more information, please refer to - ["The `externalClusters` section"](bootstrap.md#the-externalclusters-section)) -- Traffic must be allowed between the Kubernetes cluster and the - `externalCluster` during the operation -- Connection to the source database must be granted with the specified user - that needs to run `pg_dump` and retrieve roles information (*superuser* is - OK) -- Currently, the `pg_dump -Fd` result is stored temporarily inside the `dumps` - folder in the `PGDATA` volume of the destination cluster's instances, so - there should be enough available space to - temporarily contain the dump result on the assigned node, as well as the - restored data and indexes. Once the import operation is completed, this - folder is automatically deleted by the operator. -- At least one database to be specified in the `initdb.import.databases` array -- Any role that is required by the imported databases must be specified inside - `initdb.import.roles`, with the limitations below: - - The following roles, if present, are not imported: - `postgres`, `streaming_replica`, `cnp_pooler_pgbouncer` - - The `SUPERUSER` option is removed from any imported role -- Wildcard `"*"` can be used as the only element in the `databases` and/or - `roles` arrays to import every object of the kind; When matching databases - the wildcard will ignore the `postgres` database, template databases - and those databases not allowing connections -- After the clone procedure is done, `ANALYZE VERBOSE` is executed for every - database. -- The `postImportApplicationSQL` field is not supported - -!!!tip Hint -The databases and their owners are preserved exactly as they exist in the -source cluster—no `app` database or user will be created during import. If your -`bootstrap.initdb` stanza specifies custom `database` and `owner` values that -do not match any of the databases or users being imported, the instance -manager will create a new, empty application database and owner role with those -specified names, while leaving the imported databases and owners unchanged. -!!! - -## A practical example - -There is nothing to stop you from using the `monolith` approach to import a -single database. It is interesting to see how the results of doing so would -differ from using the `microservice` approach. - -Given a source cluster, for example the following, with a database named -`mydb` owned by role `me`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 1 - - postgresql: - pg_hba: - - host all all all trust - - storage: - size: 1Gi - - bootstrap: - initdb: - database: mydb - owner: me -``` - -We can import it via `microservice`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-microservice -spec: - instances: 1 - - storage: - size: 1Gi - - bootstrap: - initdb: - import: - type: microservice - databases: - - mydb - source: - externalCluster: cluster-example - - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw - dbname: postgres -``` - -as well as via monolith: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-monolith -spec: - instances: 1 - - storage: - size: 1Gi - - bootstrap: - initdb: - import: - type: monolith - databases: - - mydb - roles: - - me - source: - externalCluster: cluster-example - - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw - dbname: postgres -``` - -In both cases, the database's contents will be imported, but: - -- In the microservice case, the imported database's name and owner both become - `app`, or whichever configuration for the fields `database` and `owner` are - set in the `bootstrap.initdb` stanza. -- In the monolith case, the database and owner are kept exactly as in the source - cluster, i.e. `mydb` and `me` respectively. No `app` database nor user will be - created. If there are custom settings for `database` and `owner` in the - `bootstrap.initdb` stanza that don't match the source databases/owners to - import, the instance manager will create a new empty application database and - owner role, but will leave the imported databases/owners intact. - -## Import optimizations - -During the logical import of a database, {{name.ln}} optimizes the -configuration of PostgreSQL in order to prioritize speed versus data -durability, by forcing: - -- `archive_mode` to `off` -- `fsync` to `off` -- `full_page_writes` to `off` -- `max_wal_senders` to `0` -- `wal_level` to `minimal` - -Before completing the import job, {{name.ln}} restores the expected -configuration, then runs `initdb --sync-only` to ensure that data is -permanently written on disk. - -!!!info Important -WAL archiving, if requested, and WAL level will be honored after the -database import process has completed. Similarly, replicas will be cloned -after the bootstrap phase, when the actual cluster resource starts. -!!! - -There are other optimizations you can do during the import phase. Although this -topic is beyond the scope of {{name.ln}}, we recommend that you reduce -unnecessary writes in the checkpoint area by tuning Postgres GUCs like -`shared_buffers`, `max_wal_size`, `checkpoint_timeout` directly in the -`Cluster` configuration. - -## Customizing `pg_dump` and `pg_restore` behavior - -You can customize the behavior of `pg_dump` and `pg_restore` by specifying additional -options using the `pgDumpExtraOptions` and `pgRestoreExtraOptions` parameters. -This is especially useful for improving performance or managing import/export complexity. - -For example, enabling parallel jobs can significantly speed up data transfer: - -```yaml -bootstrap: - initdb: - import: - type: microservice - databases: - - app - source: - externalCluster: cluster-example - pgDumpExtraOptions: - - '--jobs=2' - pgRestoreExtraOptions: - - '--jobs=2' -``` - -### Stage-Specific `pg_restore` options - -For more granular control over the import process, {{name.ln}} supports -stage-specific `pg_restore` options for the following phases: - -- `pre-data` – e.g., schema definitions -- `data` – e.g., table contents -- `post-data` – e.g., indexes, constraints and triggers - -By specifying options for each phase, you can optimize parallelism and apply -flags tailored to the nature of the objects being restored. - -```yaml -bootstrap: - initdb: - import: - type: microservice - schemaOnly: false - databases: - - mynewdb - source: - externalCluster: sourcedb-external - pgRestorePredataOptions: - - '--jobs=1' - pgRestoreDataOptions: - - '--jobs=4' - pgRestorePostdataOptions: - - '--jobs=2' -``` - -In the example above: - -- `--jobs=1` is applied to the `pre-data` stage to preserve the ordering of - schema creation. -- `--jobs=4` increases parallelism during the `data` stage, speeding up large - data imports. -- `--jobs=2` balances performance and dependency handling in the `post-data` - stage. - -These stage-specific settings are particularly valuable for large databases or -resource-sensitive environments where tuning concurrency can significantly -improve performance. - -!!!note -When provided, stage-specific options take precedence over the general -`pgRestoreExtraOptions`. -!!! - -!!!warning -The `pgDumpExtraOptions`, `pgRestoreExtraOptions`, and all stage-specific -restore options (`pgRestorePredataOptions`, `pgRestoreDataOptions`, -`pgRestorePostdataOptions`) are passed directly to the underlying PostgreSQL -tools without validation by the operator. Certain flags may conflict with the -operator’s intended functionality or design. Use these options with caution -and always test them thoroughly in a safe, controlled environment before -applying them in production. -!!! - -## Online Import and Upgrades - -Logical replication offers a powerful way to import any PostgreSQL database -accessible over the network using the following approach: - -- **Import Bootstrap with Schema-Only Option**: Initialize the schema in the - target database before replication begins. -- **`Subscription` Resource**: Set up continuous replication to synchronize - data changes. - -This technique can also be leveraged for performing major PostgreSQL upgrades -with minimal downtime, making it ideal for seamless migrations and system -upgrades. - -For more details, including limitations and best practices, refer to the -[Logical Replication](logical_replication.md) section in the documentation. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/declarative_database_management.mdx b/product_docs/docs/postgres_for_kubernetes/preview/declarative_database_management.mdx deleted file mode 100644 index c9dc0e502f5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/declarative_database_management.mdx +++ /dev/null @@ -1,485 +0,0 @@ ---- -title: 'PostgreSQL Database management' -originalFilePath: 'src/declarative_database_management.md' ---- - - - -{{name.ln}} simplifies PostgreSQL database provisioning by automatically -creating an application database named `app` by default. This default behavior -is explained in the ["Bootstrap an Empty Cluster"](bootstrap.md#bootstrap-an-empty-cluster-initdb) -section. - -For more advanced use cases, {{name.ln}} introduces **declarative database -management**, which empowers users to define and control the lifecycle of -PostgreSQL databases using the `Database` Custom Resource Definition (CRD). -This method seamlessly integrates with Kubernetes, providing a scalable, -automated, and consistent approach to managing PostgreSQL databases. - -* * * - -## Key Concepts - -### Scope of Management - -!!!info Important -{{name.ln}} manages **global objects** in PostgreSQL clusters, including -databases, roles, and tablespaces. However, it does **not** manage database content -beyond extensions and schemas (e.g., tables). To manage database content, use specialized -tools or rely on the applications themselves. -!!! - -### Declarative `Database` Manifest - -The following example demonstrates how a `Database` resource interacts with a -`Cluster`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - name: cluster-example-one -spec: - name: one - owner: app - cluster: - name: cluster-example - extensions: - - name: bloom - ensure: present -``` - -When applied, this manifest creates a `Database` object called -`cluster-example-one` requesting a database named `one`, owned by the `app` -role, in the `cluster-example` PostgreSQL cluster. - -!!!info -Please refer to the [API reference](pg4k.v1.md#databasespec) -the full list of attributes you can define for each `Database` object. -!!! - -### Required Fields in the `Database` Manifest - -- `metadata.name`: Unique name of the Kubernetes object within its namespace. -- `spec.name`: Name of the database as it will appear in PostgreSQL. -- `spec.owner`: PostgreSQL role that owns the database. -- `spec.cluster.name`: Name of the target PostgreSQL cluster. - -The `Database` object must reference a specific `Cluster`, determining where -the database will be created. It is managed by the cluster's primary instance, -ensuring the database is created or updated as needed. - -!!!warning - -The `spec.cluster` field is immutable after creation. To target a -different `Cluster`, create a new `Database` resource instead of updating -an existing one. -!!! - -!!!info -The distinction between `metadata.name` and `spec.name` allows multiple -`Database` resources to reference databases with the same name across different -{{name.ln}} clusters in the same Kubernetes namespace. -!!! - -## Reserved Database Names - -PostgreSQL automatically creates databases such as `postgres`, `template0`, and -`template1`. These names are reserved and cannot be used for new `Database` -objects in {{name.ln}}. - -!!!info Important -Creating a `Database` with `spec.name` set to `postgres`, `template0`, or -`template1` is not allowed. -!!! - -## Reconciliation and Status - -Once a `Database` object is reconciled successfully: - -- `status.applied` will be set to `true`. -- `status.observedGeneration` will match the `metadata.generation` of the last - applied configuration. - -Example of a reconciled `Database` object: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - generation: 1 - name: cluster-example-one -spec: - cluster: - name: cluster-example - name: one - owner: app -status: - observedGeneration: 1 - applied: true -``` - -If an error occurs during reconciliation, `status.applied` will be `false`, and -an error message will be included in the `status.message` field. - -## Deleting a Database - -{{name.ln}} supports two methods for database deletion: - -1. Using the `delete` reclaim policy -2. Declaratively setting the database's `ensure` field to `absent` - -### Deleting via `delete` Reclaim Policy - -The `databaseReclaimPolicy` field determines the behavior when a `Database` -object is deleted: - -- `retain` (default): The database remains in PostgreSQL for manual management. -- `delete`: The database is automatically removed from PostgreSQL. - -Example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - name: cluster-example-two -spec: - databaseReclaimPolicy: delete - name: two - owner: app - cluster: - name: cluster-example -``` - -Deleting this `Database` object will automatically remove the `two` database -from the `cluster-example` cluster. - -On a replica cluster the database is read-only, so deleting a `Database` object -releases its finalizer and removes the Kubernetes object without dropping the -PostgreSQL database, even with `databaseReclaimPolicy: delete`. Dropping the -database is left to the primary cluster, which owns it. - -### Declaratively Setting `ensure: absent` - -To remove a database, set the `ensure` field to `absent` like in the following -example:. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - name: cluster-example-database-to-drop -spec: - cluster: - name: cluster-example - name: database-to-drop - owner: app - ensure: absent -``` - -This manifest ensures that the `database-to-drop` database is removed from the -`cluster-example` cluster. - -## Managing Extensions in a Database - -!!!info -While extensions are database-scoped rather than global objects, -{{name.ln}} provides a declarative interface for managing them. This approach -is necessary because installing certain extensions may require superuser -privileges, which {{name.ln}} recommends disabling by default. By leveraging -this API, users can efficiently manage extensions in a scalable and controlled -manner without requiring elevated privileges. -!!! - -{{name.ln}} simplifies and automates the management of PostgreSQL extensions within the -target database. - -To enable this feature, define the `spec.extensions` field -with a list of extension specifications, as shown in the following example: - -```yaml -# ... -spec: - extensions: - - name: bloom - ensure: present -# ... -``` - -Each extension entry supports the following properties: - -- `name` *(mandatory)*: The name of the extension. -- `ensure`: Specifies whether the extension should be present or absent in the - database: - - `present`: Ensures that the extension is installed (default). - - `absent`: Ensures that the extension is removed. -- `version`: The specific version of the extension to install or - upgrade to. -- `schema`: The schema in which the extension should be installed. - -!!!info -{{name.ln}} manages extensions using the following PostgreSQL’s SQL commands: -[`CREATE EXTENSION`](https://www.postgresql.org/docs/current/sql-createextension.html), -[`DROP EXTENSION`](https://www.postgresql.org/docs/current/sql-dropextension.html), -[`ALTER EXTENSION`](https://www.postgresql.org/docs/current/sql-alterextension.html) -(limited to `UPDATE TO` and `SET SCHEMA`). -!!! - -The operator reconciles only the extensions explicitly listed in -`spec.extensions`. Any existing extensions not specified in this list remain -unchanged. - -!!!warning -Before the introduction of declarative extension management, {{name.ln}} -did not offer a straightforward way to create extensions through configuration. -To address this, the ["managed extensions"](postgresql_conf.md#managed-extensions) -feature was introduced, enabling the automated and transparent management -of key extensions like `pg_stat_statements`. Currently, it is your -responsibility to ensure there are no conflicts between extension support in -the `Database` CRD and the managed extensions feature. -!!! - -## Managing Schemas in a Database - -!!!info -Schema management in PostgreSQL is an exception to {{name.ln}}' primary -focus on managing global objects. Since schemas exist within a database, they -are typically managed as part of the application development process. However, -{{name.ln}} provides a declarative interface for schema management, primarily -to complete the support of extensions deployment within schemas. -!!! - -{{name.ln}} simplifies and automates the management of PostgreSQL schemas within the -target database. - -To enable this feature, define the `spec.schemas` field -with a list of schema specifications, as shown in the following example: - -```yaml -# ... -spec: - schemas: - - name: app - owner: app -# ... -``` - -Each schema entry supports the following properties: - -- `name` *(mandatory)*: The name of the schema. -- `owner`: The owner of the schema. -- `ensure`: Specifies whether the schema should be present or absent in the - database: - - `present`: Ensures that the schema is installed (default). - - `absent`: Ensures that the schema is removed. - -!!!info -{{name.ln}} manages schemas using the following PostgreSQL’s SQL commands: -[`CREATE SCHEMA`](https://www.postgresql.org/docs/current/sql-createschema.html), -[`DROP SCHEMA`](https://www.postgresql.org/docs/current/sql-dropschema.html), -[`ALTER SCHEMA`](https://www.postgresql.org/docs/current/sql-alterschema.html). -!!! - -## Managing Foreign Data Wrappers (FDWs) in a Database - -!!!info -Foreign Data Wrappers (FDWs) are database-scoped objects that typically -require superuser privileges to create or modify. {{name.ln}} provides a -declarative API for managing FDWs, enabling users to define and maintain them -in a controlled, Kubernetes-native way without directly executing SQL commands -or escalating privileges. -!!! - -{{name.ln}} enables seamless and automated management of PostgreSQL foreign -data wrappers in the target database using declarative configuration. - -To enable this feature, define the `spec.fdws` field with a list of FDW -specifications, as shown in the following example: - -```yaml -# ... -spec: - fdws: - - name: postgres_fdw - usage: - - name: app - type: grant -# ... -``` - -Each FDW entry supports the following properties: - -- `name`: The name of the foreign data wrapper **(mandatory)**. -- `ensure`: Indicates whether the FDW should be `present` or `absent` in the - database (default is `present`). -- `handler`: The name of the handler function used by the FDW. If not - specified, the default handler defined by the FDW extension (if any) will be - used. -- `validator`: The name of the validator function used by the FDW. If not - specified, the default validator defined by the FDW extension (if any) will - be used. -- `owner`: The owner of the FDW **(must be a superuser)**. -- `usage`: The list of `USAGE` permissions of the FDW, with the following fields: - - `name` : The name of the role to which the usage permission should be - granted or from which it should be revoked **(mandatory)**. - - `type` : The type of the usage permission. Supports `grant` and `revoke`. -- `options`: A map of FDW-specific options to manage, where each key is the - name of an option. Each option supports the following fields: - - `value`: The string value of the option. - - `ensure`: Indicates whether the option should be `present` or `absent`. - -!!!info -Both `handler` and `validator` are optional, and if not specified, the -default handler and validator defined by the FDW extension (if any) will be -used. Setting `handler` or `validator` to `"-"` will remove the handler or -validator from the FDW respectively. This follows the PostgreSQL convention, -where "-" denotes the absence of a handler or validator. -!!! - -!!!warning -PostgreSQL restricts ownership of foreign data wrappers to **roles with -superuser privileges only**. Attempting to assign ownership to a non-superuser -(e.g., an app role) will be ignored or rejected, as PostgreSQL does not allow -non-superuser ownership of foreign data wrappers. By default, they are -owned by the `postgres` user. -!!! - -The operator reconciles only the FDWs explicitly listed in `spec.fdws`. Any -existing FDWs not declared in this list are left untouched. - -!!!info - {{name.ln}} manages FDWs using PostgreSQL's native SQL commands: - [`CREATE FOREIGN DATA WRAPPER`](https://www.postgresql.org/docs/current/sql-createforeigndatawrapper.html), - [`ALTER FOREIGN DATA WRAPPER`](https://www.postgresql.org/docs/current/sql-alterforeigndatawrapper.html), - and [`DROP FOREIGN DATA WRAPPER`](https://www.postgresql.org/docs/current/sql-dropforeigndatawrapper.html). - The `ALTER` command supports option updates. -!!! - -### Managing Foreign Servers in a Database - -{{name.ln}} provides seamless, automated management of PostgreSQL foreign -servers in a target database using declarative configuration. - -A **foreign server** encapsulates the connection details that a foreign data -wrapper (FDW) uses to access an external data source. For user-specific -connection details, you can define [user mappings](https://www.postgresql.org/docs/current/sql-createusermapping.html). - -!!!info Important -{{name.ln}} does not currently support declarative configuration of user mappings. -However, once an FDW and its foreign server are defined, you can grant -usage privileges to a standard database role. This allows you to manage user -mappings as part of your SQL schema, without requiring superuser privileges. -!!! - -To enable this feature, declare the `spec.servers` field in a `Database` -resource with a list of foreign server specifications, for example: - -```yaml -# ... -spec: - servers: - - name: angus - fdw: postgres_fdw - ensure: present - usage: - - name: app - type: grant - options: - - name: host - value: angus-rw - - name: dbname - value: app -# ... -``` - -Each foreign server entry supports the following properties: - -- `name`: The name of the foreign server **(mandatory)**. -- `fdw`: The name of the foreign data wrapper the server belongs to - **(mandatory)**. -- `ensure`: Whether the foreign server should be `present` or `absent` in the - database (default: `present`). -- `usage`: The list of `USAGE` permissions of the foreign server, with the - following fields: - - `name` : The name of the role to which the usage permission should be - granted or from which it should be revoked **(mandatory)**. - - `type` : The type of the usage permission. Supports `grant` and `revoke`. -- `options`: A list of FDW-specific option specifications. - Each entry in the list supports the following keys: - - `name`: The name of the option **(mandatory)**. - - `value`: The string value of the option. - - `ensure`: Indicates whether the option should be `present` or `absent`. - -!!!info Important -The `fdw` field must reference an existing foreign data wrapper already defined in the database. -If the specified FDW does not exist, the foreign server will not be created. -!!! - -{{name.ln}} manages foreign servers using PostgreSQL’s native SQL commands: -[`CREATE SERVER`](https://www.postgresql.org/docs/current/sql-createserver.html), -[`ALTER SERVER`](https://www.postgresql.org/docs/current/sql-alterserver.html), and -[`DROP SERVER`](https://www.postgresql.org/docs/current/sql-dropserver.html). -The `ALTER SERVER` command is used to update server options. - -The operator reconciles **only** the foreign servers explicitly listed in -`spec.servers`. Any existing servers not included in this list are left -unchanged. - -## Limitations and Caveats - -### Renaming a database - -While {{name.ln}} adheres to PostgreSQL’s -[CREATE DATABASE](https://www.postgresql.org/docs/current/sql-createdatabase.html) and -[ALTER DATABASE](https://www.postgresql.org/docs/current/sql-alterdatabase.html) -commands, **renaming databases is not supported**. -Attempting to modify `spec.name` in an existing `Database` object will result -in rejection by Kubernetes. - -### Creating vs. Altering a Database - -- For new databases, {{name.ln}} uses the `CREATE DATABASE` statement. -- For existing databases, `ALTER DATABASE` is used to apply changes. - -It is important to note that there are some differences between these two -Postgres commands: in particular, the options accepted by `ALTER` are a subset -of those accepted by `CREATE`. - -!!!warning -Some fields, such as encoding and collation settings, are immutable in -PostgreSQL. Attempts to modify these fields on existing databases will be -ignored. -!!! - -### Replica Clusters - -Database objects declared on replica clusters cannot be enforced, as replicas -lack write privileges. These objects will remain in a pending state until the -replica is promoted. - -### Conflict Resolution - -If two `Database` objects in the same namespace manage the same PostgreSQL -database (i.e., identical `spec.name` and `spec.cluster.name`), the second -object will be rejected. - -Example status message: - -```yaml -status: - applied: false - message: 'reconciliation error: database "one" is already managed by Database object "cluster-example-one"' -``` - -### Postgres Version Differences - -{{name.ln}} adheres to PostgreSQL's capabilities. For example, features like -`ICU_RULES` introduced in PostgreSQL 16 are unavailable in earlier versions. -Errors from PostgreSQL will be reflected in the `Database` object's `status`. - -### Manual Changes - -{{name.ln}} does not overwrite manual changes to databases. Once reconciled, -a `Database` object will not be reapplied unless its `metadata.generation` -changes, giving flexibility for direct PostgreSQL modifications. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/declarative_hibernation.mdx b/product_docs/docs/postgres_for_kubernetes/preview/declarative_hibernation.mdx deleted file mode 100644 index bd8d1e0a0a4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/declarative_hibernation.mdx +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: 'Declarative hibernation' -originalFilePath: 'src/declarative_hibernation.md' ---- - - - -{{name.ln}} is designed to keep PostgreSQL clusters up, running and available -anytime. - -There are some kinds of workloads that require the database to be up only when -the workload is active. Batch-driven solutions are one such case. - -In batch-driven solutions, the database needs to be up only when the batch -process is running. - -The declarative hibernation feature enables saving CPU power by removing the -database Pods, while keeping the database PVCs. - -## Hibernation - -To hibernate a cluster, set the `k8s.enterprisedb.io/hibernation=on` annotation: - -```sh -$ kubectl annotate cluster --overwrite k8s.enterprisedb.io/hibernation=on -``` - -A hibernated cluster won't have any running Pods, while the PVCs are retained -so that the cluster can be rehydrated at a later time. Replica PVCs will be -kept in addition to the primary's PVC. - -The hibernation procedure will delete the primary Pod and then the replica -Pods, avoiding switchover, to ensure the replicas are kept in sync. - -The hibernation status can be monitored by looking for the `k8s.enterprisedb.io/hibernation` -condition: - -```sh -$ kubectl get cluster -o "jsonpath={.status.conditions[?(.type==\"k8s.enterprisedb.io/hibernation\")]}" - -{ - "lastTransitionTime":"2023-03-05T16:43:35Z", - "message":"Cluster has been hibernated", - "reason":"Hibernated", - "status":"True", - "type":"k8s.enterprisedb.io/hibernation" -} -``` - -The hibernation status can also be read with the `status` sub-command of the -`cnp` plugin for `kubectl`: - -```sh -$ kubectl cnp status -Cluster Summary -Name: cluster-example -Namespace: default -PostgreSQL Image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 -Primary instance: cluster-example-2 -Status: Cluster in healthy state -Instances: 3 -Ready instances: 0 - -Hibernation -Status Hibernated -Message Cluster has been hibernated -Time 2023-03-05 16:43:35 +0000 UTC -[..] -``` - -## Rehydration - -To rehydrate a cluster, either set the `k8s.enterprisedb.io/hibernation` annotation to `off`: - -``` -$ kubectl annotate cluster --overwrite k8s.enterprisedb.io/hibernation=off -``` - -Or, just unset it altogether: - -``` -$ kubectl annotate cluster k8s.enterprisedb.io/hibernation- -``` - -The Pods will be recreated and the cluster will resume operation. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/declarative_role_management.mdx b/product_docs/docs/postgres_for_kubernetes/preview/declarative_role_management.mdx deleted file mode 100644 index 70ad12a0657..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/declarative_role_management.mdx +++ /dev/null @@ -1,642 +0,0 @@ ---- -title: 'PostgreSQL Role management' -originalFilePath: 'src/declarative_role_management.md' ---- - - - -!!!info - -From its inception, {{name.ln}} has managed the creation of specific roles -required in PostgreSQL instances: - -- some reserved users, such as the `postgres` superuser, `streaming_replica` - and `cnp_pooler_pgbouncer` (when the PgBouncer `Pooler` is used) -- The application user, set as the low-privilege owner of the application database - -This process is described in the ["Bootstrap"](bootstrap.md) section. -!!! - -{{name.ln}} provides full lifecycle management for PostgreSQL database roles. -You can define roles either: - -1. as [standalone `DatabaseRole` resources](#the-databaserole-resource) (recommended), or -2. via [the `managed` stanza within the `Cluster` spec](#inline-managed-roles). - -## Coexistence and precedence - -The two methods are not mutually exclusive: you can manage different roles with -each one at the same time, which is what makes a gradual migration from the -inline stanza to `DatabaseRole` resources possible. They only need a rule for -the case where the same role name is defined in both places. - -In that case, **the Cluster specification (`managed.roles`) always takes -precedence**: the `DatabaseRole` is not reconciled and reports the conflict in -its status (see [Status of `DatabaseRole` resources](#status-of-databaserole-resources)). - -!!!important - -Declarative role management ignores roles that exist in the database but are -not included in either the Cluster spec or a `DatabaseRole`. The lifecycle of -those roles continues to be managed within PostgreSQL, allowing you to adopt -this feature at your convenience. -!!! - -* * * - -## General role configuration notes - -Regardless of the management method used, the role specification adheres to the -[PostgreSQL structure and naming conventions](https://www.postgresql.org/docs/current/sql-createrole.html). - -!!!tip - -Please refer to the [API reference](pg4k.v1.md#roleconfiguration) -for the full list of attributes. -!!! - -A few points are worth noting: - -1. The `ensure` attribute is **not** part of PostgreSQL. It enables - declarative role management to create (`present`, the default) or remove - (`absent`) a role, and is available **only** in the inline - [`managed.roles`](#inline-managed-roles) stanza. A `DatabaseRole` does not - support `ensure`; it expresses role removal through its - [reclaim policy](#role-reclaim-policy) instead. -2. The `inherit` attribute is true by default, following PostgreSQL - conventions. -3. The `connectionLimit` attribute defaults to -1, in line with PostgreSQL - conventions. -4. Role membership with `inRoles` defaults to no memberships. - -* * * - -## The `DatabaseRole` resource - -The `DatabaseRole` custom resource provides a dedicated, Kubernetes-native way to -manage PostgreSQL database roles. - -This is the recommended approach for modern environments and -GitOps workflows, as it decouples role lifecycle from the cluster -infrastructure. - -!!!note - -A `DatabaseRole` is applied when its specification or its password Secret -changes. Changes made directly in the database, such as a manual -`ALTER ROLE`, are not detected or reverted until the next time the resource -is applied. Inline managed roles, by contrast, are periodically compared -with the database catalog and brought back to their specification. -!!! - -See [Security](security.md#rbac-on-custom-resources) for the RBAC -implications of granting access to `DatabaseRole` resources. - -A `DatabaseRole` is namespace-scoped: the resource, the `Cluster` it references -through `spec.cluster`, and the `passwordSecret` it consumes must all live in -the same namespace. - -### Example manifest - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: DatabaseRole -metadata: - name: role-dante -spec: - cluster: - name: cluster-example - name: dante - comment: "Dante Alighieri" - login: true - superuser: false - createdb: true - databaseRoleReclaimPolicy: delete - inRoles: - - pg_monitor - passwordSecret: - name: cluster-example-dante -``` - -An example manifest for a role definition can be found in the file -[`role-examples.yaml`](../samples/role-examples.yaml). - -### Role reclaim policy - -The `databaseRoleReclaimPolicy` field defines the "final act" of the operator when a -`DatabaseRole` Custom Resource is removed from the Kubernetes API. -This mirrors the behavior of Kubernetes Persistent Volumes. - -- **`retain` (default):** The role is left in the database. This is the safest - setting for production, ensuring that even if a manifest is accidentally - deleted, the database user (and any objects they own) remains untouched. -- **`delete`:** The operator attempts to execute a `DROP ROLE` in PostgreSQL - before the Kubernetes object is finalized. This is ideal for ephemeral or - automated environments. - -!!!note - -If a role owns objects (tables, schemas, etc.), `DROP ROLE` fails and the -`DatabaseRole` stays in `Terminating`, retried periodically until those objects -are reassigned or dropped. The operator never drops owned objects on your -behalf: reassign or drop them in PostgreSQL, or switch to `retain`, to let the -deletion complete. -!!! - -### Removing a role - -How you remove a role depends on how it was created: - -- **Created through a `DatabaseRole`:** delete the resource. Whether the role is - also dropped from PostgreSQL is governed by its - [reclaim policy](#role-reclaim-policy). -- **Pre-existing, or managed elsewhere:** a `DatabaseRole` is not the tool to drop - it. Declare it `absent` through the inline [`managed.roles`](#inline-managed-roles) - stanza, or run `DROP ROLE` directly. - -!!!warning - -Creating a `DatabaseRole` for a role that already exists **adopts** it: the -operator alters the existing role so that **every** attribute matches the -manifest, including the attributes you omit, which are forced back to their -defaults. In particular, memberships not listed in `inRoles` are revoked, an -omitted `connectionLimit` is reset to `-1` (unlimited), and an omitted -`validUntil` becomes `infinity` if the role had an expiration date. Review -the current attributes and memberships of a role before adopting it, and do -not point a `DatabaseRole` at a role you only want to drop, since it will be -modified before it can be removed. -!!! - -### Status of `DatabaseRole` resources - -The `DatabaseRole` resource includes a dedicated `status` section for per-role -observability: - -```yaml -status: - applied: true - observedGeneration: 3 - conditions: - - lastTransitionTime: "2026-04-04T15:06:23Z" - message: "2051" - reason: ChangeDetected - status: "True" - type: PasswordSecretChange -``` - -The `PasswordSecretChange` condition is maintained by the operator as an -internal signal for the instance manager: its message carries the -`resourceVersion` of the password Secret the operator last observed, and a -change in that value triggers the re-application of the password. The -condition appears once a password Secret is in use and is removed when -`passwordSecret` is removed from the specification. - -If a `DatabaseRole` targets a name already managed in the Cluster spec -(see [Coexistence and precedence](#coexistence-and-precedence)), the `applied` -field will be `false` with the message: - -``` -database role is already managed by the CNP cluster -``` - -On a [replica cluster](replica_cluster.md) the role is owned by the primary -cluster, not reconciled locally. In that case the instance manager reports the -role as *unknown* rather than failed: the `applied` field is left unset (`nil`) -with an explanatory message. The role is reconciled normally once the cluster -is promoted to primary. - -### Client Certificate Generation - -The `DatabaseRole` resource supports opt-in generation of TLS client -certificates, signed by the cluster's client CA and stored in a Kubernetes -Secret. This enables [PostgreSQL `cert` authentication](https://www.postgresql.org/docs/current/auth-cert.html) -as an alternative to passwords: no passwords to rotate manually, and private -keys are stored as Kubernetes Secrets and never transmitted outside the cluster. - -To enable it, add a `clientCertificate` block to the spec: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: DatabaseRole -metadata: - name: role-dante -spec: - cluster: - name: cluster-example - name: dante - login: true - clientCertificate: - enabled: true - databaseRoleReclaimPolicy: retain -``` - -`clientCertificate.enabled` defaults to `true` when the block is present, so -`clientCertificate: {}` is equivalent to enabling it. Set `enabled: false` to -turn issuance off while keeping the block in place. - -!!!important - -`login: true` is required when `clientCertificate` issuance is enabled. The -operator enforces this via validation and will reject the resource otherwise. -!!! - -#### Generated Secret - -The operator creates a Secret named `-client-cert` in the -same namespace. It contains two keys: - -| Key | Contents | -| --------- | ----------------------------------------------------------------- | -| `tls.crt` | PEM-encoded client certificate, signed by the cluster's client CA | -| `tls.key` | PEM-encoded private key | - -The expiration time of the certificate is visible in -`status.clientCertificate.expiration`: - -```yaml -status: - clientCertificate: - expiration: "2026-07-01T12:00:00Z" -``` - -#### Configuring `pg_hba.conf` - -The operator generates the certificate but does **not** modify `pg_hba.conf` -automatically. You must add a `hostssl` rule with the `cert` method to the -cluster for the role to be able to authenticate: - -```yaml -spec: - postgresql: - pg_hba: - - hostssl all dante all cert -``` - -A working connection string using the generated Secret would look like: - -``` -psql "host=-rw..svc port=5432 dbname= user=dante \ - sslcert=/path/to/tls.crt sslkey=/path/to/tls.key \ - sslrootcert=/path/to/ca.crt sslmode=verify-full" -``` - -#### Renewal - -Client certificates inherit the operator's global certificate settings: they -are issued with a **90-day** lifetime by default and renewed automatically once -they fall within **7 days** of expiry. Both values are operator-wide and -configurable via the `CERTIFICATE_DURATION` and `EXPIRING_CHECK_THRESHOLD` -operator settings; they are not configurable per `DatabaseRole`. - -Renewal is driven by the reconcile loop: the operator checks whether the -certificate is approaching expiry and re-signs it if needed. Reconciles are -scheduled at least once per hour when `clientCertificate` issuance is enabled, -so renewal happens well before expiry even without a triggering event. The -current expiration is always reflected in `status.clientCertificate.expiration`. - -#### Deletion and opt-out - -| Scenario | Result | -| ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------- | -| `clientCertificate.enabled` set to `false`, or the `clientCertificate` block removed | The cert Secret is deleted; `status.clientCertificate` is cleared | -| `DatabaseRole` deleted | The cert Secret is garbage-collected via owner reference, regardless of `databaseRoleReclaimPolicy` | - -!!!note - -`databaseRoleReclaimPolicy: retain` retains the PostgreSQL role, not the generated -Secret. The Secret is only meaningful while the operator is managing the role, -so it is always cleaned up on deletion. -!!! - -#### Bring-your-own-CA limitation - -If the cluster's client CA Secret does not contain a private key (i.e. you -supplied your own CA via `spec.certificates.clientCASecret`), the operator -cannot sign new certificates. It will record the reason in -`status.clientCertificate.message` and stop retrying: - -```yaml -status: - clientCertificate: - message: 'client CA secret "my-ca" has no private key; bring-your-own-CA - clusters require manual certificate management' -``` - -In this case, you must issue and renew client certificates manually. - -!!!note - -CNP does not manage Certificate Revocation Lists (CRLs). If a certificate must -be invalidated before it expires, rotate the cluster's client CA: on the next -reconcile the operator detects that the existing certificates are no longer -signed by the current CA and re-issues all managed client certificates. -Alternatively, delete the certificate's Secret to have the operator issue a -fresh one signed by the current CA. -!!! - -* * * - -## Inline managed roles - -With the `managed` stanza in the cluster spec, {{name.ln}} provides -management for roles specified in `.spec.managed.roles`. -This feature enables declarative management of existing roles, as well as the -creation of new roles if they are not already present. - -### Example manifest - -An example manifest for a cluster with declarative role management can be found -in the file [`cluster-example-with-roles.yaml`](../samples/cluster-example-with-roles.yaml). - -Here is an excerpt from that file: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -spec: - managed: - roles: - - name: dante - ensure: present - comment: Dante Alighieri - login: true - superuser: false - inRoles: - - pg_monitor - - pg_signal_backend -``` - -### Status of inline managed roles - -When using the inline method, the `Cluster` status includes a comprehensive -summary: - -```yaml -status: - managedRolesStatus: - byStatus: - reconciled: - - dante - reserved: - - postgres - - streaming_replica - cannotReconcile: - petrarca: - - 'could not perform UPDATE_MEMBERSHIPS on role petrarca: role "poets" does not exist' -``` - -Note the special sub-section `cannotReconcile` for operations the database (and -{{name.ln}}) cannot honor, and which require human intervention. - -This section covers roles reserved for operator use and those that are **not** -under declarative management, providing a comprehensive view of the roles in -the database instances. - -The [kubectl plugin](kubectl-plugin.md) also shows the status of managed roles -in its `status` sub-command: - -```txt -Managed roles status -Status Roles ------- ----- -pending-reconciliation petrarca -reconciled app,dante -reserved postgres,streaming_replica - -Irreconcilable roles -Role Errors ----- ------ -petrarca could not perform UPDATE_MEMBERSHIPS on role petrarca: role "poets" does not exist -``` - -* * * - -## Migrating from inline managed roles to a `DatabaseRole` - -You can move a role from the inline `managed.roles` stanza to a standalone -`DatabaseRole` without disruption: - -1. Create the `DatabaseRole` with the desired specification. Both methods - share the same [`RoleConfiguration`](pg4k.v1.md#roleconfiguration) - structure, so the stanza can be copied across as-is. -2. Remove the matching entry from `.spec.managed.roles` in the `Cluster` - manifest. -3. The operator detects the change and hands management over to the - `DatabaseRole`. - -Because the Cluster spec takes precedence while both exist (see -[Coexistence and precedence](#coexistence-and-precedence)), the handover -happens only once the inline entry is gone, so there is no window in which the -role is left unmanaged. - -When converting a role that the inline stanza removed with `ensure: absent`, -note that a `DatabaseRole` does not support `ensure: absent`. Express removal -through the [reclaim policy](#role-reclaim-policy) instead: delete the resource -with `databaseRoleReclaimPolicy: delete` to drop the role, or keep the default -`retain` to leave it in place. See [Removing a role](#removing-a-role) for the -full behavior. - -* * * - -## Password management - -The declarative role management feature (both with a `DatabaseRole` and the -inline `managed.roles` stanza) includes reconciling of role passwords. -Managed role configurations may optionally specify the name of a **Secret** -where the username and password are stored: - -```yaml - passwordSecret: - name: cluster-example-dante -``` - -The Secret must be of type `kubernetes.io/basic-auth`. The username (encoded in -*Base64* as is usual in Kubernetes) should match the role we are setting the -password for. For example: - -```yaml -apiVersion: v1 -data: - username: ZGFudGU= - password: ZGFudGU= -kind: Secret -metadata: - name: cluster-example-dante - labels: - k8s.enterprisedb.io/reload: "true" -type: kubernetes.io/basic-auth -``` - -!!!important - -Label the Secret with `k8s.enterprisedb.io/reload: "true"`, as shown above. Password -changes in labeled Secrets are applied immediately, while changes in -unlabeled Secrets are only applied at a subsequent reconciliation, for -example when the operator refreshes its internal cache. -!!! - -If no `passwordSecret` is specified, the instance manager will not try to -`CREATE/ALTER` the role with a password, keeping with PostgreSQL conventions. - -!!!important - -New roles created without `passwordSecret` will have a `NULL` password inside -PostgreSQL. -!!! - -### Disabling passwords - -To explicitly set a password to `NULL` in PostgreSQL (distinguished from simply -omitting a password update), use the `disablePassword` field: - -```yaml - disablePassword: true -``` - -!!!note - -It is an error to set both `passwordSecret` and `disablePassword` on a given role. -!!! - -### Password expiry, `VALID UNTIL` - -The `VALID UNTIL` role attribute in PostgreSQL controls password expiry. Roles -created without `VALID UNTIL` specified get NULL by default in PostgreSQL, -meaning that their password will never expire. - -PostgreSQL uses a timestamp type for `VALID UNTIL`, which includes support for -the value `'infinity'` indicating that the password never expires. Please see the -[PostgreSQL documentation](https://www.postgresql.org/docs/current/datatype-datetime.html) -for reference. - -With declarative role management, the `validUntil` attribute for managed roles -controls password expiry. `validUntil` can only take: - -- a Kubernetes timestamp, or -- be omitted (defaulting to `null`) - -In the first case, the given `validUntil` timestamp will be set in the database -as the `VALID UNTIL` attribute of the role. - -In the second case (omitted `validUntil`) the operator will ensure password -never expires, mirroring the behavior of PostgreSQL. Specifically: - -- in case of new role, it will omit the `VALID UNTIL` clause in the role - creation statement -- in case of existing role, it will set `VALID UNTIL` to `infinity` if `VALID - UNTIL` was not set to `NULL` in the database (this is due to PostgreSQL not - allowing `VALID UNTIL NULL` in the `ALTER ROLE` SQL statement) - -### Pre-hashed passwords - -You can also provide pre-encrypted passwords by specifying the password -in MD5/SCRAM-SHA-256 hash format: - -```yaml -kind: Secret -type: kubernetes.io/basic-auth -metadata: - name: cluster-example-cavalcanti - labels: - k8s.enterprisedb.io/reload: "true" -apiVersion: v1 -stringData: - username: cavalcanti - password: SCRAM-SHA-256$:$: -``` - -!!!warning - -The example above uses `stringData:`, where Kubernetes encodes the value -for you, which is the safest path for pre-hashed passwords. If you must -use `data:`, encode the bytes exactly with `printf '%s' "$hash" | base64` -(or `echo -n "$hash" | base64`). A trailing newline from a naive -`echo "$hash" | base64` makes the value miss the SCRAM/MD5 shadow-format -check, so the operator falls back to treating it as cleartext and -re-hashes it, and login stops working. -!!! - -### Safety when transmitting cleartext passwords - -Role passwords are safely managed in Kubernetes using Secrets, but the -SQL path between the operator and PostgreSQL is also a concern. As noted -in the [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-createrole.html): - -> The password will be transmitted to the server in cleartext, and it might -> also be logged in the client's command history or the server log - -{{name.ln}} protects this path in two complementary ways: - -1. Before emitting `CREATE`/`ALTER ROLE ... PASSWORD '...'`, the operator - SCRAM-SHA-256 encodes any cleartext password operator-side (client-side - from PostgreSQL's point of view). This is the standard PostgreSQL - practice for keeping cleartext out of server logs and extensions like - `pg_stat_statements` or `pgaudit`, and is the same encoding that - `psql \password` and libpq's `PQencryptPasswordConn` perform. The - literal PostgreSQL receives is the SCRAM-SHA-256 verifier stored in - `pg_authid.rolpassword`. Passwords already provided in MD5 or - SCRAM-SHA-256 shadow form are forwarded unchanged. -2. The same `CREATE`/`ALTER ROLE` statements are executed inside a - transaction that temporarily suppresses both statement logging - (`log_statement`) and error statement logging - (`log_min_error_statement`), preventing leakage to the PostgreSQL log - in both success and failure scenarios. - -The Status section of the cluster does not print the query statement for any -managed role operation. - -#### Opting out of operator-side encoding - -If you need PostgreSQL (not the operator) to decide how the password is -hashed (for example, on a cluster running `password_encryption = md5`), -set the annotation `k8s.enterprisedb.io/passwordPassthrough: "enabled"` on the -basic-auth Secret. The operator will then forward the password value -verbatim. - -!!!warning - -The `k8s.enterprisedb.io/passwordPassthrough` annotation must be set on the -**basic-auth Secret** itself, not on the `Cluster` resource. Placing it -on the `Cluster` has no effect, and the operator will continue to apply -SCRAM-SHA-256 encoding to the password before sending it to PostgreSQL. -!!! - -The opt-in is per-Secret and applies to every basic-auth Secret the -operator consumes (managed-role secrets, but also the superuser and -application-user secrets), so a single cluster can mix passthrough -secrets and operator-encoded secrets freely. The statement-logging -suppression layer described above still applies in both modes. - -!!!warning - -With `k8s.enterprisedb.io/passwordPassthrough: "enabled"`, the operator forwards -the Secret's `password` value verbatim. If that value is cleartext (the -common case on a `password_encryption = md5` cluster), extensions such -as `pg_stat_statements` or `pgaudit` will observe it. This is the -expected trade-off for letting PostgreSQL choose the hash format. -!!! - -## Unrealizable role configurations - -In PostgreSQL, in some cases, commands cannot be honored by the database and -will be rejected. Please refer to the -[PostgreSQL documentation on error codes](https://www.postgresql.org/docs/current/errcodes-appendix.html) -for details. - -Role operations can produce such fundamental errors. -Two examples: - -- We ask PostgreSQL to create the role `petrarca` as a member of the role - (group) `poets`, but `poets` does not exist. -- We ask PostgreSQL to drop the role `dante`, but the role `dante` is the owner - of the database `inferno`. - -These fundamental errors cannot be fixed by the database, nor the {{name.ln}} -operator, without clarification from the human administrator. The two examples -above could be fixed by creating the role `poets` or dropping the database -`inferno` respectively, but they might have originated due to human error, and -in such case, the "fix" proposed might be the wrong thing to do. - -{{name.ln}} will record when such fundamental errors occur, and will display -them in the cluster Status, as described in -[Status of inline managed roles](#status-of-inline-managed-roles). diff --git a/product_docs/docs/postgres_for_kubernetes/preview/default-monitoring.yaml b/product_docs/docs/postgres_for_kubernetes/preview/default-monitoring.yaml deleted file mode 100644 index be2dc2bf2dc..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/default-monitoring.yaml +++ /dev/null @@ -1,491 +0,0 @@ ---- -apiVersion: v1 -kind: ConfigMap -metadata: - name: default-monitoring - labels: - k8s.enterprisedb.io/reload: "" -data: - queries: | - backends: - query: | - SELECT sa.datname - , sa.usename - , sa.application_name - , states.state - , COALESCE(sa.count, 0) AS total - , COALESCE(sa.max_tx_secs, 0) AS max_tx_duration_seconds - FROM ( VALUES ('active') - , ('idle') - , ('idle in transaction') - , ('idle in transaction (aborted)') - , ('fastpath function call') - , ('disabled') - ) AS states(state) - LEFT JOIN ( - SELECT datname - , state - , usename - , COALESCE(application_name, '') AS application_name - , pg_catalog.count(*) - , COALESCE(EXTRACT (EPOCH FROM (pg_catalog.max(pg_catalog.now() OPERATOR(pg_catalog.-) xact_start))), 0) AS max_tx_secs - FROM pg_catalog.pg_stat_activity - GROUP BY datname, state, usename, application_name - ) sa ON states.state OPERATOR(pg_catalog.=) sa.state - WHERE sa.usename IS NOT NULL - metrics: - - datname: - usage: "LABEL" - description: "Name of the database" - - usename: - usage: "LABEL" - description: "Name of the user" - - application_name: - usage: "LABEL" - description: "Name of the application" - - state: - usage: "LABEL" - description: "State of the backend" - - total: - usage: "GAUGE" - description: "Number of backends" - - max_tx_duration_seconds: - usage: "GAUGE" - description: "Maximum duration of a transaction in seconds" - - backends_waiting: - query: | - SELECT pg_catalog.count(*) AS total - FROM pg_catalog.pg_locks blocked_locks - JOIN pg_catalog.pg_locks blocking_locks - ON blocking_locks.locktype OPERATOR(pg_catalog.=) blocked_locks.locktype - AND blocking_locks.database IS NOT DISTINCT FROM blocked_locks.database - AND blocking_locks.relation IS NOT DISTINCT FROM blocked_locks.relation - AND blocking_locks.page IS NOT DISTINCT FROM blocked_locks.page - AND blocking_locks.tuple IS NOT DISTINCT FROM blocked_locks.tuple - AND blocking_locks.virtualxid IS NOT DISTINCT FROM blocked_locks.virtualxid - AND blocking_locks.transactionid IS NOT DISTINCT FROM blocked_locks.transactionid - AND blocking_locks.classid IS NOT DISTINCT FROM blocked_locks.classid - AND blocking_locks.objid IS NOT DISTINCT FROM blocked_locks.objid - AND blocking_locks.objsubid IS NOT DISTINCT FROM blocked_locks.objsubid - AND blocking_locks.pid OPERATOR(pg_catalog.<>) blocked_locks.pid - JOIN pg_catalog.pg_stat_activity blocking_activity ON blocking_activity.pid OPERATOR(pg_catalog.=) blocking_locks.pid - WHERE NOT blocked_locks.granted - metrics: - - total: - usage: "GAUGE" - description: "Total number of backends that are currently waiting on other queries" - - pg_database: - query: | - SELECT datname - , pg_catalog.pg_database_size(datname) AS size_bytes - , pg_catalog.age(datfrozenxid) AS xid_age - , pg_catalog.mxid_age(datminmxid) AS mxid_age - FROM pg_catalog.pg_database - WHERE datallowconn - metrics: - - datname: - usage: "LABEL" - description: "Name of the database" - - size_bytes: - usage: "GAUGE" - description: "Disk space used by the database" - - xid_age: - usage: "GAUGE" - description: "Number of transactions from the frozen XID to the current one" - - mxid_age: - usage: "GAUGE" - description: "Number of multiple transactions (Multixact) from the frozen XID to the current one" - - pg_postmaster: - query: | - SELECT EXTRACT(EPOCH FROM pg_postmaster_start_time) AS start_time - FROM pg_catalog.pg_postmaster_start_time() - metrics: - - start_time: - usage: "GAUGE" - description: "Time at which postgres started (based on epoch)" - - pg_replication: - query: "SELECT CASE WHEN ( - NOT pg_catalog.pg_is_in_recovery() - OR pg_catalog.pg_last_wal_receive_lsn() OPERATOR(pg_catalog.=) pg_catalog.pg_last_wal_replay_lsn()) - THEN 0 - ELSE GREATEST (0, - EXTRACT(EPOCH FROM (pg_catalog.now() OPERATOR(pg_catalog.-) pg_catalog.pg_last_xact_replay_timestamp()))) - END AS lag, - pg_catalog.pg_is_in_recovery() AS in_recovery, - EXISTS (TABLE pg_catalog.pg_stat_wal_receiver) AS is_wal_receiver_up, - (SELECT pg_catalog.count(*) FROM pg_catalog.pg_stat_replication) AS streaming_replicas" - metrics: - - lag: - usage: "GAUGE" - description: "Replication lag behind primary in seconds" - - in_recovery: - usage: "GAUGE" - description: "Whether the instance is in recovery" - - is_wal_receiver_up: - usage: "GAUGE" - description: "Whether the instance wal_receiver is up" - - streaming_replicas: - usage: "GAUGE" - description: "Number of streaming replicas connected to the instance" - - pg_replication_slots: - query: | - SELECT slot_name, - slot_type, - database, - active, - (CASE pg_catalog.pg_is_in_recovery() - WHEN TRUE THEN pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_last_wal_receive_lsn(), restart_lsn) - ELSE pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), restart_lsn) - END) as pg_wal_lsn_diff - FROM pg_catalog.pg_replication_slots - WHERE NOT temporary - metrics: - - slot_name: - usage: "LABEL" - description: "Name of the replication slot" - - slot_type: - usage: "LABEL" - description: "Type of the replication slot" - - database: - usage: "LABEL" - description: "Name of the database" - - active: - usage: "GAUGE" - description: "Flag indicating whether the slot is active" - - pg_wal_lsn_diff: - usage: "GAUGE" - description: "Replication lag in bytes" - - pg_stat_archiver: - query: | - SELECT archived_count - , failed_count - , COALESCE(EXTRACT(EPOCH FROM (pg_catalog.now() OPERATOR(pg_catalog.-) last_archived_time)), -1) AS seconds_since_last_archival - , COALESCE(EXTRACT(EPOCH FROM (pg_catalog.now() OPERATOR(pg_catalog.-) last_failed_time)), -1) AS seconds_since_last_failure - , COALESCE(EXTRACT(EPOCH FROM last_archived_time), -1) AS last_archived_time - , COALESCE(EXTRACT(EPOCH FROM last_failed_time), -1) AS last_failed_time - , COALESCE(CAST(CAST('x' OPERATOR(pg_catalog.||) pg_catalog.right(pg_catalog.split_part(last_archived_wal, '.', 1), 16) AS pg_catalog.bit(64)) AS pg_catalog.int8), -1) AS last_archived_wal_start_lsn - , COALESCE(CAST(CAST('x' OPERATOR(pg_catalog.||) pg_catalog.right(pg_catalog.split_part(last_failed_wal, '.', 1), 16) AS pg_catalog.bit(64)) AS pg_catalog.int8), -1) AS last_failed_wal_start_lsn - , EXTRACT(EPOCH FROM stats_reset) AS stats_reset_time - FROM pg_catalog.pg_stat_archiver - predicate_query: | - SELECT NOT pg_catalog.pg_is_in_recovery() - OR pg_catalog.current_setting('archive_mode') OPERATOR(pg_catalog.=) 'always' - metrics: - - archived_count: - usage: "COUNTER" - description: "Number of WAL files that have been successfully archived" - - failed_count: - usage: "COUNTER" - description: "Number of failed attempts for archiving WAL files" - - seconds_since_last_archival: - usage: "GAUGE" - description: "Seconds since the last successful archival operation" - - seconds_since_last_failure: - usage: "GAUGE" - description: "Seconds since the last failed archival operation" - - last_archived_time: - usage: "GAUGE" - description: "Epoch of the last time WAL archiving succeeded" - - last_failed_time: - usage: "GAUGE" - description: "Epoch of the last time WAL archiving failed" - - last_archived_wal_start_lsn: - usage: "GAUGE" - description: "Archived WAL start LSN" - - last_failed_wal_start_lsn: - usage: "GAUGE" - description: "Last failed WAL LSN" - - stats_reset_time: - usage: "GAUGE" - description: "Time at which these statistics were last reset" - - pg_stat_bgwriter: - runonserver: "<17.0.0" - query: | - SELECT checkpoints_timed - , checkpoints_req - , checkpoint_write_time - , checkpoint_sync_time - , buffers_checkpoint - , buffers_clean - , maxwritten_clean - , buffers_backend - , buffers_backend_fsync - , buffers_alloc - FROM pg_catalog.pg_stat_bgwriter - metrics: - - checkpoints_timed: - usage: "COUNTER" - description: "Number of scheduled checkpoints that have been performed" - - checkpoints_req: - usage: "COUNTER" - description: "Number of requested checkpoints that have been performed" - - checkpoint_write_time: - usage: "COUNTER" - description: "Total amount of time that has been spent in the portion of checkpoint processing where files are written to disk, in milliseconds" - - checkpoint_sync_time: - usage: "COUNTER" - description: "Total amount of time that has been spent in the portion of checkpoint processing where files are synchronized to disk, in milliseconds" - - buffers_checkpoint: - usage: "COUNTER" - description: "Number of buffers written during checkpoints" - - buffers_clean: - usage: "COUNTER" - description: "Number of buffers written by the background writer" - - maxwritten_clean: - usage: "COUNTER" - description: "Number of times the background writer stopped a cleaning scan because it had written too many buffers" - - buffers_backend: - usage: "COUNTER" - description: "Number of buffers written directly by a backend" - - buffers_backend_fsync: - usage: "COUNTER" - description: "Number of times a backend had to execute its own fsync call (normally the background writer handles those even when the backend does its own write)" - - buffers_alloc: - usage: "COUNTER" - description: "Number of buffers allocated" - - pg_stat_bgwriter_17: - runonserver: ">=17.0.0" - name: pg_stat_bgwriter - query: | - SELECT buffers_clean - , maxwritten_clean - , buffers_alloc - , EXTRACT(EPOCH FROM stats_reset) AS stats_reset_time - FROM pg_catalog.pg_stat_bgwriter - metrics: - - buffers_clean: - usage: "COUNTER" - description: "Number of buffers written by the background writer" - - maxwritten_clean: - usage: "COUNTER" - description: "Number of times the background writer stopped a cleaning scan because it had written too many buffers" - - buffers_alloc: - usage: "COUNTER" - description: "Number of buffers allocated" - - stats_reset_time: - usage: "GAUGE" - description: "Time at which these statistics were last reset" - - pg_stat_checkpointer: - runonserver: ">=17.0.0" - query: | - SELECT num_timed AS checkpoints_timed - , num_requested AS checkpoints_req - , restartpoints_timed - , restartpoints_req - , restartpoints_done - , write_time - , sync_time - , buffers_written - , EXTRACT(EPOCH FROM stats_reset) AS stats_reset_time - FROM pg_catalog.pg_stat_checkpointer - metrics: - - checkpoints_timed: - usage: "COUNTER" - description: "Number of scheduled checkpoints that have been performed" - - checkpoints_req: - usage: "COUNTER" - description: "Number of requested checkpoints that have been performed" - - restartpoints_timed: - usage: "COUNTER" - description: "Number of scheduled restartpoints due to timeout or after a failed attempt to perform it" - - restartpoints_req: - usage: "COUNTER" - description: "Number of requested restartpoints that have been performed" - - restartpoints_done: - usage: "COUNTER" - description: "Number of restartpoints that have been performed" - - write_time: - usage: "COUNTER" - description: "Total amount of time that has been spent in the portion of processing checkpoints and restartpoints where files are written to disk, in milliseconds" - - sync_time: - usage: "COUNTER" - description: "Total amount of time that has been spent in the portion of processing checkpoints and restartpoints where files are synchronized to disk, in milliseconds" - - buffers_written: - usage: "COUNTER" - description: "Number of buffers written during checkpoints and restartpoints" - - stats_reset_time: - usage: "GAUGE" - description: "Time at which these statistics were last reset" - - pg_stat_database: - query: | - SELECT datname - , xact_commit - , xact_rollback - , blks_read - , blks_hit - , tup_returned - , tup_fetched - , tup_inserted - , tup_updated - , tup_deleted - , conflicts - , temp_files - , temp_bytes - , deadlocks - , blk_read_time - , blk_write_time - FROM pg_catalog.pg_stat_database - metrics: - - datname: - usage: "LABEL" - description: "Name of this database" - - xact_commit: - usage: "COUNTER" - description: "Number of transactions in this database that have been committed" - - xact_rollback: - usage: "COUNTER" - description: "Number of transactions in this database that have been rolled back" - - blks_read: - usage: "COUNTER" - description: "Number of disk blocks read in this database" - - blks_hit: - usage: "COUNTER" - description: "Number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL buffer cache, not the operating system's file system cache)" - - tup_returned: - usage: "COUNTER" - description: "Number of rows returned by queries in this database" - - tup_fetched: - usage: "COUNTER" - description: "Number of rows fetched by queries in this database" - - tup_inserted: - usage: "COUNTER" - description: "Number of rows inserted by queries in this database" - - tup_updated: - usage: "COUNTER" - description: "Number of rows updated by queries in this database" - - tup_deleted: - usage: "COUNTER" - description: "Number of rows deleted by queries in this database" - - conflicts: - usage: "COUNTER" - description: "Number of queries canceled due to conflicts with recovery in this database" - - temp_files: - usage: "COUNTER" - description: "Number of temporary files created by queries in this database" - - temp_bytes: - usage: "COUNTER" - description: "Total amount of data written to temporary files by queries in this database" - - deadlocks: - usage: "COUNTER" - description: "Number of deadlocks detected in this database" - - blk_read_time: - usage: "COUNTER" - description: "Time spent reading data file blocks by backends in this database, in milliseconds" - - blk_write_time: - usage: "COUNTER" - description: "Time spent writing data file blocks by backends in this database, in milliseconds" - - pg_stat_replication: - primary: true - query: | - SELECT usename - , COALESCE(application_name, '') AS application_name - , COALESCE(client_addr::text, '') AS client_addr - , COALESCE(client_port::text, '') AS client_port - , EXTRACT(EPOCH FROM backend_start) AS backend_start - , COALESCE(pg_catalog.age(backend_xmin), 0) AS backend_xmin_age - , pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), sent_lsn) AS sent_diff_bytes - , pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), write_lsn) AS write_diff_bytes - , pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), flush_lsn) AS flush_diff_bytes - , COALESCE(pg_catalog.pg_wal_lsn_diff(pg_catalog.pg_current_wal_lsn(), replay_lsn),0) AS replay_diff_bytes - , COALESCE((EXTRACT(EPOCH FROM write_lag)),0)::float AS write_lag_seconds - , COALESCE((EXTRACT(EPOCH FROM flush_lag)),0)::float AS flush_lag_seconds - , COALESCE((EXTRACT(EPOCH FROM replay_lag)),0)::float AS replay_lag_seconds - FROM pg_catalog.pg_stat_replication - metrics: - - usename: - usage: "LABEL" - description: "Name of the replication user" - - application_name: - usage: "LABEL" - description: "Name of the application" - - client_addr: - usage: "LABEL" - description: "Client IP address" - - client_port: - usage: "LABEL" - description: "Client TCP port" - - backend_start: - usage: "COUNTER" - description: "Time when this process was started" - - backend_xmin_age: - usage: "COUNTER" - description: "The age of this standby's xmin horizon" - - sent_diff_bytes: - usage: "GAUGE" - description: "Difference in bytes from the last write-ahead log location sent on this connection" - - write_diff_bytes: - usage: "GAUGE" - description: "Difference in bytes from the last write-ahead log location written to disk by this standby server" - - flush_diff_bytes: - usage: "GAUGE" - description: "Difference in bytes from the last write-ahead log location flushed to disk by this standby server" - - replay_diff_bytes: - usage: "GAUGE" - description: "Difference in bytes from the last write-ahead log location replayed into the database on this standby server" - - write_lag_seconds: - usage: "GAUGE" - description: "Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written it" - - flush_lag_seconds: - usage: "GAUGE" - description: "Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written and flushed it" - - replay_lag_seconds: - usage: "GAUGE" - description: "Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written, flushed and applied it" - - pg_settings: - query: | - SELECT name, - CASE setting WHEN 'on' THEN '1' WHEN 'off' THEN '0' ELSE setting END AS setting - FROM pg_catalog.pg_settings - WHERE vartype IN ('integer', 'real', 'bool') - ORDER BY 1 - metrics: - - name: - usage: "LABEL" - description: "Name of the setting" - - setting: - usage: "GAUGE" - description: "Setting value" - - pg_extensions: - query: | - SELECT - pg_catalog.current_database() as datname, - name as extname, - default_version, - installed_version, - CASE - WHEN default_version OPERATOR(pg_catalog.=) installed_version THEN 0 - ELSE 1 - END AS update_available - FROM pg_catalog.pg_available_extensions - WHERE installed_version IS NOT NULL - metrics: - - datname: - usage: "LABEL" - description: "Name of the database" - - extname: - usage: "LABEL" - description: "Extension name" - - default_version: - usage: "LABEL" - description: "Default version" - - installed_version: - usage: "LABEL" - description: "Installed version" - - update_available: - usage: "GAUGE" - description: "An update is available" - target_databases: - - '*' diff --git a/product_docs/docs/postgres_for_kubernetes/preview/evaluation.mdx b/product_docs/docs/postgres_for_kubernetes/preview/evaluation.mdx deleted file mode 100644 index fe5b1668150..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/evaluation.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: 'Free evaluation' -originalFilePath: 'src/evaluation.md' ---- - -{{name.ln}} is available for a free evaluation. - -Use your EDB account to evaluate {{name.ln}}. If you don't have an account, [register](https://www.enterprisedb.com/accounts/register) for one. Then follow the [installation guide](installation_upgrade.md) to install the operator, using the access token you obtained from your EDB account. - -## Evaluating using PostgreSQL - -By default, {{name.ln}} installs the latest available version of Community Postgresql. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/failover.mdx b/product_docs/docs/postgres_for_kubernetes/preview/failover.mdx deleted file mode 100644 index ec966611d27..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/failover.mdx +++ /dev/null @@ -1,569 +0,0 @@ ---- -title: 'Automated failover' -originalFilePath: 'src/failover.md' ---- - - - -In the case of unexpected errors on the primary for longer than the -`.spec.failoverDelay` (by default `0` seconds), the cluster will go into -**failover mode**. This may happen, for example, when: - -- The primary pod has a disk failure -- The primary pod is deleted -- The `postgres` container on the primary has any kind of sustained failure - -In the failover scenario, the primary cannot be assumed to be working properly. - -After cases like the ones above, the readiness probe for the primary pod will start -failing. This will be picked up in the controller's reconciliation loop. The -controller will initiate the failover process, in two steps: - -1. First, it will mark the `TargetPrimary` as `pending`. This change of state will - force the primary pod to shutdown, to ensure the WAL receivers on the replicas - will stop. The cluster will be marked in failover phase ("Failing over"). -2. Once all WAL receivers are stopped, there will be a leader election, and a - new primary will be named. The chosen instance will initiate promotion to - primary, and, after this is completed, the cluster will resume normal operations. - Meanwhile, the former primary pod will restart, detect that it is no longer - the primary, and become a replica node. - -!!!info Important -The two-phase procedure helps ensure the WAL receivers can stop in an orderly -fashion, and that the failing primary will not start streaming WALs again upon -restart. These safeguards prevent timeline discrepancies between the new primary -and the replicas. -!!! - -During the time the failing primary is being shut down: - -1. It will first try a PostgreSQL's *fast shutdown* with - `.spec.switchoverDelay` seconds as timeout. This graceful shutdown will attempt - to archive pending WALs. -2. If the fast shutdown fails, or its timeout is exceeded, a PostgreSQL's - *immediate shutdown* is initiated. - -!!!info -"Fast" mode does not wait for PostgreSQL clients to disconnect and will -terminate an online backup in progress. All active transactions are rolled back -and clients are forcibly disconnected, then the server is shut down. -"Immediate" mode will abort all PostgreSQL server processes immediately, -without a clean shutdown. -!!! - -## Safe primary election - -To ensure that at most one instance promotes itself to primary at any -given time, {{name.ln}} backs the election described above with a -Kubernetes `Lease` object, named after the `Cluster` and living in -its namespace. An instance must acquire and hold this lease before -it promotes to primary. On a clean shutdown the former primary -releases the lease, so an eligible replica can take over without -waiting for the lease to expire. - -### What the primary lease protects against - -Consider a replica catching up by reading WAL files from the archive -rather than streaming from the previous primary. PostgreSQL stops -replaying as soon as the archive returns "file not found" for the -next expected segment, treating it as the end of the WAL stream. If -a replica promotes while the previous primary still has WAL it has -not finished archiving, that signal arrives before the true end of -the stream: the replica forks a new timeline at an LSN earlier than -the last writes the previous primary acknowledged, and those writes -are lost. - -The lease holds promotion back until the previous primary releases -it. On a clean shutdown the release happens after PostgreSQL has -flushed and archived its remaining WAL, so the replica that takes -over sees the archive at its definitive end. If the previous primary -cannot release the lease (crash, node failure, or the instance -manager itself unreachable), the lease expires after -`leaseDurationSeconds` elapses and the replica can promote. In that -path the archive may not have caught up, and any writes the previous -primary did not finish archiving are lost. - -### Relationship with the primary isolation check - -The lease does not fence a primary that has lost connectivity to the -Kubernetes API server but is still running; that is the job of the -[primary isolation](instance_manager.md#primary-isolation) check. -The two mechanisms are complementary and both are enabled by default: - -- The lease prevents *premature* promotion: a replica cannot promote - while the former primary still holds the lease. -- The isolation check stops an *isolated* primary from continuing to - accept writes. - -Keep both enabled. Disabling the isolation check leaves the lease -alone responsible for primary safety, and the lease alone cannot -prevent split-brain when the former primary cannot reach the API -server but remains otherwise healthy. - -### Inspecting the primary lease - -The lease shares the cluster's name, so you can inspect it directly. For a -cluster called `cluster-example`: - -```sh -kubectl get lease cluster-example -``` - -The `HOLDER` column reports the pod that currently holds the lease, which is the -current primary: - -```console -NAME HOLDER AGE -cluster-example cluster-example-1 5m -``` - -For the full picture, including the lease duration in effect and the -last renewal time, use: - -```sh -kubectl get lease cluster-example -o yaml -``` - -### Tuning the primary lease - -The lease timings are exposed under `.spec.primaryLease` and default to values -suitable for most clusters. They map directly onto the underlying Kubernetes -leader-election parameters. - -| Field | Default | Description | -| ------------------------------ | ------- | ------------------------------------------------------------------------ | -| `leaseDurationSeconds` | `15` | How long the lease is valid before another instance may acquire it. | -| `renewDeadlineSeconds` | `10` | How long the primary keeps retrying to renew the lease before giving up. | -| `retryPeriodSeconds` | `2` | How frequently a non-holder retries acquiring or renewing the lease. | -| `releasedLeaseDurationSeconds` | `1` | TTL written when the primary releases the lease on a clean shutdown. | - -For example, to make the cluster more tolerant of a slow or briefly unreachable -API server: - -```yaml -spec: - primaryLease: - leaseDurationSeconds: 60 - renewDeadlineSeconds: 40 - retryPeriodSeconds: 15 -``` - -!!!warning - -Tune these values only if you understand the impact on failover timing: longer -intervals make the cluster more tolerant of transient API server unavailability -but slow down legitimate promotions. Two invariants are enforced by the -admission webhook: `leaseDurationSeconds` must be greater than -`renewDeadlineSeconds`, and `renewDeadlineSeconds` must be greater than -`retryPeriodSeconds` multiplied by `1.2`. Both mirror the requirements of the -underlying Kubernetes leader election. -!!! - -!!!note - -`leaseDurationSeconds` and `retryPeriodSeconds` govern two different timings. -After an abrupt primary loss (the previous primary did not release the lease), a -candidate must observe the lease unchanged for a full `leaseDurationSeconds` -before it may take over: this is what holds back a premature promotion while the -former primary may still be alive. After a clean switchover (the previous primary -released the lease), there is no such wait; the candidate simply notices the -released lease on its next poll, so the hand-over latency is bounded by -`retryPeriodSeconds`. Lowering `retryPeriodSeconds` speeds up switchover without -shortening the take-over wait that guards against premature promotion, at the -cost of more frequent lease renewals against the API server. -!!! - -!!!note - -The primary instance captures these timings the first time it acquires the -lease. Changing `.spec.primaryLease` on a running cluster therefore takes effect -only after the affected primary Pod restarts; until then the primary keeps using -the values it started with. -!!! - -## RTO and RPO impact - -Failover may result in the service being impacted ([RTO](before_you_start.md#postgresql-terminology)) -and/or data being lost ([RPO](before_you_start.md#postgresql-terminology)): - -1. During the time when the primary has started to fail, and before the controller - starts failover procedures, queries in transit, WAL writes, checkpoints and - similar operations, may fail. -2. Once the fast shutdown command has been issued, the cluster will no longer - accept connections, so service will be impacted but no data - will be lost. -3. If the fast shutdown fails, the immediate shutdown will stop any pending - processes, including WAL writing. Data may be lost. -4. During the time the primary is shutting down and a new primary hasn't yet - started, the cluster will operate without a primary and thus be impaired - but - with no data loss. - -!!!note -The timeout that controls fast shutdown is set by `.spec.switchoverDelay`, -as in the case of a switchover. Increasing the time for fast shutdown is safer -from an RPO point of view, but possibly delays the return to normal operation - -negatively affecting RTO. -!!! - -!!!warning -As already mentioned in the ["Instance Manager" section](instance_manager.md) -when explaining the switchover process, the `.spec.switchoverDelay` option -affects the RPO and RTO of your PostgreSQL database. Setting it to a low value, -might favor RTO over RPO but lead to data loss at cluster level and/or backup -level. On the contrary, setting it to a high value, might remove the risk of -data loss while leaving the cluster without an active primary for a longer time -during the switchover. -!!! - -## Delayed failover - -As anticipated above, the `.spec.failoverDelay` option allows you to delay the start -of the failover procedure by a number of seconds after the primary has been -detected to be unhealthy. By default, this setting is set to `0`, triggering the -failover procedure immediately. - -Sometimes failing over to a new primary can be more disruptive than waiting -for the primary to come back online. This is especially true of network -disruptions where multiple tiers are affected (i.e., downstream logical -subscribers) or when the time to perform the failover is longer than the -expected outage. - -Enabling a new configuration option to delay failover provides a mechanism to -prevent premature failover for short-lived network or node instability. - -## Detection of node-level failures - -When the node hosting the primary becomes unreachable (for example, due to a -kubelet crash or a network partition between the node and the Kubernetes API -server), the operator relies on the pod's `Ready` condition to decide that the -primary is no longer serviceable. While the node is healthy the kubelet keeps -that condition up to date from the readiness probe; once the node stops -reporting, the Kubernetes node lifecycle controller is the one that flips the -condition to `False` as soon as it declares the node `Unknown`. - -With stock kube-controller-manager settings, the transition is governed by -`--node-monitor-grace-period` (default `40s` on Kubernetes 1.29-1.31, raised -to `50s` in 1.32 and later): after that window the controller marks the node -`Unknown` and, in the same monitoring pass, issues a patch per pod on that -node to flip the `Ready` condition. In practice the operator observes the -primary as unready about **40 to 55 seconds** after the node becomes -unreachable (the grace period plus up to one `--node-monitor-period` poll, -default `5s`). Managed Kubernetes distributions (GKE, EKS, AKS) may tune -these values; consult the provider's documentation if the observed timing -does not match. After that, the failover procedure starts (further gated by -`.spec.failoverDelay`). - -The `Ready` condition flip is not subject to the rate limiters that throttle -pod *eviction* during partial-zonal or large-cluster disruptions -(`--node-eviction-rate`, `--secondary-node-eviction-rate`, -`--unhealthy-zone-threshold`). The operator reacts to the condition flip as -soon as the controller emits the patch, regardless of the zone or cluster-wide -health state. - -Pod *eviction* (actual deletion from the unreachable node) is a separate -mechanism, driven by `tolerationSeconds` on the -`node.kubernetes.io/unreachable` `NoExecute` taint (`300s` by default). That -timer does not hold up the operator's failover decision; {{name.ln}} -promotes a new primary as soon as the `Ready` condition flips. By that point -the kubelet on the isolated node has already stopped the old PostgreSQL -container locally: with the default -`.spec.probes.liveness.isolationCheck.enabled: true`, the instance manager -fails its own liveness probe once it can reach neither the API server nor -the rest of the cluster, and the kubelet kills the container within -approximately three probe periods (`~30s`). Full high availability -(recreation of the old primary on a healthy node by the operator) is still -gated on the taint-based eviction actually deleting the pod. - -## Failover Quorum (Quorum-based Failover) - -Failover quorum is a mechanism that enhances data durability and safety during -failover events in {{name.ln}}-managed PostgreSQL clusters. - -Quorum-based failover allows the controller to determine whether to promote a replica -to primary based on the state of a quorum of replicas. -This is useful when stronger data durability is required than the one offered -by [synchronous replication](replication.md#synchronous-replication) and -default automated failover procedures. - -When synchronous replication is not enabled, some data loss is expected and -accepted during failover, as a replica may lag behind the primary when -promoted. - -With synchronous replication enabled, the guarantee is that the application -will not receive explicit acknowledgment of the successful commit of a -transaction until the WAL data is known to be safely received by all required -synchronous standbys. -This is not enough to guarantee that the operator is able to promote the most -advanced replica. - -For example, in a three-node cluster with synchronous replication set to `ANY 1 -(...)`, data is written to the primary and one standby before a commit is -acknowledged. If both the primary and the aligned standby become unavailable -(such as during a network partition), the remaining replica may not have the -latest data. Promoting it could lose some data that the application considered -committed. - -Quorum-based failover addresses this risk by ensuring that failover only occurs -if the operator can confirm the presence of all synchronously committed data in -the instance to promote, and it does not occur otherwise. - -This feature allows users to choose their preferred trade-off between data -durability and data availability. - -Failover quorum can be enabled by setting the -`.spec.postgresql.synchronous.failoverQuorum` field to `true`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - - postgresql: - synchronous: - method: any - number: 1 - failoverQuorum: true - - storage: - size: 1Gi -``` - -For backward compatibility, the legacy annotation -`alpha.k8s.enterprisedb.io/failoverQuorum` is still supported by the admission webhook and -takes precedence over the `Cluster` spec option: - -- If the annotation evaluates to `"true"` and a synchronous replication stanza - is present, the webhook automatically sets - `.spec.postgresql.synchronous.failoverQuorum` to `true`. -- If the annotation evaluates to `"false"`, the feature is always disabled - -!!!info Important -Because the annotation overrides the spec, we recommend that users of this -experimental feature migrate to the native -`.spec.postgresql.synchronous.failoverQuorum` option and remove the annotation -from their manifests. The annotation is **deprecated** and will be removed in a -future release. -!!! - -### How it works - -Before promoting a replica to primary, the operator performs a quorum check, -following the principles of the Dynamo `R + W > N` consistency model[^1]. - -In the quorum failover, these values assume the following meaning: - -- `R` is the number of *promotable replicas* (read quorum); -- `W` is the number of replicas that must acknowledge the write before the - `COMMIT` is returned to the client (write quorum); -- `N` is the total number of potentially synchronous replicas; - -*Promotable replicas* are replicas that have these properties: - -- are part of the cluster; -- are able to report their state to the operator; -- are potentially synchronous; - -If `R + W > N`, then we can be sure that among the promotable replicas there is -at least one that has confirmed all the synchronous commits, and we can safely -promote it to primary. If this is not the case, the controller will not promote -any replica to primary, and will wait for the situation to change. - -Users can force a promotion of a replica to primary through the -`kubectl cnp promote` command even if the quorum check is failing. - -!!!warning -Manual promotion should only be used as a last resort. Before proceeding, -make sure you fully understand the risk of data loss and carefully consider the -consequences of prioritizing the resumption of write workloads for your -applications. -!!! - -An additional CRD is used to track the quorum state of the cluster. A `Cluster` -with the quorum failover enabled will have a `FailoverQuorum` resource with the same -name as the `Cluster` resource. The `FailoverQuorum` CR is created by the -controller when the quorum failover is enabled, and it is updated by the primary -instance during its reconciliation loop, and read by the operator during quorum -checks. It is used to track the latest known configuration of the synchronous -replication. - -!!!info Important -Users should not modify the `FailoverQuorum` resource directly. During -PostgreSQL configuration changes, when it is not possible to determine the -configuration, the `FailoverQuorum` resource will be reset, preventing any -failover until the new configuration is applied. -!!! - -The `FailoverQuorum` resource works in conjunction with PostgreSQL synchronous -replication. - -!!!warning -There is no guarantee that `COMMIT` operations returned to the -client but that have not been performed synchronously, such as those made -explicitly disabling synchronous replication with -`SET synchronous_commit TO local`, will be present on a promoted replica. -!!! - -### Quorum Failover Example Scenarios - -In the following scenarios, `R` is the number of promotable replicas, `W` is -the number of replicas that must acknowledge a write before commit, and `N` is -the total number of potentially synchronous replicas. The "Failover" column -indicates whether failover is allowed under quorum failover rules. - -#### Scenario 1: Three-node cluster, failing pod(s) - -A cluster with `instances: 3`, `synchronous.number=1`, and -`dataDurability=required`. - -- If only the primary fails, two promotable replicas remain (R=2). - Since `R + W > N` (2 + 1 > 2), failover is allowed and safe. -- If both the primary and one replica fail, only one promotable replica - remains (R=1). Since `R + W = N` (1 + 1 = 2), failover is not allowed to - prevent possible data loss. - -| R | W | N | Failover | -| :-: | :-: | :-: | :------: | -| 2 | 1 | 2 | ✅ | -| 1 | 1 | 2 | ❌ | - -#### Scenario 2: Three-node cluster, network partition - -A cluster with `instances: 3`, `synchronous.number: 1`, and -`dataDurability: required` experiences a network partition. - -- If the operator can communicate with the primary, no failover occurs. The - cluster can be impacted if the primary cannot reach any standby, since it - won't commit transactions due to synchronous replication requirements. -- If the operator cannot reach the primary but can reach both replicas (R=2), - failover is allowed. If the operator can reach only one replica (R=1), - failover is not allowed, as the synchronous one may be the other one. - -| R | W | N | Failover | -| :-: | :-: | :-: | :------: | -| 2 | 1 | 2 | ✅ | -| 1 | 1 | 2 | ❌ | - -#### Scenario 3: Five-node cluster, network partition - -A cluster with `instances: 5`, `synchronous.number=2`, and -`dataDurability=required` experiences a network partition. - -- If the operator can communicate with the primary, no failover occurs. The - cluster can be impacted if the primary cannot reach at least two standbys, - as since it won't commit transactions due to synchronous replication - requirements. -- If the operator cannot reach the primary but can reach at least three - replicas (R=3), failover is allowed. If the operator can reach only two - replicas (R=2), failover is not allowed, as the synchronous one may be the - other one. - -| R | W | N | Failover | -| :-: | :-: | :-: | :------: | -| 3 | 2 | 4 | ✅ | -| 2 | 2 | 4 | ❌ | - -#### Scenario 4: Three-node cluster with remote synchronous replicas - -A cluster with `instances: 3` and remote synchronous replicas defined in -`standbyNamesPre` or `standbyNamesPost`. We assume that the primary is failing. - -This scenario requires an important consideration. Replicas listed in -`standbyNamesPre` or `standbyNamesPost` are not counted in -`R` (they cannot be promoted), but are included in `N` (they may have received -synchronous writes). So, if -`synchronous.number <= len(standbyNamesPre) + len(standbyNamesPost)`, failover -is not possible, as no local replica can be guaranteed to have the required -data. The operator prevents such configurations during validation, but some -invalid configurations are shown below for clarity. - -**Example configurations:** - -Configuration #1 (valid): - -```yaml -instances: 3 -postgresql: - synchronous: - method: any - number: 2 - standbyNamesPre: - - angus -``` - -In this configuration, when the primary fails, `R = 2` (the local replicas), -`W = 2`, and `N = 3` (2 local replicas + 1 remote), allowing failover. -In case of an additional replica failing (`R = 1`) failover is not allowed. - -| R | W | N | Failover | -| :-: | :-: | :-: | :------: | -| 3 | 2 | 4 | ✅ | -| 2 | 2 | 4 | ❌ | - -Configuration #2 (invalid): - -```yaml -instances: 3 -postgresql: - synchronous: - method: any - number: 1 - maxStandbyNamesFromCluster: 1 - standbyNamesPre: - - angus -``` - -In this configuration, `R = 2` (the local replicas), `W = 1`, and `N = 3` -(2 local replicas + 1 remote). -Failover is not possible in this setup, so quorum failover can not be -enabled with this configuration. - -| R | W | N | Failover | -| :-: | :-: | :-: | :------: | -| 1 | 1 | 2 | ❌ | - -Configuration #3 (invalid): - -```yaml -instances: 3 -postgresql: - synchronous: - method: any - number: 1 - maxStandbyNamesFromCluster: 0 - standbyNamesPre: - - angus - - malcolm -``` - -In this configuration, `R = 0` (the local replicas), `W = 1`, and `N = 2` -(0 local replicas + 2 remote). -Failover is not possible in this setup, so quorum failover can not be -enabled with this configuration. - -| R | W | N | Failover | -| :-: | :-: | :-: | :------: | -| 0 | 1 | 2 | ❌ | - -#### Scenario 5: Three-node cluster, preferred data durability, network partition - -Consider a cluster with `instances: 3`, `synchronous.number=1`, and -`dataDurability=preferred` that experiences a network partition. - -- If the operator can communicate with both the primary and the API server, - the primary continues to operate, removing unreachable standbys from the - `synchronous_standby_names` set. -- If the primary cannot reach the operator or API server, a quorum check is - performed. The `FailoverQuorum` status cannot have changed, as the primary cannot - have received new configuration. If the operator can reach both replicas, - failover is allowed (`R=2`). If only one replica is reachable (`R=1`), - failover is not allowed. - -| R | W | N | Failover | -| :-: | :-: | :-: | :------: | -| 2 | 1 | 2 | ✅ | -| 1 | 1 | 2 | ❌ | - -[^1]: [Dynamo: Amazon’s highly available key-value store](https://www.amazon.science/publications/dynamo-amazons-highly-available-key-value-store) diff --git a/product_docs/docs/postgres_for_kubernetes/preview/failure_modes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/failure_modes.mdx deleted file mode 100644 index 0318b4a2b4a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/failure_modes.mdx +++ /dev/null @@ -1,90 +0,0 @@ ---- -title: 'Failure Modes' -originalFilePath: 'src/failure_modes.md' ---- - - - -!!!note -In previous versions of {{name.ln}}, this page included specific failure -scenarios. Since these largely follow standard Kubernetes behavior, we have -streamlined the content to avoid duplication of information that belongs to the -underlying Kubernetes stack and is not specific to {{name.ln}}. -!!! - -{{name.ln}} adheres to standard Kubernetes principles for self-healing and -high availability. We assume familiarity with core Kubernetes concepts such as -storage classes, PVCs, nodes, and Pods. For {{name.ln}}-specific details, -refer to the ["Postgres Instance Manager" section](instance_manager.md), which -covers startup, liveness, and readiness probes, as well as the -[self-healing](#self-healing) section below. - -!!!info Important -If you are running {{name.ln}} in production, we strongly recommend -seeking [professional support](https://cloudnative-pg.io/support/). -!!! - -## Self-Healing - -### Primary Failure - -If the primary Pod fails: - -- The operator promotes the most up-to-date standby with the lowest replication - lag. -- The `-rw` service is updated to point to the new primary. -- The failed Pod is removed from the `-r` and `-rw` services. -- Standby Pods begin replicating from the new primary. -- The former primary uses `pg_rewind` to re-synchronize if its PVC is available; - otherwise, a new standby is created from a backup of the new primary. - -### Standby Failure - -If a standby Pod fails: - -- It is removed from the `-r` and `-ro` services. -- The Pod is restarted using its PVC if available; otherwise, a new Pod is - created from a backup of the current primary. -- Once ready, the Pod is re-added to the `-r` and `-ro` services. - -## Manual Intervention - -For failure scenarios not covered by automated recovery, manual intervention -may be required. - -!!!info Important -Do not perform manual operations without [professional support](https://cloudnative-pg.io/support/). -!!! - -### Disabling Reconciliation - -The `k8s.enterprisedb.io/reconciliationLoop` annotation allows you to temporarily disable -the reconciliation loop for {{name.ln}} resources. When set to `"disabled"`, -the operator will stop processing updates for the annotated resource, preventing -any automated changes or self-healing actions. - -Use this annotation **with extreme caution** and only during emergency -operations. - -!!!warning - -This annotation should be removed as soon as the issue is resolved. Leaving -it in place prevents the operator from managing the annotated resource. On a -Cluster, this includes self-healing actions and failover. -!!! - -The following resources support this annotation: - -- **Cluster**: Disables reconciliation of the PostgreSQL cluster -- **Backup**: Disables reconciliation of backup operations - -Example usage: - -```yaml -metadata: - name: cluster-example-no-reconcile - annotations: - k8s.enterprisedb.io/reconciliationLoop: "disabled" -spec: - # ... -``` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/faq.mdx b/product_docs/docs/postgres_for_kubernetes/preview/faq.mdx deleted file mode 100644 index cc4aa8b8706..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/faq.mdx +++ /dev/null @@ -1,406 +0,0 @@ ---- -title: 'Frequently Asked Questions (FAQ)' -originalFilePath: 'src/faq.md' ---- - - - -## Running PostgreSQL in Kubernetes - -**Everyone knows that stateful workloads like PostgreSQL cannot run in -Kubernetes. Why do you say the contrary?** - -An [*independent research survey commissioned by the Data on Kubernetes -Community*](https://dok.community/dokc-2021-report/) in September 2021 -revealed that half of the respondents run most of their production -workloads on Kubernetes. 90% of them believe that Kubernetes is ready -for stateful workloads, and 70% of them run databases in production. -Databases like Postgres. However, according to them, significant -challenges remain, such as the knowledge gap (Kubernetes and Cloud -Native, in general, have a steep learning curve) and the quality of -Kubernetes operators. The latter is the reason why we believe that an -operator like {{name.ln}} highly contributes to the success -of your project. - -For database fanatics like us, a real game-changer has been the -introduction of the support for local persistent volumes in -[*Kubernetes 1.14 in April 2019*](https://kubernetes.io/blog/2019/04/04/kubernetes-1.14-local-persistent-volumes-ga/). - -**{{name.ln}} is built on immutable application containers. -What does it mean?** - -According to the microservice architectural pattern, a container is -designed to run a single application or process. As a result, such -container images are built to run the main application as the -single entry point (the so-called PID 1 process). - -In Kubernetes terms, the application is referred to as workload. -Workloads can be stateless like a web application server or stateful like a -database. Mapping this concept to PostgreSQL, an immutable application -container is a single "postgres" process that is running and -tied to a single and specific version - the one in the immutable -container image. - -No other processes such as SSH or systemd, or syslog are allowed. - -Immutable Application Containers are in contrast with Mutable System -Containers, which are still a very common way to interpret and use -containers. - -Immutable means that a container won't be modified during its life: no -updates, no patches, no configuration changes. If you must update the -application code or apply a patch, you build a new image and redeploy -it. Immutability makes deployments safer and more repeatable. - -For more information, please refer to -[*"Why EDB chose immutable application containers"*](https://www.enterprisedb.com/blog/why-edb-chose-immutable-application-containers). - -**What does Cloud Native mean?** - -The Cloud Native Computing Foundation defines the term -"[*Cloud Native*](https://github.com/cncf/toc/blob/main/DEFINITION.md)". -However, since the start of the Cloud Native PostgreSQL/{{name.ln}} operator -at 2ndQuadrant, the development team has been interpreting Cloud Native -as three main concepts: - -1. An existing, healthy, genuine, and prosperous DevOps culture, founded - on people, as well as principles and processes, which enables teams - and organizations (as teams of teams) to continuously change so to - innovate and accelerate the delivery of outcomes and produce value - for the business in safer, more efficient, and more engaging ways -2. A microservice architecture that is based on Immutable Application - Containers -3. A way to manage and orchestrate these containers, such as Kubernetes - -Currently, the standard de facto for container orchestration is -Kubernetes, which automates the deployment, administration and -scalability of Cloud Native Applications. - -Another definition of Cloud Native that resonates with us is the one -defined by Ibryam and Huß in -[*"Kubernetes Patterns", published by O'Reilly*](https://www.oreilly.com/library/view/kubernetes-patterns/9781492050278/): - -> Principles, Patterns, Tools to automate containerized microservices at scale - -**Can I run {{name.ln}} on bare metal Kubernetes?** - -Yes, definitely. You can run Kubernetes on bare metal. And you can dedicate one -or more physical worker nodes with locally attached storage to PostgreSQL -workloads for maximum and predictable I/O performance. - -The actual Cloud Native PostgreSQL project, from which {{name.ln}} -originated, was born after a pilot project in 2019 that benchmarked storage and -PostgreSQL on the same bare metal server, first directly in Linux, and then -inside Kubernetes. As expected, the experiment showed only negligible -performance impact introduced by the container running in Kubernetes through -local persistent volumes, allowing the Cloud Native initiative to continue. - -**Why should I use PostgreSQL replication instead of file system -replication?** - -Please read the ["Architecture: Synchronizing the state"](architecture.md#synchronizing-the-state) -section. - -**Why should I use an operator instead of running PostgreSQL as a -container?** - -The most basic approach to running PostgreSQL in Kubernetes is to have a -pod, which is the smallest unit of deployment in Kubernetes, running a -Postgres container with no replica. The volume hosting the Postgres data -directory is mounted on the pod, and it usually resides on network -storage. In this case, Kubernetes restarts the pod in case of a -problem or moves it to another Kubernetes node. - -The most sophisticated approach is to run PostgreSQL using an operator. -An operator is an extension of the Kubernetes controller and defines how -a complex application works in business continuity contexts. The -operator pattern is currently state of the art in Kubernetes for -this purpose. An operator simulates the work of a human operator in an -automated and programmatic way. - -Postgres is a complex application, and an operator not only needs to -deploy a cluster (the first step), but also properly react after -unexpected events. The typical example is that of a failover. - -An operator relies on Kubernetes for capabilities like self-healing, -scalability, replication, high availability, backup, recovery, updates, -access, resource control, storage management, and so on. It also -facilitates the integration of a PostgreSQL cluster in the log -management and monitoring infrastructure. - -{{name.ln}} enables the definition of the desired state of a -PostgreSQL cluster via declarative configuration. Kubernetes -continuously makes sure that the current state of the infrastructure -matches the desired one through reconciliation loops initiated by the -Kubernetes controller. If the desired state and the actual state don't -match, reconciliation loops trigger self-healing procedures. That's -where an operator like {{name.ln}} comes into play. - -**Are there any other operators for Postgres out there?** - -Yes, of course. And our advice is that you look at all of them and compare -them with {{name.ln}} before making your decision. You will see that -most of these operators use an external failover management tool (Patroni -or similar) and rely on StatefulSets. - -Here is a non exhaustive list, in chronological order from their -publication on GitHub: - -- [Crunchy Data Postgres Operator](https://github.com/CrunchyData/postgres-operator) (2017) -- [Zalando Postgres Operator](https://github.com/zalando/postgres-operator) (2017) -- [Stackgres](https://github.com/ongres/stackgres) (2020) -- [Percona Operator for PostgreSQL](https://github.com/percona/percona-postgresql-operator) (2021) -- [Kubegres](https://github.com/reactive-tech/kubegres) (2021) - -Feel free to report any relevant missing entry as a PR. - -!!!info -The [Data on Kubernetes Community](https://dok.community) -(which includes some of our maintainers) is working on an independent and -vendor neutral project to list the operators called -[Operator Feature Matrix](https://github.com/dokc/operator-feature-matrix). -!!! - -**You say that {{name.ln}} is a fully declarative operator. -What do you mean by that?** - -The easiest way is to explain declarative configuration through an -example that highlights the differences with imperative configuration. -In an imperative context, the state is defined as a series of tasks to -be executed in sequence. So, we can get a three-node PostgreSQL cluster -by creating the first instance, configuring the replication, cloning a -second instance, and the third one. - -In a declarative approach, the state of a system is defined using -configuration, namely: there's a PostgreSQL 18 cluster with two replicas. -This approach highly simplifies change management operations, and when -these are stored in source control systems like Git, it enables the -Infrastructure as Code capability. And Kubernetes takes it farther than -deployment, as it makes sure that our request is fulfilled at any time. - -**What are the required skills to run PostgreSQL on Kubernetes?** - -Running PostgreSQL on Kubernetes requires both PostgreSQL and Kubernetes -skills in your DevOps team. The best experience is when database -administrators familiarize themselves with Kubernetes core concepts -and are able to interact with Kubernetes administrators. - -Our advice is for everyone that wants to fully exploit Cloud Native -PostgreSQL to acquire the "Certified Kubernetes Administrator (CKA)" -status from the CNCF certification program. - -**Why isn't {{name.ln}} using StatefulSets?** - -{{name.ln}} does not rely on `StatefulSet` resources, and -instead manages the underlying PVCs directly by leveraging the selected -storage class for dynamic provisioning. Please refer to the -["Custom Pod Controller"](controller.md) section for details and reasons behind -this decision. - -## High availability - -**What happens to the PostgreSQL clusters when the operator pod dies or it is -not available for a certain amount of time?** - -The {{name.ln}} operator, among other things, is responsible for self-healing -capabilities. As such, they might not be available during an outage of the -operator. - -However, assuming that the outage does not affect the nodes where PostgreSQL -clusters are running, the database will continue to serve normal operations, -through the relevant Kubernetes services. Moreover, the [instance manager](instance_manager.md), -which runs inside each PostgreSQL pod will still work, making sure that the -database server is up, including accessory services like logging, export of -metrics, continuous archiving of WAL files, etc. - -To summarize: - -an outage of the operator does not necessarily imply a PostgreSQL -database outage; it's like running a database without a DBA or system -administrator. - -**What are the reasons behind {{name.ln}} not relying on a failover -management tool like Patroni, repmgr, or Stolon?** - -Although part of the team that develops {{name.ln}} has been heavily -involved in repmgr in the past, we decided to take a different approach -and directly extend the Kubernetes controller and rely on the Kubernetes API -server to hold the status of a Postgres cluster, and use it as the only source -of truth to: - -- control High Availability of a Postgres cluster primarily via automated - failover and switchover, coordinating itself with the [instance manager](instance_manager.md) -- control the Kubernetes services, that is the entry points for your - applications - -**Should I manually resync a former primary with the new one following a -failover?** - -No. The operator does that automatically for you, and relies on `pg_rewind` to -synchronize the former primary with the new one. - - - -## Database management - -**Why should I use PostgreSQL?** - -We believe that PostgreSQL is the equivalent in the database area of -what Linux represents in the operating system space. The current latest -major version of Postgres is version 16, which ships out of the box: - -- native streaming replication, both physical and logical -- continuous hot backup and point in time recovery -- declarative partitioning for horizontal table partitioning, which is - a very well-known technique in the database area to improve vertical - scalability on a single instance -- extensibility, with extensions like [PostGIS](postgis.md) for geographical - databases -- parallel queries for vertical scalability -- JSON support, unleashing the multi-model hybrid database for both - structured and unstructured data queried via standard SQL - -And so on ... - -**How many databases should be hosted in a single PostgreSQL instance?** - -Our recommendation is to dedicate a single PostgreSQL cluster -(intended as primary and multiple standby servers) to a single database, -entirely managed by a single microservice application. However, by -leveraging the "postgres" superuser, it is possible to create as many -users and databases as desired (subject to the available resources). - -The reason for this recommendation lies in the Cloud Native concept, -based on microservices. In a pure microservice architecture, the -microservice itself should own the data it manages exclusively. -These could be flat files, queues, key-value stores, or, in our case, a -PostgreSQL relational database containing both structured and -unstructured data. The general idea is that only the microservice can -access the database, including schema management and migrations. - -{{name.ln}} has been designed to work this way out of the -box, by default creating an application user and an application database -owned by the aforementioned application user. - -Reserving a PostgreSQL instance to a single microservice owned database, -enhances: - -- resource management: in PostgreSQL, CPU, and memory constrained - resources are generally handled at the instance level, not the - database level, making it easier to integrate it with Kubernetes - resource management policies at the pod level -- physical continuous backup and Point-In-Time-Recovery (PITR): given - that PostgreSQL handles continuous backup and recovery at the - instance level, having one database per instance simplifies PITR - operations, differentiates retention policy management, and - increases data protection of backups -- application updates: enable each application to decide their update - policies without impacting other databases owned by different - applications -- database updates: each application can decide which PostgreSQL - version to use, and independently, when to upgrade to a different - major version of PostgreSQL and at what conditions (e.g., cutover - time) - -**Is there an upper limit in database size for not considering Kubernetes?** - -No, as Kubernetes is no different from virtual machines and bare metal as far -as this is regarded. -Practically, however, it depends on the available resources of your Kubernetes -cluster. Our advice with very large databases (VLDB) is to consider a shared -nothing architecture, where a Kubernetes worker node is dedicated to a single -Postgres instance, with dedicated storage. -We proved that this extreme architectural pattern works when we benchmarked -[running PostgreSQL on bare metal Kubernetes with local persistent -volumes](https://www.2ndquadrant.com/en/blog/local-persistent-volumes-and-postgresql-usage-in-kubernetes/). -Tablespaces and horizontal partitioning are data modeling techniques that you -can use to improve the vertical scalability of you databases. - -**How can I specify a time zone in the PostgreSQL cluster?** - -PostgreSQL has an extensive support for time zones, as explained in the official -documentation: - -- [Date time data types](https://www.postgresql.org/docs/current/datatype-datetime.html) -- [Client connections config options](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-TIMEZONE) - -Although time zones can even be used at session, transaction and even as part -of a query in PostgreSQL, a very common way is to set them up globally. With -{{name.ln}} you can configure the cluster level time zone in the -`.spec.postgresql.parameters` section as in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: pg-italy -spec: - instances: 1 - - postgresql: - parameters: - timezone: "Europe/Rome" - - storage: - size: 1Gi -``` - -The time zone can be verified with: - -```console -$ kubectl exec -ti pg-italy-1 -c postgres -- psql -x -c "SHOW timezone" --[ RECORD 1 ]--------- -TimeZone | Europe/Rome -``` - -**What is the recommended architecture for best business continuity -outcomes?** - -As covered in the ["Architecture"](architecture.md) section, the main -recommendation is to adopt shared nothing architectures as much as possible, by -leveraging the native capabilities and resources that Kubernetes provides in a -single cluster, namely: - -- availability zones: spread your instances across different availability zones - in the same Kubernetes cluster -- worker nodes: as a consequence, make sure that your Postgres instances reside - on different Kubernetes worker nodes -- storage: use dedicated storage for each worker node running Postgres - -Use at least one standby, preferably at least two, so that you can configure -synchronous replication in the cluster, introducing [RPO](before_you_start.md#postgresql-terminology)=0 -for high availability. - -If you do not have availability zones - normally the case of on-premise -installations - separate on worker nodes and storage. - -Properly setup continuous backup on a local/regional object store. - -The same architecture that is in a single Kubernetes cluster can be replicated -in another Kubernetes cluster (normally in another geographical area or region) -through the [replica cluster](replica_cluster.md) feature, providing disaster -recovery and high availability at global scale. - -You can use the WAL archive in the primary object store to feed the replica in -the other region, without having to provide a streaming connection, if the default -maximum RPO of 5 minutes is enough for you. - -**How can instances be stopped or started?** - -Please look at ["Fencing"](fencing.md) or ["Hibernation"](declarative_hibernation.md). - -**What are the global objects such as roles and databases that are -automatically created by {{name.ln}}?** - -The operator automatically creates a user for the application (by default -called `app`) and a database for the application (by default called `app`) -which is owned by the aforementioned user. - -This way, the database is ready for a microservice adoption, as developers -can control migrations using the `app` user, without requiring *superuser* -access. - -Teams can then create another user for read-write operations through the -["Declarative role management"](declarative_role_management.md) feature -and assign the required `GRANT` to the tables. - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/fencing.mdx b/product_docs/docs/postgres_for_kubernetes/preview/fencing.mdx deleted file mode 100644 index d8c695dc00e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/fencing.mdx +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: 'Fencing' -originalFilePath: 'src/fencing.md' ---- - - - -Fencing in {{name.ln}} is the ultimate process of protecting the -data in one, more, or even all instances of a PostgreSQL cluster when they -appear to be malfunctioning. When an instance is fenced, the PostgreSQL server -process (`postmaster`) is guaranteed to be shut down, while the pod is kept running. -This makes sure that, until the fence is lifted, data on the pod is not modified by -PostgreSQL and that the file system can be investigated for debugging and -troubleshooting purposes. - -## How to fence instances - -In {{name.ln}} you can fence: - -- a specific instance -- a list of instances -- an entire Postgres `Cluster` - -Fencing is controlled through the content of the `k8s.enterprisedb.io/fencedInstances` -annotation, which expects a JSON formatted list of instance names. -If the annotation is set to `'["*"]'`, a singleton list with a wildcard, the -whole cluster is fenced. -If the annotation is set to an empty JSON list, the operator behaves as if the -annotation was not set. - -For example: - -- `k8s.enterprisedb.io/fencedInstances: '["cluster-example-1"]'` will fence just - the `cluster-example-1` instance - -- `k8s.enterprisedb.io/fencedInstances: '["cluster-example-1","cluster-example-2"]'` - will fence the `cluster-example-1` and `cluster-example-2` instances - -- `k8s.enterprisedb.io/fencedInstances: '["*"]'` will fence every instance in - the cluster. - -The annotation can be manually set on the Kubernetes object, for example via -the `kubectl annotate` command, or in a transparent way using the -`kubectl cnp fencing on` subcommand: - -```shell -# to fence only one instance -kubectl cnp fencing on cluster-example 1 - -# to fence all the instances in a Cluster -kubectl cnp fencing on cluster-example "*" -``` - -Here is an example of a `Cluster` with an instance that was previously fenced: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - annotations: - k8s.enterprisedb.io/fencedInstances: '["cluster-example-1"]' -[...] -``` - -## How to lift fencing - -Fencing can be lifted by clearing the annotation, or set it to a different value. - -As for fencing, this can be done either manually with `kubectl annotate`, or -using the `kubectl cnp fencing` subcommand as follows: - -```shell -# to lift the fencing only for one instance -# N.B.: at the moment this won't work if the whole cluster was fenced previously, -# in that case you will have to manually set the annotation as explained above -kubectl cnp fencing off cluster-example 1 - -# to lift the fencing for all the instances in a Cluster -kubectl cnp fencing off cluster-example "*" -``` - -## How fencing works - -Once an instance is set for fencing, the procedure to shut down the -`postmaster` process is initiated, identical to the one of the switchover. -This consists of an initial fast shutdown with a timeout set to -`.spec.switchoverDelay`, followed by an immediate shutdown. Then: - -- the Pod will be kept alive - -- the Pod won't be marked as *Ready* - -- all the changes that don't require the Postgres instance to be up will be - reconciled, including: - - configuration files - - certificates and all the cryptographic material - -- metrics will not be collected, except `cnp_collector_fencing_on` which will be - set to 1 - -!!!warning -If a **primary instance** is fenced, its postmaster process -is shut down but no failover is performed, interrupting the operativity of -the applications. When the fence will be lifted, the primary instance will be -started up again without performing a failover. - -Given that, we advise users to fence primary instances only if strictly required. -!!! - -If a fenced instance is deleted, the pod will be recreated normally, but the -postmaster won't be started. This can be extremely helpful when instances -are `Crashlooping`. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/image_catalog.mdx b/product_docs/docs/postgres_for_kubernetes/preview/image_catalog.mdx deleted file mode 100644 index 9ae1d0b9b5f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/image_catalog.mdx +++ /dev/null @@ -1,295 +0,0 @@ ---- -title: 'Image Catalog' -originalFilePath: 'src/image_catalog.md' ---- - - - -`ImageCatalog` and `ClusterImageCatalog` are Custom Resource Definitions (CRDs) -that allow you to decouple the PostgreSQL image lifecycle from the `Cluster` -definition. By using a catalog, you can manage image updates centrally; when a -catalog entry is updated, all associated clusters automatically -[roll out the new image](rolling_update.md). - -While you can build custom catalogs, {{name.ln}} provides -[official catalogs](#edb-cloudnativepg-cluster-catalogs) as `ClusterImageCatalog` -resources, covering all official Community PostgreSQL container images. - -## Catalog scoping - -The primary difference between the two resources is their scope: - -| Resource | Scope | Best use case | -| --------------------- | ------------ | ----------------------------------------------------------- | -| `ImageCatalog` | Namespaced | Application-specific versions or team-level restrictions. | -| `ClusterImageCatalog` | Cluster-wide | Global standards across all namespaces for an organization. | - -## Catalog structure - -Both resources share a common schema: - -- **Major versioning**: A list of images keyed by the `major` PostgreSQL version. -- **Uniqueness**: The `major` field must be unique within a single catalog. -- **Extensions**: Support for certified extension container images (available for - PostgreSQL 18+ via `extension_control_path`). -- **Component images**: An optional list of named images for non-PostgreSQL - components such as PgBouncer (see - [Component images](#component-images)). - -!!!warning - -While the operator trusts the user-defined `major` version without performing -image detection, the official {{name.ln}} catalogs are pre-validated by the -community to ensure that every extension and operand image entry correctly -matches the declared major version. If you are creating a custom catalog, you -must ensure the declared major version matches the actual PostgreSQL images to -maintain compatibility. -!!! - -## Component images - -In addition to PostgreSQL images, a catalog can store images for other -components via the `componentImages` field. Each entry is identified by a string -**key** — a lowercase alphanumeric identifier (hyphens allowed, 1–63 -characters) that must be unique within the catalog. - -Currently, the only consumer of component images is the `Pooler` resource, -which can reference a component image entry to centrally manage the PgBouncer -container image (see -[Using an image catalog](connection_pooling.md#using-an-image-catalog)). - -The following example defines a namespaced `ImageCatalog` with a PgBouncer -component image: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ImageCatalog -metadata: - name: my-catalog - namespace: default -spec: - images: - - major: 18 - image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 - componentImages: - - key: pgbouncer - image: docker.enterprisedb.com/k8s/pgbouncer:1.25.1-ubi9 -``` - -For a cluster-wide catalog, use `kind: ClusterImageCatalog` and drop the -`metadata.namespace` field (the `spec` is otherwise identical). - -!!!info - -A catalog may contain up to 32 component image entries. Keys are lowercase -alphanumeric characters or hyphens, starting and ending with an alphanumeric -character, up to 63 characters long. -!!! - -## Configuration examples - -### Defining a catalog - -You can define multiple major versions within a single catalog. - -The following example defines a namespaced `ImageCatalog`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ImageCatalog -metadata: - name: postgresql - namespace: default -spec: - images: - - major: 15 - image: docker.enterprisedb.com/k8s/postgresql:15.14-standard-ubi9 - - major: 16 - image: docker.enterprisedb.com/k8s/postgresql:16.10-standard-ubi9 - - major: 17 - image: docker.enterprisedb.com/k8s/postgresql:17.6-standard-ubi9 - - major: 18 - image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 -``` - -The following example defines a cluster-wide `ClusterImageCatalog`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ClusterImageCatalog -metadata: - name: postgresql-global -spec: - images: - - major: 15 - image: docker.enterprisedb.com/k8s/postgresql:15.14-standard-ubi9 - - major: 16 - image: docker.enterprisedb.com/k8s/postgresql:16.10-standard-ubi9 - - major: 17 - image: docker.enterprisedb.com/k8s/postgresql:17.6-standard-ubi9 - - major: 18 - image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 -``` - -### Referencing a Catalog in a Cluster - -A `Cluster` resource uses the `imageCatalogRef` to select its images: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - imageCatalogRef: - apiGroup: postgresql.k8s.enterprisedb.io - kind: ClusterImageCatalog # Or 'ImageCatalog' - name: postgresql-global - major: 18 - storage: - size: 1Gi -``` - -## Image Catalog with Image Volume Extensions - -[Image Volume Extensions](imagevolume_extensions.md) allow you to bundle -containers for extensions directly within the catalog entry: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ImageCatalog -metadata: - name: postgresql -spec: - images: - - major: 18 - image: docker.enterprisedb.com/k8s/postgresql:18.4-minimal-ubi9 - extensions: - - name: foo - image: - reference: # registry path for your `foo` extension image -``` - -The `extensions` section follows the [`ExtensionConfiguration`](pg4k.v1.md#extensionconfiguration) -API schema and structure. -Clusters referencing an image catalog can load any of its associated extensions -by name. - -!!!info - -Refer to the [documentation of image volume extensions](imagevolume_extensions.md) -for details on the internal image structure, configuration options, and -instructions on how to select or override catalog extensions within a cluster. -!!! - -[Image Volume Extensions](imagevolume_extensions.md) allow you to bundle -containers for extensions directly within the catalog entry: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ImageCatalog -metadata: - name: postgresql -spec: - images: - - major: 18 - image: docker.enterprisedb.com/k8s_enterprise/postgresql:18.3-minimal-ubi9 - extensions: - - name: foo - image: - reference: # registry path for your `foo` extension image -``` - -The `extensions` section follows the [`ExtensionConfiguration`](pg4k.v1.md#extensionconfiguration) -API schema and structure. -Clusters referencing an image catalog can load any of its associated extensions -by name. - -!!!info -Refer to the [documentation of image volume extensions](imagevolume_extensions.md) -for details on the internal image structure, configuration options, and -instructions on how to select or override catalog extensions within a cluster. -!!! - -## EDB CloudNativePG Cluster Catalogs - -The {{name.ln}} project maintains `ClusterImageCatalog` manifests for all -supported images. - -These catalogs are regularly updated and published in two distinct locations -within the [artifacts repository](https://github.com/cloudnative-pg/artifacts/tree/main): - -- **[`image-catalogs`](https://github.com/cloudnative-pg/artifacts/tree/main/image-catalogs):** - core catalog definitions for base image types. - -- **[`image-catalogs-extensions`](https://github.com/cloudnative-pg/artifacts/tree/main/image-catalogs-extensions):** - identical to the above catalogs, with the key difference that the `minimal` - image type includes extension definitions. - -Each catalog corresponds to a specific combination of image type and Debian -release (e.g., `trixie`). It lists the most up-to-date container images for -every supported PostgreSQL major version. - -!!!important - -To ensure maximum security and immutability, all images within official -{{name.ln}} catalogs are identified by their **SHA256 digests** rather than -just tags. -!!! - -### Version Compatibility - -While core catalogs work with older versions of the operator, **catalogs -containing an `extensions` section are only compatible with {{name.ln}} 1.29 -or later**. Using a catalog with extension definitions on an older operator -will result in those definitions being rejected. - -### Installation and Usage - -By installing these catalogs, cluster administrators can ensure that their -PostgreSQL clusters are automatically updated to the latest patch release -within a given PostgreSQL major version, for the selected Debian distribution -and image type. - -For example, to install the latest catalog for the `minimal` PostgreSQL -container images on Debian `trixie`, run: - -```shell -kubectl apply -f \ - https://raw.githubusercontent.com/cloudnative-pg/artifacts/refs/heads/main/image-catalogs/catalog-minimal-trixie.yaml -``` - -You can install all the available catalogs by using the `kustomization` file -present in the `image-catalogs` directory: - -```shell -kubectl apply -k https://github.com/cloudnative-pg/artifacts//image-catalogs?ref=main -``` - -You can then view all the catalogs deployed with: - -```shell -kubectl get clusterimagecatalogs.postgresql.k8s.enterprisedb.io -``` - -### Example: Using a Catalog in a Cluster - -To create a cluster that always tracks the latest `minimal` image for -PostgreSQL 18 on `trixie`, define your `Cluster` as follows: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: angus -spec: - instances: 3 - imageCatalogRef: - apiGroup: postgresql.k8s.enterprisedb.io - kind: ClusterImageCatalog - name: postgresql-minimal-trixie - major: 18 - storage: - size: 1Gi -``` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/apps-in-k8s.png b/product_docs/docs/postgres_for_kubernetes/preview/images/apps-in-k8s.png deleted file mode 100644 index 832dcb3c59b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/apps-in-k8s.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:afe49c1bcdb498302c3cf0af1bd058b43ca98a0a4de15c25e354912443d58eb0 -size 45106 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/apps-outside-k8s.png b/product_docs/docs/postgres_for_kubernetes/preview/images/apps-outside-k8s.png deleted file mode 100644 index 4259c49ec5c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/apps-outside-k8s.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1e687abe20e25f9589a094860769d2272ade598ecd643035712caa6a9b620e42 -size 54998 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-in-k8s.png b/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-in-k8s.png deleted file mode 100644 index 7d938404208..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-in-k8s.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7237ce42adb430948f5dea1e7449760843679cee00cb8d12f4aa82df1f11a8da -size 116084 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-r.png b/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-r.png deleted file mode 100644 index fd2ec56913a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-r.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8ba71048bf84260cf81c9d351cf9e8b4ccf40484b121eebc04a97a59044d4867 -size 100517 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-read-only.png b/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-read-only.png deleted file mode 100644 index 6c19b0cb2db..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-read-only.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1a0c1d859d922680eb77fb07cb3e9b0a0023fc5e31592849abcf43fd31f4a160 -size 95360 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-rw.png b/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-rw.png deleted file mode 100644 index e95d0f887ae..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/architecture-rw.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:448e13c114845e12cacb9e8e74bb540556ccac383333e20f21bf416427c973b8 -size 84508 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/grafana-local.png b/product_docs/docs/postgres_for_kubernetes/preview/images/grafana-local.png deleted file mode 100644 index 4788aab1c75..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/grafana-local.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6a3f34d6c747cba079665d94b19db1e562ca11526ff442e5a85a5e80b78cef14 -size 398383 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/ironbank/pulling-the-image.png b/product_docs/docs/postgres_for_kubernetes/preview/images/ironbank/pulling-the-image.png deleted file mode 100644 index a3dfebb5086..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/ironbank/pulling-the-image.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9cb5bda073e0e46d58b62167e20931db93f1f7d9ceb2d64efe8fc990913237f -size 84974 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-2-az.png b/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-2-az.png deleted file mode 100644 index 94e83d98eb7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-2-az.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:34fef36277b75d487881855084959d393f88947b583f7eede432230632e38ad3 -size 100839 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-3-az.png b/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-3-az.png deleted file mode 100644 index bbc0f09f6be..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-3-az.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4b5abe82c6febf14dc1c2c09fe5c40f129e70053fefe654983e64bac0ab301a4 -size 119593 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-multi.png b/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-multi.png deleted file mode 100644 index 51a22831b4e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-architecture-multi.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7abed062c67cca40349271f22d28595c4e18ddbd6a3da6b62570e8e19590edb2 -size 137762 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-pg-architecture.png b/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-pg-architecture.png deleted file mode 100644 index 33fc6164bb8..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/k8s-pg-architecture.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e4a3524b47563edb6b5372d1c2d651768b899f0b415be230751eb131be4eb60c -size 256099 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/microservice-import.png b/product_docs/docs/postgres_for_kubernetes/preview/images/microservice-import.png deleted file mode 100644 index 0a46f5795c0..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/microservice-import.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:83e6dd482dc826745b118e43eb97ffcf3c4b7177faf02be178eab8c542934114 -size 66198 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/monolith-import.png b/product_docs/docs/postgres_for_kubernetes/preview/images/monolith-import.png deleted file mode 100644 index 1e0d26fe572..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/monolith-import.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4ddcad2179ee80b4023f3b72a45a083b0a21b00c645cc1263dd26499d5dbbd1a -size 56714 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/multi-cluster.png b/product_docs/docs/postgres_for_kubernetes/preview/images/multi-cluster.png deleted file mode 100644 index cbee5229bc0..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/multi-cluster.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:35bfcbf1a93d05eac13ca242b0681df3cdbc6887e7e232884cb7e7eb78adea9a -size 202406 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/network-storage-architecture.png b/product_docs/docs/postgres_for_kubernetes/preview/images/network-storage-architecture.png deleted file mode 100644 index 32cf8f7a317..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/network-storage-architecture.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df55506cdc6337da76b3c48458d6de33839d74570f000eb6be6357611dc6a182 -size 214390 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/alerts-openshift.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/alerts-openshift.png deleted file mode 100644 index 6b8c6f612d8..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/alerts-openshift.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:93579c3a3e6391b323f8a0600d60306d42b178d5c2ce66e4d1a42376ba529321 -size 173985 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/oc_installation_screenshot_1.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/oc_installation_screenshot_1.png deleted file mode 100644 index 4e2c7aae2ba..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/oc_installation_screenshot_1.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1a08e22ec632f797ebdcc9e72da73946ec380b68cbbd851d77da9cfe7eb96a98 -size 34584 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/oc_installation_screenshot_2.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/oc_installation_screenshot_2.png deleted file mode 100644 index 4ce24413f1b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/oc_installation_screenshot_2.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6efd07bcd16fc88709413bdab1235a577e6903410a3061a0295b87c647faed98 -size 85968 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-operatorgroup-error.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-operatorgroup-error.png deleted file mode 100644 index e9f22e0844c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-operatorgroup-error.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f6a88e427fbcf5814e47138317844b90e2913d72ad9acd8d301e6810706855e -size 34699 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-rbac.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-rbac.png deleted file mode 100644 index 0c28046875c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-rbac.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6def4b5bdb14a7d8ce3c3a2687bf5a4609c8bd79680e7386b03234fdc698f4d6 -size 167580 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-allnamespaces.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-allnamespaces.png deleted file mode 100644 index 72e2f3839db..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-allnamespaces.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:68a599db7dab771c1580182e45f4f0afc6bb0dd0252090299889674c98a0eca0 -size 79549 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-multinamespace.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-multinamespace.png deleted file mode 100644 index 99ab9a72ff5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-multinamespace.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a5219672700425805ac2550a57fbfa50b6538358417a4579e539a1449bf674aa -size 80596 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-singlenamespace-list.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-singlenamespace-list.png deleted file mode 100644 index e016bb95798..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-singlenamespace-list.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:99ef83c8a9bd9b623d88c2a4c37b950dc5782f026a0b10b4347977e14c8319fb -size 64964 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-singlenamespace.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-singlenamespace.png deleted file mode 100644 index 32fc972ca3e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/openshift-webconsole-singlenamespace.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f93dda137ef656faca200386a740c89566c1c33b84382c65b7f66a84d959059 -size 82620 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/operatorhub_1.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/operatorhub_1.png deleted file mode 100644 index 72cceec0aa5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/operatorhub_1.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7a821983dc2af2a32a752e5e437153f6ac7c4985da9d78dc4dbb48c0a44891b8 -size 33589 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/operatorhub_2.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/operatorhub_2.png deleted file mode 100644 index e0e65d7379a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/operatorhub_2.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dc2d785d25376be97e97159f2b4721d02494894d47b2d5db7615218f95022c22 -size 105235 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/prometheus-queries.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/prometheus-queries.png deleted file mode 100644 index b8786c85f96..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/prometheus-queries.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1330ef1e7247431cc392ef98154651e26af52ea03ea8c2d2192cd5dd7b6ea901 -size 91027 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/software-catalog.png b/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/software-catalog.png deleted file mode 100644 index e129a525a3d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/openshift/software-catalog.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:93a066d4a3d4f8cd26ccb4c55bb48df6746140f4c196d790d60620d6df5b0c33 -size 56993 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/operator-capability-level.png b/product_docs/docs/postgres_for_kubernetes/preview/images/operator-capability-level.png deleted file mode 100644 index 6d66fd552e1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/operator-capability-level.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:89951317d0ffadd45c1f9f8b810f3c536d12635ce2abf5527d77ef1f7952d7ad -size 155789 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/pgadmin4.png b/product_docs/docs/postgres_for_kubernetes/preview/images/pgadmin4.png deleted file mode 100644 index 934cfc8f615..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/pgadmin4.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:658332686b109a1cf62aa84b16a14b78c5c0ad131386fd16332805dfc4f1bf59 -size 126821 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-architecture-rw.png b/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-architecture-rw.png deleted file mode 100644 index efceb9ce266..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-architecture-rw.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:27b9d1ec02c4a0f527ed3dc04c535542d2279cf327382746c742cf28b06ef735 -size 169722 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-pooler-image.png b/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-pooler-image.png deleted file mode 100644 index b5e67e7c248..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-pooler-image.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18b7f09c4c6dc18d98cb90ea3449dfdaa4dae2649e9ee90cd8b087b64b48dd34 -size 32737 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-pooler-template.png b/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-pooler-template.png deleted file mode 100644 index 7ac00a187de..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/pgbouncer-pooler-template.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ee0afb7ffa1755928b999b5ab4a64f26fc46aaa69439c43f7249e7931c08767f -size 24875 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/prometheus-local.png b/product_docs/docs/postgres_for_kubernetes/preview/images/prometheus-local.png deleted file mode 100644 index 4acf6643770..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/prometheus-local.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:19488063b3f0de9576c68fdc22130a14f0b1032e2448b862c270571207ad86d1 -size 125996 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/public-cloud-architecture-storage-replication.png b/product_docs/docs/postgres_for_kubernetes/preview/images/public-cloud-architecture-storage-replication.png deleted file mode 100644 index 5a03f36bbae..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/public-cloud-architecture-storage-replication.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:430aa00da8133731ddd105c632d39afed9df6622433cd90ead5c2e742ffa59f8 -size 106922 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/public-cloud-architecture.png b/product_docs/docs/postgres_for_kubernetes/preview/images/public-cloud-architecture.png deleted file mode 100644 index c8751005339..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/public-cloud-architecture.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b26aa19f5af2e0ed31a200cc49936c11f09326733e8bed66620092e805c9705a -size 162809 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/shared-nothing-architecture.png b/product_docs/docs/postgres_for_kubernetes/preview/images/shared-nothing-architecture.png deleted file mode 100644 index 3aa9f1544a6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/shared-nothing-architecture.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:82acabb6b2eae79a4aeddd568e47a6212a99245df35ef9242ca0b0fc93a1c994 -size 156302 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/images/write_bw.1-2Draw.png b/product_docs/docs/postgres_for_kubernetes/preview/images/write_bw.1-2Draw.png deleted file mode 100644 index 683a6522366..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/images/write_bw.1-2Draw.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:45e0fd29b8188f5596088c4c5e9a31c8a564ab499304e35635a6aa645c90670d -size 15555 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/imagevolume_extensions.mdx b/product_docs/docs/postgres_for_kubernetes/preview/imagevolume_extensions.mdx deleted file mode 100644 index 61f3c64c3ad..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/imagevolume_extensions.mdx +++ /dev/null @@ -1,695 +0,0 @@ ---- -title: 'Image Volume Extensions' -originalFilePath: 'src/imagevolume_extensions.md' ---- - - - -{{name.ln}} supports the **dynamic loading of PostgreSQL extensions** into a -`Cluster` at Pod startup using the [Kubernetes `ImageVolume` feature](https://kubernetes.io/docs/tasks/configure-pod-container/image-volumes/) -alongside the `extension_control_path` GUC introduced in PostgreSQL 18, a -feature to which the {{name.ln}} project contributed. - -This feature allows you to mount a [PostgreSQL extension](https://www.postgresql.org/docs/current/extend-extensions.html), -packaged as an OCI-compliant container image, as a read-only and immutable -volume at a designated filesystem path within a running pod. - -For extensions requiring database-level installation via the `CREATE EXTENSION` -command, you can use the [`Database` resource’s declarative extension management](declarative_database_management.md#managing-extensions-in-a-database) -to ensure consistent, automated setup across all your PostgreSQL databases. - -## Official Extension Images and Catalogs - -The {{name.ln}} Community maintains a suite of extension container -images, including -[pgvector](https://github.com/cloudnative-pg/postgres-extensions-containers/tree/main/pgvector) -and -[PostGIS](https://github.com/cloudnative-pg/postgres-extensions-containers/tree/main/postgis), -as part of the [`postgres-extensions-containers` project](https://github.com/cloudnative-pg/postgres-extensions-containers)). -These images are built on top of the -[official PostgreSQL `minimal` images](https://github.com/enterprisedb/docker-postgres?tab=readme-ov-file#minimal-images). - -!!!info - -While this documentation provides the necessary technical specifications for -third parties to build their own images and catalogs, the following -instructions focus specifically on the deployment and usage of our official -extension images and catalogs. -!!! - -## Benefits - -By decoupling the distribution of extensions from the PostgreSQL operand -images, this feature removes a significant barrier to running PostgreSQL in -containers. It eliminates the need to embed extensions at build time, allowing -you to use official minimal operand images and dynamically add only the -required extensions to your `Cluster` definitions—either directly or via an -[image catalog](image_catalog.md). - -This approach significantly reduces the attack surface of your database -clusters by ensuring that the core database container contains only the -essential binaries required for operation. -By excluding unnecessary extensions, libraries, and build-time dependencies, -you minimize potential entry points for exploits and simplify vulnerability -management. -This architecture enhances supply chain security and reduces operational -overhead by maintaining an immutable, minimal base image for your data -workloads. - -!!!important - -Extension images must be built according to the [documented specifications](#image-specifications). -!!! - -## Requirements - -To use image volume extensions with {{name.ln}}, you need: - -- **PostgreSQL 18 or later**: Required for `extension_control_path` support. -- **Kubernetes 1.35 or later**: The `ImageVolume` feature is enabled by - default. Users on Kubernetes 1.33 and 1.34 must manually enable the - `ImageVolume` feature gate. -- **Container runtime with `ImageVolume` support**: - - `containerd` v2.1.0 or later, or - - `CRI-O` v1.31 or later. -- **{{name.ln}}-compatible extension container images**, ensuring: - - Matching PostgreSQL major version of the `Cluster` resource. - - Compatible operating system distribution of the `Cluster` resource. - - Matching CPU architecture of the `Cluster` resource. - -## How it works - -An extension image can be added to a new or existing `Cluster` resource using -the `.spec.postgresql.extensions` stanza. - -!!!important - -When a new extension is added to a running `Cluster`, {{name.ln}} will -automatically trigger a [rolling update](rolling_update.md) to attach the new -image volume to each pod. Before adding a new extension in production, -ensure you have thoroughly tested it in a staging environment to prevent -configuration issues that could leave your PostgreSQL cluster in an unhealthy -state. -!!! - -!!!info -For field-level details, see the -[API reference for `ExtensionConfiguration`](pg4k.v1.md#extensionconfiguration). -!!! - -### Configuration Source and Precedence - -The `extensions` stanza accepts a list of entries, each requiring a `name` that -must be unique within the cluster. - -!!!important - -The `name` must consist of lowercase alphanumeric characters, underscores (`_`) -or hyphens (`-`) and must start and end with an alphanumeric character. It is -limited to 59 characters, leaving room for the prefix {{name.ln}} adds when -deriving the extension's Kubernetes volume name (capped at the RFC 1123 limit of -63 characters). -!!! - -Each entry defines the configuration for a container image and specifies the -options PostgreSQL needs to locate and load the extension: - -- [**Via Image Catalog**](#via-an-image-catalog-recommended): - If the cluster references an `ImageCatalog` that defines extensions for the - current PostgreSQL major version, those definitions serve as the default - configuration. This allows the catalog to centrally manage the - `image.reference`, while the cluster simply enables the extension by name. - -- [**Direct Definition**](#directly-in-the-cluster): - If a cluster does not use an image catalog, the `image.reference` field is - mandatory and must explicitly point to a valid container registry path for the - extension image. The `image` stanza follows the - [Kubernetes `ImageVolume` API](https://kubernetes.io/docs/concepts/storage/volumes/#image). - -Following the *"convention over configuration"* paradigm, {{name.ln}} -provides total flexibility: any value inherited from a catalog, including the -`image.reference`, can be selectively overridden within the `Cluster` -definition to meet specific local requirements. - -### Mounting and PostgreSQL Configuration - -Each extension is mounted as a read-only volume at -`/extensions/` inside the pod. - -By default, {{name.ln}} automatically manages the relevant GUCs by setting: - -- `extension_control_path` to `/extensions//share`, allowing - PostgreSQL to locate any extension control file within `/extensions//share/extension` -- `dynamic_library_path` to `/extensions//lib` - -!!!note -Extension names containing underscores (e.g., `pg_ivm`) are converted to use -hyphens (e.g., `pg-ivm`) for Kubernetes volume names to comply with RFC 1123 -DNS label requirements. Do not use extension names that become identical after -sanitization (e.g., `pg_ivm` and `pg-ivm` both sanitize to `pg-ivm`). The -webhook validation will prevent such conflicts. -!!! - -These values are appended in the order in which the extensions are defined in -the `extensions` list, ensuring deterministic path resolution within -PostgreSQL. This allows PostgreSQL to discover and load the extension without -requiring manual configuration inside the pod. - -While you can manually adjust these paths to match a custom image layout, -official {{name.ln}} catalogs pre-configure these options to the correct -values for each extension, ensuring they work out-of-the-box. - -!!!important - -If an extension image includes shared libraries, they must be compiled for the -same PostgreSQL major version, operating system distribution, and CPU -architecture as the operand image. Using official {{name.ln}} catalogs -ensures this compatibility automatically: the catalogs are designed to match -the specific environment of the cluster, preventing runtime issues caused by -library or architecture mismatches. -!!! - -### Installation in a Database - -You can leverage [declarative database management](declarative_database_management#managing-extensions-in-a-database) -to automate the final activation of any extension that supports the standard -PostgreSQL `CREATE EXTENSION` mechanism. - -Once the extension image is mounted and the GUCs are configured, the extension -is available to the PostgreSQL instance but is not yet active within a specific -database. To install it, define a `Database` resource. The example below uses -`pgvector`, following the implementation standards of the -[official `postgres-extensions-containers` project](https://github.com/cloudnative-pg/postgres-extensions-containers/tree/main/pgvector): - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - name: cluster-example-app -spec: - name: app - owner: app - cluster: - name: cluster-example - extensions: - - name: vector - version: "" -``` - -{{name.ln}} automatically reconciles this resource by executing -`CREATE EXTENSION IF NOT EXISTS vector` within the target database. This -ensures your desired state is maintained and consistently applied across all -instances. - -!!!note - -Some PostgreSQL components, often referred to as modules, do not use the -`CREATE EXTENSION` mechanism. These typically consist of shared libraries that -must be loaded via `shared_preload_libraries` at server start. -Even when using an image catalog to simplify the distribution of these -binaries, you must still manually add the library name to the -[`shared_preload_libraries` option](postgresql_conf.md#shared-preload-libraries) -in your `Cluster` definition to ensure it is loaded into memory. -!!! - -## Adding an Extension to a Postgres Cluster - -As anticipated earlier, {{name.ln}} offers two ways to define extension -images. While both achieve the same result at the Pod level, using an image -catalog is the recommended approach for maintaining a consistent, -production-ready supply chain. - -### Via an Image Catalog (Recommended) - -!!!info - -Support for extension container images in image catalogs was introduced in -{{name.ln}} 1.29. -!!! - -When you use an [image catalog that covers extensions](image_catalog.md#image-catalog-with-image-volume-extensions) -like the [official ones](image_catalog.md#edb-cloudnativepg-cluster-catalogs) -provided by the community, the complex configuration details, such as the -specific container image `reference` and the required filesystem paths, are -managed centrally. - -Your `Cluster` definition remains clean and declarative, as it only needs to -"opt-in" to the extension by name. The operator automatically handles the -resolution of the image and the required PostgreSQL settings based on the -catalog's definitions. - -To enable an extension like `pgvector` from a catalog, add it to the -`extensions` list in your cluster like in the following excerpt: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - # ... - imageCatalogRef: - apiGroup: postgresql.k8s.enterprisedb.io - kind: ClusterImageCatalog - name: postgresql-minimal-ubi9 - major: 18 - - postgresql: - extensions: - - name: pgvector # Resolves all details, including the image reference, from the catalog - # ... -``` - -This method ensures that the extension image is always compatible with the -PostgreSQL operand image defined in the same catalog entry. - -### Directly in the Cluster - -!!!info - -Defining extensions directly in the `Cluster` resource is the original method -and remains the only option for versions prior to {{name.ln}} 1.29. -It is also useful if you need to use an extension not present in your current -catalog or for testing custom images. -!!! - -You can define an extension directly within the `Cluster` resource without a -catalog. In this case, you must explicitly provide the image `reference`. - -The following example shows how to add `pgvector` by explicitly pointing to its -official container image: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - # ... - postgresql: - extensions: - - name: pgvector - image: - reference: ghcr.io/cloudnative-pg/pgvector: -``` - -!!!tip - -Remember that configuration provided directly in the `Cluster` takes -precedence. If you reference a catalog but also define the same extension name -in the `Cluster` stanza, the settings in the `Cluster` will override those in -the catalog. -While every field in an [`ExtensionConfiguration`](pg4k.v1.md#extensionconfiguration) -can be overridden at the `Cluster` level to provide total flexibility, the -`name` field is the exception. -!!! - -!!!warning - -The `name` serves as the unique identifier; changing it will define a new -extension entry rather than overriding an existing one from a catalog. -!!! - -### Verifying Extension Status - -Because extensions can be sourced from both image catalogs and direct cluster -definitions, {{name.ln}} provides a "resolved" view of the configuration in -the `Cluster` status. This is the final, effective state the operator uses to -provision the pods. - -You can inspect the `status.pgDataImageInfo.extensions` field to see the -results of any inheritance or overrides: - -```yaml -# ... -status: - # ... - pgDataImageInfo: - image: # registry path for your PostgreSQL image - majorVersion: 18 - extensions: - - name: foo - image: - reference: # registry path for your `foo` extension image - - name: bar - image: - reference: # registry path for your `bar` extension image - # ... -``` - -This section is particularly useful for: - -- **Validating Resolution:** Confirming that an extension requested by name in - the `Cluster` has correctly pulled its `image.reference` from the associated - catalog. -- **Confirming Overrides:** Verifying that a cluster-level override (such as a - specific image version) has successfully replaced the catalog's default - value. -- **Troubleshooting:** Ensuring all desired extensions are recognized by the - operator before the pods undergo a rolling update. - -## Removing an Extension from a PostgreSQL Cluster - -Removing an extension involves a two-step process to clean up both the -infrastructure and the database metadata. - -You should first remove the extension from the database to avoid "library not -found" errors. If you are using declarative management, update your `Database` -resource by setting `ensure: absent` for the extension: - -```yaml -spec: - # ... - extensions: - - name: pgvector - ensure: absent - # ... -``` - -This triggers {{name.ln}} to execute `DROP EXTENSION` within the database. - -If the extension was added to `shared_preload_libraries`, you must also remove -it from your `Cluster` configuration. - -Then, remove the extension entry from the `.spec.postgresql.extensions` list in -your `Cluster` resource. The operator will perform a rolling update to detach -the `ImageVolume` and update the relevant GUC paths. - -## Advanced Topics - -In some cases, the default expected structure may be insufficient for your -extension image, particularly when: - -- The extension requires additional system libraries. -- Multiple extensions are bundled in the same image. -- The image uses a custom directory structure. -- The extension requires external binaries to function properly. -- The extension requires setting specific environment variables. - -Following the *"convention over configuration"* paradigm, {{name.ln}} allows -you to finely control the configuration of each extension image through the -following fields: - -- `extension_control_path`: A list of relative paths within the container image - to be appended to PostgreSQL’s `extension_control_path`, allowing it to - locate extension control files. -- `dynamic_library_path`: A list of relative paths within the container image - to be appended to PostgreSQL’s `dynamic_library_path`, enabling it to locate - shared library files for extensions. -- `ld_library_path`: A list of relative paths within the container image to be - appended to the `LD_LIBRARY_PATH` environment variable of the Postgres - process, allowing PostgreSQL to locate required system libraries at - runtime. -- `bin_path`: A list of relative paths within the container image to be - appended to the `PATH` environment variable of the Postgres process, - allowing PostgreSQL to locate binaries at runtime. -- `env`: A list of `name` and `value` pairs to be set as environment variables within - the Postgres process. - -This flexibility enables you to support complex or non-standard extension -images while maintaining clarity and predictability. - -### Setting Custom Paths - -If your extension image does not use the default `lib` and `share` directories -for its libraries and control files, you can override the defaults by -explicitly setting `extension_control_path` and `dynamic_library_path`. - -For example: - -```yaml -spec: - # ... - postgresql: - extensions: - - name: my-extension - extension_control_path: - - my/share/path - dynamic_library_path: - - my/lib/path - image: - reference: # registry path for your extension image - # ... - # ... - # ... -``` - -{{name.ln}} will configure PostgreSQL with: - -- `/extensions/my-extension/my/share/path` appended to `extension_control_path` -- `/extensions/my-extension/my/lib/path` appended to `dynamic_library_path` - -This allows PostgreSQL to discover your extension’s control files and shared -libraries correctly, even with a non-standard layout. - -### Multi-extension Images - -You may need to include multiple extensions within the same container image, -adopting a structure where each extension’s files reside in their own -subdirectory. - -For example, to package PostGIS and pgRouting together in a single image, each -in its own subdirectory: - -```yaml -# ... -spec: - # ... - postgresql: - extensions: - - name: geospatial - extension_control_path: - - postgis/share - - pgrouting/share - dynamic_library_path: - - postgis/lib - - pgrouting/lib - # ... - image: - reference: # registry path for your geospatial image - # ... - # ... - # ... -``` - -### Including System Libraries - -Some extensions, such as PostGIS, require system libraries that may not be -present in the base PostgreSQL image. To support these requirements, you can -package the necessary libraries within your extension container image and make -them available to PostgreSQL using the `ld_library_path` field. - -For example, if your extension image includes a `system` directory with the -required libraries: - -```yaml -# ... -spec: - # ... - postgresql: - extensions: - - name: postgis - # ... - ld_library_path: - - system - image: - reference: # registry path for your PostGIS image - # ... - # ... - # ... -``` - -{{name.ln}} will set the `LD_LIBRARY_PATH` environment variable to include -`/extensions/postgis/syslib`, allowing PostgreSQL to locate and load these -system libraries at runtime. - -!!!important - -Since `ld_library_path` must be set when the PostgreSQL process starts, -changing this value requires a **cluster restart** for the new value to take -effect. -{{name.ln}} does not currently trigger this restart automatically; you will -need to manually restart the cluster (e.g., using `cnp restart`) after -modifying `ld_library_path`. -!!! - -### Including external binaries - -Some extensions might need to provide some binaries required to interact with -the extension itself. To support these requirements, you can -package the necessary binaries within your extension container image and make -them available to PostgreSQL using the `bin_path` field. - -For example, if your extension image includes a `bin` directory with the -required binaries: - -```yaml -# ... -spec: - # ... - postgresql: - extensions: - - name: my-extension - # ... - bin_path: - - bin - image: - reference: # registry path for your extension image - # ... - # ... - # ... -``` - -{{name.ln}} will append `/extensions/my-extension/bin` to the `PATH` environment -variable of the Postgres process, allowing PostgreSQL to locate these -binaries at runtime. - -!!!warning - -Since `bin_path` must be set when the PostgreSQL process starts, -changing this value requires a **cluster restart** for the new value to take -effect. -{{name.ln}} does not currently trigger this restart automatically; you will -need to manually restart the cluster (e.g., using `cnp restart`) after -modifying `bin_path`. -!!! - -### Environment variables for extensions - -Certain extensions require specific environment variables to be set within the -PostgreSQL process to function correctly. You can define these variables using -the `env` field within the extension's configuration. - -The following example demonstrates how to set a static variable (`FOO`) and a -variable using a placeholder (`BAR`): - -```yaml -# ... -spec: - # ... - postgresql: - # ... - extensions: - - name: my-extension - image: - reference: "ghcr.io/org/my-extension:latest" - env: - - name: FOO - value: "static_value" - - name: BAR - value: "${image_root}/lib" - # ... -# ... -``` - -#### Dynamic Placeholder Expansion - -The `value` field supports placeholder expansion to allow for dynamic -configuration based on the extension's environment. -The following placeholders are currently supported: - -| Placeholder | Description | -| :-------------- | :------------------------------------------------------------------------------------------------ | -| `${image_root}` | Resolves to the absolute mount path of the extension's volume (e.g., `/extensions/my-extension`). | - -The `${image_root}` placeholder is particularly useful when an application or a -shared library within the extension image needs an environment variable to -point to a specific subdirectory or file inside its own mounted volume. - -In the example above, if the extension is mounted at -`/extensions/my-extension`, the variable `BAR` will resolve to -`/extensions/my-extension/lib`, allowing the library to locate its -dependencies regardless of the specific mount path chosen by the operator. - -!!!tip - -Unrecognized placeholders (e.g., `${typo}`) are rejected at admission time. -If you need a literal `${...}` in a value, escape it by doubling the dollar -sign: `$${...}`. For example, a value of `$${not_expanded}` will produce the -literal string `${not_expanded}`. -!!! - -#### Precedence and Conflict Resolution - -Environment variables for the PostgreSQL process can be defined in multiple -places. When the same variable name appears in more than one location, the -following precedence order applies (highest priority last): - -1. **`spec.env` / `spec.envFrom`**: Variables defined at the cluster level are - injected by Kubernetes into the container environment and serve as the base. -2. **Extension `env`**: Variables defined in the `env` field of each extension - override any cluster-level variable with the same name. -3. **Extension order**: If multiple extensions define the same variable, the - extension listed last in the `extensions` array takes precedence. - -{{name.ln}} emits a warning in the instance manager logs when an extension -environment variable overwrites a value that was already set by a previous -extension, to help diagnose potential conflicts. - -!!!important - -**Reserved variables**: Environment variables reserved for operator usage -(names starting with `PG` or `CNP_`, plus `POD_NAME`, `NAMESPACE`, and -`CLUSTER_NAME`) and variables managed by dedicated fields (`PATH` via -`bin_path`, `LD_LIBRARY_PATH` via `ld_library_path`) cannot be set through -the `env` field and are rejected at admission time. -!!! - -!!!warning - -**Manual Restart Required**: Because environment variables are injected when -the PostgreSQL process starts, any changes to the `env` section **require a -cluster restart**. {{name.ln}} does **not** automatically trigger a rollout -for these changes. After updating the `env` field in your manifest, you must -manually restart the cluster (e.g., using `kubectl cnp restart`) for the new -values to take effect. -!!! - -## Image Specifications - -A standard extension container image for {{name.ln}} includes two -required directories at its root: - -- `/share/`: contains an `extension` subdirectory with the extension control - file (e.g. `.control`) and the corresponding SQL files. -- `/lib/`: contains the extension’s shared library (e.g. `.so`) as - well as any other required libraries. - -Following this structure ensures that the extension will be automatically -discoverable and usable by PostgreSQL within {{name.ln}} without requiring -manual configuration. - -!!!important - -We encourage PostgreSQL extension developers and third-party providers to -publish OCI-compliant extension images following this layout. -For practical implementation details, we recommend reviewing the -[`postgres-extensions-containers` project](https://github.com/cloudnative-pg/postgres-extensions-containers), -which serves as the reference for building official {{name.ln}} extension images. - -Ideally, extension images should: - -- Target a specific operating system distribution and set of CPU architectures. -- Be tied to a particular PostgreSQL major version. -- Be built using the distribution’s native packaging system (e.g., `.deb` or - `.rpm` packages) to ensure consistency, security, and compatibility with the - PostgreSQL operand images used in your clusters. -!!! - -## Caveats - -Currently, adding, removing, or updating an extension image triggers a -restart of the PostgreSQL pods. This behavior is inherited from how -[image volumes](https://kubernetes.io/docs/tasks/configure-pod-container/image-volumes/) -work in Kubernetes. - -Before performing an extension update, ensure you have: - -- Thoroughly tested the update process in a staging environment. -- Verified that the extension image contains the required upgrade path between - the currently installed version and the target version. -- Updated the `version` field for the extension in the relevant `Database` - resource definition to align with the new version in the image. - -These steps help prevent downtime or data inconsistencies in your PostgreSQL -clusters during extension updates. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/index.mdx b/product_docs/docs/postgres_for_kubernetes/preview/index.mdx deleted file mode 100644 index 494801d1c2e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/index.mdx +++ /dev/null @@ -1,223 +0,0 @@ ---- -title: '{{name.ln}}' -description: The {{name.ln}} operator is a fork based on CloudNativePG™ which provides additional value such as compatibility with Oracle databases and additional supported platforms such as IBM Power and OpenShift. -originalFilePath: src/index.md -indexCards: none -directoryDefaults: - version: "1.30.0-rc1" - displayBanner: | - This documentation covers the upcoming release of - {{name.ln}}; you may want to read the docs for - the current version -navigation: - - rel_notes - - '!commercial_support.mdx' - - '!release_notes*' - - '!e2e.mdx' - - '!supported_releases.mdx' - - '#Getting Started' - - before_you_start - - use_cases - - architecture - - installation_upgrade - - quickstart - - preview_version - - '#Configuration' - - postgresql_conf - - operator_conf - - cluster_conf - - samples - - '#Using' - - bootstrap - - image_catalog - - database_import - - security - - instance_manager - - scheduling - - job_scheduling - - resource_management - - failure_modes - - rolling_update - - replication - - logical_replication - - backup - - recovery - - wal_archiving - - service_management - - declarative_role_management - - declarative_database_management - - tablespaces - - storage - - labels_annotations - - monitoring - - logging - - certificates - - ssl_connections - - applications - - connection_pooling - - replica_cluster - - kubernetes_upgrade - - postgres_upgrades - - expose_pg_services - - kubectl-plugin - - failover - - fencing - - declarative_hibernation - - postgis - - container_images - - imagevolume_extensions - - cnp_i - - controller - - networking - - benchmarking - - '#EDB Enhancements' - - evaluation - - license_keys - - private_edb_registries - - openshift - - iron-bank - - tde - - addons - - '#Reference' - - operator_capability_levels - - faq - - troubleshooting - - migrating_edb_registries - - pg4k.v1 - - backup_recovery - - cncf-projects - - '#Appendix' - - backup_volumesnapshot - - backup_barmanobjectstore - - object_stores -navRootedTo: /edb-postgres-ai/platforms-and-tools/kubernetes -pdf: true ---- - -The {{name.ln}} operator is a fork based on [CloudNativePG™](https://cloudnative-pg.io). -It provides additional value such as compatibility with Oracle using EDB -Postgres Advanced Server and additional supported platforms such as IBM Power -and OpenShift. It is designed, developed, and supported by EDB and covers the -full lifecycle of a highly available Postgres database clusters with a -primary/standby architecture, using native streaming replication. - -{{name.ln}} was made generally available on February 4, 2021. Earlier versions were made available to selected customers prior to the GA release. - -!!!note - -The operator has been renamed from Cloud Native PostgreSQL. Existing users -of Cloud Native PostgreSQL will not experience any change, as the underlying -components and resources have not changed. -!!! - -## Key features in common with CloudNativePG™ - -- Kubernetes API integration for high availability - - CloudNativePG™ uses the `postgresql.cnpg.io/v1` API version - - {{name.ln}} uses the `postgresql.k8s.enterprisedb.io/v1` API version -- Self-healing through failover and automated recreation of replicas -- Capacity management with scale up/down capabilities -- Planned switchovers for scheduled maintenance -- Read-only and read-write Kubernetes services definitions -- Rolling updates for Postgres minor versions and operator upgrades -- Continuous backup and point-in-time recovery -- Connection Pooling with PgBouncer -- Integrated metrics exporter out of the box -- PostgreSQL replication across multiple Kubernetes clusters -- Separate volume for WAL files - -## Features unique to EDB Postgres of Kubernetes - -- [Long Term Support](#long-term-support) -- Support on IBM Power and z/Linux through partnership with IBM -- [Oracle compatibility](/epas/latest/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/) through EDB Postgres Advanced Sever -- [Transparent Data Encryption (TDE)](/tde/latest/) through EDB Postgres Advanced Server -- Cold backup support with Kasten and Velero/OADP -- Generic adapter for third-party Kubernetes backup tools - -You can [evaluate {{name.ln}} for free](evaluation.md) as part of a trial subscription. -You need a valid EDB subscription to use {{name.ln}} in production. - -!!!note - -Based on the [Operator Capability Levels model](operator_capability_levels.md), -users can expect a **"Level V - Auto Pilot"** set of capabilities from the -{{name.ln}} Operator. -!!! - -### Long Term Support - -EDB is committed to declaring a Long Term Support (LTS) version of {{name.ln}} annually. 1.28 is the current LTS version. Each LTS version will -receive maintenance releases and be supported for an additional 12 months beyond the standard 6 months for a total of 18 months from the initial release. - -For example, v1.25 of {{name.ln}} was released in December, 2024. -Because it was declared an LTS version, it will be supported for a total of 18 months, until June, 2026. - -For a list of currently supported versions and their statuses, see: [Platform Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#edb%20postgres%C2%AE%20ai%20for%20cloudnativepg%E2%84%A2%20cluster). - -While we encourage customers to regularly upgrade to the latest version of the operator to take -advantage of new features, having LTS versions allows customers desiring additional stability to stay on the same -version for 12-18 months before upgrading. - -## Licensing - -{{name.ln}} works with both PostgreSQL, EDB Postgres Extended and EDB Postgres -Advanced server, and is available under the -[EDB End User License Agreement](https://www.enterprisedb.com/legal/EDB-Eula). - -You can [evaluate {{name.ln}} for free](evaluation.md) as part of a trial subscription. -You need a valid EDB subscription to use {{name.ln}} in production. - -## Supported releases and Kubernetes distributions - -For a list of the minor releases of {{name.ln}} that are -supported by EDB, please refer to the -["Platform Compatibility"](https://www.enterprisedb.com/resources/platform-compatibility#pgk8s) -page. Here you can also find which Kubernetes distributions and versions are -supported for each of them and the EOL dates. - -### Multiple architectures - -The {{name.ln}} Operator container images support the multi-arch -format for the following platforms: `linux/amd64`, `linux/arm64`, `linux/ppc64le`, `linux/s390x`. - -!!!warning - -{{name.ln}} requires that all nodes in a Kubernetes cluster have the -same CPU architecture, thus a hybrid CPU architecture Kubernetes cluster is not -supported. Additionally, EDB supports `linux/ppc64le` and `linux/s390x` architectures -on OpenShift only. -!!! - -## Supported Postgres versions - -The following versions of Postgres are currently supported by version 1.28: - -- PostgreSQL: 14 - 18 -- EDB Postgres Advanced: 14 - 18 -- EDB Postgres Extended: 14 - 18 - -PostgreSQL and EDB Postgres Advanced are available on the following platforms: -`linux/amd64`, `linux/ppc64le`, `linux/s390x`. -In addition, PostgreSQL is also supported on `linux/arm64`. -EDB Postgres Extended is supported only on `linux/amd64`. -EDB supports operand images for `linux/ppc64le` and `linux/s390x` architectures -on OpenShift only. - -## About this guide - -Follow the instructions in the ["Quickstart"](quickstart.md) to test {{name.ln}} -on a local Kubernetes cluster using Kind, or Minikube. - -In case you are not familiar with some basic terminology on Kubernetes and PostgreSQL, -please consult the ["Before you start" section](before_you_start.md). - -!!!note - -Although the guide primarily addresses Kubernetes, all concepts can -be extended to OpenShift as well. -!!! - -*[Postgres, PostgreSQL and the Slonik Logo](https://www.postgresql.org/about/policies/trademarks/) -are trademarks or registered trademarks of the PostgreSQL Community Association -of Canada, and used with their permission.* diff --git a/product_docs/docs/postgres_for_kubernetes/preview/installation_upgrade.mdx b/product_docs/docs/postgres_for_kubernetes/preview/installation_upgrade.mdx deleted file mode 100644 index bd65061da97..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/installation_upgrade.mdx +++ /dev/null @@ -1,456 +0,0 @@ ---- -title: 'Installation and upgrades' -originalFilePath: 'src/installation_upgrade.md' ---- - -!!!note OpenShift - -For instructions on how to install Cloud Native PostgreSQL on Red Hat -OpenShift Container Platform, please refer to the ["OpenShift"](openshift.md) -section. -!!! - -!!!warning - -OLM (via [operatorhub.io](https://operatorhub.io/) is no longer supported -as an installation method for {{name.ln}}. -!!! - -## Installation on Kubernetes - -### Obtaining an EDB subscription token - -!!!info Important - -You must obtain an EDB subscription token to install {{name.ln}}. Without a token, you will not be able to access the EDB private software repositories. -!!! - -Installing EDB Postgres Distributed for Kubernetes requires an EDB Repos 2.0 token to gain access to the EDB private software repositories. -For instructions on obtaining this token, see: [Get your token](/repos/getting_started/get_your_token/). - -Then set the Repos 2.0 token as an environment variable `EDB_SUBSCRIPTION_TOKEN`: - -```shell -EDB_SUBSCRIPTION_TOKEN= -``` - -!!!warning - -The token is sensitive information. Please ensure that you don't expose it to unauthorized users. -!!! - -You can now proceed with the installation. - -### Using the Helm Chart - -The operator can be installed using the provided [Helm chart](https://github.com/EnterpriseDB/edb-postgres-for-kubernetes-charts). - -### Directly using the operator manifest - -#### Install the EDB pull secret - -Before installing {{name.ln}}, you need to create a pull secret for EDB software in the `postgresql-operator-system` namespace. - -The pull secret needs to be saved in the namespace where the operator will reside. Create the `postgresql-operator-system` namespace using this command: - -```shell -kubectl create namespace postgresql-operator-system -``` - -To create the pull secret itself, run the following command: - -```shell -kubectl create secret -n postgresql-operator-system docker-registry edb-pull-secret \ - --docker-server=docker.enterprisedb.com \ - --docker-username=k8s \ - --docker-password="$EDB_SUBSCRIPTION_TOKEN" -``` - -#### Install the operator - -Now that the pull-secret has been added to the namespace, the operator can be installed like any other resource in Kubernetes, -through a YAML manifest applied via `kubectl`. - -You can install the [latest operator manifest](https://get.enterprisedb.io/pg4k/pg4k-1.30.0-rc1.yaml) -for this minor release as follows: - -```sh -kubectl apply --server-side -f \ - https://get.enterprisedb.io/pg4k/pg4k-1.30.0-rc1.yaml -``` - -You can verify that with: - -```sh -kubectl rollout status deployment \ - -n postgresql-operator-system postgresql-operator-controller-manager -``` - -### Using the `cnp` plugin for `kubectl` - -You can use the `cnp` plugin to override the default configuration options -that are in the static manifests. - -For example, to generate the default latest manifest but change the watch -namespaces to only be a specific namespace, you could run: - -```shell -kubectl cnp install generate \ - --watch-namespace "specific-namespace" \ - > cnp_for_specific_namespace.yaml -``` - -Please refer to ["`cnp` plugin"](./kubectl-plugin.md#generation-of-installation-manifests) documentation -for a more comprehensive example. - -!!!warning - -If you are deploying {{name.ln}} on GKE and get an error (`... failed to -call webhook...`), be aware that by default traffic between worker nodes -and control plane is blocked by the firewall except for a few specific -ports, as explained in the official -[docs](https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules) -and by this -[issue](https://github.com/cloudnative-pg/cloudnative-pg/issues/1360). -You'll need to either change the `targetPort` in the webhook service, to be -one of the allowed ones, or open the webhooks' port (`9443`) on the -firewall. -!!! - -## Details about the deployment - -In Kubernetes, the operator is by default installed in the `postgresql-operator-system` -namespace as a Kubernetes `Deployment`. The name of this deployment -depends on the installation method. -When installed through the manifest or the `cnp` plugin, by default, it is called `postgresql-operator-controller-manager`. -When installed via Helm, by default, the deployment name is derived from the helm release name, appended with the suffix `-edb-postgres-for-kubernetes` (e.g., `-edb-postgres-for-kubernetes`). - -!!!note - -With Helm you can customize the name of the deployment via the -`fullnameOverride` field in the [*"values.yaml"* file](https://helm.sh/docs/chart_template_guide/values_files/). -!!! - -You can get more information using the `describe` command in `kubectl`: - -```sh -$ kubectl get deployments -n postgresql-operator-system -NAME READY UP-TO-DATE AVAILABLE AGE - 1/1 1 1 18m -``` - -```sh -kubectl describe deploy \ - -n postgresql-operator-system \ - -``` - -As with any Deployment, it sits on top of a ReplicaSet and supports rolling -upgrades. The default configuration of the {{name.ln}} operator -comes with a Deployment of a single replica, which is suitable for most -installations. In case the node where the pod is running is not reachable -anymore, the pod will be rescheduled on another node. - -If you require high availability at the operator level, it is possible to -specify multiple replicas in the Deployment configuration - given that the -operator supports leader election. Also, you can take advantage of taints and -tolerations to make sure that the operator does not run on the same nodes where -the actual PostgreSQL clusters are running (this might even include the control -plane for self-managed Kubernetes installations). - -!!!note Operator configuration - -You can change the default behavior of the operator by overriding -some default options. For more information, please refer to the -["Operator configuration"](operator_conf.md) section. -!!! - -## Upgrades - -!!!warning CRITICAL WARNING: UPGRADING OPERATORS - -OpenShift users, or any customer attempting an operator upgrade, MUST configure the new unified repository pull secret (docker.enterprisedb.com/k8s) before running the upgrade. If the old, deprecated repository path is still in use during the upgrade process, image pull failure will occur, leading to deployment failure and potential downtime. Follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/) first. -!!! - -!!!info Important - -Please carefully read the [release notes](rel_notes) -before performing an upgrade as some versions might require -extra steps. -!!! - -Upgrading {{name.ln}} operator is a two-step process: - -1. upgrade the controller and the related Kubernetes resources -1. upgrade the instance manager running in every PostgreSQL pod - -Unless differently stated in the release notes, the first step is normally done -by applying the manifest of the newer version for plain Kubernetes -installations, or using the native package manager of the used distribution -(please follow the instructions in the above sections). - -The second step is automatically triggered after updating the controller. By -default, this initiates a rolling update of every deployed PostgreSQL cluster, -upgrading one instance at a time to use the new instance manager. The rolling -update concludes with a switchover, which is governed by the -`primaryUpdateStrategy` option. The default value, `unsupervised`, completes -the switchover automatically. If set to `supervised`, the user must manually -promote the new primary instance using the `cnp` plugin for `kubectl`. - -!!!note Rolling updates - -This process is discussed in-depth on the [Rolling Updates](rolling_update.md) page. -!!! - -!!!info Important - -In case `primaryUpdateStrategy` is set to the default value of `unsupervised`, -an upgrade of the operator will trigger a switchover on your PostgreSQL cluster, -causing a (normally negligible) downtime. If your PostgreSQL Cluster has only one -instance, the instance will be automatically restarted as `supervised` value is -not supported for `primaryUpdateStrategy`. In either case, your applications will -have to reconnect to PostgreSQL. -!!! - -The default rolling update behavior can be replaced with in-place updates of -the instance manager. This approach does not require a restart of the -PostgreSQL instance, thereby avoiding a switchover within the cluster. This -feature, which is disabled by default, is described in detail below. - -### Spread Upgrades - -By default, all PostgreSQL clusters are rolled out simultaneously, which may -lead to a spike in resource usage, especially when managing multiple clusters. -{{name.ln}} provides two configuration options at the [operator level](operator_conf.md) -that allow you to introduce delays between cluster roll-outs or even between -instances within the same cluster, helping to distribute resource usage over -time: - -- `CLUSTERS_ROLLOUT_DELAY`: Defines the number of seconds to wait between - roll-outs of different PostgreSQL clusters (default: `0`). -- `INSTANCES_ROLLOUT_DELAY`: Defines the number of seconds to wait between - roll-outs of individual instances within the same PostgreSQL cluster (default: - `0`). - -### In-place updates of the instance manager - -By default, {{name.ln}} issues a rolling update of the cluster -every time the operator is updated. The new instance manager shipped with the -operator is added to each PostgreSQL pod via an init container. - -However, this behavior can be changed via configuration to enable in-place -updates of the instance manager, which is the PID 1 process that keeps the -container alive. - -Internally, each instance manager in {{name.ln}} supports the injection of a -new executable that replaces the existing one after successfully completing an -integrity verification phase and gracefully terminating all internal processes. -Upon restarting with the new binary, the instance manager seamlessly adopts the -already running *postmaster*. - -As a result, the PostgreSQL process is unaffected by the update, refraining -from the need to perform a switchover. The other side of the coin, is that -the Pod is changed after the start, breaking the pure concept of immutability. - -You can enable this feature by setting the `ENABLE_INSTANCE_MANAGER_INPLACE_UPDATES` -environment variable to `'true'` in the -[operator configuration](operator_conf.md#available-options). - -The in-place upgrade process will not change the init container image inside the -Pods. Therefore, the Pod definition will not reflect the current version of the -operator. - -### Compatibility among versions - -{{name.ln}} follows semantic versioning. Every release of the -operator within the same API version is compatible with the previous one. -The current API version is v1, corresponding to versions 1.x.y of the operator. - -In addition to new features, new versions of the operator contain bug fixes and -stability enhancements. Because of this, **we strongly encourage users to upgrade -to the latest version of the operator**, as each version is released in order to -maintain the most secure and stable Postgres environment. - -{{name.ln}} currently releases new versions of the operator at -least monthly. If you are unable to apply updates as each version becomes -available, we recommend upgrading through each version in sequential order to -come current periodically and not skipping versions. - -The [release notes](rel_notes) page contains a detailed list of the -changes introduced in every released version of {{name.ln}}, -and it must be read before upgrading to a newer version of the software. - -Most versions are directly upgradable and in that case, applying the newer -manifest for plain Kubernetes installations or using the native package -manager of the chosen distribution is enough. - -When versions are not directly upgradable, the old version needs to be -removed before installing the new one. This won't affect user data but -only the operator itself. - -### Upgrading to 1.30.0, 1.29.2, or 1.28.4 - -!!!info Important - -We strongly recommend that all {{name.ln}} users upgrade to version -1.30.0, or at least to the latest stable version of your current minor release -(e.g., 1.29.2 or 1.28.4). -!!! - -These releases introduce changes worth reviewing before you upgrade. Two are -security changes that apply to **1.30.0, 1.29.2, and 1.28.4**: operator-side -password encoding and `search_path` hardening. The other three are new in -**1.30.0** only: the `DatabaseRole` resource for declarative role management, -safe primary election via a per-cluster Lease, and operator-to-instance -authentication on the instance manager's status port. -In addition, if you are upgrading from a release **older than 1.29.1, 1.28.3, or -1.25.8**, the metrics-exporter privilege separation from `CVE-2026-44477` also -applies. -Each is covered in its own subsection below. - -#### Operator-side password encoding - -Starting from versions 1.30.0, 1.29.2, and 1.28.4, for security reasons, -{{name.ln}} SCRAM-SHA-256 encodes role passwords **operator-side** -(client-side from PostgreSQL's point of view) before issuing -`CREATE`/`ALTER ROLE` statements. As a result, the literal that reaches -the PostgreSQL parser (and that extensions such as `pg_stat_statements` -or `pgaudit` may observe) is the same hash that ends up in -`pg_authid.rolpassword`, never the cleartext secret. The encoding is -applied to every basic-auth `Secret` the operator consumes: the -`postgres` superuser secret, the application-user secret, and any -managed-role password secret. Passwords already supplied in MD5 or -SCRAM-SHA-256 shadow form are passed through unchanged. - -Since PostgreSQL [14](https://www.postgresql.org/docs/release/14.0/), -`password_encryption` defaults to `scram-sha-256`, so we do not expect -existing installations to be affected by this change. - -If your cluster has explicitly overridden `password_encryption` to a -value other than `scram-sha-256` (for example, `md5`) and you want -PostgreSQL (not the operator) to decide how the password is hashed, -opt out by setting the annotation `k8s.enterprisedb.io/passwordPassthrough: "enabled"` -on each basic-auth `Secret` the operator consumes. The operator will -then forward the password value verbatim, and PostgreSQL will encode it -according to its own `password_encryption` GUC. - -!!!warning - -The `k8s.enterprisedb.io/passwordPassthrough` annotation must be set on the -**basic-auth Secret** itself, not on the `Cluster` resource. Placing it -on the `Cluster` has no effect, and the operator will continue to apply -SCRAM-SHA-256 encoding to the password before sending it to PostgreSQL. -!!! - -!!!warning - -With `k8s.enterprisedb.io/passwordPassthrough: "enabled"` the operator forwards the -Secret's `password` value verbatim. If that value is cleartext, as is -common on `password_encryption = md5` clusters, extensions such as -`pg_stat_statements` or `pgaudit` will observe it. -!!! - -See ["Opting out of operator-side encoding"](declarative_role_management.md#opting-out-of-operator-side-encoding) -for details. - -#### `search_path` hardening - -Also starting from versions 1.30.0, 1.29.2, and 1.28.4, for security reasons, -{{name.ln}} pins the `search_path` to a fixed `pg_catalog, public, -pg_temp` on every connection it opens to PostgreSQL, so that a -tenant-controlled `ALTER DATABASE`/`ALTER ROLE` setting can no longer -influence how operator-issued queries resolve unqualified object names. -The `SECURITY DEFINER` lookup function used by the PgBouncer integration -is recreated automatically with its own pinned `search_path` during the -first reconciliation after the upgrade. -See [Schema resolution and `search_path` hardening](security.md#schema-resolution-and-search_path-hardening) -for the rationale. - -This change also affects custom monitoring queries, which now run inside -a transaction whose `search_path` is pinned to `pg_catalog, public, -pg_temp`. If any of your custom metrics reference objects that live in -other user-defined schemas through an unqualified name, schema-qualify -them (for example `myschema.mytable`) so they keep resolving after the -upgrade. User-authored bootstrap (`postInit*`) and logical-import -post-import SQL are unaffected: they continue to run with the standard -`"$user", public` resolution. - -#### Declarative role management with the `DatabaseRole` resource - -Starting from version 1.30.0, you can also manage a PostgreSQL role as a -standalone [`DatabaseRole`](declarative_role_management.md) resource instead -of declaring it inline in the Cluster's `.spec.managed.roles` stanza. This is -an opt-in enhancement and requires no action on upgrade: existing inline roles -keep working unchanged, and the inline `managed.roles` method remains fully -supported. - -To move an existing inline role under a `DatabaseRole` without disruption, -create the `DatabaseRole` first and only then remove the matching entry from -`.spec.managed.roles`. While both exist the Cluster spec always takes -precedence, so management is handed over only once the inline entry is gone. -See [Migrating from inline managed roles](declarative_role_management.md#migrating-from-inline-managed-roles-to-a-databaserole) -for the full procedure. - -A `DatabaseRole` does not support `ensure: absent`: where the inline -`managed.roles` stanza drops a role by setting `ensure: absent`, a -`DatabaseRole` instead relies on the `databaseRoleReclaimPolicy` field. Delete -the resource with `databaseRoleReclaimPolicy: delete` to drop the role from -PostgreSQL, or keep the default `retain` to leave the role in place. - -#### Safe primary election - -Starting from version 1.30.0, {{name.ln}} coordinates primary promotion -through a per-cluster Kubernetes `Lease`, ensuring that at most one instance -promotes itself at any given time. The behavior is enabled automatically and -requires no configuration; the lease timings can optionally be tuned via -`.spec.primaryLease` (see ["Safe primary election"](failover.md#safe-primary-election)). - -!!!warning - -This feature requires the operator to manage `Lease` objects in the -`coordination.k8s.io` API group. The bundled operator manifest and the Helm -chart grant the required permissions automatically. If you manage the -operator's RBAC yourself, you must add the `create`, `get`, `list`, `update` -and `watch` verbs on `leases` in the `coordination.k8s.io` API group before -upgrading, otherwise primaries will be unable to promote. -!!! - -#### Operator-to-instance authentication - -Starting from version 1.30.0, the operator authenticates its calls to the -sensitive endpoints of the instance manager's status port (backup, -`pg_controldata`, partial WAL archive, and instance-manager upgrade) by pinning -an in-memory client certificate. This is enabled automatically and requires no -configuration. Status, health, and probe endpoints remain unauthenticated. See -[Operator-to-instance authentication](security.md#operator-to-instance-authentication) -for details. - -!!!warning - -This protection has a hard requirement: the status port **must** be served over -TLS, which has been the default since v1.24. Instances created by an operator -older than v1.24 serve the status port over plain HTTP; once their instance -manager is upgraded to 1.30.0 the operator can no longer authenticate to them -and every call to the protected endpoints is **permanently** rejected with -`401 Unauthorized`. If you still run such instances, perform a rolling update so -their Pods are recreated with a TLS-enabled status port. Instances created by -v1.24 or later are unaffected. -!!! - -#### Metrics exporter privilege separation (`CVE-2026-44477`) - -This applies only if you are upgrading from a release **older than 1.29.1, -1.28.3, or 1.25.8** (for example 1.29.0, 1.28.2, 1.25.7, or any earlier -version); installations already on 1.29.1, 1.28.3, 1.25.8, or later already -have this change. - -The fix for `CVE-2026-44477` / `GHSA-423p-g724-fr39` makes the metrics exporter -authenticate as a dedicated `cnp_metrics_exporter` role with `pg_monitor` -privileges only, instead of the `postgres` superuser. - -Custom monitoring queries that read user-owned tables, or use -`target_databases: '*'` against databases where `PUBLIC` `CONNECT` has been -revoked, need explicit `GRANT` statements to `cnp_metrics_exporter`. -See ["Custom query privileges and safety"](monitoring.md#custom-query-privileges-and-safety) -and ["Manually creating the metrics exporter role"](monitoring.md#manually-creating-the-metrics-exporter-role) -in the monitoring documentation. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/instance_manager.mdx b/product_docs/docs/postgres_for_kubernetes/preview/instance_manager.mdx deleted file mode 100644 index dc40ad1b96e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/instance_manager.mdx +++ /dev/null @@ -1,449 +0,0 @@ ---- -title: 'Postgres Instance Manager' -originalFilePath: 'src/instance_manager.md' ---- - - - -{{name.ln}} does not rely on an external tool for failover management. -It simply relies on the Kubernetes API server and a native key component called: -the **Postgres instance manager**. - -The instance manager takes care of the entire lifecycle of the PostgreSQL -server process (also known as `postmaster`). - -When you create a new cluster, the operator makes a Pod per instance. -The field `.spec.instances` specifies how many instances to create. - -Each Pod will start the instance manager as the parent process (PID 1) for the -main container, which in turn runs the PostgreSQL instance. During the lifetime -of the Pod, the instance manager acts as a backend to handle the -[startup, liveness and readiness probes](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes). - -## Startup Probe - -The startup probe ensures that a PostgreSQL instance, whether a primary or -standby, has fully started. - -!!!info -By default, the startup probe uses -[`pg_isready`](https://www.postgresql.org/docs/current/app-pg-isready.html). -However, the behavior can be customized by specifying a different startup -strategy. -!!! - -While the startup probe is running, the liveness and readiness probes remain -disabled. Following Kubernetes standards, if the startup probe fails, the -kubelet will terminate the container, which will then be restarted. - -The `.spec.startDelay` parameter specifies the maximum time, in seconds, -allowed for the startup probe to succeed. - -By default, the `startDelay` is set to `3600` seconds. It is recommended to -adjust this setting based on the time PostgreSQL needs to fully initialize in -your specific environment. - -!!!warning -Setting `.spec.startDelay` too low can cause the liveness probe to activate -prematurely, potentially resulting in unnecessary Pod restarts if PostgreSQL -hasn’t fully initialized. -!!! - -{{name.ln}} configures the startup probe with the following default parameters: - -```yaml -failureThreshold: FAILURE_THRESHOLD -periodSeconds: 10 -successThreshold: 1 -timeoutSeconds: 5 -``` - -The `failureThreshold` value is automatically calculated by dividing -`startDelay` by `periodSeconds`. - -You can customize any of the probe settings in the `.spec.probes.startup` -section of your configuration. - -!!!warning -Be sure that any custom probe settings are tailored to your cluster's -operational requirements to avoid unintended disruptions. -!!! - -!!!info -For more details on probe configuration, refer to the -[probe API documentation](pg4k.v1.md#probewithstrategy). -!!! - -If you manually specify `.spec.probes.startup.failureThreshold`, it will -override the default behavior and disable the automatic use of `startDelay`. - -For example, the following configuration explicitly sets custom probe -parameters, bypassing `startDelay`: - -```yaml -# ... snip -spec: - probes: - startup: - periodSeconds: 3 - timeoutSeconds: 3 - failureThreshold: 10 -``` - -### Startup Probe Strategy - -In certain scenarios, you may need to customize the startup strategy for your -PostgreSQL cluster. For example, you might delay marking a replica as started -until it begins streaming from the primary or define a replication lag -threshold that must be met before considering the replica ready. - -To accommodate these requirements, {{name.ln}} extends the -`.spec.probes.startup` stanza with two optional parameters: - -- `type`: specifies the criteria for considering the probe successful. Accepted - values, in increasing order of complexity/depth, include: - - - `pg_isready`: marks the probe as successful when the `pg_isready` command - exits with `0`. This is the default for primary instances and replicas. - - `query`: marks the probe as successful when a basic query is executed on - the `postgres` database locally. - - `streaming`: marks the probe as successful when the replica begins - streaming from its source and meets the specified lag requirements (details - below). - -- `maximumLag`: defines the maximum acceptable replication lag, measured in bytes - (expressed as Kubernetes quantities). This parameter is only applicable when - `type` is set to `streaming`. If `maximumLag` is not specified, the replica is - considered successfully started as soon as it begins streaming. - -!!!info Important -The `.spec.probes.startup.maximumLag` option is validated and enforced only -during the startup phase of the pod, meaning it applies exclusively when the -replica is starting. -!!! - -!!!warning -Incorrect configuration of the `maximumLag` option can cause continuous -failures of the startup probe, leading to repeated replica restarts. Ensure -you understand how this option works and configure appropriate values for -`failureThreshold` and `periodSeconds` to give the replica enough time to -catch up with its source. -!!! - -The following example requires a replica to have a maximum lag of 16Mi from the -source to be considered started: - -```yaml -# -probes: - startup: - type: streaming - maximumLag: 16Mi -``` - -## Liveness Probe - -The liveness probe begins after the startup probe successfully completes. Its -primary role is to ensure the PostgreSQL instance manager is operating -correctly. - -Following Kubernetes standards, if the liveness probe fails, the kubelet will -terminate the container, which will then be restarted. - -The amount of time before a Pod is classified as not alive is configurable via -the `.spec.livenessProbeTimeout` parameter. - -{{name.ln}} configures the liveness probe with the following default -parameters: - -```yaml -failureThreshold: FAILURE_THRESHOLD -periodSeconds: 10 -successThreshold: 1 -timeoutSeconds: 5 -``` - -The `failureThreshold` value is automatically calculated by dividing -`livenessProbeTimeout` by `periodSeconds`. - -By default, `.spec.livenessProbeTimeout` is set to `30` seconds. This means the -liveness probe will report a failure if it detects three consecutive probe -failures, with a 10-second interval between each check. - -You can customize any of the probe settings in the `.spec.probes.liveness` -section of your configuration. - -!!!warning -Be sure that any custom probe settings are tailored to your cluster's -operational requirements to avoid unintended disruptions. -!!! - -!!!info -For more details on probe configuration, refer to the -[probe API documentation](pg4k.v1.md#probe). -!!! - -If you manually specify `.spec.probes.liveness.failureThreshold`, it will -override the default behavior and disable the automatic use of -`livenessProbeTimeout`. - -For example, the following configuration explicitly sets custom probe -parameters, bypassing `livenessProbeTimeout`: - -```yaml -# ... snip -spec: - probes: - liveness: - periodSeconds: 3 - timeoutSeconds: 3 - failureThreshold: 10 -``` - -### Primary Isolation - -{{name.ln}} 1.27 introduces an additional behavior for the liveness -probe of a PostgreSQL primary, which will report a failure if **both** of the -following conditions are met: - -1. The instance manager cannot reach the Kubernetes API server -2. The instance manager cannot reach **any** other instance via the instance manager’s REST API - -The effect of this behavior is to consider an isolated primary to be not alive and subsequently **shut it down** when the liveness probe fails. - -It is **enabled by default** and can be disabled by adding the following: - -```yaml -spec: - probes: - liveness: - isolationCheck: - enabled: false -``` - -!!!info Important -Be aware that the default liveness probe settings—automatically derived from `livenessProbeTimeout`—might -be aggressive (30 seconds). As such, we recommend explicitly setting the -liveness probe configuration to suit your environment. -!!! - -The spec also accepts two optional network settings: `requestTimeout` -and `connectionTimeout`, both defaulting to `1000` (in milliseconds). -In cloud environments, you may need to increase these values. -For example: - -```yaml -spec: - probes: - liveness: - isolationCheck: - enabled: true - requestTimeout: "2000" - connectionTimeout: "2000" -``` - -!!!info - -Primary isolation is distinct from the [safe primary election](failover.md#safe-primary-election) -mechanism. The isolation check *fences* a primary that has lost connectivity to -both the API server and the other instances, while the primary lease coordinates -*which instance is allowed to promote*. The two mechanisms are complementary. -!!! - -## Readiness Probe - -The readiness probe starts once the startup probe has successfully completed. -Its primary purpose is to check whether the PostgreSQL instance is ready to -accept traffic and serve requests at any point during the pod's lifecycle. - -!!!info -By default, the readiness probe uses -[`pg_isready`](https://www.postgresql.org/docs/current/app-pg-isready.html). -However, the behavior can be customized by specifying a different readiness -strategy. -!!! - -Following Kubernetes standards, if the readiness probe fails, the pod will be -marked unready and will not receive traffic from any services. An unready pod -is also ineligible for promotion during automated failover scenarios. - -{{name.ln}} uses the following default configuration for the readiness probe: - -```yaml -failureThreshold: 3 -periodSeconds: 10 -successThreshold: 1 -timeoutSeconds: 5 -``` - -If the default settings do not suit your requirements, you can fully customize -the readiness probe by specifying parameters in the `.spec.probes.readiness` -stanza. For example: - -```yaml -# ... snip -spec: - probes: - readiness: - periodSeconds: 3 - timeoutSeconds: 3 - failureThreshold: 10 -``` - -!!!warning -Ensure that any custom probe settings are aligned with your cluster’s -operational requirements to prevent unintended disruptions. -!!! - -!!!info -For more information on configuring probes, see the -[probe API](pg4k.v1.md#probewithstrategy). -!!! - -### Readiness Probe Strategy - -In certain scenarios, you may need to customize the readiness strategy for your -cluster. For example, you might delay marking a replica as ready until it -begins streaming from the primary or define a maximum replication lag threshold -before considering the replica ready. - -To accommodate these requirements, {{name.ln}} extends the -`.spec.probes.readiness` stanza with two optional parameters: `type` and -`maximumLag`. Please refer to the [Startup Probe Strategy](#startup-probe-strategy) -section for detailed information on these options. - -!!!info Important -Unlike the startup probe, the `.spec.probes.readiness.maximumLag` option is -continuously monitored. A lagging replica may become unready if this setting is -not appropriately tuned. -!!! - -!!!warning -Incorrect configuration of the `maximumLag` option can lead to repeated -readiness probe failures, causing serious consequences, such as: - -- Exclusion of the replica from key operator features, such as promotion - during failover or participation in synchronous replication quorum. -- Disruptions in read/read-only services. -- In longer failover times scenarios, replicas might be declared unready, - leading to a cluster stall requiring manual intervention. -!!! - -!!!note Recommendation -Use the `streaming` and `maximumLag` options with extreme caution. If -you're unfamiliar with PostgreSQL replication, rely on the default -strategy. Seek professional advice if unsure. -!!! - -The following example requires a replica to have a maximum lag of 64Mi from the -source to be considered ready. It also provides approximately 300 seconds (30 -failures × 10 seconds) for the startup probe to succeed: - -```yaml -# -probes: - readiness: - type: streaming - maximumLag: 64Mi - failureThreshold: 30 - periodSeconds: 10 -``` - -## Shutdown control - -When a Pod running Postgres is deleted, either manually or by Kubernetes -following a node drain operation, the kubelet will send a termination signal to the -instance manager, and the instance manager will take care of shutting down -PostgreSQL in an appropriate way. -The `.spec.smartShutdownTimeout` and `.spec.stopDelay` options, expressed in seconds, -control the amount of time given to PostgreSQL to shut down. The values default -to 180 and 1800 seconds, respectively. - -The shutdown procedure is composed of two steps: - -1. The instance manager first issues a `CHECKPOINT`, then initiates a **smart** - shut down, disallowing any new connection to PostgreSQL. This step will last - for up to `.spec.smartShutdownTimeout` seconds. - -2. If PostgreSQL is still up, the instance manager requests a **fast** - shut down, terminating any existing connection and exiting promptly. - If the instance is archiving and/or streaming WAL files, the process - will wait for up to the remaining time set in `.spec.stopDelay` to complete the - operation and then forcibly shut down. Such a timeout needs to be at least 15 - seconds. - -!!!info Important -In order to avoid any data loss in the Postgres cluster, which impacts -the database [RPO](before_you_start.md#postgresql-terminology), don't delete the Pod where -the primary instance is running. In this case, perform a switchover to -another instance first. -!!! - -### Shutdown of the primary during a switchover - -During a switchover, the shutdown procedure slightly differs from the general -case. The instance manager of the former primary first issues a `CHECKPOINT`, -then initiates a **fast** shutdown of PostgreSQL before the designated new -primary is promoted, ensuring that all data are safely available on the new -primary. - -For this reason, the `.spec.switchoverDelay`, expressed in seconds, controls -the time given to the former primary to shut down gracefully and archive all -the WAL files. By default it is set to `3600` (1 hour). - -!!!warning -The `.spec.switchoverDelay` option affects the [RPO](before_you_start.md#postgresql-terminology) -and [RTO](before_you_start.md#postgresql-terminology) of your PostgreSQL database. Setting it to -a low value, might favor RTO over RPO but lead to data loss at cluster level -and/or backup level. On the contrary, setting it to a high value, might remove -the risk of data loss while leaving the cluster without an active primary for a -longer time during the switchover. -!!! - -## Failover - -In case of primary pod failure, the cluster will go into failover mode. -Please refer to the ["Failover" section](failover.md) for details. - -## Disk Full Failure - -Storage exhaustion is a well known issue for PostgreSQL clusters. -The [PostgreSQL documentation](https://www.postgresql.org/docs/current/diskusage.html#DISK-FULL) -highlights the possible failure scenarios and the importance of monitoring disk -usage to prevent it from becoming full. - -The same applies to {{name.ln}} and Kubernetes as well: the -["Monitoring" section](monitoring.md#predefined-set-of-metrics) -provides details on checking the disk space used by WAL segments and standard -metrics on disk usage exported to Prometheus. - -!!!info Important -In a production system, it is critical to monitor the database -continuously. Exhausted disk storage can lead to a database server shutdown. -!!! - -!!!note -The detection of exhausted storage relies on a storage class that -accurately reports disk size and usage. This may not be the case in simulated -Kubernetes environments like Kind or with test storage class implementations -such as `csi-driver-host-path`. -!!! - -If the disk containing the WALs becomes full and no more WAL segments can be -stored, PostgreSQL will stop working. {{name.ln}} correctly detects this issue -by verifying that there is enough space to store the next WAL segment, -and avoids triggering a failover, which could complicate recovery. - -That allows a human administrator to address the root cause. - -In such a case, if supported by the storage class, the quickest course of action -is currently to: - -1. Expand the storage size of the full PVC -2. Increase the size in the `Cluster` resource to the same value - -Once the issue is resolved and there is sufficient free space for WAL segments, -the Pod will restart and the cluster will become healthy. - -See also the ["Volume expansion" section](storage.md#volume-expansion) of the -documentation. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/iron-bank.mdx b/product_docs/docs/postgres_for_kubernetes/preview/iron-bank.mdx deleted file mode 100644 index 332fae06b44..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/iron-bank.mdx +++ /dev/null @@ -1,138 +0,0 @@ ---- -title: 'Iron Bank' -originalFilePath: 'src/iron-bank.md' ---- - -{{name.ln}}({{name.abbr}}) is available on [Iron Bank](https://p1.dso.mil/services/iron-bank). -As you can read in the -[overview page](https://docs-ironbank.dso.mil/overview/): - -> Iron Bank is the DoD's source for hardened containers. -> -> [… snipped …] -> -> Iron Bank ultimately is for anyone to consume or contribute. However, we specifically target the following personas: -> -> - DoD organizations wishing to consume hardened containers and Iron Banks BoE (Body of Evidence) for each container -> - DoD organizations wishing to help contribute to containers (e.g. bug fixes, new applications, updates) -> - DoD Authorization Officials wishing to understand the risks associated with applications -> - Commercial vendors wishing to bring their application to the DoD - -Iron Bank is a part of DoD's [Platform One](https://p1.dso.mil/). - -You will need your Iron Bank credentials to access the Iron Bank page for -[{{name.ln}}](https://repo1.dso.mil/dsop/enterprisedb/edb-pg4k-operator). - -## Pulling the EDB {{name.short}} and operand images from Iron Bank - -The images are pulled from the separate [Iron Bank container registry](https://registry1.dso.mil/). -To be able to pull images from the Iron Bank registry, please follow the -[instructions from Iron Bank](https://docs-ironbank.dso.mil/tutorials/image-pull/). - -Specifically, you will need to use your -[registry1](https://registry1.dso.mil/harbor/projects) -credentials to pull images. - -To find the desired operator or operand images, we recommend to use the search tool to look -with the string `enterprisedb`, and filter by `Tags`, looking for `stable`, as shown in -the image. From there, you can get the instruction to pull the image: - -![pulling-ironbank-images](./images/ironbank/pulling-the-image.png) - -For example, to pull the EPAS 18 operand from Ironbank, you can run: - -```bash -docker pull registry1.dso.mil/ironbank/enterprisedb/edb-postgres-advanced-18:18 -``` - -Similarly, for EPAS 16 or 17: - -```bash -docker pull registry1.dso.mil/ironbank/enterprisedb/edb-postgres-advanced-17:17 -docker pull registry1.dso.mil/ironbank/enterprisedb/edb-postgres-advanced-16:16 -``` - -If you want to pick a more specific tag or use a specific SHA, you need to find it from the Harbor page (e.g., [EPAS 18](https://registry1.dso.mil/harbor/projects/3/repositories/enterprisedb%2Fedb-postgres-advanced-18/artifacts-tab), [EPAS 17](https://registry1.dso.mil/harbor/projects/3/repositories/enterprisedb%2Fedb-postgres-advanced-17/artifacts-tab), [EPAS 16](https://registry1.dso.mil/harbor/projects/3/repositories/enterprisedb%2Fedb-postgres-advanced-16/artifacts-tab)). - -## Installing the {{name.short}} operator using the Iron Bank image - -For installation, you will need a deployment manifest that points to your Iron Bank image. -You can take the deployment manifest from the [installation instructions for EDB {{name.short}}](/postgres_for_kubernetes/latest/installation_upgrade/). -For example, for the 1.22.0 release, the manifest is available at -`https://get.enterprisedb.io/cnp/postgresql-operator-1.22.0.yaml`. -There are a couple of places where you will need to set the image path for the IronBank image. - -```yaml -apiVersion: apps/v1 -kind: Deployment -metadata: - labels: - app.kubernetes.io/name: cloud-native-postgresql - name: postgresql-operator-controller-manager - namespace: postgresql-operator-system -spec: - [… snipped …] - template: - metadata: - labels: - app.kubernetes.io/name: cloud-native-postgresql - spec: - containers: - - args: - - controller - [… snipped …] - env: - - name: PULL_SECRET_NAME - value: postgresql-operator-pull-secret - - name: OPERATOR_IMAGE_NAME - value: - - [… snipped …] - image: -``` - -If you wish for the operator to be deployed from Iron Bank directly, you will -need to create and set the pull secret with the credentials to the registry, -as described above. - -It may be easier to get the image from Iron Bank with the instructions on the -site, and from there, re-tag and publish it to a local registry, or push it -directly to your Kubernetes nodes. - -Once you have this in place, you can apply your manifest normally with -`kubectl apply -f`, as described in the [installation instructions](/postgres_for_kubernetes/latest/installation_upgrade/). - -## Deploying clusters with EPAS operands using IronBank images - -To deploy a cluster using the EPAS [operand](/postgres_for_kubernetes/latest/private_edb_registries/#operand-images) you must reference the Ironbank operand image appropriately in the `Cluster` resource YAML. -For example, to deploy a {{name.short}} Cluster using the EPAS 18 operand: - -1. Create or edit a `Cluster` resource YAML file with the following content: - - ```yaml - apiVersion: postgresql.k8s.enterprisedb.io/v1 - kind: Cluster - metadata: - name: cluster-example-full - spec: - imageName: registry1.dso.mil/ironbank/enterprisedb/edb-postgres-advanced-18:18 - imagePullSecrets: - - name: my_ironbank_secret - ``` - - For EPAS 17 or 16, use the corresponding image: - -- EPAS 17: `registry1.dso.mil/ironbank/enterprisedb/edb-postgres-advanced-17:17` -- EPAS 16: `registry1.dso.mil/ironbank/enterprisedb/edb-postgres-advanced-16:16` - -2. Apply the YAML: - - ``` - kubectl apply -f - ``` - -3. Verify the status of the resource: - - ``` - kubectl get clusters - ``` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/job_scheduling.mdx b/product_docs/docs/postgres_for_kubernetes/preview/job_scheduling.mdx deleted file mode 100644 index 0552ddc2f87..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/job_scheduling.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Job scheduling with EDB Postgres AI for CloudNativePG -navTitle: Job scheduling ---- - -If you need to perform regular maintenance or automation tasks in your PostgreSQL environment, there are two primary approaches: - -1. Kubernetes-native scheduling using Kubernetes [Jobs](https://kubernetes.io/docs/concepts/workloads/controllers/job/) or [CronJobs](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/). -2. In-database scheduling, using tools like: - - [pg_cron](/pg_extensions/pg_cron/), a lightweight cron-based job scheduler for PostgreSQL and EDB Postgres Extended (PGE) Server. - - [DBMS_SCHEDULER](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/), a robust built-in job scheduler available in EDB Postgres Advanced Server (EPAS). - - !!! Warning Pitfalls of in-database scheduling on distributed systems - - With an in-database job scheduler, jobs might run only on the primary instance. After a switchover or failover, scheduled jobs will continue only when the promoted primary carries the same scheduler configuration. A missing configuration might produce no error and jobs would simply stop firing. - - Verify that jobs still run after any failover. - -!!! Warning Transaction Semantics Still Apply - - Regardless of whether you use Kubernetes or in-database scheduling, database transaction semantics still govern the outcome of the job: - - - A job may be initiated and marked as successful by the scheduler. - - However, if a failover occurs during execution, the underlying transaction may not be committed. - - Depending on your replication setup, changes may not be propagated to the new primary node. - - Therefore, a successful job report doesn't guarantee successful data persistence. - -## Examples of scheduled maintenance tasks - -Common scheduled operations include: - -- Performing manual VACUUM on high-churn tables during off-peak hours. -- Refreshing materialized views to keep analytics up-to-date. -- Archiving or purging old records from transactional tables. - -However, scheduled jobs may also serve mission-critical business purposes, such as: - -- End-of-Day (EOD) financial reconciliation. -- Trade settlement and clearing processes. -- Periodic risk calculations or regulatory reporting. - -## Best practices for business-critical jobs - -It's the user's responsibility to implement custom retry and idempotency logic for jobs that are business-critical. -This may include: - -- Checking for existing records before inserts. -- Using advisory locks or state markers to avoid duplication. -- Re-running jobs safely without data corruption. - -In EPAS, you can also leverage [autonomous transactions](/epas/latest/application_programming/epas_compat_spl/06_transaction_control/03_pragma_autonomous_transaction/) for certain scenarios: these allow a block of work to commit independently of the parent transaction, which can be useful in logging, auditing, or compensating operations. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/kubectl-plugin.mdx b/product_docs/docs/postgres_for_kubernetes/preview/kubectl-plugin.mdx deleted file mode 100644 index e053358f23e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/kubectl-plugin.mdx +++ /dev/null @@ -1,1535 +0,0 @@ ---- -title: '{{name.ln}} Plugin' -originalFilePath: 'src/kubectl-plugin.md' -deepToC: true ---- - -{{name.ln}} provides a plugin for `kubectl` to manage a cluster in Kubernetes. -The plugin also works with `oc` in an OpenShift environment. - -## Install - -You can install the `cnp` plugin using a variety of methods. - -!!!note -For air-gapped systems, installation via package managers, using previously -downloaded files, may be a good option. -!!! - -### Via the installation script - -```sh -curl -sSfL \ - https://github.com/EnterpriseDB/kubectl-cnp/raw/main/install.sh | \ - sudo sh -s -- -b /usr/local/bin -``` - -### Using the Debian or RedHat packages - -In the -[releases section of the GitHub repository](https://github.com/EnterpriseDB/kubectl-cnp/releases), -you can navigate to any release of interest (pick the same or newer release -than your {{name.ln}} operator), and in it you will find an **Assets** -section. In that section are pre-built packages for a variety of systems. -As a result, you can follow standard practices and instructions to install -them in your systems. - -#### Debian packages - -For example, let's install the 1.30.0-rc1 release of the plugin, for an Intel based -64 bit server. First, we download the right `.deb` file. - -```sh -wget https://github.com/EnterpriseDB/kubectl-cnp/releases/download/v1.30.0-rc1/kubectl-cnp_1.30.0-rc1_linux_x86_64.deb \ - --output-document kube-plugin.deb -``` - -Then, with superuser privileges, install from the local file using `dpkg`: - -```console -$ sudo dpkg -i kube-plugin.deb -Selecting previously unselected package cnp. -(Reading database ... 6688 files and directories currently installed.) -Preparing to unpack kube-plugin.deb ... -Unpacking kubectl-cnp (1.30.0-rc1) ... -Setting up kubectl-cnp (1.30.0-rc1) ... -``` - -#### RPM packages - -As in the example for `.rpm` packages, let's install the 1.30.0-rc1 release for an -Intel 64 bit machine. Note the `--output` flag to provide a file name. - -```sh -curl -L https://github.com/EnterpriseDB/kubectl-cnp/releases/download/v1.30.0-rc1/kubectl-cnp_1.30.0-rc1_linux_x86_64.rpm \ - --output kube-plugin.rpm -``` - -Then, with superuser privileges, install with `yum`, and you're ready to use: - -```console -$ sudo yum --disablerepo=* localinstall kube-plugin.rpm -Failed to set locale, defaulting to C.UTF-8 -Dependencies resolved. -==================================================================================================== - Package Architecture Version Repository Size -==================================================================================================== -Installing: - cnp x86_64 1.30.0-rc1-1 @commandline 20 M - -Transaction Summary -==================================================================================================== -Install 1 Package - -Total size: 20 M -Installed size: 78 M -Is this ok [y/N]: y -``` - -### Supported Architectures - -{{name.ln}} Plugin is currently built for the following -operating system and architectures: - -* Linux - * amd64 - * arm 5/6/7 - * arm64 - * s390x - * ppc64le -* macOS - * amd64 - * arm64 -* Windows - * 386 - * amd64 - * arm 5/6/7 - * arm64 - -### Configuring auto-completion - -To configure auto-completion for the plugin, a helper shell script needs to be -installed into your current PATH. Assuming the latter contains `/usr/local/bin`, -this can be done with the following commands: - -```shell -cat > kubectl_complete-cnp < -``` - -!!!note -The plugin automatically detects if the standard output channel is connected to a terminal. -In such cases, it may add ANSI colors to the command output. To disable colors, use the -`--color=never` option with the command. -!!! - -### Generation of installation manifests - -The `cnp` plugin can be used to generate the YAML manifest for the -installation of the operator. This option would typically be used if you want -to override some default configurations such as number of replicas, -installation namespace, namespaces to watch, and so on. - -For details and available options, run: - -```sh -kubectl cnp install generate --help -``` - -The main options are: - -- `-n`: specifies the namespace in which to install the operator (default: - `postgresql-operator-system`). -- `--control-plane`: if set to true, the operator deployment will include a - toleration and affinity for `node-role.kubernetes.io/control-plane`. -- `--replicas`: sets the number of replicas in the deployment. -- `--watch-namespace`: specifies a comma-separated list of namespaces to watch - (default: all namespaces). -- `--version`: defines the minor version of the operator to be installed, such - as `1.23`. If a minor version is specified, the plugin installs the latest - patch version of that minor version. If no version is supplied, the plugin - installs the latest `MAJOR.MINOR.PATCH` version of the operator. - -An example of the `generate` command, which will generate a YAML manifest that -will install the operator, is as follows: - -```sh -kubectl cnp install generate \ - -n king \ - --version 1.23 \ - --replicas 3 \ - --watch-namespace "albert, bb, freddie" \ - > operator.yaml -``` - -The flags in the above command have the following meaning: - -- `-n king` install the {{name.abbr}} operator into the `king` namespace -- `--version 1.23` install the latest patch version for minor version 1.23 -- `--replicas 3` install the operator with 3 replicas -- `--watch-namespace "albert, bb, freddie"` have the operator watch for - changes in the `albert`, `bb` and `freddie` namespaces only - -### Status - -The `status` command provides an overview of the current status of your -cluster, including: - -* **general information**: name of the cluster, PostgreSQL's system ID, number of - instances, current timeline and position in the WAL -* **backup**: point of recoverability, and WAL archiving status as returned by - the `pg_stat_archiver` view from the primary - or designated primary in the - case of a replica cluster -* **streaming replication**: information taken directly from the `pg_stat_replication` - view on the primary instance -* **instances**: information about each Postgres instance, taken directly by each - instance manager; in the case of a standby, the `Current LSN` field corresponds - to the latest write-ahead log location that has been replayed during recovery - (replay LSN). - -!!!info Important -The status information above is taken at different times and at different -locations, resulting in slightly inconsistent returned values. For example, -the `Current Write LSN` location in the main header, might be different -from the `Current LSN` field in the instances status as it is taken at -two different time intervals. -!!! - -```sh -kubectl cnp status sandbox -``` - -```output -Cluster Summary -Name: default/sandbox -System ID: 7423474350493388827 -PostgreSQL Image: docker.enterprisedb.com/k8s/edb-postgres-extended:18.1-standard-ubi9 -Primary instance: sandbox-1 -Primary start time: 2024-10-08 18:31:57 +0000 UTC (uptime 1m14s) -Status: Cluster in healthy state -Instances: 3 -Ready instances: 3 -Size: 126M -Current Write LSN: 0/604DE38 (Timeline: 1 - WAL File: 000000010000000000000006) - -Continuous Backup status -Not configured - -Streaming Replication status -Replication Slots Enabled -Name Sent LSN Write LSN Flush LSN Replay LSN Write Lag Flush Lag Replay Lag State Sync State Sync Priority Replication Slot ----- -------- --------- --------- ---------- --------- --------- ---------- ----- ---------- ------------- ---------------- -sandbox-2 0/604DE38 0/604DE38 0/604DE38 0/604DE38 00:00:00 00:00:00 00:00:00 streaming async 0 active -sandbox-3 0/604DE38 0/604DE38 0/604DE38 0/604DE38 00:00:00 00:00:00 00:00:00 streaming async 0 active - -Instances status -Name Current LSN Replication role Status QoS Manager Version Node ----- ----------- ---------------- ------ --- --------------- ---- -sandbox-1 0/604DE38 Primary OK BestEffort 1.30.0-rc1 k8s-eu-worker -sandbox-2 0/604DE38 Standby (async) OK BestEffort 1.30.0-rc1 k8s-eu-worker2 -sandbox-3 0/604DE38 Standby (async) OK BestEffort 1.30.0-rc1 k8s-eu-worker -``` - -If you require more detailed status information, use the `--verbose` option (or -`-v` for short). The level of detail increases each time the flag is repeated: - -```sh -kubectl cnp status sandbox --verbose -``` - -```output -Cluster Summary -Name: default/sandbox -System ID: 7423474350493388827 -PostgreSQL Image: docker.enterprisedb.com/k8s/edb-postgres-extended:18.1-standard-ubi8 -Primary instance: sandbox-1 -Primary start time: 2024-10-08 18:31:57 +0000 UTC (uptime 2m4s) -Status: Cluster in healthy state -Instances: 3 -Ready instances: 3 -Size: 126M -Current Write LSN: 0/6053720 (Timeline: 1 - WAL File: 000000010000000000000006) - -Continuous Backup status -Not configured - -Physical backups -No running physical backups found - -Streaming Replication status -Replication Slots Enabled -Name Sent LSN Write LSN Flush LSN Replay LSN Write Lag Flush Lag Replay Lag State Sync State Sync Priority Replication Slot Slot Restart LSN Slot WAL Status Slot Safe WAL Size ----- -------- --------- --------- ---------- --------- --------- ---------- ----- ---------- ------------- ---------------- ---------------- --------------- ------------------ -sandbox-2 0/6053720 0/6053720 0/6053720 0/6053720 00:00:00 00:00:00 00:00:00 streaming async 0 active 0/6053720 reserved NULL -sandbox-3 0/6053720 0/6053720 0/6053720 0/6053720 00:00:00 00:00:00 00:00:00 streaming async 0 active 0/6053720 reserved NULL - -Unmanaged Replication Slot Status -No unmanaged replication slots found - -Managed roles status -No roles managed - -Tablespaces status -No managed tablespaces - -Pod Disruption Budgets status -Name Role Expected Pods Current Healthy Minimum Desired Healthy Disruptions Allowed ----- ---- ------------- --------------- ----------------------- ------------------- -sandbox replica 2 2 1 1 -sandbox-primary primary 1 1 1 0 - -Instances status -Name Current LSN Replication role Status QoS Manager Version Node ----- ----------- ---------------- ------ --- --------------- ---- -sandbox-1 0/6053720 Primary OK BestEffort 1.30.0-rc1 k8s-eu-worker -sandbox-2 0/6053720 Standby (async) OK BestEffort 1.30.0-rc1 k8s-eu-worker2 -sandbox-3 0/6053720 Standby (async) OK BestEffort 1.30.0-rc1 k8s-eu-worker -``` - -With an additional `-v` (e.g. `kubectl cnp status sandbox -v -v`), you can -also view PostgreSQL configuration, HBA settings, and certificates. - -The command also supports output in `yaml` and `json` format. - -### Promote - -The meaning of this command is to `promote` a pod in the cluster to primary, so you -can start with maintenance work or test a switch-over situation in your cluster - -```sh -kubectl cnp promote cluster-example cluster-example-2 -``` - -Or you can use the instance node number to promote - -```sh -kubectl cnp promote cluster-example 2 -``` - -### Certificates - -Clusters created using the {{name.ln}} operator work with a CA to sign -a TLS authentication certificate. - -To get a certificate, you need to provide a name for the secret to store -the credentials, the cluster name, and a user for this certificate - -```sh -kubectl cnp certificate cluster-cert --cnp-cluster cluster-example --cnp-user appuser -``` - -After the secret it's created, you can get it using `kubectl` - -```sh -kubectl get secret cluster-cert -``` - -And the content of the same in plain text using the following commands: - -```sh -kubectl get secret cluster-cert -o json | jq -r '.data | map(@base64d) | .[]' -``` - -### Restart - -The `kubectl cnp restart` command can be used in two cases: - -- requesting the operator to orchestrate a rollout restart - for a certain cluster. This is useful to apply - configuration changes to cluster dependent objects, such as ConfigMaps - containing custom monitoring queries. - -- request a single instance restart, either in-place if the instance is - the cluster's primary or deleting and recreating the pod if - it is a replica. - -```sh -# this command will restart a whole cluster in a rollout fashion -kubectl cnp restart [clusterName] - -# this command will restart a single instance, according to the policy above -kubectl cnp restart [clusterName] [pod] -``` - -If the in-place restart is requested but the change cannot be applied without -a switchover, the switchover will take precedence over the in-place restart. A -common case for this will be a minor upgrade of PostgreSQL image. - -!!!note -If you want ConfigMaps and Secrets to be **automatically** reloaded -by instances, you can add a label with key `k8s.enterprisedb.io/reload` to it. -!!! - -### Reload - -The `kubectl cnp reload` command requests the operator to trigger a reconciliation -loop for a certain cluster. This is useful to apply configuration changes -to cluster dependent objects, such as ConfigMaps containing custom monitoring queries. - -The following command will reload all configurations for a given cluster: - -```sh -kubectl cnp reload [cluster_name] -``` - -### Maintenance - -The `kubectl cnp maintenance` command helps to modify one or more clusters -across namespaces and set the maintenance window values, it will change -the following fields: - -* .spec.nodeMaintenanceWindow.inProgress -* .spec.nodeMaintenanceWindow.reusePVC - -Accepts as argument `set` and `unset` using this to set the -`inProgress` to `true` in case `set`and to `false` in case of `unset`. - -By default, `reusePVC` is always set to `false` unless the `--reusePVC` flag is passed. - -The plugin will ask for a confirmation with a list of the cluster to modify -and their new values, if this is accepted this action will be applied to -all the cluster in the list. - -If you want to set in maintenance all the PostgreSQL in your Kubernetes cluster, -just need to write the following command: - -```sh -kubectl cnp maintenance set --all-namespaces -``` - -And you'll have the list of all the cluster to update - -```output -The following are the new values for the clusters -Namespace Cluster Name Maintenance reusePVC ---------- ------------ ----------- -------- -default cluster-example true false -default pg-backup true false -test cluster-example true false -Do you want to proceed? [y/n]: y -``` - -### Report - -The `kubectl cnp report` command bundles various pieces -of information into a ZIP file. -It aims to provide the needed context to debug problems -with clusters in production. - -It has two sub-commands: `operator` and `cluster`. - -#### report Operator - -The `operator` sub-command requests the operator to provide information -regarding the operator deployment, configuration and events. - -!!!info Important -All confidential information in Secrets and ConfigMaps is REDACTED. -The Data map will show the **keys** but the values will be empty. -The flag `-S` / `--stopRedaction` will defeat the redaction and show the -values. Use only at your own risk, this will share private data. -!!! - -!!!note -By default, operator logs are not collected, but you can enable operator -log collection with the `--logs` flag -!!! - -* **deployment information**: the operator Deployment and operator Pod -* **configuration**: the Secrets and ConfigMaps in the operator namespace -* **events**: the Events in the operator namespace -* **webhook configuration**: the mutating and validating webhook configurations -* **webhook service**: the webhook service -* **logs**: logs for the operator Pod (optional, off by default) in JSON-lines format - -The command will generate a ZIP file containing various manifest in YAML format -(by default, but settable to JSON with the `-o` flag). -Use the `-f` flag to name a result file explicitly. If the `-f` flag is not used, a -default time-stamped filename is created for the zip file. - -!!!note -The report plugin obeys `kubectl` conventions, and will look for objects constrained -by namespace. The {{name.short}} Operator will generally not be installed in the same -namespace as the clusters. -E.g. the default installation namespace is postgresql-operator-system -!!! - -```sh -kubectl cnp report operator -n -``` - -results in - -```output -Successfully written report to "report_operator_.zip" (format: "yaml") -``` - -With the `-f` flag set: - -```sh -kubectl cnp report operator -n -f reportRedacted.zip -``` - -Unzipping the file will produce a time-stamped top-level folder to keep the -directory tidy: - -```sh -unzip reportRedacted.zip -``` - -will result in: - -```output -Archive: reportRedacted.zip - creating: report_operator_/ - creating: report_operator_/manifests/ - inflating: report_operator_/manifests/deployment.yaml - inflating: report_operator_/manifests/operator-pod.yaml - inflating: report_operator_/manifests/events.yaml - inflating: report_operator_/manifests/validating-webhook-configuration.yaml - inflating: report_operator_/manifests/mutating-webhook-configuration.yaml - inflating: report_operator_/manifests/webhook-service.yaml - inflating: report_operator_/manifests/postgresql-operator-ca-secret.yaml - inflating: report_operator_/manifests/postgresql-operator-webhook-cert.yaml -``` - -If you activated the `--logs` option, you'd see an extra subdirectory: - -```output -Archive: report_operator_.zip - - creating: report_operator_/operator-logs/ - inflating: report_operator_/operator-logs/postgresql-operator-controller-manager-66fb98dbc5-pxkmh-logs.jsonl -``` - -!!!note -The plugin will try to get the PREVIOUS operator's logs, which is helpful -when investigating restarted operators. -In all cases, it will also try to get the CURRENT operator logs. If current -and previous logs are available, it will show them both. -!!! - -```output -====== Begin of Previous Log ===== -2023-03-28T12:56:41.251711811Z {"level":"info","ts":"2023-03-28T12:56:41Z","logger":"setup","msg":"Starting EDB Postgres for Kubernetes Operator","version":"1.30.0-rc1","build":{"Version":"1.30.0-rc1+dev107","Commit":"cc9bab17","Date":"2023-03-28"}} -2023-03-28T12:56:41.251851909Z {"level":"info","ts":"2023-03-28T12:56:41Z","logger":"setup","msg":"Starting pprof HTTP server","addr":"0.0.0.0:6060"} - - -====== End of Previous Log ===== -2023-03-28T12:57:09.854306024Z {"level":"info","ts":"2023-03-28T12:57:09Z","logger":"setup","msg":"Starting EDB Postgres for Kubernetes Operator","version":"1.30.0-rc1","build":{"Version":"1.30.0-rc1+dev107","Commit":"cc9bab17","Date":"2023-03-28"}} -2023-03-28T12:57:09.854363943Z {"level":"info","ts":"2023-03-28T12:57:09Z","logger":"setup","msg":"Starting pprof HTTP server","addr":"0.0.0.0:6060"} -``` - -If the operator hasn't been restarted, you'll still see the `====== Begin …` -and `====== End …` guards, with no content inside. - -You can verify that the confidential information is REDACTED by default: - -```sh -cd report_operator_/manifests/ -head postgresql-operator-ca-secret.yaml -``` - -```yaml -data: - ca.crt: "" - ca.key: "" -metadata: - creationTimestamp: "2022-03-22T10:42:28Z" - managedFields: - - apiVersion: v1 - fieldsType: FieldsV1 - fieldsV1: -``` - -With the `-S` (`--stopRedaction`) option activated, secrets are shown: - -```sh -kubectl cnp report operator -n -f reportNonRedacted.zip -S -``` - -You'll get a reminder that you're about to view confidential information: - -```output -WARNING: secret Redaction is OFF. Use it with caution -Successfully written report to "reportNonRedacted.zip" (format: "yaml") -``` - -```sh -unzip reportNonRedacted.zip -head postgresql-operator-ca-secret.yaml -``` - -```yaml -data: - ca.crt: LS0tLS1CRUdJTiBD… - ca.key: LS0tLS1CRUdJTiBF… -metadata: - creationTimestamp: "2022-03-22T10:42:28Z" - managedFields: - - apiVersion: v1 - fieldsType: FieldsV1 -``` - -#### report Cluster - -The `cluster` sub-command gathers the following: - -* **cluster resources**: the cluster information, same as `kubectl get cluster -o yaml` -* **cluster pods**: pods in the cluster namespace matching the cluster name -* **cluster jobs**: jobs, if any, in the cluster namespace matching the cluster name -* **events**: events in the cluster namespace -* **pod logs**: logs for the cluster Pods (optional, off by default) in JSON-lines format -* **job logs**: logs for the Pods created by jobs (optional, off by default) in JSON-lines format - -The `cluster` sub-command accepts the `-f` and `-o` flags, as the `operator` does. -If the `-f` flag is not used, a default timestamped report name will be used. -Note that the cluster information does not contain configuration Secrets / ConfigMaps, -so the `-S` is disabled. - -!!!note -By default, cluster logs are not collected, but you can enable cluster -log collection with the `--logs` flag -!!! - -Usage: - -```sh -kubectl cnp report cluster [flags] -``` - -Note that, unlike the `operator` sub-command, for the `cluster` sub-command you -need to provide the cluster name, and very likely the namespace, unless the cluster -is in the default one. - -```sh -kubectl cnp report cluster example -f report.zip -n example_namespace -``` - -and then: - -```sh -unzip report.zip -``` - -```output -Archive: report.zip - creating: report_cluster_example_/ - creating: report_cluster_example_/manifests/ - inflating: report_cluster_example_/manifests/cluster.yaml - inflating: report_cluster_example_/manifests/cluster-pods.yaml - inflating: report_cluster_example_/manifests/cluster-jobs.yaml - inflating: report_cluster_example_/manifests/events.yaml -``` - -Remember that you can use the `--logs` flag to add the pod and job logs to the ZIP. - -```sh -kubectl cnp report cluster example -n example_namespace --logs -``` - -will result in: - -```output -Successfully written report to "report_cluster_example_.zip" (format: "yaml") -``` - -```sh -unzip report_cluster_.zip -``` - -```output -Archive: report_cluster_example_.zip - creating: report_cluster_example_/ - creating: report_cluster_example_/manifests/ - inflating: report_cluster_example_/manifests/cluster.yaml - inflating: report_cluster_example_/manifests/cluster-pods.yaml - inflating: report_cluster_example_/manifests/cluster-jobs.yaml - inflating: report_cluster_example_/manifests/events.yaml - creating: report_cluster_example_/logs/ - inflating: report_cluster_example_/logs/cluster-example-full-1.jsonl - creating: report_cluster_example_/job-logs/ - inflating: report_cluster_example_/job-logs/cluster-example-full-1-initdb-qnnvw.jsonl - inflating: report_cluster_example_/job-logs/cluster-example-full-2-join-tvj8r.jsonl -``` - -##### OpenShift support - -The `report operator` directive will detect automatically if the cluster is -running on OpenShift, and will get the Cluster Service Version and the -Install Plan, and add them automatically to the zip under the `openshift` -sub-folder. - -!!!note -the namespace becomes very important on OpenShift. The default namespace -for OpenShift in CNP is "openshift-operators". Many (most) clients will use -a different namespace for the CNP operator. -!!! - -```sh -kubectl cnp report operator -n openshift-operators -``` - -results in - -```sh -Successfully written report to "report_operator_.zip" (format: "yaml") -``` - -You can find the OpenShift-related files in the `openshift` sub-folder: - -```sh -unzip report_operator_.zip -cd report_operator_/ -cd openshift -head clusterserviceversions.yaml -``` - -```yaml -apiVersion: operators.coreos.com/v1alpha1 -items: -- apiVersion: operators.coreos.com/v1alpha1 - kind: ClusterServiceVersion - metadata: - annotations: - alm-examples: |- - [ - { - "apiVersion": "postgresql.k8s.enterprisedb.io/v1", -``` - -### Logs - -The `kubectl cnp logs` command allows to follow the logs of a collection -of pods related to {{name.ln}} in a single go. - -It has at the moment one available sub-command: `cluster`. - -#### Cluster logs - -The `cluster` sub-command gathers all the pod logs for a cluster in a single -stream or file. -This means that you can get all the pod logs in a single terminal window, with a -single invocation of the command. - -As in all the cnp plugin sub-commands, you can get instructions and help with -the `-h` flag: - -`kubectl cnp logs cluster -h` - -The `logs` command will display logs in JSON-lines format, unless the -`--timestamps` flag is used, in which case, a human-readable timestamp will be -prepended to each line. In this case, lines will no longer be valid JSON, -and tools such as `jq` may not work as desired. - -If the `logs cluster` sub-command is given the `-f` flag (aka `--follow`), it -will follow the cluster pod logs, and will also watch for any new pods created -in the cluster after the command has been invoked. -Any new pods found, including pods that have been restarted or re-created, -will also have their pods followed. -The logs will be displayed in the terminal's standard-out. -This command will only exit when the cluster has no more pods left, or when it -is interrupted by the user. - -If `logs` is called without the `-f` option, it will read the logs from all -cluster pods until the time of invocation and display them in the terminal's -standard-out, then exit. -The `-o` or `--output` flag can be provided, to specify the name -of the file where the logs should be saved, instead of displaying over -standard-out. -The `--tail` flag can be used to specify how many log lines will be retrieved -from each pod in the cluster. By default, the `logs cluster` sub-command will -display all the logs from each pod in the cluster. If combined with the "follow" -flag `-f`, the number of logs specified by `--tail` will be retrieved until the -current time, and from then the new logs will be followed. - -NOTE: unlike other `cnp` plugin commands, the `-f` is used to denote "follow" -rather than specify a file. This keeps with the convention of `kubectl logs`, -which takes `-f` to mean the logs should be followed. - -Usage: - -```sh -kubectl cnp logs cluster [flags] -``` - -Using the `-f` option to follow: - -```sh -kubectl cnp report cluster cluster-example -f -``` - -Using `--tail` option to display 3 lines from each pod and the `-f` option -to follow: - -```sh -kubectl cnp report cluster cluster-example -f --tail 3 -``` - -```output -{"level":"info","ts":"2023-06-30T13:37:33Z","logger":"postgres","msg":"2023-06-30 13:37:33.142 UTC [26] LOG: ending log output to stderr","source":"/controller/log/postgres","logging_pod":"cluster-example-3"} -{"level":"info","ts":"2023-06-30T13:37:33Z","logger":"postgres","msg":"2023-06-30 13:37:33.142 UTC [26] HINT: Future log output will go to log destination \"csvlog\".","source":"/controller/log/postgres","logging_pod":"cluster-example-3"} -… -… -``` - -With the `-o` option omitted, and with `--output` specified: - -```console -$ kubectl cnp logs cluster cluster-example --output my-cluster.log - -Successfully written logs to "my-cluster.log" -``` - -#### Pretty - -The `pretty` sub-command reads a log stream from standard input, formats it -into a human-readable output, and attempts to sort the entries by timestamp. - -It can be used in combination with `kubectl cnp logs cluster`, as -shown in the following example: - -```console -$ kubectl cnp logs cluster cluster-example | kubectl cnp logs pretty -2024-10-15T17:35:00.336 INFO cluster-example-1 instance-manager Starting {{name.ln}} Instance Manager -2024-10-15T17:35:00.336 INFO cluster-example-1 instance-manager Checking for free disk space for WALs before starting PostgreSQL -2024-10-15T17:35:00.347 INFO cluster-example-1 instance-manager starting tablespace manager -2024-10-15T17:35:00.347 INFO cluster-example-1 instance-manager starting external server manager -[...] -``` - -Alternatively, it can be used in combination with other commands that produce -{{name.abbr}} logs in JSON format, such as `stern`, or `kubectl logs`, as in the -following example: - -```console -$ kubectl logs cluster-example-1 | kubectl cnp logs pretty -2024-10-15T17:35:00.336 INFO cluster-example-1 instance-manager Starting {{name.ln}} Instance Manager -2024-10-15T17:35:00.336 INFO cluster-example-1 instance-manager Checking for free disk space for WALs before starting PostgreSQL -2024-10-15T17:35:00.347 INFO cluster-example-1 instance-manager starting tablespace manager -2024-10-15T17:35:00.347 INFO cluster-example-1 instance-manager starting external server manager -[...] -``` - -The `pretty` sub-command also supports advanced log filtering, allowing users -to display logs for specific pods or loggers, or to filter logs by severity -level. -Here's an example: - -```console -$ kubectl cnp logs cluster cluster-example | kubectl cnp logs pretty --pods cluster-example-1 --loggers postgres --log-level info -2024-10-15T17:35:00.509 INFO cluster-example-1 postgres 2024-10-15 17:35:00.509 UTC [29] LOG: redirecting log output to logging collector process -2024-10-15T17:35:00.509 INFO cluster-example-1 postgres 2024-10-15 17:35:00.509 UTC [29] HINT: Future log output will appear in directory "/controller/log"... -2024-10-15T17:35:00.510 INFO cluster-example-1 postgres 2024-10-15 17:35:00.509 UTC [29] LOG: ending log output to stderr -2024-10-15T17:35:00.510 INFO cluster-example-1 postgres ending log output to stderr -[...] -``` - -The `pretty` sub-command will try to sort the log stream, -to make logs easier to reason about. In order to achieve this, it gathers the -logs into groups, and within groups it sorts by timestamp. This is the only -way to sort interactively, as `pretty` may be piped from a command in "follow" -mode. The sub-command will add a group separator line, `---`, at the end of -each sorted group. The size of the grouping can be configured via the -`--sorting-group-size` flag (default: 1000), as illustrated in the following example: - -```console -$ kubectl cnp logs cluster cluster-example | kubectl cnp logs pretty --sorting-group-size=3 -2024-10-15T17:35:20.426 INFO cluster-example-2 instance-manager Starting {{name.ln}} Instance Manager -2024-10-15T17:35:20.426 INFO cluster-example-2 instance-manager Checking for free disk space for WALs before starting PostgreSQL -2024-10-15T17:35:20.438 INFO cluster-example-2 instance-manager starting tablespace manager ---- -2024-10-15T17:35:20.438 INFO cluster-example-2 instance-manager starting external server manager -2024-10-15T17:35:20.438 INFO cluster-example-2 instance-manager starting controller-runtime manager -2024-10-15T17:35:20.439 INFO cluster-example-2 instance-manager Starting EventSource ---- -[...] -``` - -To explore all available options, use the `-h` flag for detailed explanations -of the supported flags and their usage. - -!!!info -You can also increase the verbosity of the log by adding more `-v` options. -!!! - -### Destroy - -The `kubectl cnp destroy` command helps remove an instance and all the -associated PVCs from a Kubernetes cluster. - -The optional `--keep-pvc` flag, if specified, allows you to keep the PVCs, -while removing all `metadata.ownerReferences` that were set by the instance. -Additionally, the `k8s.enterprisedb.io/pvcStatus` label on the PVCs will change from -`ready` to `detached` to signify that they are no longer in use. - -Running again the command without the `--keep-pvc` flag will remove the -detached PVCs. - -Usage: - -```sh -kubectl cnp destroy [CLUSTER_NAME] [INSTANCE_ID] -``` - -The following example removes the `cluster-example-2` pod and the associated -PVCs: - -```sh -kubectl cnp destroy cluster-example 2 -``` - -### Cluster hibernation - -Sometimes you may want to suspend the execution of a {{name.ln}} `Cluster` -while retaining its data, then resume its activity at a later time. We've -called this feature **cluster hibernation**. - -Hibernation is only available via the `kubectl cnp hibernate [on|off]` -commands. - -Hibernating a {{name.ln}} cluster means destroying all the resources -generated by the cluster, except the PVCs that belong to the PostgreSQL primary -instance. - -You can hibernate a cluster with: - -```sh -kubectl cnp hibernate on -``` - -This will: - -1. shutdown every PostgreSQL instance -2. detach the PVCs containing the data of the primary instance, and annotate - them with the latest database status and the latest cluster configuration -3. delete the `Cluster` resource, including every generated resource - except - the aforementioned PVCs - -When hibernated, a {{name.ln}} cluster is represented by just a group of -PVCs, in which the one containing the `PGDATA` is annotated with the latest -available status, including content from `pg_controldata`. - -!!!warning -A cluster having fenced instances cannot be hibernated, as fencing is -part of the hibernation procedure too. -!!! - -In case of error the operator will not be able to revert the procedure. You can -still force the operation with: - -```sh -kubectl cnp hibernate on cluster-example --force -``` - -A hibernated cluster can be resumed with: - -```sh -kubectl cnp hibernate off -``` - -Once the cluster has been hibernated, it's possible to show the last -configuration and the status that PostgreSQL had after it was shut down. -That can be done with: - -```sh -kubectl cnp status -``` - -### Benchmarking the database with pgbench - -Pgbench can be run against an existing PostgreSQL cluster with following -command: - -```sh -kubectl cnp pgbench -- --time 30 --client 1 --jobs 1 -``` - -Refer to the [Benchmarking pgbench section](benchmarking.md#pgbench) for more -details. - -### Benchmarking the storage with fio - -fio can be run on an existing storage class with following command: - -```sh -kubectl cnp fio -n -``` - -Refer to the [Benchmarking fio section](benchmarking.md#fio) for more details. - -### Requesting a new physical backup - -The `kubectl cnp backup` command requests a new physical backup for -an existing Postgres cluster by creating a new `Backup` resource. - -!!!info -From release 1.21, the `backup` command accepts a new flag, `-m` -to specify the backup method. -To request a backup using volume snapshots, set `-m volumeSnapshot` -!!! - -The following example requests an on-demand backup for a given cluster: - -```sh -kubectl cnp backup [cluster_name] -``` - -or, if using volume snapshots: - -```sh -kubectl cnp backup [cluster_name] -m volumeSnapshot -``` - -The created backup will be named after the request time: - -```console -$ kubectl cnp backup cluster-example -backup/cluster-example-20230121002300 created -``` - -By default, a newly created backup will use the backup target policy defined -in the cluster to choose which instance to run on. -However, you can override this policy with the `--backup-target` option. - -In the case of volume snapshot backups, you can also use the `--online` option -to request an online/hot backup or an offline/cold one: additionally, you can -also tune online backups by explicitly setting the `--immediate-checkpoint` and -`--wait-for-archive` options. - -The ["Backup" section](./backup.md) contains more information about -the configuration settings. - -### Launching psql - -The `kubectl cnp psql` command starts a new PostgreSQL interactive front-end -process (psql) connected to an existing Postgres cluster, as if you were running -it from the actual pod. This means that you will be using the `postgres` user. - -!!!info Important -As you will be connecting as `postgres` user, in production environments this -method should be used with extreme care, by authorized personnel only. -!!! - -```console -$ kubectl cnp psql cluster-example - -psql (17.0 (Debian 17.0-1.pgdg110+1)) -Type "help" for help. - -postgres=# -``` - -By default, the command will connect to the primary instance. The user can -select to work against a replica by using the `--replica` option: - -```console -$ kubectl cnp psql --replica cluster-example - -psql (17.0 (Debian 17.0-1.pgdg110+1)) - -Type "help" for help. - -postgres=# select pg_is_in_recovery(); - pg_is_in_recovery -------------------- - t -(1 row) - -postgres=# \q -``` - -This command will start `kubectl exec`, and the `kubectl` executable must be -reachable in your `PATH` variable to correctly work. - -!!!note -When connecting to instances running on OpenShift, you must explicitly -pass a username to the `psql` command, because of a [security measure built into -OpenShift](https://cloud.redhat.com/blog/a-guide-to-openshift-and-uids): - -```sh -kubectl cnp psql cluster-example -- -U postgres -``` -!!! - -### Snapshotting a Postgres cluster - -!!!warning -The `kubectl cnp snapshot` command has been removed. -Please use the [`backup` command](#requesting-a-new-physical-backup) to request -backups using volume snapshots. -!!! - -### Using pgAdmin4 for evaluation/demonstration purposes only - -[pgAdmin](https://www.pgadmin.org/) stands as the most popular and feature-rich -open-source administration and development platform for PostgreSQL. -For more information on the project, please refer to the official -[documentation](https://www.pgadmin.org/docs/). - -Given that the pgAdmin Development Team maintains official Docker container -images, you can install pgAdmin in your environment as a standard -Kubernetes deployment. - -!!!info Important -Deployment of pgAdmin in Kubernetes production environments is beyond the -scope of this document and, more broadly, of the {{name.ln}} project. -!!! - -However, **for the purposes of demonstration and evaluation**, {{name.ln}} -offers a suitable solution. The `cnp` plugin implements the `pgadmin4` -command, providing a straightforward method to connect to a given database -`Cluster` and navigate its content in a local environment such as `kind`. - -For example, you can install a demo deployment of pgAdmin4 for the -`cluster-example` cluster as follows: - -```sh -kubectl cnp pgadmin4 cluster-example -``` - -This command will produce: - -```output -ConfigMap/cluster-example-pgadmin4 created -Deployment/cluster-example-pgadmin4 created -Service/cluster-example-pgadmin4 created -Secret/cluster-example-pgadmin4 created - -[...] -``` - -After deploying pgAdmin, forward the port using kubectl and connect -through your browser by following the on-screen instructions. - -![Screenshot of desktop installation of pgAdmin](images/pgadmin4.png) - -As usual, you can use the `--dry-run` option to generate the YAML file: - -```sh -kubectl cnp pgadmin4 --dry-run cluster-example -``` - -pgAdmin4 can be installed in either desktop or server mode, with the default -being server. - -In `server` mode, authentication is required using a randomly generated password, -and users must manually specify the database to connect to. - -On the other hand, `desktop` mode initiates a pgAdmin web interface without -requiring authentication. It automatically connects to the `app` database as the -`app` user, making it ideal for quick demos, such as on a local deployment using -`kind`: - -```sh -kubectl cnp pgadmin4 --mode desktop cluster-example -``` - -After concluding your demo, ensure the termination of the pgAdmin deployment by -executing: - -```sh -kubectl cnp pgadmin4 --dry-run cluster-example | kubectl delete -f - -``` - -!!!warning -Never deploy pgAdmin in production using the plugin. -!!! - -### Logical Replication Publications - -The `cnp publication` command group is designed to streamline the creation and -removal of [PostgreSQL logical replication publications](https://www.postgresql.org/docs/current/logical-replication-publication.html). -Be aware that these commands are primarily intended for assisting in the -creation of logical replication publications, particularly on remote PostgreSQL -databases. - -!!!warning -It is crucial to have a solid understanding of both the capabilities and -limitations of PostgreSQL's native logical replication system before using -these commands. -In particular, be mindful of the [logical replication restrictions](https://www.postgresql.org/docs/current/logical-replication-restrictions.html). -!!! - -#### Creating a new publication - -To create a logical replication publication, use the `cnp publication create` -command. The basic structure of this command is as follows: - -```sh -kubectl cnp publication create \ - --publication \ - [--external-cluster ] - [options] -``` - -There are two primary use cases: - -- With `--external-cluster`: Use this option to create a publication on an - external cluster (i.e. defined in the `externalClusters` stanza). The commands - will be issued from the ``, but the publication will be for the - data in ``. - -- Without `--external-cluster`: Use this option to create a publication in the - `` PostgreSQL `Cluster` (by default, the `app` database). - -!!!warning -When connecting to an external cluster, ensure that the specified user has -sufficient permissions to execute the `CREATE PUBLICATION` command. -!!! - -You have several options, similar to the [`CREATE PUBLICATION`](https://www.postgresql.org/docs/current/sql-createpublication.html) -command, to define the group of tables to replicate. Notable options include: - -- If you specify the `--all-tables` option, you create a publication `FOR ALL TABLES`. -- Alternatively, you can specify multiple occurrences of: - - `--table`: Add a specific table (with an expression) to the publication. - - `--schema`: Include all tables in the specified database schema (available - from PostgreSQL 15). - -The `--dry-run` option enables you to preview the SQL commands that the plugin -will execute. - -For additional information and detailed instructions, type the following -command: - -```sh -kubectl cnp publication create --help -``` - -##### Example - -Given a `source-cluster` and a `destination-cluster`, we would like to create a -publication for the data on `source-cluster`. -The `destination-cluster` has an entry in the `externalClusters` stanza pointing -to `source-cluster`. - -We can run: - -```sh -kubectl cnp publication create destination-cluster \ - --external-cluster=source-cluster --all-tables -``` - -which will create a publication for all tables on `source-cluster`, running -the SQL commands on the `destination-cluster`. - -Or instead, we can run: - -```sh -kubectl cnp publication create source-cluster \ - --publication=app --all-tables -``` - -which will create a publication named `app` for all the tables in the -`source-cluster`, running the SQL commands on the source cluster. - -!!!info -There are two sample files that have been provided for illustration and inspiration: -[logical-source](../samples/cluster-example-logical-source.yaml) and -[logical-destination](../samples/cluster-example-logical-destination.yaml). -!!! - -#### Dropping a publication - -The `cnp publication drop` command seamlessly complements the `create` command -by offering similar key options, including the publication name, cluster name, -and an optional external cluster. You can drop a `PUBLICATION` with the -following command structure: - -```sh -kubectl cnp publication drop \ - --publication \ - [--external-cluster ] - [options] -``` - -To access further details and precise instructions, use the following command: - -```sh -kubectl cnp publication drop --help -``` - -### Logical Replication Subscriptions - -The `cnp subscription` command group is a dedicated set of commands designed -to simplify the creation and removal of -[PostgreSQL logical replication subscriptions](https://www.postgresql.org/docs/current/logical-replication-subscription.html). -These commands are specifically crafted to aid in the establishment of logical -replication subscriptions, especially when dealing with remote PostgreSQL -databases. - -!!!warning -Before using these commands, it is essential to have a comprehensive -understanding of both the capabilities and limitations of PostgreSQL's -native logical replication system. -In particular, be mindful of the [logical replication restrictions](https://www.postgresql.org/docs/current/logical-replication-restrictions.html). -!!! - -In addition to subscription management, we provide a helpful command for -synchronizing all sequences from the source cluster. While its applicability -may vary, this command can be particularly useful in scenarios involving major -upgrades or data import from remote servers. - -#### Creating a new subscription - -To create a logical replication subscription, use the `cnp subscription create` -command. The basic structure of this command is as follows: - -```sh -kubectl cnp subscription create \ - --subscription \ - --publication \ - --external-cluster \ - [options] -``` - -This command configures a subscription directed towards the specified -publication in the designated external cluster, as defined in the -`externalClusters` stanza of the ``. - -For additional information and detailed instructions, type the following -command: - -```sh -kubectl cnp subscription create --help -``` - -##### Example - -As in the section on publications, we have a `source-cluster` and a -`destination-cluster`, and we have already created a publication called -`app`. - -The following command: - -```sh -kubectl cnp subscription create destination-cluster \ - --external-cluster=source-cluster \ - --publication=app --subscription=app -``` - -will create a subscription for `app` on the destination cluster. - -!!!warning -Prioritize testing subscriptions in a non-production environment to ensure -their effectiveness and identify any potential issues before implementing them -in a production setting. -!!! - -!!!info -There are two sample files that have been provided for illustration and inspiration: -[logical-source](../samples/cluster-example-logical-source.yaml) and -[logical-destination](../samples/cluster-example-logical-destination.yaml). -!!! - -#### Dropping a subscription - -The `cnp subscription drop` command seamlessly complements the `create` command. -You can drop a `SUBSCRIPTION` with the following command structure: - -```sh -kubectl cnp subcription drop \ - --subscription \ - [options] -``` - -To access further details and precise instructions, use the following command: - -```sh -kubectl cnp subscription drop --help -``` - -#### Synchronizing sequences - -One notable constraint of PostgreSQL logical replication, implemented through -publications and subscriptions, is the lack of sequence synchronization. This -becomes particularly relevant when utilizing logical replication for live -database migration, especially to a higher version of PostgreSQL. A crucial -step in this process involves updating sequences before transitioning -applications to the new database (*cutover*). - -To address this limitation, the `cnp subscription sync-sequences` command -offers a solution. This command establishes a connection with the source -database, retrieves all relevant sequences, and subsequently updates local -sequences with matching identities (based on database schema and sequence -name). - -You can use the command as shown below: - -```sh -kubectl cnp subscription sync-sequences \ - --subscription \ - -``` - -For comprehensive details and specific instructions, utilize the following -command: - -```sh -kubectl cnp subscription sync-sequences --help -``` - -##### Example - -As in the previous sections for publication and subscription, we have -a `source-cluster` and a `destination-cluster`. The publication and the -subscription, both called `app`, are already present. - -The following command will synchronize the sequences involved in the -`app` subscription, from the source cluster into the destination cluster. - -```sh -kubectl cnp subscription sync-sequences destination-cluster \ - --subscription=app -``` - -!!!warning -Prioritize testing subscriptions in a non-production environment to -guarantee their effectiveness and detect any potential issues before deploying -them in a production setting. -!!! - -## Integration with K9s - -The `cnp` plugin can be easily integrated in [K9s](https://k9scli.io/), a -popular terminal-based UI to interact with Kubernetes clusters. - -See [`k9s/plugins.yml`](../samples/k9s/plugins.yml) for details. - -## Permissions required by the plugin - -The plugin requires a set of Kubernetes permissions that depends on the command -to execute. These permissions may affect resources and sub-resources like Pods, -PDBs, PVCs, and enable actions like `get`, `delete`, `patch`. The following -table contains the full details: - -| Command | Resource Permissions | -| :-------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| backup | clusters: get
backups: create | -| certificate | clusters: get
secrets: get,create | -| destroy | pods: get,delete
jobs: delete,list
PVCs: list,delete,update | -| fencing | clusters: get,patch
pods: get | -| fio | PVCs: create
configmaps: create
deployment: create | -| hibernate | clusters: get,patch,delete
pods: list,get,delete
pods/exec: create
jobs: list
PVCs: get,list,update,patch,delete | -| install | none | -| logs | clusters: get
pods: list
pods/log: get | -| maintenance | clusters: get,patch,list
| -| pgadmin4 | clusters: get
configmaps: create
deployments: create
services: create
secrets: create | -| pgbench | clusters: get
jobs: create
| -| promote | clusters: get
clusters/status: patch
pods: get | -| psql | pods: get,list
pods/exec: create | -| publication | clusters: get
pods: get,list
pods/exec: create | -| reload | clusters: get,patch | -| report cluster | clusters: get
pods: list
pods/log: get
jobs: list
events: list
PVCs: list | -| report operator | configmaps: get
deployments: get
events: list
pods: list
pods/log: get
secrets: get
services: get
mutatingwebhookconfigurations: list[^1]
validatingwebhookconfigurations: list[^1]
If OLM is present on the K8s cluster, also:
clusterserviceversions: list
installplans: list
subscriptions: list | -| restart | clusters: get,patch
pods: get,delete | -| status | clusters: get
pods: list
pods/exec: create
pods/proxy: create
PDBs: list | -| subscription | clusters: get
pods: get,list
pods/exec: create | -| version | none | - -[^1]: The permissions are cluster scope ClusterRole resources. - -///Footnotes Go Here/// - -Additionally, assigning the `list` permission on the `clusters` will enable -autocompletion for multiple commands. - -### Role examples - -It is possible to create roles with restricted permissions. -The following example creates a role that only has access to the cluster logs: - -```yaml ---- -apiVersion: rbac.authorization.k8s.io/v1 -kind: Role -metadata: - name: cnp-log -rules: - - verbs: - - get - apiGroups: - - postgresql.k8s.enterprisedb.io - resources: - - clusters - - verbs: - - list - apiGroups: - - '' - resources: - - pods - - verbs: - - get - apiGroups: - - '' - resources: - - pods/log -``` - -The next example shows a role with the minimal permissions required to get -the cluster status using the plugin's `status` command: - -```yaml -apiVersion: rbac.authorization.k8s.io/v1 -kind: Role -metadata: - name: cnp-status -rules: - - verbs: - - get - apiGroups: - - postgresql.k8s.enterprisedb.io - resources: - - clusters - - verbs: - - list - apiGroups: - - '' - resources: - - pods - - verbs: - - create - apiGroups: - - '' - resources: - - pods/exec - - verbs: - - create - apiGroups: - - '' - resources: - - pods/proxy - - verbs: - - list - apiGroups: - - policy - resources: - - poddisruptionbudgets -``` - -!!!info Important -Keeping the verbs restricted per `resources` and per `apiGroups` helps to -prevent inadvertently granting more than intended permissions. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/kubernetes_upgrade.mdx b/product_docs/docs/postgres_for_kubernetes/preview/kubernetes_upgrade.mdx deleted file mode 100644 index 2fbdd3229b6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/kubernetes_upgrade.mdx +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: 'Kubernetes upgrade and maintenance' -originalFilePath: 'src/kubernetes_upgrade.md' ---- - - - -Maintaining an up-to-date Kubernetes cluster is crucial for ensuring optimal -performance and security, particularly for self-managed clusters, especially -those running on bare metal infrastructure. Regular updates help address -technical debt and mitigate business risks, despite the controlled downtimes -associated with temporarily removing a node from the cluster for maintenance -purposes. For further insights on embracing risk in operations, refer to the -["Embracing Risk"](https://landing.google.com/sre/sre-book/chapters/embracing-risk/) -chapter from the Site Reliability Engineering book. - -## Importance of Regular Updates - -Updating Kubernetes involves planning and executing maintenance tasks, such as -applying security updates to underlying Linux servers, replacing malfunctioning -hardware components, or upgrading the cluster to the latest Kubernetes version. -These activities are essential for maintaining a robust and secure -infrastructure. - -## Maintenance Operations in a Cluster - -Typically, maintenance operations are carried out on one node at a time, following a [structured process](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/): - -1. eviction of workloads (`drain`): workloads are gracefully moved away from - the node to be updated, ensuring a smooth transition. -2. performing the operation: the actual maintenance operation, such as a - system update or hardware replacement, is executed. -3. rejoining the node to the cluster (`uncordon`): the updated node is - reintegrated into the cluster, ready to resume its responsibilities. - -This process requires either stopping workloads for the entire upgrade duration -or migrating them to other nodes in the cluster. - -## Temporary PostgreSQL Cluster Degradation - -While the standard approach ensures service reliability and leverages -Kubernetes' self-healing capabilities, there are scenarios where operating with -a temporarily degraded cluster may be acceptable. This is particularly relevant -for PostgreSQL clusters relying on **node-local storage**, where the storage is -local to the Kubernetes worker node running the PostgreSQL database. Node-local -storage, or simply *local storage*, is employed to enhance performance. - -!!!note -If your database files reside on shared storage accessible over the -network, the default self-healing behavior of the operator can efficiently -handle scenarios where volumes are reused by pods on different nodes after a -drain operation. In such cases, you can skip the remaining sections of this -document. -!!! - -## Pod Disruption Budgets - -By default, {{name.ln}} safeguards Postgres cluster operations. If a node is -to be drained and contains a cluster's primary instance, a switchover happens -ahead of the drain. Once the instance in the node is downgraded to replica, the -draining can resume. -For single-instance clusters, a switchover is not possible, so {{name.ln}} -will prevent draining the node where the instance is housed. -Additionally, in clusters with 3 or more instances, {{name.ln}} guarantees that -only one replica at a time is gracefully shut down during a drain operation. - -Each PostgreSQL `Cluster` is equipped with two associated `PodDisruptionBudget` -resources - you can easily confirm it with the `kubectl get pdb` command. - -Our recommendation is to leave pod disruption budgets enabled for every -production Postgres cluster. This can be effortlessly managed by toggling the -`.spec.enablePDB` option, as detailed in the -[API reference](pg4k.v1.md#clusterspec). - -## PostgreSQL Clusters used for Development or Testing - -For PostgreSQL clusters used for development purposes, often consisting of -a single instance, it is essential to disable pod disruption budgets. Failure -to do so will prevent the node hosting that cluster from being drained. - -The following example illustrates how to disable pod disruption budgets for a -1-instance development cluster: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: dev -spec: - instances: 1 - enablePDB: false - - storage: - size: 1Gi -``` - -This configuration ensures smoother maintenance procedures without restrictions -on draining the node during development activities. - -## Node Maintenance Window - -!!!info Important -While {{name.ln}} will continue supporting the node maintenance window, -it is currently recommended to transition to direct control of pod disruption -budgets, as explained in the previous section. This section is retained -mainly for backward compatibility. -!!! - -Prior to release 1.23, {{name.ln}} had just one declarative mechanism to manage -Kubernetes upgrades when dealing with local storage: you had to temporarily put -the cluster in **maintenance mode** through the `nodeMaintenanceWindow` option -to avoid standard self-healing procedures to kick in, while, for example, -enlarging the partition on the physical node or updating the node itself. - -!!!warning -Limit the duration of the maintenance window to the shortest -amount of time possible. In this phase, some of the expected -behaviors of Kubernetes are either disabled or running with -some limitations, including self-healing, rolling updates, -and Pod disruption budget. -!!! - -The `nodeMaintenanceWindow` option of the cluster has two further -settings: - -`inProgress`: -Boolean value that states if the maintenance window for the nodes -is currently in progress or not. By default, it is set to `off`. -During the maintenance window, the `reusePVC` option below is -evaluated by the operator. - -`reusePVC`: -Boolean value that defines if an existing PVC is reused or -not during the maintenance operation. By default, it is set to `on`. -When **enabled**, Kubernetes waits for the node to come up -again and then reuses the existing PVC; the `PodDisruptionBudget` -policy is temporarily removed. -When **disabled**, Kubernetes forces the recreation of the -Pod on a different node with a new PVC by relying on -PostgreSQL's physical streaming replication, then destroys -the old PVC together with the Pod. This scenario is generally -not recommended unless the database's size is small, and re-cloning -the new PostgreSQL instance takes shorter than waiting. This behavior -does **not** apply to clusters with only one instance and -reusePVC disabled: see section below. - -!!!note -When performing the `kubectl drain` command, you will need -to add the `--delete-emptydir-data` option. -Don't be afraid: it refers to another volume internally used -by the operator - not the PostgreSQL data directory. -!!! - -!!!info Important -`PodDisruptionBudget` management can be disabled by setting the -`.spec.enablePDB` field to `false`. In that case, the operator won't -create `PodDisruptionBudgets` and will delete them if they were -previously created. -!!! - -### Single instance clusters with `reusePVC` set to `false` - -!!!info Important -We recommend to always create clusters with more -than one instance in order to guarantee high availability. -!!! - -Deleting the only PostgreSQL instance in a single instance cluster with -`reusePVC` set to `false` would imply all data being lost, -therefore we prevent users from draining nodes such instances might be running -on, even in maintenance mode. - -However, in case maintenance is required for such a node you have two options: - -1. Enable `reusePVC`, accepting the downtime -2. Replicate the instance on a different node and switch over the primary - -As long as a database service downtime is acceptable for your environment, -draining the node is as simple as setting the `nodeMaintenanceWindow` to -`inProgress: true` and `reusePVC: true`. This will allow the instance to -be deleted and recreated as soon as the original PVC is available -(e.g. with node local storage, as soon as the node is back up). - -Otherwise you will have to scale up the cluster, creating a new instance -on a different node and promoting the new instance to primary in order to -shut down the original one on the node undergoing maintenance. The only -downtime in this case will be the duration of the switchover. - -A possible approach could be: - -1. Cordon the node on which the current instance is running. -2. Scale up the cluster to 2 instances, could take some time depending on the database size. -3. As soon as the new instance is running, the operator will automatically - perform a switchover given that the current primary is running on a cordoned node. -4. Scale back down the cluster to a single instance, this will delete the old instance -5. The old primary's node can now be drained successfully, while leaving the new primary - running on a new node. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/labels_annotations.mdx b/product_docs/docs/postgres_for_kubernetes/preview/labels_annotations.mdx deleted file mode 100644 index e89ddf7ba80..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/labels_annotations.mdx +++ /dev/null @@ -1,368 +0,0 @@ ---- -title: 'Labels and Annotations' -originalFilePath: 'src/labels_annotations.md' ---- - - - -Resources in Kubernetes are organized in a flat structure, with no hierarchical -information or relationship between them. However, such resources and objects -can be linked together and put in relationship through *labels* and -*annotations*. - -!!!info -For more information, see the Kubernetes documentation on -[annotations](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/) and -[labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/). -!!! - -In brief: - -- An annotation is used to assign additional non-identifying information to - resources with the goal of facilitating integration with external tools. -- A label is used to group objects and query them through the Kubernetes native - selector capability. - -You can select one or more labels or annotations to use -in your {{name.ln}} deployments. Then you need to configure the operator -so that when you define these labels or annotations in a cluster's metadata, -they're inherited by all resources created by it (including pods). - -!!!note -Label and annotation inheritance is the technique adopted by {{name.ln}} -instead of alternative approaches such as pod templates. -!!! - -## Predefined labels - -{{name.ln}} manages the following predefined labels: - -`k8s.enterprisedb.io/backupDate` -: The date of the backup in ISO 8601 format (`YYYYMMDD`). - This label is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/backupName` -: Backup identifier. - This label is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/backupMonth` -: The year/month when a backup was taken. - This label is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/backupTimeline` -: The timeline of the instance when a backup was taken. - This label is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/backupYear` -: The year a backup was taken. - This label is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/cluster` -: Name of the cluster. - -`k8s.enterprisedb.io/immediateBackup` -: Applied to a `Backup` resource if the backup is the first one created from - a `ScheduledBackup` object having `immediate` set to `true`. - -`k8s.enterprisedb.io/instanceName` -: Name of the PostgreSQL instance (replaces the old and - deprecated `postgresql` label). - -`k8s.enterprisedb.io/jobRole` -: Role of the job (that is, `import`, `initdb`, `join`, ...) - -`k8s.enterprisedb.io/majorVersion` -: Integer PostgreSQL major version of the backup's data directory (for example, `17`). -This label is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/onlineBackup` -: Whether the backup is online (hot) or taken when Postgres is down (cold). - This label is available only on `VolumeSnapshot` resources. - -`postgresql` -: deprecated, Name of the PostgreSQL instance. Use `k8s.enterprisedb.io/instanceName` -instead - -`k8s.enterprisedb.io/podRole` -: Distinguishes pods dedicated to pooler deployment from those used for - database instances. - -`k8s.enterprisedb.io/poolerName` -: Name of the PgBouncer pooler. - -`k8s.enterprisedb.io/pvcRole` -: Purpose of the PVC, such as `PG_DATA` or `PG_WAL`. - -`k8s.enterprisedb.io/reload` -: Available on `ConfigMap` and `Secret` resources. When set to `true`, - a change in the resource is automatically reloaded by the operator. - -`k8s.enterprisedb.io/userType` -: Specifies the type of PostgreSQL user associated with the - `Secret`, either `superuser` (Postgres superuser access) or `app` - (application-level user in {{name.ln}} terminology), and is limited to the - default users created by {{name.ln}} (typically `postgres` and `app`). - -`role` - **deprecated** -: Role of the instance running in a pod: `primary`, `replica`, or - `unhealthy`. The `unhealthy` value is transient: the operator sets - it on the old primary during a failover or switchover and clears it - automatically once the transition completes. This label is deprecated, - you should use `k8s.enterprisedb.io/instanceRole` instead. - -`k8s.enterprisedb.io/scheduled-backup` -: When available, name of the `ScheduledBackup` resource that created a given - `Backup` object. - -`k8s.enterprisedb.io/instanceRole` -: Role of the instance running in a pod: `primary`, `replica`, or - `unhealthy`. The `unhealthy` value is transient: the operator sets - it on the old primary during a failover or switchover and clears it - automatically once the transition completes. - -`app.kubernetes.io/managed-by` -: Name of the manager. It will always be `cloudnative-pg`. - Available across all {{name.ln}} managed resources. - -`app.kubernetes.io/name` -: Name of the application. It will always be `postgresql`. - Available on pods, jobs, deployments, services, persistentVolumeClaims, volumeSnapshots, - podDisruptionBudgets, podMonitors. - -`app.kubernetes.io/component` -: Name of the component (`database`, `pooler`, ...). - Available on pods, jobs, deployments, services, persistentVolumeClaims, volumeSnapshots, - podDisruptionBudgets, podMonitors. - -`app.kubernetes.io/instance` -: Name of the owning `Cluster` resource. - Available on pods, jobs, deployments, services, volumeSnapshots, podDisruptionBudgets, podMonitors. - -`app.kubernetes.io/version` -: Major version of PostgreSQL. - Available on pods, jobs, services, volumeSnapshots, podDisruptionBudgets, podMonitors. - -## Predefined annotations - -{{name.ln}} manages the following predefined annotations: - -`container.apparmor.security.beta.kubernetes.io/*` -: Name of the AppArmor profile to apply to the named container. - See [AppArmor](security.md#restricting-pod-access-using-apparmor) - for details. - -`k8s.enterprisedb.io/backupEndTime` -: The time a backup ended. - This annotation is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/backupEndWAL` -: The WAL at the conclusion of a backup. - This annotation is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/backupStartTime` -: The time a backup started. - -`k8s.enterprisedb.io/backupStartWAL` -: The WAL at the start of a backup. - This annotation is available only on `VolumeSnapshot` resources. - -`k8s.enterprisedb.io/coredumpFilter` -: Filter to control the coredump of Postgres processes, expressed with a - bitmask. By default it's set to `0x31` to exclude shared memory - segments from the dump. See [PostgreSQL core dumps](troubleshooting.md#postgresql-core-dumps) - for more information. - -`k8s.enterprisedb.io/clusterManifest` -: Manifest of the `Cluster` owning this resource (such as a PVC). This label - replaces the old, deprecated `k8s.enterprisedb.io/hibernateClusterManifest` label. - -`k8s.enterprisedb.io/fencedInstances` -: List of the instances that need to be fenced, expressed in JSON format. - The whole cluster is fenced if the list contains the `*` element. - -`k8s.enterprisedb.io/forceLegacyBackup` -: Applied to a `Cluster` resource for testing purposes only, to - simulate the behavior of `barman-cloud-backup` prior to version 3.4 (Jan 2023) - when the `--name` option wasn't available. - -`k8s.enterprisedb.io/hash` -: The hash value of the resource. - -`k8s.enterprisedb.io/hibernation` -: Applied to a `Cluster` resource to control the [declarative hibernation feature](declarative_hibernation.md). - Allowed values are `on` and `off`. - -`k8s.enterprisedb.io/managedSecrets` -: Pull secrets managed by the operator and automatically set in the - `ServiceAccount` resources for each Postgres cluster. - -`k8s.enterprisedb.io/nodeSerial` -: On a pod resource, identifies the serial number of the instance within the - Postgres cluster. - -`k8s.enterprisedb.io/operatorVersion` -: Version of the operator. - -`k8s.enterprisedb.io/passwordPassthrough` -: When set to `enabled` on a basic-auth `Secret` consumed by the - operator (superuser, application user, or a managed-role password - secret), the operator forwards the password value verbatim in the - `CREATE`/`ALTER ROLE` statement instead of SCRAM-SHA-256 encoding - it operator-side. PostgreSQL then encodes the value according to its - own `password_encryption` setting. See [Opting out of operator-side encoding](declarative_role_management.md#opting-out-of-operator-side-encoding). - -`k8s.enterprisedb.io/pgControldata` -: Output of the `pg_controldata` command. This annotation replaces the old, - deprecated `k8s.enterprisedb.io/hibernatePgControlData` annotation. - -`k8s.enterprisedb.io/podEnvHash` -: Deprecated, as the `k8s.enterprisedb.io/podSpec` annotation now also contains the pod environment. - -`k8s.enterprisedb.io/podPatch` -: Annotation can be applied on a `Cluster` resource. - -``` -When set to a JSON-patch formatted patch, the patch will be applied to the -instance Pods. The patch can modify any field of the Pod specification, -including security-sensitive fields. The operator validates only that the -patch is syntactically correct and applicable. - -As with all Cluster fields that affect Pod specifications, enforcement of -security constraints is delegated to the Kubernetes admission control chain. -See the -[Trust Model and Security Boundaries](security.md#trust-model-and-security-boundaries) -section for details. - -**⚠️ WARNING:** This feature may introduce discrepancies between the -operator's expectations and Kubernetes behavior. Use with caution and only as a -last resort. - -**IMPORTANT**: adding or changing this annotation won't trigger a rolling deployment -of the generated Pods. The latter can be triggered manually by the user with -`kubectl cnp restart`. -``` - -`k8s.enterprisedb.io/podSpec` -: Snapshot of the `spec` of the pod generated by the operator. This annotation replaces - the old, deprecated `k8s.enterprisedb.io/podEnvHash` annotation. - -`k8s.enterprisedb.io/poolerSpecHash` -: Hash of the pooler resource. - -`k8s.enterprisedb.io/pvcStatus` -: Current status of the PVC: `initializing`, `ready`, or `detached`. - -`k8s.enterprisedb.io/reconcilePodSpec` -: Annotation can be applied to a `Cluster` or `Pooler` to prevent restarts. - -``` -When set to `disabled` on a `Cluster`, the operator prevents instances -from restarting due to changes in the PodSpec. This includes changes to: - - - Topology or affinity - - Scheduler - - Volumes or containers - -When set to `disabled` on a `Pooler`, the operator restricts any modifications -to the deployment specification, except for changes to `spec.instances`. -``` - -`k8s.enterprisedb.io/reconciliationLoop` -: When set to `disabled` on a `Cluster`, the operator prevents the - reconciliation loop from running. - -`k8s.enterprisedb.io/reloadedAt` -: Contains the latest cluster `reload` time. `reload` is triggered by the user through a plugin. - -`k8s.enterprisedb.io/skipEmptyWalArchiveCheck` -: When set to `enabled` on a `Cluster` resource, the operator disables the check - that ensures that the WAL archive is empty before writing data. Use at your own - risk. - -`k8s.enterprisedb.io/skipWalArchiving` -: When set to `enabled` on a `Cluster` resource, the operator disables WAL archiving. - This will set `archive_mode` to `off` and require a restart of all PostgreSQL - instances. Use at your own risk. - -`k8s.enterprisedb.io/snapshotStartTime` -: The time a snapshot started. - -`k8s.enterprisedb.io/snapshotEndTime` -: The time a snapshot was marked as ready to use. - -`k8s.enterprisedb.io/validation` -: When set to `disabled` on a {{name.ln}}-managed custom resource, the - validation webhook allows all changes without restriction. - -``` -**⚠️ WARNING:** Disabling validation may permit unsafe or destructive -operations. Use this setting with caution and at your own risk. -``` - -`k8s.enterprisedb.io/volumeSnapshotDeadline` -: Applied to `Backup` and `ScheduledBackup` resources, allows you to control - how long the operator should retry recoverable errors before considering the - volume snapshot backup failed. In minutes, defaulting to 10. - -`kubectl.kubernetes.io/restartedAt` -: When available, the time of last requested restart of a Postgres cluster. - -`alpha.k8s.enterprisedb.io/unrecoverable` -: Experimental annotation applied to a `Pod` running a PostgreSQL instance. - It instructs the operator to delete the `Pod` and all its associated PVCs. - The instance will then be recreated according to the configured join - strategy. This annotation can only be used on instances that are neither the - current primary nor the designated target primary. - -## Prerequisites - -By default, no label or annotation defined in the cluster's metadata is -inherited by the associated resources. -To enable label/annotation inheritance, follow the -instructions provided in [Operator configuration](operator_conf.md). - -The following continues from that example and limits it to the following: - -- Annotations: `categories` -- Labels: `app`, `environment`, and `workload` - -!!!note -Feel free to select the names that most suit your context for both -annotations and labels. You can also use wildcards -in naming and adopt strategies like using `mycompany/*` for all labels -or setting annotations starting with `mycompany/` to be inherited. -!!! - -## Defining cluster's metadata - -When defining the cluster, before any resource is deployed, you can -set the metadata as follows: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example - annotations: - categories: database - labels: - environment: production - workload: database - app: sso -spec: - # ... -``` - -Once the cluster is deployed, you can verify, for example, that the labels -were correctly set in the pods: - -```shell -kubectl get pods --show-labels -``` - -## Current limitations - -Currently, {{name.ln}} doesn't automatically propagate labels or -annotations deletions. Therefore, when an annotation or label is removed from -a cluster that was previously propagated to the underlying pods, the operator -doesn't remove it on the associated resources. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/license_keys.mdx b/product_docs/docs/postgres_for_kubernetes/preview/license_keys.mdx deleted file mode 100644 index edeb750157d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/license_keys.mdx +++ /dev/null @@ -1,114 +0,0 @@ ---- -title: 'License and License keys' -originalFilePath: 'src/license_keys.md' ---- - -License keys are a legacy management mechanism for {{name.ln}}. You do not need a license key if you have installed using an EDB subscription token, and in this case, the licensing commands in this section can be ignored. - -If you are not using an EDB subscription token and installing from public repositories, then you will need a license key. The only exception is when you run the operator with Community PostgreSQL: in this case, if the license key is unset, a cluster will be started with the default trial license - which automatically expires after 30 days. This is not the recommended way of trialing {{name.ln}} - see the [installation guide](installation_upgrade.md) for the recommended options. - -!!!warning CRITICAL WARNING: UPGRADING OPERATORS - -OpenShift users, or any customer attempting an operator upgrade, MUST configure the new unified repository pull secret (docker.enterprisedb.com/k8s) before running the upgrade. If the old, deprecated repository path is still in use during the upgrade process, image pull failure will occur, leading to deployment failure and potential downtime. Follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/) first. -!!! - -The following documentation is only for users who have installed the operator using a license key. - -## Company level license keys - -A license key allows you to create an unlimited number of PostgreSQL -clusters in your installation. - -The license key needs to be available in a `Secret` in the same namespace where -the operator is deployed (`ConfigMap` is also available, but not recommended -for a license key). - -!!!note Operator configuration - -For more information, refer to [Operator configuration](operator_conf.md). -!!! - -Once the company level license is installed, the validity of the -license key can be checked inside the cluster status. - -```sh -kubectl get cluster cluster_example -o yaml -[...] -status: - [...] - licenseStatus: - licenseExpiration: "2021-11-06T09:36:02Z" - licenseStatus: Trial - valid: true - isImplicit: false - isTrial: true -[...] -``` - -### Kubernetes installations via YAML manifest - -When the operator is installed in Kubernetes using the YAML manifest, -it is deployed by default in the `postgresql-operator-system` namespace. - -Given the namespace name, and the license key, you can create -the config map with the following command: - -``` -kubectl create configmap -n [NAMESPACE_NAME_HERE] \ - postgresql-operator-controller-manager-config \ - --from-literal=EDB_LICENSE_KEY=[LICENSE_KEY_HERE] -``` - -Operator pods will need to be recreated to apply the new configuration. You -can use the following command: - -```sh -kubectl rollout restart deployment -n [NAMESPACE_NAME_HERE] \ - postgresql-operator-controller-manager -``` - -## Cluster level license keys - -Each `Cluster` resource has a `licenseKey` parameter in its definition. -You can find the expiration date, as well as more information about the license, -in the cluster status: - -```sh -kubectl get cluster cluster_example -o yaml -[...] -status: - [...] - licenseStatus: - licenseExpiration: "2021-11-06T09:36:02Z" - licenseStatus: Trial - valid: true - isImplicit: false - isTrial: true -[...] -``` - -A cluster license key can be updated with a new one at any moment, to extend -the expiration date or move the cluster to a production license. - -## License key secret at cluster level - -Each `Cluster` resource can also have a `licenseKeySecret` parameter, which contains -the name and key of a secret. That secret contains the license key provided by EDB. - -This field will take precedence over `licenseKey`: it will be refreshed -when you change the secret, in order to extend the expiration date, or switching from a trial -license to a production license. - -{{name.ln}} is distributed under the EDB End User License -Agreement, available at [enterprisedb.com/legal/EDB-Eula](https://www.enterprisedb.com/legal/EDB-Eula). - -{{name.ln}}: Copyright (C) 2019-2022 EnterpriseDB Corporation. - -## What happens when a license expires - -After the license expiration, the operator will cease any reconciliation -attempt on the cluster, effectively stopping to manage its status. This also -includes any self-healing and high availability capabilities, such as automated -failover and switchovers. - -The pods and the data will still be available. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/logging.mdx b/product_docs/docs/postgres_for_kubernetes/preview/logging.mdx deleted file mode 100644 index e78635b40d0..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/logging.mdx +++ /dev/null @@ -1,315 +0,0 @@ ---- -title: 'Logging' -originalFilePath: 'src/logging.md' ---- - - - -{{name.ln}} outputs logs in JSON format directly to standard output, including -PostgreSQL logs, without persisting them to storage for security reasons. This -design facilitates seamless integration with most Kubernetes-compatible log -management tools, including command line ones like -[stern](https://github.com/stern/stern). - -!!!info Important -Long-term storage and management of logs are outside the scope of the -operator and should be handled at the Kubernetes infrastructure level. -For more information, see the -[Kubernetes Logging Architecture](https://kubernetes.io/docs/concepts/cluster-administration/logging/) -documentation. -!!! - -Each log entry includes the following fields: - -- `level` – The log level (e.g., `info`, `notice`). -- `ts` – The timestamp. -- `logger` – The type of log (e.g., `postgres`, `pg_controldata`). -- `msg` – The log message, or the keyword `record` if the message is in JSON - format. -- `record` – The actual record, with a structure that varies depending on the - `logger` type. -- `logging_pod` – The name of the pod where the log was generated. - -!!!info -If your log ingestion system requires custom field names, you can rename -the `level` and `ts` fields using the `log-field-level` and -`log-field-timestamp` flags in the operator controller. This can be configured -by editing the `Deployment` definition of the `cloudnative-pg` operator. -!!! - -## Cluster Logs - -You can configure the log level for the instance pods in the cluster -specification using the `logLevel` option. Available log levels are: `error`, -`warning`, `info` (default), `debug`, and `trace`. - -!!!info Important -Currently, the log level can only be set at the time the instance starts. -Changes to the log level in the cluster specification after the cluster has -started will only apply to new pods, not existing ones. -!!! - -## Operator Logs - -The logs produced by the operator pod can be configured with log -levels, same as instance pods: `error`, `warning`, `info` (default), `debug`, -and `trace`. - -The log level for the operator can be configured by editing the `Deployment` -definition of the operator and setting the `--log-level` command line argument -to the desired value. - -## PostgreSQL Logs - -Each PostgreSQL log entry is a JSON object with the `logger` key set to -`postgres`. The structure of the log entries is as follows: - -```json -{ - "level": "info", - "ts": 1619781249.7188137, - "logger": "postgres", - "msg": "record", - "record": { - "log_time": "2021-04-30 11:14:09.718 UTC", - "user_name": "", - "database_name": "", - "process_id": "25", - "connection_from": "", - "session_id": "608be681.19", - "session_line_num": "1", - "command_tag": "", - "session_start_time": "2021-04-30 11:14:09 UTC", - "virtual_transaction_id": "", - "transaction_id": "0", - "error_severity": "LOG", - "sql_state_code": "00000", - "message": "database system was interrupted; last known up at 2021-04-30 11:14:07 UTC", - "detail": "", - "hint": "", - "internal_query": "", - "internal_query_pos": "", - "context": "", - "query": "", - "query_pos": "", - "location": "", - "application_name": "", - "backend_type": "startup" - }, - "logging_pod": "cluster-example-1", -} -``` - -!!!info -Internally, the operator uses PostgreSQL's CSV log format. For more details, -refer to the [PostgreSQL documentation on CSV log format](https://www.postgresql.org/docs/current/runtime-config-logging.html). -!!! - -## PGAudit Logs - -{{name.ln}} offers seamless and native support for -[PGAudit](https://www.pgaudit.org/) on PostgreSQL clusters. - -To enable PGAudit, add the necessary `pgaudit` parameters in the `postgresql` -section of the cluster configuration. - -!!!info Important -The PGAudit library must be added to `shared_preload_libraries`. -{{name.ln}} automatically manages this based on the presence of `pgaudit.*` -parameters in the PostgreSQL configuration. The operator handles both the -addition and removal of the library from `shared_preload_libraries`. -!!! - -Additionally, the operator manages the creation and removal of the PGAudit -extension across all databases within the cluster. - -!!!info Important -{{name.ln}} executes the `CREATE EXTENSION` and `DROP EXTENSION` commands -in all databases within the cluster that accept connections. -!!! - -The following example demonstrates a PostgreSQL `Cluster` deployment with -PGAudit enabled and configured: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - - postgresql: - parameters: - "pgaudit.log": "all, -misc" - "pgaudit.log_catalog": "off" - "pgaudit.log_parameter": "on" - "pgaudit.log_relation": "on" - - storage: - size: 1Gi -``` - -The audit CSV log entries generated by PGAudit are parsed and routed to -standard output in JSON format, similar to all other logs: - -- `.logger` is set to `pgaudit`. -- `.msg` is set to `record`. -- `.record` contains the entire parsed record as a JSON object. This structure - resembles that of `logging_collector` logs, with the exception of - `.record.audit`, which contains the PGAudit CSV message formatted as a JSON - object. - -This example shows sample log entries: - -```json -{ - "level": "info", - "ts": 1627394507.8814096, - "logger": "pgaudit", - "msg": "record", - "record": { - "log_time": "2021-07-27 14:01:47.881 UTC", - "user_name": "postgres", - "database_name": "postgres", - "process_id": "203", - "connection_from": "[local]", - "session_id": "610011cb.cb", - "session_line_num": "1", - "command_tag": "SELECT", - "session_start_time": "2021-07-27 14:01:47 UTC", - "virtual_transaction_id": "3/336", - "transaction_id": "0", - "error_severity": "LOG", - "sql_state_code": "00000", - "backend_type": "client backend", - "audit": { - "audit_type": "SESSION", - "statement_id": "1", - "substatement_id": "1", - "class": "READ", - "command": "SELECT FOR KEY SHARE", - "statement": "SELECT pg_current_wal_lsn()", - "parameter": "" - } - }, - "logging_pod": "cluster-example-1", -} -``` - -See the -[PGAudit documentation](https://github.com/pgaudit/pgaudit/blob/master/README.md#format) -for more details about each field in a record. - -## EDB Audit logs - -Clusters that are running on EDB Postgres Advanced Server (EPAS) -can enable [EDB Audit](/epas/latest/epas_security_guide/05_edb_audit_logging/) as follows: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - imageName: docker.enterprisedb.com/k8s/edb-postgres-advanced:18-standard-ubi9 - - postgresql: - epas: - audit: true - - storage: - size: 1Gi -``` - -Setting `.spec.postgresql.epas.audit: true` enforces the following parameters: - -```text -edb_audit = 'csv' -edb_audit_destination = 'file' -edb_audit_directory = '/controller/log' -edb_audit_filename = 'edb_audit' -edb_audit_rotation_day = 'none' -edb_audit_rotation_seconds = '0' -edb_audit_rotation_size = '0' -edb_audit_tag = '' -edb_log_every_bulk_value = 'false' -``` - -Other parameters can be passed via `.spec.postgresql.parameters` as usual. - -The audit CSV logs are parsed and routed to stdout in JSON format, similarly to all the remaining logs: - -- `.logger` set to `edb_audit` -- `.msg` set to `record` -- `.record` containing the whole parsed record as a JSON object - -See the example below: - -```json -{ - "level": "info", - "ts": 1624629110.7641866, - "logger": "edb_audit", - "msg": "record", - "record": { - "log_time": "2021-06-25 13:51:50.763 UTC", - "user_name": "postgres", - "database_name": "postgres", - "process_id": "68", - "connection_from": "[local]", - "session_id": "60d5df76.44", - "session_line_num": "5", - "process_status": "idle in transaction", - "session_start_time": "2021-06-25 13:51:50 UTC", - "virtual_transaction_id": "3/93", - "transaction_id": "1183", - "error_severity": "AUDIT", - "sql_state_code": "00000", - "message": "statement: GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text) TO \"streaming_replica\"", - "detail": "", - "hint": "", - "internal_query": "", - "internal_query_pos": "", - "context": "", - "query": "", - "query_pos": "", - "location": "", - "application_name": "", - "backend_type": "client backend", - "command_tag": "GRANT", - "audit_tag": "", - "type": "grant" - }, - "logging_pod": "cluster-example-1", -} -``` - -See EDB [Audit file](/epas/latest/epas_security_guide/05_edb_audit_logging/) -for more details about the records' fields. - -## Other Logs - -All logs generated by the operator and its instances are in JSON format, with -the `logger` field indicating the process that produced them. The possible -`logger` values are as follows: - -- `barman-cloud-wal-archive`: logs from `barman-cloud-wal-archive` -- `barman-cloud-wal-restore`: logs from `barman-cloud-wal-restore` -- `edb_audit`: from the EDB Audit extension -- `initdb`: logs from running `initdb` -- `pg_basebackup`: logs from running `pg_basebackup` -- `pg_controldata`: logs from running `pg_controldata` -- `pg_ctl`: logs from running any `pg_ctl` subcommand -- `pg_rewind`: logs from running `pg_rewind` -- `pgaudit`: logs from the PGAudit extension -- `postgres`: logs from the `postgres` instance (with `msg` distinct from - `record`) -- `wal-archive`: logs from the `wal-archive` subcommand of the instance manager -- `wal-restore`: logs from the `wal-restore` subcommand of the instance manager -- `instance-manager`: from the [PostgreSQL instance manager](./instance_manager.md) - -With the exception of `postgres` and `edb_audit`, which follows a specific structure, -all other `logger` values contain the `msg` field with the escaped message that is -logged. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/logical_replication.mdx b/product_docs/docs/postgres_for_kubernetes/preview/logical_replication.mdx deleted file mode 100644 index fd0fc9c06c1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/logical_replication.mdx +++ /dev/null @@ -1,536 +0,0 @@ ---- -title: 'Logical Replication' -originalFilePath: 'src/logical_replication.md' ---- - - - -PostgreSQL extends its replication capabilities beyond physical replication, -which operates at the level of exact block addresses and byte-by-byte copying, -by offering [logical replication](https://www.postgresql.org/docs/current/logical-replication.html). -Logical replication replicates data objects and their changes based on a -defined replication identity, typically the primary key. - -Logical replication uses a publish-and-subscribe model, where subscribers -connect to publications on a publisher node. Subscribers pull data changes from -these publications and can re-publish them, enabling cascading replication and -complex topologies. - -!!!info Important -To protect your logical replication subscribers after a failover of the -publisher cluster in {{name.ln}}, ensure that replication slot -synchronization for logical decoding is enabled. Without this, your logical -replication clients may lose data and fail to continue seamlessly after a -failover. For configuration details, see -["Replication: Logical Decoding Slot Synchronization"](replication.md#logical-decoding-slot-synchronization). -!!! - -This flexible model is particularly useful for: - -- Online data migrations -- Live PostgreSQL version upgrades -- Data distribution across systems -- Real-time analytics -- Integration with external applications - -!!!info -For more details, examples, and limitations, please refer to the -[official PostgreSQL documentation on Logical Replication](https://www.postgresql.org/docs/current/logical-replication.html). -!!! - -**{{name.ln}}** enhances this capability by providing declarative support for -key PostgreSQL logical replication objects: - -- **Publications** via the `Publication` resource -- **Subscriptions** via the `Subscription` resource - -## Publications - -In PostgreSQL's publish-and-subscribe replication model, a -[**publication**](https://www.postgresql.org/docs/current/logical-replication-publication.html) -is the source of data changes. It acts as a logical container for the change -sets (also known as *replication sets*) generated from one or more tables within -a database. Publications can be defined on any PostgreSQL 10+ instance acting -as the *publisher*, including instances managed by popular DBaaS solutions in the -public cloud. Each publication is tied to a single database and provides -fine-grained control over which tables and changes are replicated. - -For publishers outside Kubernetes, you can [create publications using SQL](https://www.postgresql.org/docs/current/sql-createpublication.html) -or leverage the [`cnp publication create` plugin command](kubectl-plugin.md#logical-replication-publications). - -When managing `Cluster` objects with **{{name.ln}}**, PostgreSQL publications -can be defined declaratively through the `Publication` resource. - -!!!info -Please refer to the [API reference](pg4k.v1.md#publication) -for the full list of attributes you can define for each `Publication` object. -!!! - -Suppose you have a cluster named `freddie` and want to replicate all tables in -the `app` database. Here's a `Publication` manifest: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Publication -metadata: - name: freddie-publisher -spec: - cluster: - name: freddie - dbname: app - name: publisher - target: - allTables: true -``` - -In the above example: - -- The publication object is named `freddie-publisher` (`metadata.name`). -- The publication is created via the primary of the `freddie` cluster - (`spec.cluster.name`) with name `publisher` (`spec.name`). -- It includes all tables (`spec.target.allTables: true`) from the `app` - database (`spec.dbname`). - -### Fine-grained control over publication tables - -While the `allTables` option provides a convenient way to replicate all tables -in a database, PostgreSQL version 15 and later introduce enhanced flexibility -through the [`CREATE PUBLICATION`](https://www.postgresql.org/docs/current/sql-createpublication.html) -command. This allows you to precisely define which tables, or even which types -of data changes, should be included in a publication. - -!!!info Important -If you are using PostgreSQL versions earlier than 15, review the syntax and -options available for `CREATE PUBLICATION` in your specific release. Some -parameters and features may not be supported. -!!! - -For complex or tailored replication setups, refer to the -[PostgreSQL logical replication documentation](https://www.postgresql.org/docs/current/logical-replication.html). - -Additionally, refer to the [{{name.ln}} API reference](pg4k.v1.md#publicationtarget) -for details on declaratively customizing replication targets. - -The following example defines a publication that replicates all tables in the -`portal` schema of the `app` database, along with the `users` table from the -`access` schema: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Publication -metadata: - name: publisher -spec: - cluster: - name: freddie - dbname: app - name: publisher - target: - objects: - - tablesInSchema: portal - - table: - name: users - schema: access -``` - -### Required Fields in the `Publication` Manifest - -The following fields are required for a `Publication` object: - -- `metadata.name`: Unique name for the Kubernetes `Publication` object. -- `spec.cluster.name`: Name of the PostgreSQL cluster. -- `spec.dbname`: Database name where the publication is created. -- `spec.name`: Publication name in PostgreSQL. -- `spec.target`: Specifies the tables or changes to include in the publication. - -The `Publication` object must reference a specific `Cluster`, determining where -the publication will be created. It is managed by the cluster's primary instance, -ensuring the publication is created or updated as needed. - -!!!warning - -The `spec.cluster` field is immutable after creation. To create a -publication on a different `Cluster`, create a new `Publication` resource -instead of updating an existing one. -!!! - -### Reconciliation and Status - -After creating a `Publication`, {{name.ln}} manages it on the primary -instance of the specified cluster. Following a successful reconciliation cycle, -the `Publication` status will reflect the following: - -- `applied: true`, indicates the configuration has been successfully applied. -- `observedGeneration` matches `metadata.generation`, confirming the applied - configuration corresponds to the most recent changes. - -If an error occurs during reconciliation, `status.applied` will be `false`, and -an error message will be included in the `status.message` field. - -### Removing a publication - -The `publicationReclaimPolicy` field controls the behavior when deleting a -`Publication` object: - -- `retain` (default): Leaves the publication in PostgreSQL for manual - management. -- `delete`: Automatically removes the publication from PostgreSQL. - -Consider the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Publication -metadata: - name: freddie-publisher -spec: - cluster: - name: freddie - dbname: app - name: publisher - target: - allTables: true - publicationReclaimPolicy: delete -``` - -In this case, deleting the `Publication` object also removes the `publisher` -publication from the `app` database of the `freddie` cluster. - -On a replica cluster the database is read-only, so deleting a `Publication` -object releases its finalizer and removes the Kubernetes object without dropping -the publication in PostgreSQL, even with `publicationReclaimPolicy: delete`. -Dropping the publication is left to the primary cluster, which owns it. - -## Subscriptions - -In PostgreSQL's publish-and-subscribe replication model, a -[**subscription**](https://www.postgresql.org/docs/current/logical-replication-subscription.html) -represents the downstream component that consumes data changes. -A subscription establishes the connection to a publisher's database and -specifies the set of publications (one or more) it subscribes to. Subscriptions -can be created on any supported PostgreSQL instance acting as the *subscriber*. - -!!!info Important -Since schema definitions are not replicated, the subscriber must have the -corresponding tables already defined before data replication begins. -!!! - -{{name.ln}} simplifies subscription management by enabling you to define them -declaratively using the `Subscription` resource. - -!!!info -Please refer to the [API reference](pg4k.v1.md#subscription) -for the full list of attributes you can define for each `Subscription` object. -!!! - -Suppose you want to replicate changes from the `publisher` publication on the -`app` database of the `freddie` cluster (*publisher*) to the `app` database of -the `king` cluster (*subscriber*). Here's an example of a `Subscription` -manifest: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Subscription -metadata: - name: freddie-to-king-subscription -spec: - cluster: - name: king - dbname: app - name: subscriber - externalClusterName: freddie - publicationName: publisher -``` - -In the above example: - -- The subscription object is named `freddie-to-king-subscriber` (`metadata.name`). -- The subscription is created in the `app` database (`spec.dbname`) of the - `king` cluster (`spec.cluster.name`), with name `subscriber` (`spec.name`). -- It connects to the `publisher` publication in the external `freddie` cluster, - referenced by `spec.externalClusterName`. - -To facilitate this setup, the `freddie` external cluster must be defined in the -`king` cluster's configuration. Below is an example excerpt showing how to -define the external cluster in the `king` manifest: - -```yaml -externalClusters: - - name: freddie - connectionParameters: - host: freddie-rw.default.svc - user: postgres - dbname: app -``` - -!!!info -For more details on configuring the `externalClusters` section, see the -["Bootstrap" section](bootstrap.md#the-externalclusters-section) of the -documentation. -!!! - -As you can see, a subscription can connect to any PostgreSQL database -accessible over the network. This flexibility allows you to seamlessly migrate -your data into Kubernetes with nearly zero downtime. It’s an excellent option -for transitioning from various environments, including popular cloud-based -Database-as-a-Service (DBaaS) platforms. - -### Required Fields in the `Subscription` Manifest - -The following fields are mandatory for defining a `Subscription` object: - -- `metadata.name`: A unique name for the Kubernetes `Subscription` object - within its namespace. -- `spec.cluster.name`: The name of the PostgreSQL cluster where the - subscription will be created. -- `spec.dbname`: The name of the database in which the subscription will be - created. -- `spec.name`: The name of the subscription as it will appear in PostgreSQL. -- `spec.externalClusterName`: The name of the external cluster, as defined in - the `spec.cluster.name` cluster's configuration. This references the - publisher database. -- `spec.publicationName`: The name of the publication in the publisher database - to which the subscription will connect. - -The `Subscription` object must reference a specific `Cluster`, determining -where the subscription will be managed. {{name.ln}} ensures that the -subscription is created or updated on the primary instance of the specified -cluster. - -!!!warning - -The `spec.cluster` field is immutable after creation. To manage the -subscription on a different `Cluster`, create a new `Subscription` -resource instead of updating an existing one. -!!! - -### Reconciliation and Status - -After creating a `Subscription`, {{name.ln}} manages it on the primary -instance of the specified cluster. Following a successful reconciliation cycle, -the `Subscription` status will reflect the following: - -- `applied: true`, indicates the configuration has been successfully applied. -- `observedGeneration` matches `metadata.generation`, confirming the applied - configuration corresponds to the most recent changes. - -If an error occurs during reconciliation, `status.applied` will be `false`, and -an error message will be included in the `status.message` field. - -### Removing a Subscription - -The `subscriptionReclaimPolicy` field controls the behavior when deleting a -`Subscription` object: - -- `retain` (default): Leaves the subscription in PostgreSQL for manual - management. -- `delete`: Automatically removes the subscription from PostgreSQL. - -Consider the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Subscription -metadata: - name: freddie-to-king-subscription -spec: - cluster: - name: king - dbname: app - name: subscriber - externalClusterName: freddie - publicationName: publisher - subscriptionReclaimPolicy: delete -``` - -In this case, deleting the `Subscription` object also removes the `subscriber` -subscription from the `app` database of the `king` cluster. - -On a replica cluster the database is read-only, so deleting a `Subscription` -object releases its finalizer and removes the Kubernetes object without dropping -the subscription in PostgreSQL, even with `subscriptionReclaimPolicy: delete`. -Dropping the subscription is left to the primary cluster, which owns it. - -### Resilience to Failovers - -To ensure that your logical replication subscriptions remain operational after -a failover of the publisher, configure {{name.ln}} to synchronize logical -decoding slots across the cluster. For detailed instructions, see -[Logical Decoding Slot Synchronization](replication.md#logical-decoding-slot-synchronization). - -## Limitations - -Logical replication in PostgreSQL has some inherent limitations, as outlined in -the [official documentation](https://www.postgresql.org/docs/current/logical-replication-restrictions.html). -Notably, the following objects are not replicated: - -- **Database schema and DDL commands** -- **Sequence data** -- **Large objects** - -### Addressing Schema Replication - -The first limitation, related to schema replication, can be easily addressed -using {{name.ln}}' capabilities. For instance, you can leverage the `import` -bootstrap feature to copy the schema of the tables you need to replicate. -Alternatively, you can manually create the schema as you would for any -PostgreSQL database. - -### Handling Sequences - -While sequences are not automatically kept in sync through logical replication, -{{name.ln}} provides a solution to be used in live migrations. -You can use the [`cnp` plugin](kubectl-plugin.md#synchronizing-sequences) -to synchronize sequence values, ensuring consistency between the publisher and -subscriber databases. - -## Example of live migration and major Postgres upgrade with logical replication - -To highlight the powerful capabilities of logical replication, this example -demonstrates how to replicate data from a publisher database (`freddie`) -running PostgreSQL 16 to a subscriber database (`king`) running the latest -PostgreSQL version. This setup can be deployed in your Kubernetes cluster for -evaluation and hands-on learning. - -This example illustrates how logical replication facilitates live migrations -and upgrades between PostgreSQL versions while ensuring data consistency. By -combining logical replication with {{name.ln}}, you can easily set up, -manage, and evaluate such scenarios in a Kubernetes environment. - -### Step 1: Setting Up the Publisher (`freddie`) - -The first step involves creating a `freddie` PostgreSQL cluster with version 16. -The cluster contains a single instance and includes an `app` database -initialized with a table, `n`, storing 10,000 numbers. A logical replication -publication named `publisher` is also configured to include all tables in the -database. - -Here’s the manifest for setting up the `freddie` cluster and its publication -resource: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: DatabaseRole -metadata: - name: freddie-app -spec: - cluster: - name: freddie - name: app - login: true - replication: true ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: freddie -spec: - instances: 1 - - imageName: docker.enterprisedb.com/k8s/postgresql:18-standard-ubi9 - - storage: - size: 1Gi - - bootstrap: - initdb: - postInitApplicationSQL: - - CREATE TABLE n (i SERIAL PRIMARY KEY, m INTEGER) - - INSERT INTO n (m) (SELECT generate_series(1, 10000)) - - ALTER TABLE n OWNER TO app ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Publication -metadata: - name: freddie-publisher -spec: - cluster: - name: freddie - dbname: app - name: publisher - target: - allTables: true -``` - -### Step 2: Setting Up the Subscriber (`king`) - -Next, create the `king` PostgreSQL cluster, running the latest version of -PostgreSQL. This cluster initializes by importing the schema from the `app` -database on the `freddie` cluster using the external cluster configuration. A -`Subscription` resource, `freddie-to-king-subscription`, is then configured to -consume changes published by the `publisher` on `freddie`. - -Below is the manifest for setting up the `king` cluster and its subscription: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: king -spec: - instances: 1 - - imageName: docker.enterprisedb.com/k8s/postgresql:18-standard-ubi9 - - storage: - size: 1Gi - - bootstrap: - initdb: - import: - type: microservice - schemaOnly: true - databases: - - app - source: - externalCluster: freddie - - externalClusters: - - name: freddie - connectionParameters: - host: freddie-rw.default.svc - user: app - dbname: app - password: - name: freddie-app - key: password ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Subscription -metadata: - name: freddie-to-king-subscription -spec: - cluster: - name: king - dbname: app - name: subscriber - externalClusterName: freddie - publicationName: publisher -``` - -Once the `king` cluster is running, you can verify that the replication is -working by connecting to the `app` database and counting the records in the `n` -table. The following example uses the `psql` command provided by the `cnp` -plugin for simplicity: - -```console -kubectl cnp psql king -- app -qAt -c 'SELECT count(*) FROM n' -10000 -``` - -This command should return `10000`, confirming that the data from the `freddie` -cluster has been successfully replicated to the `king` cluster. - -Using the `cnp` plugin, you can also synchronize existing sequences to ensure -consistency between the publisher and subscriber. The example below -demonstrates how to synchronize a sequence for the `king` cluster: - -```console -kubectl cnp subscription sync-sequences king --subscription=subscriber -SELECT setval('"public"."n_i_seq"', 10000); - -10000 -``` - -This command updates the sequence `n_i_seq` in the `king` cluster to match the -current value, ensuring it is in sync with the source database. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/monitoring.mdx b/product_docs/docs/postgres_for_kubernetes/preview/monitoring.mdx deleted file mode 100644 index 3d8a4467b9e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/monitoring.mdx +++ /dev/null @@ -1,1137 +0,0 @@ ---- -title: 'Monitoring' -originalFilePath: 'src/monitoring.md' ---- - - - -!!!info Important -Installing Prometheus and Grafana is beyond the scope of this project. -We assume they are correctly installed in your system. However, for -experimentation we provide instructions in -[Part 4 of the Quickstart](quickstart.md#part-4-monitor-clusters-with-prometheus-and-grafana). -!!! - -## Monitoring Instances - -For each PostgreSQL instance, the operator provides an exporter of metrics for -[Prometheus](https://prometheus.io/) via HTTP or HTTPS, on port 9187, named `metrics`. -The operator comes with a [predefined set of metrics](#predefined-set-of-metrics), as well as a highly -configurable and customizable system to define additional queries via one or -more `ConfigMap` or `Secret` resources (see the -["User defined metrics" section](#user-defined-metrics) below for details). - -!!!info Important -{{name.ln}}, by default, installs a set of [predefined metrics](#default-set-of-metrics) -in a `ConfigMap` named `postgresql-operator-default-monitoring`. -!!! - -!!!info -You can inspect the exported metrics by following the instructions in -the ["How to inspect the exported metrics"](#how-to-inspect-the-exported-metrics) -section below. -!!! - -All monitoring queries that are performed on PostgreSQL are: - -- atomic (one read-only transaction per query) -- executed as the `cnp_metrics_exporter` role (a member of `pg_monitor`) -- executed with `application_name` set to `cnp_metrics_exporter` - -The connection uses peer authentication on the pod-local Unix socket; -because `session_user` is never a superuser, the monitoring session -cannot escalate via `RESET ROLE` or `RESET SESSION AUTHORIZATION`. Do -not grant additional privileges or role memberships to -`cnp_metrics_exporter` beyond `pg_monitor` and the table-level grants -required by your custom queries: any extra membership flows into the -scrape session via inheritance and weakens this property. - -Please refer to the "Predefined Roles" section in PostgreSQL -[documentation](https://www.postgresql.org/docs/current/predefined-roles.html) -for details on the `pg_monitor` role. - -Queries, by default, are run against the *main database*, as defined by -the specified `bootstrap` method of the `Cluster` resource, according -to the following logic: - -- using `initdb`: queries will be run by default against the specified database - in `initdb.database`, or `app` if not specified -- using `recovery`: queries will be run by default against the specified database - in `recovery.database`, or `postgres` if not specified -- using `pg_basebackup`: queries will be run by default against the specified database - in `pg_basebackup.database`, or `postgres` if not specified - -The default database can always be overridden for a given user-defined metric, -by specifying a list of one or more databases in the `target_databases` option. - -!!!note Prometheus/Grafana -If you are interested in evaluating the integration of {{name.ln}} -with Prometheus and Grafana, you can find a quick setup guide -in [Part 4 of the quickstart](quickstart.md#part-4-monitor-clusters-with-prometheus-and-grafana) -!!! - -### Output caching - -By default, the outputs of monitoring queries are cached for thirty -seconds. This is done to enhance resource efficiency and to avoid -PostgreSQL to run monitoring queries every time the prometheus -endpoint is scraped. - -The cache itself can be observed by the `cache_hits`, `cache_misses` -and `last_update_timestamp` metrics. - -Setting the `cluster.spec.monitoring.metricsQueriesTTL` to zero will -disable the cache, and in that case the metrics will be run on every -metrics endpoint scrape. - -### Monitoring with the Prometheus operator - -You can monitor a specific PostgreSQL cluster using the -[Prometheus Operator's](https://github.com/prometheus-operator/prometheus-operator) -[`PodMonitor` resource](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api-reference/api.md#monitoring.coreos.com/v1.PodMonitor). - -The recommended approach is to manually create and manage a `PodMonitor` for -each {{name.ln}} cluster. This method provides you with full control over the -monitoring configuration and lifecycle. - -#### Creating a `PodMonitor` - -To monitor your cluster, define a `PodMonitor` resource as follows. Be sure to -deploy it in the same namespace where your Prometheus Operator is configured to -find `PodMonitor` resources. - -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: PodMonitor -metadata: - name: cluster-example -spec: - selector: - matchLabels: - k8s.enterprisedb.io/cluster: cluster-example - podMetricsEndpoints: - - port: metrics -``` - -!!!info Important Configuration Details -- `metadata.name`: Give your `PodMonitor` a unique name. -- `spec.namespaceSelector`: Use this to specify the namespace where - your PostgreSQL cluster is running. -- `spec.selector.matchLabels`: You must use the `k8s.enterprisedb.io/cluster: ` - label to correctly target the PostgreSQL instances. -!!! - -#### Deprecation of Automatic `PodMonitor` Creation - -!!!warning Feature Deprecation Notice -The `.spec.monitoring.enablePodMonitor` field in the `Cluster` resource is -now deprecated and will be removed in a future version of the operator. -!!! - -If you are currently using this feature, we strongly recommend you either -remove or set `.spec.monitoring.enablePodMonitor` to `false` and manually -create a `PodMonitor` resource for your cluster as described above. -This change ensures that you have complete ownership of your monitoring -configuration, preventing it from being managed or overwritten by the operator. - -### Enabling TLS on the Metrics Port - -To enable TLS communication on the metrics port, configure the `.spec.monitoring.tls.enabled` -setting to `true`. This setup ensures that the metrics exporter uses the same -server certificate used by PostgreSQL to secure communication on port 5432. - -!!!info Important -Changing the `.spec.monitoring.tls.enabled` setting will trigger a rolling restart of the Cluster. -!!! - -If the `PodMonitor` is managed by the operator (`.spec.monitoring.enablePodMonitor` set to `true`), -it will automatically contain the necessary configurations to access the metrics via TLS. - -To manually deploy a `PodMonitor` suitable for reading metrics via TLS, define it as follows and -adjust as needed: - -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: PodMonitor -metadata: - name: cluster-example -spec: - selector: - matchLabels: - "k8s.enterprisedb.io/cluster": cluster-example - podMetricsEndpoints: - - port: metrics - scheme: https - tlsConfig: - ca: - secret: - name: cluster-example-ca - key: ca.crt - serverName: cluster-example-rw -``` - -!!!info Important -Ensure you modify the example above with a unique name, as well as the -correct Cluster's namespace and labels (e.g., `cluster-example`). -!!! - -!!!info Important -The `serverName` field in the metrics endpoint must match one of the names -defined in the server certificate. If the default certificate is in use, -the `serverName` value should be in the format `-rw`. -!!! - -### Predefined set of metrics - -Every PostgreSQL instance exporter automatically exposes a set of predefined -metrics, which can be classified in two major categories: - -- PostgreSQL related metrics, starting with `cnp_collector_*`, including: - - - number of WAL files and total size on disk - - number of `.ready` and `.done` files in the archive status folder - - requested minimum and maximum number of synchronous replicas, as well as - the expected and actually observed values - - number of distinct nodes accommodating the instances - - timestamps indicating last failed and last available backup, as well - as the first point of recoverability for the cluster - - flag indicating if replica cluster mode is enabled or disabled - - flag indicating if a manual switchover is required - - flag indicating if fencing is enabled or disabled - -- Go runtime related metrics, starting with `go_*` - -Below is a sample of the metrics returned by the `localhost:9187/metrics` -endpoint of an instance. As you can see, the Prometheus format is -self-documenting: - -```text -# HELP cnp_collector_collection_duration_seconds Collection time duration in seconds -# TYPE cnp_collector_collection_duration_seconds gauge -cnp_collector_collection_duration_seconds{collector="Collect.up"} 0.0031393 - -# HELP cnp_collector_collections_total Total number of times PostgreSQL was accessed for metrics. -# TYPE cnp_collector_collections_total counter -cnp_collector_collections_total 2 - -# HELP cnp_collector_fencing_on 1 if the instance is fenced, 0 otherwise -# TYPE cnp_collector_fencing_on gauge -cnp_collector_fencing_on 0 - -# HELP cnp_collector_nodes_used NodesUsed represents the count of distinct nodes accommodating the instances. A value of '-1' suggests that the metric is not available. 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 match the number of instances in the cluster. -# TYPE cnp_collector_nodes_used gauge -cnp_collector_nodes_used 3 - -# HELP cnp_collector_last_collection_error 1 if the last collection ended with error, 0 otherwise. -# TYPE cnp_collector_last_collection_error gauge -cnp_collector_last_collection_error 0 - -# HELP cnp_collector_manual_switchover_required 1 if a manual switchover is required, 0 otherwise -# TYPE cnp_collector_manual_switchover_required gauge -cnp_collector_manual_switchover_required 0 - -# HELP cnp_collector_pg_wal Total size in bytes of WAL segments in the '/var/lib/postgresql/data/pgdata/pg_wal' directory computed as (wal_segment_size * count) -# TYPE cnp_collector_pg_wal gauge -cnp_collector_pg_wal{value="count"} 9 -cnp_collector_pg_wal{value="slots_max"} NaN -cnp_collector_pg_wal{value="keep"} 32 -cnp_collector_pg_wal{value="max"} 64 -cnp_collector_pg_wal{value="min"} 5 -cnp_collector_pg_wal{value="size"} 1.50994944e+08 -cnp_collector_pg_wal{value="volume_max"} 128 -cnp_collector_pg_wal{value="volume_size"} 2.147483648e+09 - -# HELP cnp_collector_pg_wal_archive_status Number of WAL segments in the '/var/lib/postgresql/data/pgdata/pg_wal/archive_status' directory (ready, done) -# TYPE cnp_collector_pg_wal_archive_status gauge -cnp_collector_pg_wal_archive_status{value="done"} 6 -cnp_collector_pg_wal_archive_status{value="ready"} 0 - -# HELP cnp_collector_replica_mode 1 if the cluster is in replica mode, 0 otherwise -# TYPE cnp_collector_replica_mode gauge -cnp_collector_replica_mode 0 - -# HELP cnp_collector_sync_replicas Number of requested synchronous replicas (synchronous_standby_names) -# TYPE cnp_collector_sync_replicas gauge -cnp_collector_sync_replicas{value="expected"} 0 -cnp_collector_sync_replicas{value="max"} 0 -cnp_collector_sync_replicas{value="min"} 0 -cnp_collector_sync_replicas{value="observed"} 0 - -# HELP cnp_collector_up 1 if PostgreSQL is up, 0 otherwise. -# TYPE cnp_collector_up gauge -cnp_collector_up{cluster="cluster-example"} 1 - -# HELP cnp_collector_postgres_version Postgres version -# TYPE cnp_collector_postgres_version gauge -cnp_collector_postgres_version{cluster="cluster-example",full="18.4"} 18.4 - -# HELP cnp_collector_last_failed_backup_timestamp The last failed backup as a unix timestamp (Deprecated) -# TYPE cnp_collector_last_failed_backup_timestamp gauge -cnp_collector_last_failed_backup_timestamp 0 - -# HELP cnp_collector_last_available_backup_timestamp The last available backup as a unix timestamp (Deprecated) -# TYPE cnp_collector_last_available_backup_timestamp gauge -cnp_collector_last_available_backup_timestamp 1.63238406e+09 - -# HELP cnp_collector_first_recoverability_point The first point of recoverability for the cluster as a unix timestamp (Deprecated) -# TYPE cnp_collector_first_recoverability_point gauge -cnp_collector_first_recoverability_point 1.63238406e+09 - -# HELP cnp_collector_lo_pages Estimated number of pages in the pg_largeobject table -# TYPE cnp_collector_lo_pages gauge -cnp_collector_lo_pages{datname="app"} 0 -cnp_collector_lo_pages{datname="postgres"} 78 - -# HELP cnp_collector_wal_buffers_full Number of times WAL data was written to disk because WAL buffers became full. Only available on PG 14+ -# TYPE cnp_collector_wal_buffers_full gauge -cnp_collector_wal_buffers_full{stats_reset="2023-06-19T10:51:27.473259Z"} 6472 - -# HELP cnp_collector_wal_bytes Total amount of WAL generated in bytes. Only available on PG 14+ -# TYPE cnp_collector_wal_bytes gauge -cnp_collector_wal_bytes{stats_reset="2023-06-19T10:51:27.473259Z"} 1.0035147e+07 - -# HELP cnp_collector_wal_fpi Total number of WAL full page images generated. Only available on PG 14+ -# TYPE cnp_collector_wal_fpi gauge -cnp_collector_wal_fpi{stats_reset="2023-06-19T10:51:27.473259Z"} 1474 - -# HELP cnp_collector_wal_records Total number of WAL records generated. Only available on PG 14+ -# TYPE cnp_collector_wal_records gauge -cnp_collector_wal_records{stats_reset="2023-06-19T10:51:27.473259Z"} 26178 - -# HELP cnp_collector_wal_sync Number of times WAL files were synced to disk via issue_xlog_fsync request (if fsync is on and wal_sync_method is either fdatasync, fsync or fsync_writethrough, otherwise zero). Only available on PG 14+ -# TYPE cnp_collector_wal_sync gauge -cnp_collector_wal_sync{stats_reset="2023-06-19T10:51:27.473259Z"} 37 - -# HELP cnp_collector_wal_sync_time Total amount of time spent syncing WAL files to disk via issue_xlog_fsync request, in milliseconds (if track_wal_io_timing is enabled, fsync is on, and wal_sync_method is either fdatasync, fsync or fsync_writethrough, otherwise zero). Only available on PG 14+ -# TYPE cnp_collector_wal_sync_time gauge -cnp_collector_wal_sync_time{stats_reset="2023-06-19T10:51:27.473259Z"} 0 - -# HELP cnp_collector_wal_write Number of times WAL buffers were written out to disk via XLogWrite request. Only available on PG 14+ -# TYPE cnp_collector_wal_write gauge -cnp_collector_wal_write{stats_reset="2023-06-19T10:51:27.473259Z"} 7243 - -# HELP cnp_collector_wal_write_time Total amount of time spent writing WAL buffers to disk via XLogWrite request, in milliseconds (if track_wal_io_timing is enabled, otherwise zero). This includes the sync time when wal_sync_method is either open_datasync or open_sync. Only available on PG 14+ -# TYPE cnp_collector_wal_write_time gauge -cnp_collector_wal_write_time{stats_reset="2023-06-19T10:51:27.473259Z"} 0 - -# HELP cnp_last_error 1 if the last collection ended with error, 0 otherwise. -# TYPE cnp_last_error gauge -cnp_last_error 0 - -# HELP go_gc_duration_seconds A summary of the pause duration of garbage collection cycles. -# TYPE go_gc_duration_seconds summary -go_gc_duration_seconds{quantile="0"} 5.01e-05 -go_gc_duration_seconds{quantile="0.25"} 7.27e-05 -go_gc_duration_seconds{quantile="0.5"} 0.0001748 -go_gc_duration_seconds{quantile="0.75"} 0.0002959 -go_gc_duration_seconds{quantile="1"} 0.0012776 -go_gc_duration_seconds_sum 0.0035741 -go_gc_duration_seconds_count 13 - -# HELP go_goroutines Number of goroutines that currently exist. -# TYPE go_goroutines gauge -go_goroutines 25 - -# HELP go_info Information about the Go environment. -# TYPE go_info gauge -go_info{version="go1.20.5"} 1 - -# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use. -# TYPE go_memstats_alloc_bytes gauge -go_memstats_alloc_bytes 4.493744e+06 - -# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed. -# TYPE go_memstats_alloc_bytes_total counter -go_memstats_alloc_bytes_total 2.1698216e+07 - -# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table. -# TYPE go_memstats_buck_hash_sys_bytes gauge -go_memstats_buck_hash_sys_bytes 1.456234e+06 - -# HELP go_memstats_frees_total Total number of frees. -# TYPE go_memstats_frees_total counter -go_memstats_frees_total 172118 - -# HELP go_memstats_gc_cpu_fraction The fraction of this program's available CPU time used by the GC since the program started. -# TYPE go_memstats_gc_cpu_fraction gauge -go_memstats_gc_cpu_fraction 1.0749468700447189e-05 - -# HELP go_memstats_gc_sys_bytes Number of bytes used for garbage collection system metadata. -# TYPE go_memstats_gc_sys_bytes gauge -go_memstats_gc_sys_bytes 5.530048e+06 - -# HELP go_memstats_heap_alloc_bytes Number of heap bytes allocated and still in use. -# TYPE go_memstats_heap_alloc_bytes gauge -go_memstats_heap_alloc_bytes 4.493744e+06 - -# HELP go_memstats_heap_idle_bytes Number of heap bytes waiting to be used. -# TYPE go_memstats_heap_idle_bytes gauge -go_memstats_heap_idle_bytes 5.8236928e+07 - -# HELP go_memstats_heap_inuse_bytes Number of heap bytes that are in use. -# TYPE go_memstats_heap_inuse_bytes gauge -go_memstats_heap_inuse_bytes 7.528448e+06 - -# HELP go_memstats_heap_objects Number of allocated objects. -# TYPE go_memstats_heap_objects gauge -go_memstats_heap_objects 26306 - -# HELP go_memstats_heap_released_bytes Number of heap bytes released to OS. -# TYPE go_memstats_heap_released_bytes gauge -go_memstats_heap_released_bytes 5.7401344e+07 - -# HELP go_memstats_heap_sys_bytes Number of heap bytes obtained from system. -# TYPE go_memstats_heap_sys_bytes gauge -go_memstats_heap_sys_bytes 6.5765376e+07 - -# HELP go_memstats_last_gc_time_seconds Number of seconds since 1970 of last garbage collection. -# TYPE go_memstats_last_gc_time_seconds gauge -go_memstats_last_gc_time_seconds 1.6311727586032727e+09 - -# HELP go_memstats_lookups_total Total number of pointer lookups. -# TYPE go_memstats_lookups_total counter -go_memstats_lookups_total 0 - -# HELP go_memstats_mallocs_total Total number of mallocs. -# TYPE go_memstats_mallocs_total counter -go_memstats_mallocs_total 198424 - -# HELP go_memstats_mcache_inuse_bytes Number of bytes in use by mcache structures. -# TYPE go_memstats_mcache_inuse_bytes gauge -go_memstats_mcache_inuse_bytes 14400 - -# HELP go_memstats_mcache_sys_bytes Number of bytes used for mcache structures obtained from system. -# TYPE go_memstats_mcache_sys_bytes gauge -go_memstats_mcache_sys_bytes 16384 - -# HELP go_memstats_mspan_inuse_bytes Number of bytes in use by mspan structures. -# TYPE go_memstats_mspan_inuse_bytes gauge -go_memstats_mspan_inuse_bytes 191896 - -# HELP go_memstats_mspan_sys_bytes Number of bytes used for mspan structures obtained from system. -# TYPE go_memstats_mspan_sys_bytes gauge -go_memstats_mspan_sys_bytes 212992 - -# HELP go_memstats_next_gc_bytes Number of heap bytes when next garbage collection will take place. -# TYPE go_memstats_next_gc_bytes gauge -go_memstats_next_gc_bytes 8.689632e+06 - -# HELP go_memstats_other_sys_bytes Number of bytes used for other system allocations. -# TYPE go_memstats_other_sys_bytes gauge -go_memstats_other_sys_bytes 2.566622e+06 - -# HELP go_memstats_stack_inuse_bytes Number of bytes in use by the stack allocator. -# TYPE go_memstats_stack_inuse_bytes gauge -go_memstats_stack_inuse_bytes 1.343488e+06 - -# HELP go_memstats_stack_sys_bytes Number of bytes obtained from system for stack allocator. -# TYPE go_memstats_stack_sys_bytes gauge -go_memstats_stack_sys_bytes 1.343488e+06 - -# HELP go_memstats_sys_bytes Number of bytes obtained from system. -# TYPE go_memstats_sys_bytes gauge -go_memstats_sys_bytes 7.6891144e+07 - -# HELP go_threads Number of OS threads created. -# TYPE go_threads gauge -go_threads 18 -``` - -!!!note -`cnp_collector_postgres_version` is a GaugeVec metric containing the -`Major.Minor` version of Postgres (either PostgreSQL or EPAS). The full -semantic version `Major.Minor.Patch` can be found inside one of its label -field named `full`. -!!! - -!!!warning -The metrics `cnp_collector_last_failed_backup_timestamp`, -`cnp_collector_last_available_backup_timestamp`, and -`cnp_collector_first_recoverability_point` have been deprecated starting -from version 1.26. These metrics will continue to function with native backup -solutions such as in-core Barman Cloud (deprecated) and volume snapshots. Note -that for these cases, `cnp_collector_first_recoverability_point` and -`cnp_collector_last_available_backup_timestamp` will remain zero until the -first backup is completed to the object store. This is separate from WAL -archiving. -!!! - -### User defined metrics - -This feature is currently in *beta* state and the format is inspired by the -[queries.yaml file (release 0.12)](https://github.com/prometheus-community/postgres_exporter/blob/v0.12.1/queries.yaml) -of the PostgreSQL Prometheus Exporter. - -Custom metrics can be defined by users by referring to the created `Configmap`/`Secret` in a `Cluster` definition -under the `.spec.monitoring.customQueriesConfigMap` or `customQueriesSecret` section as in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example - namespace: test -spec: - instances: 3 - - storage: - size: 1Gi - - monitoring: - customQueriesConfigMap: - - name: example-monitoring - key: custom-queries -``` - -The `customQueriesConfigMap`/`customQueriesSecret` sections contain a list of -`ConfigMap`/`Secret` references specifying the key in which the custom queries are defined. -Take care that the referred resources have to be created **in the same namespace as the Cluster** resource. - -!!!note -If you want ConfigMaps and Secrets to be **automatically** reloaded by instances, you can -add a label with key `k8s.enterprisedb.io/reload` to it, otherwise you will have to reload -the instances using the `kubectl cnp reload` subcommand. -!!! - -!!!info Important -When a user defined metric overwrites an already existing metric the instance manager prints a json warning log, -containing the message:`Query with the same name already found. Overwriting the existing one.` -and a key `queryName` containing the overwritten query name. -!!! - -#### Custom query privileges and safety - -!!!warning - -Custom queries run as the `cnp_metrics_exporter` role, which inherits -`pg_monitor`. Queries within `pg_monitor`'s scope (catalog reads, -`pg_stat_*` views, configuration parameters) work without modification. -Queries that read user-owned tables or superuser-only catalogs (e.g. -`pg_authid`, `pg_subscription`) need explicit grants. Reading a table -also requires USAGE on its schema: - -```sql -GRANT USAGE ON SCHEMA myschema TO cnp_metrics_exporter; -GRANT SELECT ON TABLE myschema.mytable TO cnp_metrics_exporter; -``` - -Every database in `target_databases` must allow -`cnp_metrics_exporter` to `CONNECT`. On clusters that have -revoked `CONNECT` from `PUBLIC` for a database, grant it -explicitly to that role: - -```sql -GRANT CONNECT ON DATABASE domainapp TO cnp_metrics_exporter; -``` - -Prefer an explicit list of trusted databases (e.g. -`target_databases: ["domainapp"]`) over the `"*"` wildcard. The -wildcard scrapes every database the role can connect to and -silently skips the rest, so an explicit list makes a missing grant -easier to notice. Use `"*"` only when the query is meant to -collect per-database metrics across the whole cluster. - -Schema-qualify catalog references (`pg_catalog.now()`, -`pg_catalog.current_database()`) to prevent `search_path` shadowing -by user-owned objects. - -Custom monitoring queries run inside a transaction whose -`search_path` is pinned to `pg_catalog, public, pg_temp`, -regardless of any `search_path` configured on the database or the -role. Unqualified references to objects in other user-defined -schemas will therefore fail to resolve: schema-qualify them (e.g. -`myschema.mytable`) so the query does not depend on the -`search_path`. -!!! - -#### Example of a user defined metric - -Here you can see an example of a `ConfigMap` containing a single custom query, -referenced by the `Cluster` example above: - -```yaml -apiVersion: v1 -kind: ConfigMap -metadata: - name: example-monitoring - namespace: test - labels: - k8s.enterprisedb.io/reload: "" -data: - custom-queries: | - pg_replication: - query: "SELECT CASE WHEN NOT pg_catalog.pg_is_in_recovery() - THEN 0 - ELSE GREATEST (0, - EXTRACT(EPOCH FROM (pg_catalog.now() OPERATOR(pg_catalog.-) pg_catalog.pg_last_xact_replay_timestamp()))) - END AS lag, - pg_catalog.pg_is_in_recovery() AS in_recovery, - EXISTS (TABLE pg_catalog.pg_stat_wal_receiver) AS is_wal_receiver_up, - (SELECT pg_catalog.count(*) FROM pg_catalog.pg_stat_replication) AS streaming_replicas" - - metrics: - - lag: - usage: "GAUGE" - description: "Replication lag behind primary in seconds" - - in_recovery: - usage: "GAUGE" - description: "Whether the instance is in recovery" - - is_wal_receiver_up: - usage: "GAUGE" - description: "Whether the instance wal_receiver is up" - - streaming_replicas: - usage: "GAUGE" - description: "Number of streaming replicas connected to the instance" -``` - -A list of basic monitoring queries can be found in the -[`default-monitoring.yaml` file](../default-monitoring.yaml) -that is already installed in your {{name.ln}} deployment (see ["Default set of metrics"](#default-set-of-metrics)). - -#### Example of a user defined metric with predicate query - -The `predicate_query` option allows the user to execute the `query` to collect the metrics only under the specified conditions. -To do so the user needs to provide a predicate query that returns at most one row with a single `boolean` column. - -The predicate query is executed in the same transaction as the main query and against the same databases. - -```yaml -some_query: | - predicate_query: | - SELECT - some_bool as predicate - FROM some_table - query: | - SELECT - pg_catalog.count(*) as rows - FROM some_table - metrics: - - rows: - usage: "GAUGE" - description: "number of rows" -``` - -#### Example of a user defined metric running on multiple databases - -If the `target_databases` option lists more than one database -the metric is collected from each of them. - -Database auto-discovery can be enabled for a specific query by specifying a -*shell-like pattern* (i.e., containing `*`, `?` or `[]`) in the list of -`target_databases`. If provided, the operator will expand the list of target -databases by adding all the databases returned by the execution of `SELECT -datname FROM pg_catalog.pg_database WHERE datallowconn AND NOT datistemplate -AND pg_catalog.has_database_privilege(datname, 'CONNECT')` and matching the -pattern according to [path.Match()](https://pkg.go.dev/path#Match) rules. -Databases on which `cnp_metrics_exporter` lacks the `CONNECT` privilege are -silently skipped; if you want a database with revoked `PUBLIC` access to be -scraped, grant `CONNECT` explicitly (see "Custom query privileges and safety" -above). - -!!!note -The `*` character has a [special meaning](https://yaml.org/spec/1.2/spec.html#id2786448) in yaml, -so you need to quote (`"*"`) the `target_databases` value when it includes such a pattern. -!!! - -It is recommended that you always include the name of the database -in the returned labels, for example using the `pg_catalog.current_database()` -function as in the following example: - -```yaml -some_query: | - query: | - SELECT - pg_catalog.current_database() as datname, - pg_catalog.count(*) as rows - FROM some_table - metrics: - - datname: - usage: "LABEL" - description: "Name of current database" - - rows: - usage: "GAUGE" - description: "number of rows" - target_databases: - - albert - - bb - - freddie -``` - -This will produce in the following metric being exposed: - -```text -cnp_some_query_rows{datname="albert"} 2 -cnp_some_query_rows{datname="bb"} 5 -cnp_some_query_rows{datname="freddie"} 10 -``` - -Here is an example of a query with auto-discovery enabled which also -runs on the `template1` database (otherwise not returned by the -aforementioned query): - -```yaml -some_query: | - query: | - SELECT - pg_catalog.current_database() as datname, - pg_catalog.count(*) as rows - FROM some_table - metrics: - - datname: - usage: "LABEL" - description: "Name of current database" - - rows: - usage: "GAUGE" - description: "number of rows" - target_databases: - - "*" - - "template1" -``` - -The above example will produce the following metrics (provided the databases exist): - -```text -cnp_some_query_rows{datname="albert"} 2 -cnp_some_query_rows{datname="bb"} 5 -cnp_some_query_rows{datname="freddie"} 10 -cnp_some_query_rows{datname="template1"} 7 -cnp_some_query_rows{datname="postgres"} 42 -``` - -### Structure of a user defined metric - -Every custom query has the following basic structure: - -```yaml -: - query: "" - metrics: - - : - usage: "" - description: "" -``` - -Here is a short description of all the available fields: - -- ``: the name of the Prometheus metric - - `name`: override ``, if defined - - `query`: the SQL query to run on the target database to generate the metrics - - `primary`: whether to run the query only on the primary instance - - `master`: same as `primary` (for compatibility with the Prometheus PostgreSQL exporter's syntax - deprecated) - - `runonserver`: a semantic version range to limit the versions of PostgreSQL the query should run on - (e.g. `">=11.0.0"` or `">=12.0.0 <=15.0.0"`) - - `target_databases`: a list of databases to run the `query` against, - or a [shell-like pattern](#example-of-a-user-defined-metric-running-on-multiple-databases) - to enable auto discovery. Overwrites the default database if provided. - - `predicate_query`: a SQL query that returns at most one row and one `boolean` column to run on the target database. - The system evaluates the predicate and if `true` executes the `query`. - - `metrics`: section containing a list of all exported columns, defined as follows: - - ``: the name of the column returned by the query - - `name`: override the `ColumnName` of the column in the metric, if defined - - `usage`: one of the values described below - - `description`: the metric's description - - `metrics_mapping`: the optional column mapping when `usage` is set to `MAPPEDMETRIC` - -The possible values for `usage` are: - -| Column Usage Label | Description | -| :----------------- | :------------------------------------------------------- | -| `DISCARD` | this column should be ignored | -| `LABEL` | use this column as a label | -| `COUNTER` | use this column as a counter | -| `GAUGE` | use this column as a gauge | -| `MAPPEDMETRIC` | use this column with the supplied mapping of text values | -| `DURATION` | use this column as a text duration (in milliseconds) | -| `HISTOGRAM` | use this column as a histogram | - -Please visit the ["Metric Types" page](https://prometheus.io/docs/concepts/metric_types/) -from the Prometheus documentation for more information. - -### Output of a user defined metric - -Custom defined metrics are returned by the Prometheus exporter endpoint (`:9187/metrics`) -with the following format: - -```text -cnp__{= ... } -``` - -!!!note -`LabelColumnName` are metrics with `usage` set to `LABEL` and their `Value` -!!! - -Considering the `pg_replication` example above, the exporter's endpoint would -return the following output when invoked: - -```text -# HELP cnp_pg_replication_in_recovery Whether the instance is in recovery -# TYPE cnp_pg_replication_in_recovery gauge -cnp_pg_replication_in_recovery 0 -# HELP cnp_pg_replication_lag Replication lag behind primary in seconds -# TYPE cnp_pg_replication_lag gauge -cnp_pg_replication_lag 0 -# HELP cnp_pg_replication_streaming_replicas Number of streaming replicas connected to the instance -# TYPE cnp_pg_replication_streaming_replicas gauge -cnp_pg_replication_streaming_replicas 2 -# HELP cnp_pg_replication_is_wal_receiver_up Whether the instance wal_receiver is up -# TYPE cnp_pg_replication_is_wal_receiver_up gauge -cnp_pg_replication_is_wal_receiver_up 0 -``` - -### Default set of metrics - -The operator can be configured to automatically inject in a Cluster a set of -monitoring queries defined in a ConfigMap or a Secret, inside the operator's namespace. -You have to set the `MONITORING_QUERIES_CONFIGMAP` or -`MONITORING_QUERIES_SECRET` key in the ["operator configuration"](operator_conf.md), -respectively to the name of the ConfigMap or the Secret; -the operator will then use the content of the `queries` key. - -Any change to the `queries` content will be immediately reflected on all the -deployed Clusters using it. - -The operator installation manifests come with a predefined ConfigMap, -called `postgresql-operator-default-monitoring`, to be used by all Clusters. -`MONITORING_QUERIES_CONFIGMAP` is by default set to `postgresql-operator-default-monitoring` in the operator configuration. - -If you want to disable the default set of metrics, you can: - -- disable it at operator level: set the `MONITORING_QUERIES_CONFIGMAP`/`MONITORING_QUERIES_SECRET` key to `""` - (empty string), in the operator ConfigMap. Changes to operator ConfigMap require an operator restart. -- disable it for a specific Cluster: set `.spec.monitoring.disableDefaultQueries` to `true` in the Cluster. - -!!!info Important -The ConfigMap or Secret specified via `MONITORING_QUERIES_CONFIGMAP`/`MONITORING_QUERIES_SECRET` -will always be copied to the Cluster's namespace with a fixed name: `postgresql-operator-default-monitoring`. -So that, if you intend to have default metrics, you should not create a ConfigMap with this name in the cluster's namespace. -!!! - -### Differences with the Prometheus Postgres exporter - -{{name.ln}} is inspired by the PostgreSQL Prometheus Exporter, but -presents some differences. In particular, the `cache_seconds` field is not implemented -in {{name.ln}}' exporter. - -### Manually creating the metrics exporter role - -The operator creates the `cnp_metrics_exporter` PostgreSQL role on the -primary during reconciliation; it then propagates to standbys and -replica clusters via streaming replication. - -If the role is missing (replica cluster upgraded before its primary, -restore from a backup that predates the role, accidental removal), -recreate it as a superuser on the writable primary of the replication -chain (the source primary, not a designated primary of a replica -cluster): - -```sql -CREATE ROLE cnp_metrics_exporter WITH LOGIN NOSUPERUSER NOCREATEDB - NOCREATEROLE NOREPLICATION NOBYPASSRLS INHERIT; -GRANT pg_monitor TO cnp_metrics_exporter; -``` - -If your custom monitoring queries need access to objects outside -`pg_monitor`'s scope, grant the necessary privileges explicitly. SELECT -on a table also requires USAGE on its schema: - -```sql -GRANT USAGE ON SCHEMA myschema TO cnp_metrics_exporter; -GRANT SELECT ON TABLE myschema.mytable TO cnp_metrics_exporter; -``` - -## Monitoring the {{name.ln}} operator - -The operator internally exposes [Prometheus](https://prometheus.io/) metrics -via HTTP on port 8080, named `metrics`. - -!!!info -You can inspect the exported metrics by following the instructions in -the ["How to inspect the exported metrics"](#how-to-inspect-the-exported-metrics) -section below. -!!! - -Currently, the operator exposes default `kubebuilder` metrics. See -[kubebuilder documentation](https://book.kubebuilder.io/reference/metrics.html) -for more details. - -### Monitoring the operator with Prometheus - -The operator can be monitored using the -[Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator) by defining a -[PodMonitor](https://github.com/prometheus-operator/prometheus-operator/blob/v0.47.1/Documentation/api.md#podmonitor) -pointing to the operator pod(s), as follows (note it's applied in the same -namespace as the operator): - -```yaml -kubectl -n postgresql-operator-system apply -f - < - tls.key: -``` - -Next, update the operator deployment to mount the secret and configure the -environment variable: - -```yaml -spec: - template: - spec: - containers: - - name: manager - env: - - name: METRICS_CERT_DIR - value: /run/secrets/k8s.enterprisedb.io/metrics - volumeMounts: - - mountPath: /run/secrets/k8s.enterprisedb.io/metrics - name: metrics-certificates - readOnly: true - volumes: - - name: metrics-certificates - secret: - secretName: postgresql-operator-metrics-cert - defaultMode: 420 -``` - -!!!note -When `METRICS_CERT_DIR` is set, the operator automatically enables TLS for -the metrics server. You must also update your PodMonitor configuration to -use the `https` scheme. -!!! - -Example `PodMonitor` configuration with TLS enabled: - -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: PodMonitor -metadata: - name: postgresql-operator-controller-manager - namespace: postgresql-operator-system -spec: - selector: - matchLabels: - app.kubernetes.io/name: cloud-native-postgresql - podMetricsEndpoints: - - port: metrics - scheme: https - tlsConfig: - insecureSkipVerify: true # or configure proper CA validation -``` - -## How to inspect the exported metrics - -In this section we provide basic instructions on how to inspect -the metrics exported by a specific PostgreSQL instance manager (primary -or replica) or the operator. - -!!!note -In the examples below we assume we are working in the default namespace, and -with the operator installed in the `postgresql-operator-system` namespace. -Please adapt to your use case. -!!! - -### Using port forwarding - -The simplest way to inspect the metrics is to port-forward the metrics ports -of the pods involved. - -For example, to inspect the metrics on the `-1` instance of `cluster-example`, -we port-forward the 9187 port: - -```sh -kubectl port-forward cluster-example-1 9187:9187 -``` - -With port-forwarding active, the metrics can be inspected easily, for -example on a web browser, using HTTP or HTTPS depending on the configuration, -with address: `localhost:9187/metrics`. - -The operator pod also exports metrics, on port 8080. Similarly to instances, we -port-forward the operator pod, which is located in the operator namespace: - -```sh -kubectl -n postgresql-operator-system port-forward pod/ 8080:8080 -``` - -With port forwarding active, the metrics are easily viewable on a browser at -[`localhost:8080/metrics`](http://localhost:8080/metrics). - -### Using curl - -Create the `curl` pod with the following command: - -```yaml -kubectl apply -f - <:9187/metrics -``` - -For example, if your PostgreSQL cluster is called `cluster-example` and -you want to retrieve the exported metrics of the first pod in the cluster, -you can run the following command to programmatically get the IP of -that pod: - -```shell -POD_IP=$(kubectl get pod cluster-example-1 --template '{{.status.podIP}}') -``` - -And then run: - -```shell -kubectl exec -ti curl -- curl -s ${POD_IP}:9187/metrics -``` - -If you enabled TLS metrics, run instead: - -```shell -kubectl exec -ti curl -- curl -sk https://${POD_IP}:9187/metrics -``` - -To access the metrics of the operator, you need to point -to the pod where the operator is running, and use TCP port 8080 as target. - -When you're done inspecting metrics, please remember to delete the `curl` pod: - -```shell -kubectl delete -f curl.yaml -``` - -## Auxiliary resources - -!!!info Important -These resources are provided for illustration and experimentation, and do -not represent any kind of recommendation for your production system -!!! - -In the [`doc/src/samples/monitoring/`](https://github.com/EnterpriseDB/docs/tree/main/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring) -directory you will find a series of sample files for observability. -Please refer to [Part 4 of the quickstart](quickstart.md#part-4-monitor-clusters-with-prometheus-and-grafana) -section for context: - -- `kube-stack-config.yaml`: a configuration file for the kube-stack helm chart - installation. It ensures that Prometheus listens for all PodMonitor resources. -- `prometheusrule.yaml`: a `PrometheusRule` with alerts for {{name.ln}}. - NOTE: this does not include inter-operation with notification services. Please refer - to the [Prometheus documentation](https://prometheus.io/docs/alerting/latest/alertmanager/). -- `podmonitor.yaml`: a `PodMonitor` for the {{name.ln}} Operator deployment. - -In addition, we provide the "raw" sources for the Prometheus alert rules in the -`alerts.yaml` file. - -A Grafana dashboard for {{name.ln}} clusters and operator, is kept in the -dedicated repository [`cloudnative-pg/grafana-dashboards`](https://github.com/cloudnative-pg/grafana-dashboards/tree/main) -as a dashboard JSON configuration: -[`grafana-dashboard.json`](https://github.com/cloudnative-pg/grafana-dashboards/blob/main/charts/cluster/grafana-dashboard.json). -The file can be downloaded, and imported into Grafana -(menus: Dashboard > New > Import). - -For a general reference on the settings available on `kube-prometheus-stack`, -you can execute `helm show values prometheus-community/kube-prometheus-stack`. -Please refer to the -[kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack) -page for more detail. - -## Monitoring on OpenShift - -Starting on Openshift 4.6 there is a complete monitoring stack called -["Monitoring for user-defined projects"](https://docs.openshift.com/container-platform/4.6/monitoring/enabling-monitoring-for-user-defined-projects.html) -which can be enabled by cluster administrators. Cloud Native PostgreSQL will -automatically create a `PodMonitor` object if the option -`spec.monitoring.enablePodMonitor` of the `Cluster` definition is set to -`true`. - -To enable cluster wide `user-defined` monitoring you must first create a -`ConfigMap` with the name `cluster-monitoring-config` in the -`openshift-monitoring` namespace/project with the following content: - -```yaml -apiVersion: v1 -kind: ConfigMap -metadata: - name: cluster-monitoring-config - namespace: openshift-monitoring -data: - config.yaml: | - enableUserWorkload: true -``` - -If the `ConfigMap` already exists, just add the variable `enableUserWorkload: true`. - -!!!info Important -This will enable the monitoring for the whole cluster, if it is needed only -for one namespace/project please refer to the official Red Hat documentation or -talk with your cluster administrator. -!!! - -After that, just create the proper PodMonitor in the namespace/project with -something similar to this: - -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: PodMonitor -metadata: - name: cluster-sample -spec: - selector: - matchLabels: - postgresql: cluster-sample - podMetricsEndpoints: - - port: metrics -``` - -!!!note -We currently don’t use `ServiceMonitor` because our service doesn’t define -a port pointing to the metrics. If we added a metric port this could expose -sensitive data. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/networking.mdx b/product_docs/docs/postgres_for_kubernetes/preview/networking.mdx deleted file mode 100644 index 114a1eb7992..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/networking.mdx +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: 'Networking' -originalFilePath: 'src/networking.md' ---- - - - -{{name.ln}} assumes the underlying Kubernetes cluster has the required -connectivity already set up. -Networking on Kubernetes is an important and extended topic; please refer to -the [Kubernetes documentation](https://kubernetes.io/docs/concepts/services-networking/) for further information. - -If you're following the quickstart guide to install {{name.ln}} on a local KinD or K3d cluster, you should not encounter any networking issues as neither -platform will add any networking restrictions by default. - -However, when deploying {{name.ln}} on existing infrastructure, networking -restrictions might be in place that could impair the communication of the -operator with PostgreSQL clusters. -Specifically, existing [Network Policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) -might restrict certain types of traffic. - -Or, you might be interested in adding network policies in your environment for -increased security. -As mentioned in the [security document](security.md), please ensure the operator can reach every cluster pod on ports 8000 and 5432, and that pods can connect to each other. - -## Cross-namespace network policy for the operator - -Following the quickstart guide or using helm chart for deployment will install the operator in -a dedicated namespace (`postgresql-operator-system` by default). -We recommend that you create clusters in a different namespace. - -The operator *must* be able to connect to cluster pods. -This might be precluded if there is a `NetworkPolicy` restricting -cross-namespace traffic. - -For example, the -[kubernetes guide on network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) -contains an example policy denying all ingress traffic by default. - -If your local kubernetes setup has this kind of restrictive network policy, you -will need to create a `NetworkPolicy` to explicitly allow connection from the -operator namespace and pod to the cluster namespace and pods. You can find an example in the -[`networkpolicy-example.yaml`](../samples/networkpolicy-example.yaml) file in this repository. -Please note, you'll need to adjust the cluster name and cluster namespace to -match your specific setup, and also the operator namespace if it is not -the default namespace. - -## Cross-cluster networking - -While [bootstrapping](bootstrap.md) from another cluster or when using the `externalClusters` section, -ensure connectivity among all clusters, object stores, and namespaces involved. - -Again, we refer you to the [Kubernetes documentation](https://kubernetes.io/docs/concepts/services-networking/) -for setup information. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/object_stores.mdx b/product_docs/docs/postgres_for_kubernetes/preview/object_stores.mdx deleted file mode 100644 index 5ab5b7c71f3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/object_stores.mdx +++ /dev/null @@ -1,384 +0,0 @@ ---- -title: 'Appendix C - Common object stores for backups' -originalFilePath: 'src/appendixes/object_stores.md' ---- - - - -!!!warning -As of {{name.ln}} 1.26, **native Barman Cloud support is deprecated** in -favor of the **Barman Cloud Plugin**. While the native integration remains -functional for now, we strongly recommend beginning a gradual migration to -the plugin-based interface after appropriate testing. The Barman Cloud -Plugin documentation describes -[how to use common object stores](https://cloudnative-pg.io/plugin-barman-cloud/docs/object_stores/). -!!! - -You can store the [backup](backup.md) files in any service that is supported -by the Barman Cloud infrastructure. That is: - -- [Amazon S3](#aws-s3) -- [Microsoft Azure Blob Storage](#azure-blob-storage) -- [Google Cloud Storage](#google-cloud-storage) - -You can also use any compatible implementation of the supported services. - -The required setup depends on the chosen storage provider and is -discussed in the following sections. - -!!!note Authentication Methods -{{name.ln}} does not independently test all authentication methods -supported by `barman-cloud`. {{name.ln}}' responsibility is limited to passing -the provided credentials to `barman-cloud`, which then handles authentication -according to its own implementation. Users should refer to the -[Barman Cloud documentation](https://docs.pgbarman.org/release/latest/) to -verify that their chosen authentication method is supported and properly -configured. -!!! - -## AWS S3 - -[AWS Simple Storage Service (S3)](https://aws.amazon.com/s3/) is -a very popular object storage service offered by Amazon. - -As far as {{name.ln}} backup is concerned, you can define the permissions to -store backups in S3 buckets in two ways: - -- If {{name.ln}} is running in EKS. you may want to use the - [IRSA authentication method](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) -- Alternatively, you can use the `ACCESS_KEY_ID` and `ACCESS_SECRET_KEY` credentials - -### AWS Access key - -You will need the following information about your environment: - -- `ACCESS_KEY_ID`: the ID of the access key that will be used - to upload files into S3 - -- `ACCESS_SECRET_KEY`: the secret part of the access key mentioned above - -- `ACCESS_SESSION_TOKEN`: the optional session token, in case it is required - -The access key used must have permission to upload files into -the bucket. Given that, you must create a Kubernetes secret with the -credentials, and you can do that with the following command: - -```sh -kubectl create secret generic aws-creds \ - --from-literal=ACCESS_KEY_ID= \ - --from-literal=ACCESS_SECRET_KEY= -# --from-literal=ACCESS_SESSION_TOKEN= # if required -``` - -The credentials will be stored inside Kubernetes and will be encrypted -if encryption at rest is configured in your installation. - -Once that secret has been created, you can configure your cluster like in -the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - destinationPath: "" - s3Credentials: - accessKeyId: - name: aws-creds - key: ACCESS_KEY_ID - secretAccessKey: - name: aws-creds - key: ACCESS_SECRET_KEY -``` - -The destination path can be any URL pointing to a folder where -the instance can upload the WAL files, e.g. -`s3://BUCKET_NAME/path/to/folder`. - -### IAM Role for Service Account (IRSA) - -In order to use IRSA you need to set an `annotation` in the `ServiceAccount` of -the Postgres cluster. - -We can configure {{name.ln}} to inject them using the `serviceAccountTemplate` -stanza: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: -[...] -spec: - serviceAccountTemplate: - metadata: - annotations: - eks.amazonaws.com/role-arn: arn:[...] - [...] -``` - -### S3 lifecycle policy - -Barman Cloud writes objects to S3, then does not update them until they are -deleted by the Barman Cloud retention policy. A recommended approach for an S3 -lifecycle policy is to expire the current version of objects a few days longer -than the Barman retention policy, enable object versioning, and expire -non-current versions after a number of days. Such a policy protects against -accidental deletion, and also allows for restricting permissions to the -{{name.ln}} workload so that it may delete objects from S3 without granting -permissions to permanently delete objects. - -### Other S3-compatible Object Storages providers - -In case you're using S3-compatible object storage, like **MinIO** or -**Linode Object Storage**, you can specify an endpoint instead of using the -default S3 one. - -In this example, it will use the `bucket` of **Linode** in the region -`us-east1`. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - destinationPath: "s3://bucket/" - endpointURL: "https://us-east1.linodeobjects.com" - s3Credentials: - [...] -``` - -In case you're using **Digital Ocean Spaces**, you will have to use the Path-style syntax. -In this example, it will use the `bucket` from **Digital Ocean Spaces** in the region `SFO3`. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - destinationPath: "s3://[your-bucket-name]/[your-backup-folder]/" - endpointURL: "https://sfo3.digitaloceanspaces.com" - s3Credentials: - [...] -``` - -### Using Object Storage with a private CA - -Suppose you configure an Object Storage provider which uses a certificate -signed with a private CA, for example when using OpenShift or MinIO via HTTPS. In that case, -you need to set the option `endpointCA` inside `barmanObjectStore` referring -to a secret containing the CA bundle, so that Barman can verify the certificate -correctly. -You can find instructions on creating a secret using your cert files in the -[certificates](certificates.md#example) document. -Once you have created the secret, you can populate the `endpointCA` as in the -following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - [...] - backup: - barmanObjectStore: - endpointURL: - endpointCA: - name: my-ca-secret - key: ca.crt -``` - -!!!note -If you want ConfigMaps and Secrets to be **automatically** reloaded by instances, you can -add a label with key `k8s.enterprisedb.io/reload` to the Secrets/ConfigMaps. Otherwise, you will have to reload -the instances using the `kubectl cnp reload` subcommand. -!!! - -## Azure Blob Storage - -[Azure Blob Storage](https://azure.microsoft.com/en-us/services/storage/blobs/) is the -object storage service provided by Microsoft. - -{{name.ln}} supports the following authentication methods for Azure Blob Storage: - -- [Connection String](https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string#configure-a-connection-string-for-an-azure-storage-account) -- Storage Account Name + [Storage Account Access Key](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage) -- Storage Account Name + [Storage Account SAS Token](https://docs.microsoft.com/en-us/azure/storage/blobs/sas-service-create) -- [Azure AD Managed Identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview) -- [Default Azure Credentials](https://learn.microsoft.com/en-us/python/api/azure-identity/azure.identity.defaultazurecredential?view=azure-python) - -Using **Azure AD Managed Identity**, you can avoid saving the credentials into a Kubernetes Secret, -and have a Cluster configuration adding the `inheritFromAzureAD` as follows: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - destinationPath: "" - azureCredentials: - inheritFromAzureAD: true -``` - -Alternatively, you can use the **Default Azure Credentials** authentication mechanism, which provides -a seamless authentication experience by supporting multiple authentication methods including environment -variables, managed identities, and Azure CLI credentials. Add the `useDefaultAzureCredentials` flag -as follows: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - destinationPath: "" - azureCredentials: - useDefaultAzureCredentials: true -``` - -On the other side, using both **Storage account access key** or **Storage account SAS Token**, -the credentials need to be stored inside a Kubernetes Secret, adding data entries only when -needed. The following command performs that: - -```sh -kubectl create secret generic azure-creds \ - --from-literal=AZURE_STORAGE_ACCOUNT= \ - --from-literal=AZURE_STORAGE_KEY= \ - --from-literal=AZURE_STORAGE_SAS_TOKEN= \ - --from-literal=AZURE_STORAGE_CONNECTION_STRING= -``` - -The credentials will be encrypted at rest, if this feature is enabled in the used -Kubernetes cluster. - -Given the previous secret, the provided credentials can be injected inside the cluster -configuration: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - destinationPath: "" - azureCredentials: - connectionString: - name: azure-creds - key: AZURE_CONNECTION_STRING - storageAccount: - name: azure-creds - key: AZURE_STORAGE_ACCOUNT - storageKey: - name: azure-creds - key: AZURE_STORAGE_KEY - storageSasToken: - name: azure-creds - key: AZURE_STORAGE_SAS_TOKEN -``` - -When using the Azure Blob Storage, the `destinationPath` fulfills the following -structure: - -```sh -://..core.windows.net/ -``` - -where `` is `/`. The **account name**, -which is also called **storage account name**, is included in the used host name. - -### Other Azure Blob Storage compatible providers - -If you are using a different implementation of the Azure Blob Storage APIs, -the `destinationPath` will have the following structure: - -```sh -://:// -``` - -In that case, `` is the first component of the path. - -This is required if you are testing the Azure support via the Azure Storage -Emulator or [Azurite](https://github.com/Azure/Azurite). - -## Google Cloud Storage - -Currently, the {{name.ln}} operator supports two authentication methods for -[Google Cloud Storage](https://cloud.google.com/storage/): - -- the first one assumes that the pod is running inside a Google Kubernetes Engine cluster -- the second one leverages the environment variable `GOOGLE_APPLICATION_CREDENTIALS` - -### Running inside Google Kubernetes Engine - -When running inside Google Kubernetes Engine you can configure your backups to -simply rely on [Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity), -without having to set any credentials. In particular, you need to: - -- set `.spec.backup.barmanObjectStore.googleCredentials.gkeEnvironment` to `true` -- set the `iam.gke.io/gcp-service-account` annotation in the `serviceAccountTemplate` stanza - -Please use the following example as a reference: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - [...] - backup: - barmanObjectStore: - destinationPath: "gs://" - googleCredentials: - gkeEnvironment: true - - serviceAccountTemplate: - metadata: - annotations: - iam.gke.io/gcp-service-account: [...].iam.gserviceaccount.com - [...] -``` - -### Using authentication - -Following the [instruction from Google](https://cloud.google.com/docs/authentication/getting-started) -you will get a JSON file that contains all the required information to authenticate. - -The content of the JSON file must be provided using a `Secret` that can be created -with the following command: - -```shell -kubectl create secret generic backup-creds --from-file=gcsCredentials=gcs_credentials_file.json -``` - -This will create the `Secret` with the name `backup-creds` to be used in the yaml file like this: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - backup: - barmanObjectStore: - destinationPath: "gs://" - googleCredentials: - applicationCredentials: - name: backup-creds - key: gcsCredentials -``` - -Now the operator will use the credentials to authenticate against Google Cloud Storage. - -!!!info Important -This way of authentication will create a JSON file inside the container with all the needed -information to access your Google Cloud Storage bucket, meaning that if someone gets access to the pod -will also have write permissions to the bucket. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/openshift.mdx b/product_docs/docs/postgres_for_kubernetes/preview/openshift.mdx deleted file mode 100644 index 4d0bdee91e3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/openshift.mdx +++ /dev/null @@ -1,1099 +0,0 @@ ---- -title: 'Red Hat OpenShift' -originalFilePath: 'src/openshift.md' ---- - -{{name.ln}} is certified to run on -[Red Hat OpenShift Container Platform (OCP) version 4.x](https://www.openshift.com/products/container-platform) -and is available directly from the -[Red Hat Catalog](https://catalog.redhat.com/software/operators/detail/5fb41c88abd2a6f7dbe1b37b). - -The goal of this section is to help you decide the best installation method for -{{name.ln}} based on your organizations' security and access -control policies. - -The first and critical step is to design the [architecture](#architecture) of -your PostgreSQL clusters in your OpenShift environment. - -Once the architecture is clear, you can proceed with the installation. {{name.ln}} can be installed and managed via: - -- [OpenShift web console](#installation-via-web-console) -- [OpenShift command-line interface (CLI)](#installation-via-the-oc-cli) called `oc`, for full control - -{{name.ln}} supports all available install modes defined by -OpenShift: - -- cluster-wide, in all namespaces -- local, in a single namespace -- local, watching multiple namespaces (only available using `oc`) - -!!!note - -A project is a Kubernetes namespace with additional annotations, and is the -central vehicle by which access to resources for regular users is managed. -!!! - -In most cases, the default cluster-wide installation of {{name.ln}} -is the recommended one, with either central management of PostgreSQL clusters -or delegated management (limited to specific users/projects according to RBAC -definitions - see ["Important OpenShift concepts"](#important-openshift-concepts) -and ["Users and Permissions"](#users-and-permissions) below). - -!!!info Important - -Both the installation and upgrade processes require access to an OpenShift -Container Platform cluster using an account with `cluster-admin` permissions. -From ["Default cluster roles"](https://docs.openshift.com/container-platform/4.16/authentication/using-rbac.html#default-roles_using-rbac), -a `cluster-admin` is *"a super-user that can perform any action in any -project. When bound to a user with a local binding, they have full control over -quota and every action on every resource in the project"*. -!!! - -## Architecture - -The same concepts that have been included in the generic -[Kubernetes/PostgreSQL architecture page](architecture.md) -apply for OpenShift as well. - -Here as well, the critical factor is the number of availability -zones or data centers for your OpenShift environment. - -As outlined in the -["Disaster Recovery Strategies for Applications Running on OpenShift"](https://cloud.redhat.com/blog/disaster-recovery-strategies-for-applications-running-on-openshift) -blog article written by Raffaele Spazzoli back in 2020 about stateful -applications, in order to fully exploit {{name.ln}}, you need -to plan, design and implement an OpenShift cluster spanning 3 or more -availability zones. While this doesn't pose an issue in most of the public -cloud provider deployments, it is definitely a challenge in on-premise -scenarios. - -If your OpenShift cluster has only **one availability zone**, the zone is your -Single Point of Failure (SPoF) from a High Availability standpoint - provided -that you have wisely adopted a share-nothing architecture, making sure that -your PostgreSQL clusters have at least one standby (two if using synchronous -replication), and that each PostgreSQL instance runs on a different Kubernetes -worker node using different storage. Make sure that continuous backup data is -stored additionally in a storage service outside the OpenShift cluster, -allowing you to perform Disaster Recovery operations beyond your data center. - -Most likely you will have another OpenShift cluster in another data center, -either in the same metropolitan area or in another region, in an active/passive -strategy. You can set up an independent ["Replica cluster"](replica_cluster.md), -with the understanding that this is primarily a Disaster Recovery solution - very -effective but with some limitations that require manual intervention, as -explained in the feature page. The same solution can be applied to additional -OpenShift clusters, even in a cascading manner. - -On the other hand, if your OpenShift cluster spans **multiple availability -zones** in a region, you can fully leverage the capabilities of the operator for -resilience and self-healing, and the region can become your SPoF, i.e. -it would take a full region outage to bring down your cluster. -Moreover, you can take advantage of multiple OpenShift clusters in different -regions by setting up replica clusters, as previously mentioned. - -### Reserving Nodes for PostgreSQL Workloads - -For optimal performance and resource allocation in your PostgreSQL database -operations, it is highly recommended to isolate PostgreSQL workloads by -dedicating specific worker nodes solely to `postgres` in production. This is -particularly crucial whether you're operating in a single availability zone or -a multi-availability zone environment. - -A worker node in OpenShift that is dedicated to running PostgreSQL workloads is -commonly referred to as a **Postgres node** or `postgres` node. - -This dedicated approach ensures that your PostgreSQL workloads are not -competing for resources with other applications, leading to enhanced stability -and performance. - -For further details, please refer to the ["Reserving Nodes for PostgreSQL Workloads" section within the broader "Architecture"](architecture.md#reserving-nodes-for-postgresql-workloads) -documentation. The primary difference when working in OpenShift involves how -labels and taints are applied to the nodes, as described below. - -To label a node as a `postgres` node, execute the following command: - -```sh -oc label node node-role.kubernetes.io/postgres= -``` - -To apply a `postgres` taint to a node, use the following command: - -```sh -oc adm taint node node-role.kubernetes.io/postgres=:NoSchedule -``` - -By correctly labeling and tainting your nodes, you ensure that only PostgreSQL -workloads are scheduled on these dedicated nodes via affinity and tolerations, -reinforcing the stability and performance of your database environment. - -## Important OpenShift concepts - -To understand how the {{name.ln}} operator fits in an OpenShift environment, -you must familiarize yourself with the following Kubernetes-related topics: - -- Operators -- Authentication -- Authorization via Role-based Access Control (RBAC) -- Service Accounts and Users -- Rules, Roles and Bindings -- Cluster RBAC vs local RBAC through projects - -This is especially true in case you are not comfortable with the elevated -permissions required by the default cluster-wide installation of the operator. - -We have also selected the diagram below from the OpenShift documentation, as it -clearly illustrates the relationships between cluster roles, local roles, -cluster role bindings, local role bindings, users, groups and service accounts. - -![OpenShift Cluster Roles](./images/openshift/openshift-rbac.png) -The ["Predefined RBAC objects" section](#predefined-rbac-objects) -below contains important information about how {{name.ln}} adheres -to Kubernetes and OpenShift RBAC implementation, covering default installed -cluster roles, roles, service accounts. - -If you are familiar with the above concepts, you can proceed directly to the -selected installation method. Otherwise, we recommend that you read the -following resources taken from the OpenShift documentation and the Red Hat -blog: - -- ["Operator Lifecycle Manager (OLM) concepts and resources"](https://docs.openshift.com/container-platform/4.16/operators/understanding/olm/olm-understanding-olm.html) -- ["Understanding authentication"](https://docs.openshift.com/container-platform/4.16/authentication/understanding-authentication.html) -- ["Role-based access control (RBAC)"](https://docs.openshift.com/container-platform/4.16/authentication/using-rbac.html), - covering rules, roles and bindings for authorization, as well as cluster RBAC vs local RBAC through projects -- ["Default project service accounts and roles"](https://docs.openshift.com/container-platform/4.16/authentication/using-service-accounts-in-applications.html#service-accounts-default_using-service-accounts) -- ["With Kubernetes Operators comes great responsibility" blog article](https://www.redhat.com/en/blog/kubernetes-operators-comes-great-responsibility) - -### Cluster Service Version (CSV) - -Technically, the operator is designed to run in OpenShift via the Operator -Lifecycle Manager (OLM), according to the Cluster Service Version (CSV) defined -by EDB. - -The CSV is a YAML manifest that defines not only the user interfaces (available -through the web dashboard), but also the RBAC rules required by the operator -and the custom resources defined and owned by the operator (such as the -`Cluster` one, for example). The CSV defines also the available `installModes` -for the operator, namely: `AllNamespaces` (cluster-wide), `SingleNamespace` -(single project), `MultiNamespace` (multi-project), and `OwnNamespace`. - -!!!note There's more ... - -You can find out more about CSVs and install modes by reading -["Operator group membership"](https://docs.openshift.com/container-platform/4.16/operators/understanding/olm/olm-understanding-operatorgroups.html#olm-operatorgroups-membership_olm-understanding-operatorgroups) -and ["Defining cluster service versions (CSVs)"](https://docs.openshift.com/container-platform/4.16/operators/operator_sdk/osdk-generating-csvs.html) -from the OpenShift documentation. -!!! - -### Limitations for multi-tenant management - -Red Hat OpenShift Container Platform provides limited support for -simultaneously installing different variations of an operator on a single -cluster. Like any other operator, {{name.ln}} becomes an extension -of the control plane. As the control plane is shared among all tenants -(projects) of an OpenShift cluster, operators too become shared resources in a -multi-tenant environment. - -Operator Lifecycle Manager (OLM) can install operators multiple times in -different namespaces, with one important limitation: they all need to share the -same API version of the operator. - -For more information, please refer to -["Operator groups"](https://docs.openshift.com/container-platform/4.16/operators/understanding/olm/olm-understanding-operatorgroups.html) -in OpenShift documentation. - -## Channels - -{{name.ln}} is distributed through the following -[OLM channels](https://olm.operatorframework.io/docs/best-practices/channel-naming/), -each serving a distinct purpose: - -- `candidate`: this channel provides early access to the next potential `fast` - release. It includes the latest pre-release versions with new features and - fixes, but is considered experimental and not supported. Use this channel only - for testing and validation purposes—**not in production environments**. Versions in - `candidate` may not appear in other channels if no further updates are - recommended. - -- `fast`: designed for users who want timely access to the latest stable - features and patches. The head of the `fast` channel always points to the - latest **patch release** of the latest **minor release** of EDB Postgres for - Kubernetes. - -- `stable`: similar to `fast`, but restricted to the latest **minor release** - currently under EDB’s Long Term Support (LTS) policy. Designed for users who - require predictable updates and official support while benefiting from ongoing - stability and maintenance. - -- `stable-vX.Y`: tracks the latest patch release within a specific minor - version (e.g., `stable-v1.26`). These channels are ideal for environments - that require version pinning and predictable updates within a stable minor - release. - -The `fast` and `stable` channels may span multiple minor versions, whereas -each `stable-vX.Y` channel is limited to patch updates within a specific minor -release. - -**{{name.ln}}** follow *trunk-based development* and -*continuous delivery* principles. As a result, we generally recommend using the -`fast` channel to stay current with the latest stable improvements and fixes. - -## Installation via web console - -### Ensuring access to EDB private registry - -!!!info Important - -You'll need access to the private EDB repository where both the operator -and operand images are stored. Access requires a valid -[EDB subscription plan](https://www.enterprisedb.com/products/plans-comparison). -Please refer to ["Accessing EDB private image registries"](private_edb_registries.md) for further details. -!!! - -!!!warning CRITICAL WARNING: UPGRADING OPERATORS - -OpenShift users, or any customer attempting an operator upgrade, MUST configure the new unified repository pull secret (docker.enterprisedb.com/k8s) before running the upgrade. If the old, deprecated repository path is still in use during the upgrade process, image pull failure will occur, leading to deployment failure and potential downtime. Follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/) first. -!!! - -The OpenShift install will use pull secrets in order to access the -operand and operator images, which are held in a private repository. - -Once you have credentials to the private repository, you will need to create -a pull secret in the `openshift-operators` namespace, named: - -- `postgresql-operator-pull-secret`, for the {{name.ln}} operator images - -You can create this secret using the `oc create` command by replacing `` with -the repository token for your EDB account, as explained in -[Get your token](/repos/getting_started/get_your_token/). - -```sh -oc create secret docker-registry postgresql-operator-pull-secret \ - -n openshift-operators \ - --docker-server=docker.enterprisedb.com \ - --docker-username=k8s \ - --docker-password="" -``` - -The {{name.ln}} operator can be found in the Red Hat OperatorHub -directly from your OpenShift dashboard. - -1. Navigate in the web console to the `Operators -> OperatorHub` page: - - ![Menu OperatorHub](./images/openshift/operatorhub_1.png) - -1. Scroll in the `Database` section or type a keyword into the `Filter by keyword` - box (in this case, "PostgreSQL") to find the {{name.ln}} - Operator, then select it: - - ![Install OperatorHub](./images/openshift/operatorhub_2.png) - -1. Read the information about the Operator and select `Install`. - -1. The following `Operator installation` page expects you to choose: - - - the installation mode: [cluster-wide](#cluster-wide-installation) or - [single namespace](#single-project-installation) installation - - the update channel (see [the "Channels" section](#channels) for more - information - if unsure, pick `fast`) - - the approval strategy, following the availability on the market place of - a new release of the operator, certified by Red Hat: - - `Automatic`: OLM automatically upgrades the running operator with the - new version - - `Manual`: OpenShift waits for human intervention, by requiring an - approval in the `Installed Operators` section - - !!!info Important - - The process of the operator upgrade is described in the - ["Upgrades" section](installation_upgrade.md#upgrades). - !!! - -!!!info Important - -It is possible to install the operator in a single project -(technically speaking: `OwnNamespace` install mode) multiple times -in the same cluster. There will be an operator installation in every namespace, -with different upgrade policies as long as the API is the same (see -["Limitations for multi-tenant management"](#limitations-for-multi-tenant-management)). -!!! - -!!!note - -If you are running with OpenShift 4.20 or later, OperatorHub has been integrated into the -Software Catalog. In the web console, navigate to `Operators -> Software Catalog` -and select a Project to view the software catalog. -![Menu Software Catalog](./images/openshift/software-catalog.png) -!!! - -Choosing cluster-wide vs local installation of the operator is a critical -turning point. Trying to install the operator globally with an existing local -installation is blocked, by throwing the error below. If you want to proceed -you need to remove every local installation of the operator first. - -![Install failing](./images/openshift/openshift-operatorgroup-error.png) - -### Cluster-wide installation - -With cluster-wide installation, you are asking OpenShift to install the -Operator in the default `openshift-operators` namespace and to make it -available to all the projects in the cluster. This is the default and normally -recommended approach to install {{name.ln}}. - -!!!warning - -This doesn't mean that every user in the OpenShift cluster can use the {{name.ln}} Operator, deploy a `Cluster` object or even see the `Cluster` objects that -are running in their own namespaces. There are some special roles that users must -have in the namespace in order to interact with {{name.ln}}' managed -custom resources - primarily the `Cluster` one. Please refer to the -["Users and Permissions" section below](#users-and-permissions) for details. -!!! - -From the web console, select `All namespaces on the cluster (default)` as -`Installation mode`: - -![Install all namespaces](./images/openshift/openshift-webconsole-allnamespaces.png) - -As a result, the operator will be visible in every namespaces. Otherwise, as with any -other OpenShift operator, check the logs in any pods in the `openshift-operators` -project on the `Workloads → Pods` page that are reporting issues to troubleshoot further. - -!!!info Beware - -By choosing the cluster-wide installation you cannot easily move to a -single project installation at a later time. -!!! - -### Single project installation - -With single project installation, you are asking OpenShift to install the -Operator in a given namespace, and to make it available to that project only. - -!!!warning - -This doesn't mean that every user in the namespace can use the {{name.ln}} Operator, deploy a `Cluster` object or even see the `Cluster` objects that -are running in the namespace. Similarly to the cluster-wide installation mode, -there are some special roles that users must have in the namespace in order to -interact with {{name.ln}}' managed custom resources - primarily the `Cluster` -one. Please refer to the ["Users and Permissions" section below](#users-and-permissions) -for details. -!!! - -From the web console, select `A specific namespace on the cluster` as -`Installation mode`, then pick the target namespace (in our example -`proj-dev`): - -![Install one namespace](./images/openshift/openshift-webconsole-singlenamespace.png) - -As a result, the operator will be visible in the selected namespace only. You -can verify this from the `Installed operators` page: - -![Install one namespace list](./images/openshift/openshift-webconsole-singlenamespace-list.png) - -In case of a problem, from the `Workloads → Pods` page check the logs in any -pods in the selected installation namespace that are reporting issues to -troubleshoot further. - -!!!info Beware - -By choosing the single project installation you cannot easily move to a -cluster-wide installation at a later time. -!!! - -This installation process can be repeated in multiple namespaces in the same -OpenShift cluster, enabling independent installations of the operator in -different projects. In this case, make sure you read -["Limitations for multi-tenant management"](#limitations-for-multi-tenant-management). - -## Installation via the `oc` CLI - -!!!info Important - -Please refer to the ["Installing the OpenShift CLI" section below](#installing-the-openshift-cli-oc) -for information on how to install the `oc` command-line interface. -!!! - -!!!warning CRITICAL WARNING: UPGRADING OPERATORS - -OpenShift users, or any customer attempting an operator upgrade, MUST configure the new unified repository pull secret (docker.enterprisedb.com/k8s) before running the upgrade. If the old, deprecated repository path is still in use during the upgrade process, image pull failure will occur, leading to deployment failure and potential downtime. Follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/) first. -!!! - -Instead of using the OpenShift Container Platform web console, you can install -the {{name.ln}} Operator from the OperatorHub and create a -subscription using the `oc` command-line interface. Through the `oc` CLI you -can install the operator in all namespaces, a single namespace or multiple -namespaces. - -!!!warning - -Multiple namespace installation is currently supported by OpenShift. -However, [definition of multiple target namespaces for an operator may be removed in future versions of OpenShift](https://docs.openshift.com/container-platform/4.16/operators/understanding/olm/olm-understanding-operatorgroups.html#olm-operatorgroups-target-namespace_olm-understanding-operatorgroups). -!!! - -This section primarily covers the installation of the operator in multiple -projects with a simple example, by creating an `OperatorGroup` and a -`Subscription` objects. - -!!!info - -In our example, we will install the operator in the `my-operators` -namespace and make it only available in the `web-staging`, `web-prod`, -`bi-staging`, and `bi-prod` namespaces. Feel free to change the names of the -projects as you like or add/remove some namespaces. -!!! - -1. Check that the `cloud-native-postgresql` operator is available from the - OperatorHub: - - ``` - oc get packagemanifests -n openshift-marketplace cloud-native-postgresql - ``` - -1. Inspect the operator to verify the installation modes (`MultiNamespace` in - particular) and the available channels: - - ``` - oc describe packagemanifests -n openshift-marketplace cloud-native-postgresql - ``` - -1. Create an `OperatorGroup` object in the `my-operators` namespace so that it - targets the `web-staging`, `web-prod`, `bi-staging`, and `bi-prod` namespaces: - - ``` - apiVersion: operators.coreos.com/v1 - kind: OperatorGroup - metadata: - name: cloud-native-postgresql - namespace: my-operators - spec: - targetNamespaces: - - web-staging - - web-prod - - bi-staging - - bi-prod - ``` - - !!!info Important - - Alternatively, you can list namespaces using a label selector, as explained in - ["Target namespace selection"](https://docs.openshift.com/container-platform/4.16/operators/understanding/olm/olm-understanding-operatorgroups.html#olm-operatorgroups-target-namespace_olm-understanding-operatorgroups). - !!! - -1. Create a `Subscription` object in the `my-operators` namespace to subscribe - to the `fast` channel of the `cloud-native-postgresql` operator that is - available in the `certified-operators` source of the `openshift-marketplace` - (as previously located in steps 1 and 2): - - ``` - apiVersion: operators.coreos.com/v1alpha1 - kind: Subscription - metadata: - name: cloud-native-postgresql - namespace: my-operators - spec: - channel: fast - name: cloud-native-postgresql - source: certified-operators - sourceNamespace: openshift-marketplace - ``` - -1. Use `oc apply -f` with the above YAML file definitions for the - `OperatorGroup` and `Subscription` objects. - -The method described in this section can be very powerful in conjunction with -proper `RoleBinding` objects, as it enables mapping {{name.ln}}' -predefined `ClusterRole`s to specific users in selected namespaces. - -!!!info - -The above instructions can also be used for single project binding. The -only difference is the number of specified target namespaces (one) and, -possibly, the namespace of the operator group (ideally, the same as the target -namespace). -!!! - -The result of the above operation can also be verified from the webconsole, as -shown in the image below. - -![Multi namespace installation displayed in the web console](./images/openshift/openshift-webconsole-multinamespace.png) - -### Cluster-wide installation with `oc` - -If you prefer, you can also use `oc` to install the operator globally, by -taking advantage of the default `OperatorGroup` called `global-operators` in -the `openshift-operators` namespace, and create a new `Subscription` object for -the `cloud-native-postgresql` operator in the same namespace: - -```yaml -apiVersion: operators.coreos.com/v1alpha1 -kind: Subscription -metadata: - name: cloud-native-postgresql - namespace: openshift-operators -spec: - channel: fast - name: cloud-native-postgresql - source: certified-operators - sourceNamespace: openshift-marketplace -``` - -Once you run `oc apply -f` with the above YAML file, the operator will be available in all namespaces. - -### Installing the OpenShift CLI (`oc`) - -The `oc` command represents the OpenShift command-line interface (CLI). It is -highly recommended to install it on your system. Below you find a basic set of -instructions to install `oc` from your OpenShift dashboard. - -First, select the question mark at the top right corner of the dashboard: - -![Command Line Tools menu](./images/openshift/oc_installation_screenshot_1.png) - -Then follow the instructions you are given, by downloading the binary that -suits your needs in terms of operating system and architecture: - -![Command Line Tools](./images/openshift/oc_installation_screenshot_2.png) - -!!!note OpenShift CLI - -For more detailed and updated information, please refer to the official -[OpenShift CLI documentation](https://docs.openshift.com/container-platform/4.16/cli_reference/openshift_cli/getting-started-cli.html) -directly maintained by Red Hat. -!!! - -## Predefined RBAC objects - -{{name.ln}} comes with a predefined set of resources that play an -important role when it comes to RBAC policy configuration. - -### Custom Resource Definitions (CRD) - -The {{name.ln}} operator owns the following custom resource -definitions (CRD): - -- `Backup` -- `Cluster` -- `Pooler` -- `ScheduledBackup` -- `ImageCatalog` -- `ClusterImageCatalog` - -You can verify this by running: - -```sh -oc get customresourcedefinitions.apiextensions.k8s.io | grep postgresql -``` - -which returns something similar to: - -```console -backups.postgresql.k8s.enterprisedb.io 20YY-MM-DDTHH:MM:SSZ -clusterimagecatalogs.postgresql.k8s.enterprisedb.io 20YY-MM-DDTHH:MM:SSZ -clusters.postgresql.k8s.enterprisedb.io 20YY-MM-DDTHH:MM:SSZ -imagecatalogs.postgresql.k8s.enterprisedb.io 20YY-MM-DDTHH:MM:SSZ -poolers.postgresql.k8s.enterprisedb.io 20YY-MM-DDTHH:MM:SSZ -scheduledbackups.postgresql.k8s.enterprisedb.io 20YY-MM-DDTHH:MM:SSZ -``` - -### Service accounts - -The namespace where the operator has been installed (by default -`openshift-operators`) contains the following predefined service accounts: -`builder`, `default`, `deployer`, and most importantly -`postgresql-operator-manager` (managed by the CSV). - -!!!info Important - -Service accounts in Kubernetes are namespaced resources. Unless explicitly -authorized, a service account cannot be accessed outside the defined namespace. -!!! - -You can verify this by running: - -```sh -oc get serviceaccounts -n openshift-operators -``` - -which returns something similar to: - -```console -NAME SECRETS AGE -builder 2 ... -default 2 ... -deployer 2 ... -postgresql-operator-manager 2 ... -``` - -The `default` service account is automatically created by Kubernetes and -present in every namespace. The `builder` and `deployer` service accounts are -automatically created by OpenShift (see ["Default project service accounts and roles"](https://docs.openshift.com/container-platform/4.16/authentication/using-service-accounts-in-applications.html#default-service-accounts-and-roles_using-service-accounts)). - -The `postgresql-operator-manager` service account is the one used by the Cloud -Native PostgreSQL operator to work as part of the Kubernetes/OpenShift control -plane in managing PostgreSQL clusters. - -!!!info Important - -Do not delete the `postgresql-operator-manager` ServiceAccount as it can -stop the operator from working. -!!! - -### Cluster roles - -The Operator Lifecycle Manager (OLM) automatically creates a set of cluster -role objects to facilitate role binding definitions and granular implementation -of RBAC policies. Some cluster roles have rules that apply to Custom Resource -Definitions that are part of {{name.ln}}, while others that are -part of the broader Kubernetes/OpenShift realm. - -#### Cluster roles on EDB Postgres® AI for CloudNativePG™ Cluster CRDs - -For [every CRD owned by {{name.ln}}' CSV](#custom-resource-definitions-crd), -OLM deploys some predefined cluster roles that can be used by customer facing -users and service accounts. In particular: - -- a role for the full administration of the resource (`admin` suffix) -- a role to edit the resource (`edit` suffix) -- a role to view the resource (`view` suffix) -- a role to view the actual CRD (`crdview` suffix) - -!!!info Important - -Cluster roles per se are no security threat. They are the recommended way -in OpenShift to define templates for roles to be later "bound" to actual users -in a specific project or globally. Indeed, cluster roles can be used in -conjunction with `ClusterRoleBinding` objects for global permissions or with -`RoleBinding` objects for local permissions. This makes it possible to reuse -cluster roles across multiple projects while enabling customization within -individual projects through local roles. -!!! - -You can verify the list of predefined cluster roles by running: - -```sh -oc get clusterroles | grep postgresql -``` - -which returns something similar to: - -```console -backups.postgresql.k8s.enterprisedb.io-v1-admin YYYY-MM-DDTHH:MM:SSZ -backups.postgresql.k8s.enterprisedb.io-v1-crdview YYYY-MM-DDTHH:MM:SSZ -backups.postgresql.k8s.enterprisedb.io-v1-edit YYYY-MM-DDTHH:MM:SSZ -backups.postgresql.k8s.enterprisedb.io-v1-view YYYY-MM-DDTHH:MM:SSZ -cloud-native-postgresql.VERSION-HASH YYYY-MM-DDTHH:MM:SSZ -clusterimagecatalogs.postgresql.k8s.enterprisedb.io-v1-admin YYYY-MM-DDTHH:MM:SSZ -clusterimagecatalogs.postgresql.k8s.enterprisedb.io-v1-crdview YYYY-MM-DDTHH:MM:SSZ -clusterimagecatalogs.postgresql.k8s.enterprisedb.io-v1-edit YYYY-MM-DDTHH:MM:SSZ -clusterimagecatalogs.postgresql.k8s.enterprisedb.io-v1-view YYYY-MM-DDTHH:MM:SSZ -clusters.postgresql.k8s.enterprisedb.io-v1-admin YYYY-MM-DDTHH:MM:SSZ -clusters.postgresql.k8s.enterprisedb.io-v1-crdview YYYY-MM-DDTHH:MM:SSZ -clusters.postgresql.k8s.enterprisedb.io-v1-edit YYYY-MM-DDTHH:MM:SSZ -clusters.postgresql.k8s.enterprisedb.io-v1-view YYYY-MM-DDTHH:MM:SSZ -imagecatalogs.postgresql.k8s.enterprisedb.io-v1-admin YYYY-MM-DDTHH:MM:SSZ -imagecatalogs.postgresql.k8s.enterprisedb.io-v1-crdview YYYY-MM-DDTHH:MM:SSZ -imagecatalogs.postgresql.k8s.enterprisedb.io-v1-edit YYYY-MM-DDTHH:MM:SSZ -imagecatalogs.postgresql.k8s.enterprisedb.io-v1-view YYYY-MM-DDTHH:MM:SSZ -poolers.postgresql.k8s.enterprisedb.io-v1-admin YYYY-MM-DDTHH:MM:SSZ -poolers.postgresql.k8s.enterprisedb.io-v1-crdview YYYY-MM-DDTHH:MM:SSZ -poolers.postgresql.k8s.enterprisedb.io-v1-edit YYYY-MM-DDTHH:MM:SSZ -poolers.postgresql.k8s.enterprisedb.io-v1-view YYYY-MM-DDTHH:MM:SSZ -scheduledbackups.postgresql.k8s.enterprisedb.io-v1-admin YYYY-MM-DDTHH:MM:SSZ -scheduledbackups.postgresql.k8s.enterprisedb.io-v1-crdview YYYY-MM-DDTHH:MM:SSZ -scheduledbackups.postgresql.k8s.enterprisedb.io-v1-edit YYYY-MM-DDTHH:MM:SSZ -scheduledbackups.postgresql.k8s.enterprisedb.io-v1-view YYYY-MM-DDTHH:MM:SSZ -``` - -You can inspect an actual role as any other Kubernetes resource with the `get` -command. For example: - -```sh -oc get -o yaml clusterrole clusters.postgresql.k8s.enterprisedb.io-v1-admin -``` - -By looking at the relevant skimmed output below, you can notice that the -`clusters.postgresql.k8s.enterprisedb.io-v1-admin` cluster role enables -everything on the `cluster` resource defined by the -`postgresql.k8s.enterprisedb.io` API group: - -```yaml -apiVersion: rbac.authorization.k8s.io/v1 -kind: ClusterRole -metadata: - name: clusters.postgresql.k8s.enterprisedb.io-v1-admin -rules: -- apiGroups: - - postgresql.k8s.enterprisedb.io - resources: - - clusters - verbs: - - '*' -``` - -!!!note There's more ... - -If you are interested in the actual implementation of RBAC by an -OperatorGroup, please refer to the -["OperatorGroup: RBAC" section from the Operator Lifecycle Manager documentation](https://olm.operatorframework.io/docs/concepts/crds/operatorgroup/#rbac). -!!! - -#### Cluster roles on Kubernetes CRDs - -When installing a `Subscription` object in a given namespace (e.g. -`openshift-operators` for cluster-wide installation of the operator), OLM also -creates a cluster role that is used to grant permissions to the -`postgresql-operator-manager` service account that the operator uses. The name -of this cluster role varies, as it depends on the installed version of the -operator and the time of installation. - -You can retrieve it by running the following command: - -```sh -oc get clusterrole --selector=olm.owner.kind=ClusterServiceVersion -``` - -You can then use the name returned by the above query (which should have the -form of `cloud-native-postgresql.VERSION-HASH`) to look at the rules, resources -and verbs via the `describe` command: - -```sh -oc describe clusterrole cloud-native-postgresql.VERSION-HASH -``` - -```console -Name: cloud-native-postgresql.VERSION.HASH -Labels: olm.owner=cloud-native-postgresql.VERSION - olm.owner.kind=ClusterServiceVersion - olm.owner.namespace=openshift-operators - operators.coreos.com/cloud-native-postgresql.openshift-operators= -Annotations: -PolicyRule: - Resources Non-Resource URLs Resource Names Verbs - --------- ----------------- -------------- ----- - configmaps [] [] [create delete get list patch update watch] - secrets [] [] [create delete get list patch update watch] - services [] [] [create delete get list patch update watch] - deployments.apps [] [] [create delete get list patch update watch] - poddisruptionbudgets.policy [] [] [create delete get list patch update watch] - backups.postgresql.k8s.enterprisedb.io [] [] [create delete get list patch update watch] - clusters.postgresql.k8s.enterprisedb.io [] [] [create delete get list patch update watch] - poolers.postgresql.k8s.enterprisedb.io [] [] [create delete get list patch update watch] - scheduledbackups.postgresql.k8s.enterprisedb.io [] [] [create delete get list patch update watch] - persistentvolumeclaims [] [] [create delete get list patch watch] - pods/exec [] [] [create delete get list patch watch] - pods [] [] [create delete get list patch watch] - jobs.batch [] [] [create delete get list patch watch] - podmonitors.monitoring.coreos.com [] [] [create delete get list patch watch] - serviceaccounts [] [] [create get list patch update watch] - rolebindings.rbac.authorization.k8s.io [] [] [create get list patch update watch] - roles.rbac.authorization.k8s.io [] [] [create get list patch update watch] - leases.coordination.k8s.io [] [] [create get update] - events [] [] [create patch] - mutatingwebhookconfigurations.admissionregistration.k8s.io [] [] [get list update] - validatingwebhookconfigurations.admissionregistration.k8s.io [] [] [get list update] - customresourcedefinitions.apiextensions.k8s.io [] [] [get list update] - namespaces [] [] [get list watch] - nodes [] [] [get list watch] - clusters.postgresql.k8s.enterprisedb.io/status [] [] [get patch update watch] - poolers.postgresql.k8s.enterprisedb.io/status [] [] [get patch update watch] - configmaps/status [] [] [get patch update] - secrets/status [] [] [get patch update] - backups.postgresql.k8s.enterprisedb.io/status [] [] [get patch update] - scheduledbackups.postgresql.k8s.enterprisedb.io/status [] [] [get patch update] - pods/status [] [] [get] - clusters.postgresql.k8s.enterprisedb.io/finalizers [] [] [update] - poolers.postgresql.k8s.enterprisedb.io/finalizers [] [] [update] -``` - -!!!info Important - -The above permissions are exclusively reserved for the operator's service -account to interact with the Kubernetes API server. They are not directly -accessible by the users of the operator that interact only with `Cluster`, -`Pooler`, `Backup`, and `ScheduledBackup` resources (see -["Cluster roles on {{name.ln}} CRDs"](#cluster-roles-on-edb-postgres-ai-for-cloudnativepg-cluster-crds)). -!!! - -The operator automates in a declarative way a lot of operations related to -PostgreSQL management that otherwise would require manual and imperative -interventions. Such operations also include security related matters at RBAC -(e.g. service accounts), pod (e.g. security context constraints) and Postgres -levels (e.g. TLS certificates). - -For more information about the reasons why the operator needs these elevated -permissions, please refer to the -["Security / Cluster / RBAC" section](security.md#role-based-access-control-rbac). - -## Users and Permissions - -A very common way to use the {{name.ln}} operator is to rely on the -`cluster-admin` role and manage resources centrally. - -Alternatively, you can use the RBAC framework made available by -Kubernetes/OpenShift, as with any other operator or resources. - -For example, you might be interested in binding the -`clusters.postgresql.k8s.enterprisedb.io-v1-admin` cluster role to specific -groups or users in a specific namespace, as any other cloud native application. -The following example binds that cluster role to a specific user in the -`web-prod` project: - -```yaml -kind: RoleBinding -apiVersion: rbac.authorization.k8s.io/v1 -metadata: - name: web-prod-admin - namespace: web-prod -subjects: - - kind: User - apiGroup: rbac.authorization.k8s.io - name: mario@cioni.org -roleRef: - apiGroup: rbac.authorization.k8s.io - kind: ClusterRole - name: clusters.postgresql.k8s.enterprisedb.io-v1-admin -``` - -The same process can be repeated with any other predefined `ClusterRole`. - -If, on the other hand, you prefer not to use cluster roles, you can create -specific namespaced roles like in this example: - -```yaml -apiVersion: rbac.authorization.k8s.io/v1 -kind: Role -metadata: - name: web-prod-view - namespace: web-prod -rules: -- apiGroups: - - postgresql.k8s.enterprisedb.io - resources: - - clusters - verbs: - - get - - list - - watch -``` - -Then, assign this role to a given user: - -```yaml -apiVersion: rbac.authorization.k8s.io/v1 -kind: RoleBinding -metadata: - name: web-prod-view - namespace: web-prod -roleRef: - apiGroup: rbac.authorization.k8s.io - kind: Role - name: web-prod-view -subjects: -- apiGroup: rbac.authorization.k8s.io - kind: User - name: web-prod-developer1 -``` - -This final example creates a role with administration permissions (`verbs` is -equal to `*`) to all the resources managed by the operator in that namespace -(`web-prod`): - -```yaml -apiVersion: rbac.authorization.k8s.io/v1 -kind: Role -metadata: - name: web-prod-admin - namespace: web-prod -rules: -- apiGroups: - - postgresql.k8s.enterprisedb.io - resources: - - clusters - - backups - - scheduledbackups - - poolers - verbs: - - '*' -``` - -## Pod Security Standards - -{{name.ln}} on OpenShift works with the `restricted-v2` SCC -(`SecurityContextConstraints`). - -Since the operator has been developed with a security focus from the beginning, -in addition to always adhering to the Red Hat Certification process, {{name.ln}} works under the new SCCs introduced in OpenShift 4.11. - -By default, {{name.ln}} will drop all capabilities. This -ensures that during its lifecycle the operator will never make use of any -unsafe capabilities. - -On OpenShift we inherit the `SecurityContext.SeccompProfile` for each Pod from -the OpenShift deployment, which in turn is set by the Pod Security Admission -Controller. - -!!!note - -Even if `nonroot-v2` and `hostnetwork-v2` are qualified as less restricted -SCCs, we don't run tests on them, and therefore we cannot guarantee that these -SCCs will work. That being said, `nonroot-v2` and `hostnetwork-v2` are a subset -of rules in `restricted-v2` so there is no reason to believe that they would -not work. -!!! - -## Customization of the Pooler image - -By default, the `Pooler` resource creates pods having the `pgbouncer` container -that runs with the `docker.enterprisedb.com/k8s/pgbouncer` image. - -!!!note There's more - -For more details about pod customization for the pooler, please refer to -the ["Pod templates"](connection_pooling.md#pod-templates) section in the -connection pooling documentation. -!!! - -You can change the image name from the advanced interface, specifically by -opening the *"Template"* section, then selecting *"Add container"* -under *"Spec > Containers"*: - -![Pooler template](./images/pgbouncer-pooler-template.png) - -Then: - -- set `pgbouncer` as the name of the container (required field in the pod template) -- set the *"Image"* field as desired (see the image below) - -![Pooler image](./images/pgbouncer-pooler-image.png) - -## OADP for Velero - -The {{name.ln}} operator recommends the use of the -[Openshift API for Data Protection](https://github.com/openshift/oadp-operator) operator for managing [Velero](https://velero.io/) -in OpenShift environments. -Specific details about how {{name.ln}} integrates with Velero -can be found in the [Velero section](addons.md#velero) of the Addons documentation. -The [OADP operator](https://docs.openshift.com/container-platform/latest/backup_and_restore/application_backup_and_restore/installing/about-installing-oadp.html) -is a community operator that is not directly supported by EDB. -The OADP operator is not required to use Velero with EDB Postgres but is a -convenient way to install Velero on OpenShift. - -## Monitoring and metrics - -OpenShift includes a [Prometheus](https://prometheus.io) installation out of -the box that can be leveraged for user-defined projects, including {{name.ln}}. - -Grafana integration is out of scope for this guide, as Grafana is no longer -included with OpenShift. - -In this section, we show you how to get started with basic observability, -leveraging the default OpenShift installation. - -Please refer to the [OpenShift monitoring stack overview](https://docs.openshift.com/container-platform/4.16/observability/monitoring/monitoring-overview.html) -for further background. - -Depending on your OpenShift configuration, you may need to do a bit of setup -before you can monitor your {{name.ln}} clusters. - -You will need to have your OpenShift configured to -[enable monitoring for user-defined projects](https://docs.openshift.com/container-platform/4.16/observability/monitoring/enabling-monitoring-for-user-defined-projects.html). - -You should check, perhaps with your OpenShift administrator, if your -installation has the `cluster-monitoring-config` configMap, and if so, -if user workload monitoring is enabled. - -You can check for the presence of this `configMap` (note that it should be in the -`openshift-monitoring` namespace): - -```sh -oc -n openshift-monitoring get configmap cluster-monitoring-config -``` - -To enable user workload monitoring, you might want to `oc apply` or `oc edit` -the configmap to look something like this: - -```yaml -apiVersion: v1 -kind: ConfigMap -metadata: - name: cluster-monitoring-config - namespace: openshift-monitoring -data: - config.yaml: | - enableUserWorkload: true -``` - -After `enableUserWorkload` is set, several monitoring components will be -created in the `openshift-user-workload-monitoring` namespace. - -```sh -$ oc -n openshift-user-workload-monitoring get pod -NAME READY STATUS RESTARTS AGE -prometheus-operator-58768d7cc-28xb5 2/2 Running 0 5h10m -prometheus-user-workload-0 6/6 Running 0 5h10m -prometheus-user-workload-1 6/6 Running 0 5h10m -thanos-ruler-user-workload-0 3/3 Running 0 5h10m -thanos-ruler-user-workload-1 3/3 Running 0 5h10m -``` - -You should now be able to see metrics from any cluster enabling them. - -For example, we can create the following cluster with monitoring on the `foo` -namespace: - -```sh -kubectl apply -n foo -f - <` (e.g. `postgresql-operator-mutating-webhook-configuration-postgresql-operator-team-a` and `postgresql-operator-validating-webhook-configuration-postgresql-operator-team-a`). Use this when running multiple namespaced operator instances on the same cluster to avoid name collisions. The operator does not create the suffixed configurations; you must create them before starting the operator with this flag enabled. If `OPERATOR_NAMESPACE` is not set when this flag is enabled, the operator will refuse to start. Default is `false`. | -| `EXPIRING_CHECK_THRESHOLD` | Determines the threshold, in days, for identifying a certificate as expiring. Default is 7. | -| `EXTERNAL_BACKUP_ADDON_CONFIGURATION` | Configuration for the `external-backup-adapter` add-on. (See ["Customizing the adapter" in Add-ons](addons.md#customizing-the-adapter)) | -| `INCLUDE_PLUGINS` | A comma-separated list of plugins to be always included in the Cluster's reconciliation. | -| `INHERITED_ANNOTATIONS` | List of annotation names that, when defined in a `Cluster` metadata, will be inherited by all the generated resources, including pods | -| `INHERITED_LABELS` | List of label names that, when defined in a `Cluster` metadata, will be inherited by all the generated resources, including pods | -| `INSTANCES_ROLLOUT_DELAY` | The duration (in seconds) to wait between roll-outs of individual PostgreSQL instances within the same cluster during an operator upgrade. The default value is `0`, meaning no delay between upgrades of instances in the same PostgreSQL cluster. | -| `KUBERNETES_CLUSTER_DOMAIN` | Defines the domain suffix for service FQDNs within the Kubernetes cluster. If left unset, it defaults to "cluster.local". | -| `MANAGE_WEBHOOK_CONFIGURATIONS` | When set to `true` (default), the operator injects its CA bundle into the `MutatingWebhookConfiguration` and `ValidatingWebhookConfiguration`. Set to `false` when the CA bundle is injected externally, for example by cert-manager's CA injector or by GitOps. This is independent of the webhook serving certificate, which the operator always manages when it owns its PKI. | -| `METRICS_CERT_DIR` | The directory where TLS certificates for the operator metrics server are stored. When set, enables TLS for the metrics endpoint on port 8080. The directory must contain `tls.crt` and `tls.key` files following standard Kubernetes TLS secret conventions. If not set, the metrics server operates without TLS (default behavior). | -| `MONITORING_QUERIES_CONFIGMAP` | The name of a ConfigMap in the operator's namespace with a set of default queries (to be specified under the key `queries`) to be applied to all created Clusters | -| `MONITORING_QUERIES_SECRET` | The name of a Secret in the operator's namespace with a set of default queries (to be specified under the key `queries`) to be applied to all created Clusters | -| `OPERATOR_IMAGE_NAME` | The name of the operator image used to bootstrap Pods. Defaults to the image specified during installation. | -| `PGBOUNCER_IMAGE_NAME` | The name of the PgBouncer image used by default for new poolers. Defaults to the version specified in the operator. | -| `POSTGRES_IMAGE_NAME` | The name of the PostgreSQL image used by default for new clusters. Defaults to the version specified in the operator. | -| `PULL_SECRET_NAME` | Name of an additional pull secret to be defined in the operator's namespace and to be used to download images | -| `STANDBY_TCP_USER_TIMEOUT` | Defines the [`TCP_USER_TIMEOUT` socket option](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-TCP-USER-TIMEOUT) in milliseconds for replication connections from standby instances to the primary. Default is 5000 (5 seconds). Set to `0` to use the system's default. | -| `WATCH_NAMESPACE` | Specifies the namespace(s) where the operator should watch for resources. Multiple namespaces can be specified separated by commas. If not set, the operator watches all namespaces (cluster-wide mode). | - -Values in `INHERITED_ANNOTATIONS` and `INHERITED_LABELS` support path-like wildcards. For example, the value `example.com/*` will match -both the value `example.com/one` and `example.com/two`. - -When you specify an additional pull secret name using the `PULL_SECRET_NAME` parameter, -the operator will use that secret to create a pull secret for every created PostgreSQL -cluster. That secret will be named `-pull`. - -The namespace where the operator looks for the `PULL_SECRET_NAME` secret is where -you installed the operator. If the operator is not able to find that secret, it -will ignore the configuration parameter. - -## Defining an operator config map - -The example below customizes the behavior of the operator, by defining -a default license key (namely a company key), -the label/annotation names to be inherited by the resources created by -any `Cluster` object that is deployed at a later time, by enabling -[in-place updates for the instance -manager](installation_upgrade.md#in-place-updates-of-the-instance-manager), -and by spreading upgrades. - -```yaml -apiVersion: v1 -kind: ConfigMap -metadata: - name: postgresql-operator-controller-manager-config - namespace: postgresql-operator-system -data: - CLUSTERS_ROLLOUT_DELAY: '60' - ENABLE_INSTANCE_MANAGER_INPLACE_UPDATES: 'true' - EDB_LICENSE_KEY: - INHERITED_ANNOTATIONS: categories - INHERITED_LABELS: environment, workload, app - INSTANCES_ROLLOUT_DELAY: '10' -``` - -## Defining an operator secret - -The example below customizes the behavior of the operator, by defining -a default license key (namely a company key), -the label/annotation names to be inherited by the resources created by -any `Cluster` object that is deployed at a later time, and by enabling -[in-place updates for the instance -manager](installation_upgrade.md#in-place-updates-of-the-instance-manager), -and by spreading upgrades. - -```yaml -apiVersion: v1 -kind: Secret -metadata: - name: postgresql-operator-controller-manager-config - namespace: postgresql-operator-system -type: Opaque -stringData: - CLUSTERS_ROLLOUT_DELAY: '60' - ENABLE_INSTANCE_MANAGER_INPLACE_UPDATES: 'true' - EDB_LICENSE_KEY: - INHERITED_ANNOTATIONS: categories - INHERITED_LABELS: environment, workload, app - INSTANCES_ROLLOUT_DELAY: '10' -``` - -## Restarting the operator to reload configs - -For the change to be effective, you need to recreate the operator pods to -reload the config map. If you have installed the operator on Kubernetes -using the manifest you can do that by issuing: - -```shell -kubectl rollout restart deployment \ - -n postgresql-operator-system \ - postgresql-operator-controller-manager -``` - -Otherwise, If you have installed the operator using OLM, or you are running on -Openshift, run the following command specifying the namespace the operator is -installed in: - -```shell -kubectl delete pods -n [NAMESPACE_NAME_HERE] \ - -l app.kubernetes.io/name=cloud-native-postgresql -``` - -!!!warning -Customizations will be applied only to `Cluster` resources created -after the reload of the operator deployment. -!!! - -Following the above example, if the `Cluster` definition contains a `categories` -annotation and any of the `environment`, `workload`, or `app` labels, these will -be inherited by all the resources generated by the deployment. - -## Defaulting and validation without admission webhooks - -{{name.ln}} normally defaults and validates its resources through admission -webhooks. When the webhooks are not installed, or are temporarily unable to -respond, the operator performs the same defaulting and validation during -reconciliation as a fallback. - -If a resource fails validation, reconciliation stops and the reason is surfaced -on the resource status: `Cluster` and `Backup` move to the `Invalid cluster -definition` and `invalid backup definition` phases respectively, while `Pooler` -and `ScheduledBackup` report it in `.status.error`. The status lists only the -offending field paths; the full validation error, which may contain field -values, is written to the operator logs only. Correcting the spec clears the -error and resumes reconciliation. - -Validation performed during reconciliation honors the `k8s.enterprisedb.io/validation: -disabled` annotation, exactly as the admission webhook does. - -## Profiling tools - -The operator can expose a pprof HTTP server on `localhost:6060`. -To enable it, edit the operator deployment and add the flag -`--pprof-server=true` to the container args: - -```shell -kubectl edit deployment -n postgresql-operator-system postgresql-operator-controller-manager -``` - -Add `--pprof-server=true` to the args list, for example: - -```yaml - containers: - - args: - - controller - - --leader-elect - - --config-map-name=postgresql-operator-controller-manager-config - - --secret-name=postgresql-operator-controller-manager-config - - --log-level=info - - --pprof-server=true # relevant line - command: - - /manager -``` - -After saving, the deployment will roll out and the new pod will -have the pprof server enabled. - -!!!info Important -The pprof server only serves plain HTTP on port `6060`. -!!! - -To access the pprof endpoints from your local machine, use -port-forwarding: - -```shell -kubectl port-forward -n postgresql-operator-system deploy/postgresql-operator-controller-manager 6060 -curl -sS http://localhost:6060/debug/pprof/ -go tool pprof http://localhost:6060/debug/pprof/profile?seconds=30 -``` - -You can also access pprof using the browser at . - -!!!warning -The example above uses `kubectl port-forward` for local testing only. -This is **not** the intended way to expose the feature in production. -Treat pprof as a sensitive debugging interface and never expose it publicly. -If you must access it remotely, secure it with proper network policies and access controls. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/index.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/index.mdx deleted file mode 100644 index 336d903b019..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/index.mdx +++ /dev/null @@ -1,2727 +0,0 @@ ---- -title: API Reference - v1.30.0-rc1 -originalFilePath: src/pg4k.v1.md -navTitle: API Reference -navigation: - - v1.30.0-rc1 - - v1.29.1 - - v1.29.0 - - v1.28.1 - - v1.28.0 - - v1.27.1 - - v1.27.0 - - v1.26.1 - - v1.26.0 - - v1.25.1 - - v1.25.0 - - v1.24.3 - - v1.24.2 - - v1.24.1 - - v1.24.0 - - v1.23.6 - - v1.23.5 - - v1.23.4 - - v1.23.3 - - v1.23.2 - - v1.23.1 - - v1.23.0 - - v1.22.9 - - v1.22.8 - - v1.22.7 - - v1.22.6 - - v1.22.5 - - v1.22.4 - - v1.22.3 - - v1.22.2 - - v1.22.1 - - v1.22.0 - - v1.21.6 - - v1.21.5 - - v1.21.4 - - v1.21.3 - - v1.21.2 - - v1.21.1 - - v1.21.0 - - v1.20.6 - - v1.20.5 - - v1.20.4 - - v1.20.3 - - v1.20.2 - - v1.20.1 - - v1.20.0 - - v1.19.6 - - v1.19.5 - - v1.19.4 - - v1.19.3 - - v1.19.2 - - v1.19.1 - - v1.19.0 - - v1.18.13 - - v1.18.12 - - v1.18.11 - - v1.18.10 - - v1.18.9 - - v1.18.8 - - v1.18.7 - - v1.18.6 - - v1.18.5 - - v1.18.4 - - v1.18.3 - - v1.18.2 - - v1.18.1 - - v1.18.0 - - v1.17.5 - - v1.17.4 - - v1.17.3 - - v1.17.2 - - v1.17.1 - - v1.17.0 - - v1.16.5 - - v1.16.4 - - v1.16.3 - - v1.16.2 - - v1.16.1 - - v1.16.0 - - v1.15.5 - - v1.15.4 - - v1.15.3 - - v1.15.2 - - v1.15.1 - - v1.15.0 - - v1.14.0 - - v1.13.0 - - v1.12.0 - - v1.11.0 - - v1.10.0 - - v1.9.2 - - v1.9.1 - - v1.9.0 - - v1.8.0 - - v1.7.1 - - v1.7.0 - - v1.6.0 - - v1.5.1 - - v1.5.0 - - v1.4.0 - - v1.3.0 - - v1.2.1 - - v1.2.0 - - v1.1.0 - - v1.0.0 - - v0.8.0 - - v0.7.0 - - v0.6.0 - ---- - -## Packages - -- [postgresql.k8s.enterprisedb.io/v1](#postgresqlk8senterprisedbiov1) - -## postgresql.k8s.enterprisedb.io/v1 - -Package v1 contains API Schema definitions for the postgresql v1 API group - -### Resource Types - -- [Backup](#backup) -- [Cluster](#cluster) -- [ClusterImageCatalog](#clusterimagecatalog) -- [Database](#database) -- [DatabaseRole](#databaserole) -- [DatabaseRoleList](#databaserolelist) -- [FailoverQuorum](#failoverquorum) -- [ImageCatalog](#imagecatalog) -- [Pooler](#pooler) -- [Publication](#publication) -- [ScheduledBackup](#scheduledbackup) -- [Subscription](#subscription) - -#### AffinityConfiguration - -AffinityConfiguration contains the info we need to create the -affinity rules for Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `enablePodAntiAffinity` *boolean* | Activates anti-affinity for the pods. The operator will define pods
anti-affinity unless this field is explicitly set to false | | | | -| `topologyKey` *string* | TopologyKey to use for anti-affinity configuration. See k8s documentation
for more info on that | | | | -| `nodeSelector` *object (keys:string, values:string)* | NodeSelector is map of key-value pairs used to define the nodes on which
the pods can run.
More info: | | | | -| `nodeAffinity` *[NodeAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#nodeaffinity-v1-core)* | NodeAffinity describes node affinity scheduling rules for the pod.
More info: | | | | -| `tolerations` *[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#toleration-v1-core) array* | 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: | | | | -| `podAntiAffinityType` *string* | 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:
| | | | -| `additionalPodAntiAffinity` *[PodAntiAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podantiaffinity-v1-core)* | 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` *[PodAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podaffinity-v1-core)* | AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods. | | | | - -#### AvailableArchitecture - -AvailableArchitecture represents the state of a cluster's architecture - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------- | ------------------------------------------------- | -------- | ------- | ---------- | -| `goArch` *string* | GoArch is the name of the executable architecture | True | | | -| `hash` *string* | Hash is the hash of the executable | True | | | - -#### Backup - -A Backup resource is a request for a PostgreSQL backup by the user. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Backup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[BackupSpec](#backupspec)* | Specification of the desired behavior of the backup.
More info: | True | | | -| `status` *[BackupStatus](#backupstatus)* | Most recently observed status of the backup. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### BackupConfiguration - -BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `volumeSnapshot` *[VolumeSnapshotConfiguration](#volumesnapshotconfiguration)* | VolumeSnapshot provides the configuration for the execution of volume snapshot backups. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `retentionPolicy` *string* | 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. | | | Pattern: `^[1-9][0-9]*[dwm]$`
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| - -#### BackupMethod - -*Underlying type:* *string* - -BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance - -*Appears in:* - -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [ClusterStatus](#clusterstatus) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | -| ------------------- | -------------------------------------------------------------------------------------------- | -| `volumeSnapshot` | BackupMethodVolumeSnapshot means using the volume snapshot
Kubernetes feature
| -| `barmanObjectStore` | BackupMethodBarmanObjectStore means using barman to backup the
PostgreSQL cluster
| -| `plugin` | BackupMethodPlugin means that this backup should be handled by
a plugin
| - -#### BackupPhase - -*Underlying type:* *string* - -BackupPhase is the phase of the backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -#### BackupPluginConfiguration - -BackupPluginConfiguration contains the backup configuration used by -the backup plugin - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin managing this backup | True | | | -| `parameters` *object (keys:string, values:string)* | Parameters are the configuration parameters passed to the backup
plugin for this backup | | | | - -#### BackupSnapshotElementStatus - -BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup - -*Appears in:* - -- [BackupSnapshotStatus](#backupsnapshotstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the snapshot resource name | True | | | -| `type` *string* | Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE | True | | | -| `tablespaceName` *string* | TablespaceName is the name of the snapshotted tablespace. Only set
when type is PG_TABLESPACE | | | | - -#### BackupSnapshotStatus - -BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `elements` *[BackupSnapshotElementStatus](#backupsnapshotelementstatus) array* | The elements list, populated with the gathered volume snapshots | | | | - -#### BackupSource - -BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name of the referent. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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 - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### BackupStatus - -BackupStatus defines the observed state of Backup - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `googleCredentials` *[GoogleCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#GoogleCredentials)* | The credentials to use to upload data to Google Cloud Storage | | | | -| `s3Credentials` *[S3Credentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#S3Credentials)* | The credentials to use to upload data to S3 | | | | -| `azureCredentials` *[AzureCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#AzureCredentials)* | The credentials to use to upload data to Azure Blob Storage | | | | -| `majorVersion` *integer* | The PostgreSQL major version that was running when the
backup was taken. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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` *string* | Endpoint to be used to upload data to the cloud,
overriding the automatic endpoint discovery | | | | -| `destinationPath` *string* | 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. | | | | -| `serverName` *string* | The server name on S3, the cluster name is used if this
parameter is omitted | | | | -| `encryption` *string* | Encryption method required to S3 API | | | | -| `backupId` *string* | The ID of the Barman backup | | | | -| `backupName` *string* | The Name of the Barman backup | | | | -| `phase` *[BackupPhase](#backupphase)* | The last backup status | | | | -| `startedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup execution was started by the backup tool | | | | -| `stoppedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup execution was terminated by the backup tool | | | | -| `reconciliationStartedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup process was started by the operator | | | | -| `reconciliationTerminatedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the reconciliation was terminated by the operator (either successfully or not) | | | | -| `beginWal` *string* | The starting WAL | | | | -| `endWal` *string* | The ending WAL | | | | -| `beginLSN` *string* | The starting xlog | | | | -| `endLSN` *string* | The ending xlog | | | | -| `error` *string* | The detected error | | | | -| `commandOutput` *string* | Unused. Retained for compatibility with old versions. | | | | -| `commandError` *string* | The backup command output in case of error | | | | -| `backupLabelFile` *integer array* | Backup label file content as returned by Postgres in case of online (hot) backups | | | | -| `tablespaceMapFile` *integer array* | Tablespace map file content as returned by Postgres in case of online (hot) backups | | | | -| `instanceID` *[InstanceID](#instanceid)* | Information to identify the instance where the backup has been taken from | | | | -| `snapshotBackupStatus` *[BackupSnapshotStatus](#backupsnapshotstatus)* | Status of the volumeSnapshot backup | | | | -| `method` *[BackupMethod](#backupmethod)* | The backup method being used | | | | -| `online` *boolean* | Whether the backup was online/hot (`true`) or offline/cold (`false`) | | | | -| `pluginMetadata` *object (keys:string, values:string)* | A map containing the plugin metadata | | | | - -#### BackupTarget - -*Underlying type:* *string* - -BackupTarget describes the preferred targets for a backup - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initdb` *[BootstrapInitDB](#bootstrapinitdb)* | Bootstrap the cluster via initdb | | | | -| `recovery` *[BootstrapRecovery](#bootstraprecovery)* | Bootstrap the cluster from a backup | | | | -| `pg_basebackup` *[BootstrapPgBaseBackup](#bootstrappgbasebackup)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | -| `redwood` *boolean* | If we need to enable/disable Redwood compatibility. Requires
EPAS and for EPAS defaults to true | | | | -| `options` *string array* | 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. | | | | -| `dataChecksums` *boolean* | Whether the `-k` option should be passed to initdb,
enabling checksums on data pages (default: `false`) | | | | -| `encoding` *string* | The value to be passed as option `--encoding` for initdb (default:`UTF8`) | | | | -| `localeCollate` *string* | The value to be passed as option `--lc-collate` for initdb (default:`C`) | | | | -| `localeCType` *string* | The value to be passed as option `--lc-ctype` for initdb (default:`C`) | | | | -| `locale` *string* | Sets the default collation order and character classification in the new database. | | | | -| `localeProvider` *string* | This option sets the locale provider for databases created in the new cluster.
Available from PostgreSQL 16. | | | | -| `icuLocale` *string* | Specifies the ICU locale when the ICU provider is used.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Specifies additional collation rules to customize the behavior of the default collation.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Specifies the locale name when the builtin provider is used.
This option requires `localeProvider` to be set to `builtin`.
Available from PostgreSQL 17. | | | | -| `walSegmentSize` *integer* | The value in megabytes (1 to 1024) to be passed to the `--wal-segsize`
option for initdb (default: empty, resulting in PostgreSQL default: 16MB) | | | Maximum: 1024
Minimum: 1
| -| `postInitSQL` *string array* | List of SQL queries to be executed as a superuser in the `postgres`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitApplicationSQL` *string array* | List of SQL queries to be executed as a superuser in the application
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitTemplateSQL` *string array* | List of SQL queries to be executed as a superuser in the `template1`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `import` *[Import](#import)* | Bootstraps the new cluster by importing data from an existing PostgreSQL
instance using logical backup (`pg_dump` and `pg_restore`) | | | | -| `postInitApplicationSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the application database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitTemplateSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `template1` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `postgres` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | - -#### BootstrapPgBaseBackup - -BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ------------------- | -| `source` *string* | The name of the server of which we need to take a physical backup | True | | MinLength: 1
| -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backup` *[BackupSource](#backupsource)* | The backup object containing the physical base backup from which to
initiate the recovery procedure.
Mutually exclusive with `source` and `volumeSnapshots`. | | | | -| `source` *string* | 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`. | | | | -| `volumeSnapshots` *[DataSource](#datasource)* | 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 {{name.ln}}, 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`. | | | | -| `recoveryTarget` *[RecoveryTarget](#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: | | | | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | - -#### CatalogComponentImage - -CatalogComponentImage is a named image entry for a non-PostgreSQL component. - -*Appears in:* - -- [ImageCatalogSpec](#imagecatalogspec) - -| Field | Description | Required | Default | Validation | -| ---------------- | --------------------------------------------------------------- | -------- | ------- | --------------------------------------------------------------------- | -| `key` *string* | Key is the unique identifier for this image within the catalog. | True | | MaxLength: 63
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| -| `image` *string* | Image is the container image reference. | True | | | - -#### CatalogImage - -CatalogImage defines the image and major version - -*Appears in:* - -- [ImageCatalogSpec](#imagecatalogspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------- | -------- | ------- | ------------------ | -| `image` *string* | The image reference | True | | | -| `major` *integer* | The PostgreSQL major version of the image. Must be unique within the catalog. | True | | Minimum: 10
| -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | - -#### CertificatesConfiguration - -CertificatesConfiguration contains the needed configurations to handle server certificates. - -*Appears in:* - -- [CertificatesStatus](#certificatesstatus) -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | - -#### CertificatesStatus - -CertificatesStatus contains configuration certificates and related expiration dates. - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | -| `expirations` *object (keys:string, values:string)* | Expiration dates for all certificates. | | | | - -#### ClientCertificateConfiguration - -ClientCertificateConfiguration configures operator-managed issuance of a TLS -client certificate for a DatabaseRole. - -*Appears in:* - -- [DatabaseRoleSpec](#databaserolespec) - -| Field | Description | Required | Default | Validation | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Enabled turns on client certificate issuance for this role. When true,
the role must have login enabled. Defaults to true when the block is present. | | true | | - -#### ClientCertificateState - -ClientCertificateState holds the observed state of the generated TLS client certificate. - -*Appears in:* - -- [DatabaseRoleStatus](#databaserolestatus) - -| Field | Description | Required | Default | Validation | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `expiration` *string* | Expiration is the expiration time of the generated client certificate, in RFC3339 format. | | | | -| `message` *string* | Message contains a human-readable explanation of the current certificate status,
such as why issuance was skipped or why an existing Secret was left untouched. | | | | - -#### Cluster - -Cluster defines the API schema for a highly available PostgreSQL database cluster -managed by {{name.ln}}. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Cluster` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ClusterSpec](#clusterspec)* | Specification of the desired behavior of the cluster.
More info: | True | | | -| `status` *[ClusterStatus](#clusterstatus)* | Most recently observed status of the cluster. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ClusterImageCatalog - -ClusterImageCatalog is the Schema for the clusterimagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ClusterImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ClusterImageCatalog.
More info: | True | | | - -#### ClusterMonitoringTLSConfiguration - -ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring - -*Appears in:* - -- [MonitoringConfiguration](#monitoringconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------- | -------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Enable TLS for the monitoring endpoint.
Changing this option will force a rollout of all instances. | | false | | - -#### ClusterSpec - -ClusterSpec defines the desired state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ | ---------------------------------------------------------------------- | -| `description` *string* | Description of this PostgreSQL cluster | | | | -| `inheritedMetadata` *[EmbeddedObjectMetadata](#embeddedobjectmetadata)* | Metadata that will be inherited by all objects related to the Cluster | | | | -| `imageName` *string* | Name of the container image, supporting both tags (`:`)
and digests for deterministic and repeatable deployments
(`:@sha256:`) | | | | -| `imageCatalogRef` *[ImageCatalogRef](#imagecatalogref)* | Defines the major PostgreSQL version we want to use within an ImageCatalog | | | | -| `imagePullPolicy` *[PullPolicy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#pullpolicy-v1-core)* | Image pull policy.
One of `Always`, `Never` or `IfNotPresent`.
If not defined, it defaults to `IfNotPresent`.
Cannot be updated.
More info: | | | | -| `schedulerName` *string* | 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:
| | | | -| `postgresUID` *integer* | The UID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `postgresGID` *integer* | The GID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `instances` *integer* | Number of instances required in the cluster | True | 1 | Minimum: 1
| -| `minSyncReplicas` *integer* | Minimum number of instances required in synchronous replication with the
primary. Undefined or 0 allow writes to complete when no standby is
available. | | 0 | Minimum: 0
| -| `maxSyncReplicas` *integer* | 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. | | 0 | Minimum: 0
| -| `postgresql` *[PostgresConfiguration](#postgresconfiguration)* | Configuration of the PostgreSQL server | | | | -| `podSelectorRefs` *[PodSelectorRef](#podselectorref) array* | PodSelectorRefs defines named pod label selectors that can be referenced
in pg_hba rules using the ${podselector:NAME} syntax in the address field.
The operator resolves matching pod IPs and the instance manager expands
pg_hba lines accordingly. Only pods in the Cluster's own namespace are considered. | | | | -| `replicationSlots` *[ReplicationSlotsConfiguration](#replicationslotsconfiguration)* | Replication slots management configuration | | | | -| `bootstrap` *[BootstrapConfiguration](#bootstrapconfiguration)* | Instructions to bootstrap this cluster | | | | -| `replica` *[ReplicaClusterConfiguration](#replicaclusterconfiguration)* | Replica cluster configuration | | | | -| `superuserSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The secret containing the superuser password. If not defined a new
secret will be created with a randomly generated password | | | | -| `enableSuperuserAccess` *boolean* | 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`. Disabled by default. | | | | -| `certificates` *[CertificatesConfiguration](#certificatesconfiguration)* | The configuration for the CA and related certificates | | | | -| `imagePullSecrets` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference) array* | 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. | | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage of the instances | | | | -| `serviceAccountTemplate` *[ServiceAccountTemplate](#serviceaccounttemplate)* | Configure the generation of the service account | | | | -| `serviceAccountName` *string* | Name of an existing ServiceAccount in the same namespace to use for the cluster.
When specified, the operator will not create a new ServiceAccount
but will use the provided one. This is useful for sharing a single
ServiceAccount across multiple clusters (e.g., for cloud IAM configurations).
If not specified, a ServiceAccount will be created with the cluster name.
Mutually exclusive with ServiceAccountTemplate. | | | MaxLength: 253
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| -| `walStorage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `ephemeralVolumeSource` *[EphemeralVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#ephemeralvolumesource-v1-core)* | EphemeralVolumeSource allows the user to configure the source of ephemeral volumes. | | | | -| `startDelay` *integer* | 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). | | 3600 | | -| `stopDelay` *integer* | The time in seconds that is allowed for a PostgreSQL instance to
gracefully shutdown (default 1800) | | 1800 | | -| `smartStopDelay` *integer* | Deprecated: please use SmartShutdownTimeout instead | | | | -| `smartShutdownTimeout` *integer* | 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`). Default is 180 seconds. | | 180 | | -| `switchoverDelay` *integer* | 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). | | 3600 | | -| `failoverDelay` *integer* | 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 | | 0 | | -| `livenessProbeTimeout` *integer* | 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` *[AffinityConfiguration](#affinityconfiguration)* | Affinity/Anti-affinity rules for Pods | | | | -| `topologySpreadConstraints` *[TopologySpreadConstraint](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#topologyspreadconstraint-v1-core) array* | TopologySpreadConstraints specifies how to spread matching pods among the given topology.
More info:
| | | | -| `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#resourcerequirements-v1-core)* | Resources requirements of every generated Pod. Please refer to

for more information. | | | | -| `ephemeralVolumesSizeLimit` *[EphemeralVolumesSizeLimitConfiguration](#ephemeralvolumessizelimitconfiguration)* | EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral
volumes | | | | -| `priorityClassName` *string* | 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

for more information | | | | -| `primaryUpdateStrategy` *[PrimaryUpdateStrategy](#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`) | | unsupervised | Enum: [unsupervised supervised]
| -| `primaryUpdateMethod` *[PrimaryUpdateMethod](#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).
Note: when using `switchover`, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process. | | | Enum: [switchover restart]
| -| `backup` *[BackupConfiguration](#backupconfiguration)* | The configuration to be used for backups | | | | -| `nodeMaintenanceWindow` *[NodeMaintenanceWindow](#nodemaintenancewindow)* | Define a maintenance window for the Kubernetes nodes | | | | -| `licenseKey` *string* | 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. | | | | -| `licenseKeySecret` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the license key. When this is set it take precedence over LicenseKey. | | | | -| `monitoring` *[MonitoringConfiguration](#monitoringconfiguration)* | The configuration of the monitoring infrastructure of this cluster | | | | -| `externalClusters` *[ExternalCluster](#externalcluster) array* | The list of external clusters which are used in the configuration | | | | -| `logLevel` *string* | The instances' log level, one of the following values: error, warning, info (default), debug, trace | | info | Enum: [error warning info debug trace]
| -| `projectedVolumeTemplate` *[ProjectedVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#projectedvolumesource-v1-core)* | Template to be used to define projected volumes, projected volumes will be mounted
under `/projected` base folder | | | | -| `env` *[EnvVar](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envvar-v1-core) array* | Env follows the Env format to pass environment variables
to the pods created in the cluster | | | | -| `envFrom` *[EnvFromSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envfromsource-v1-core) array* | EnvFrom follows the EnvFrom format to pass environment variables
sources to the pods to be used by Env | | | | -| `managed` *[ManagedConfiguration](#managedconfiguration)* | The configuration that is used by the portions of PostgreSQL that are managed by the instance manager | | | | -| `seccompProfile` *[SeccompProfile](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#seccompprofile-v1-core)* | The SeccompProfile applied to every Pod and Container.
Defaults to: `RuntimeDefault` | | | | -| `podSecurityContext` *[PodSecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podsecuritycontext-v1-core)* | Override the PodSecurityContext applied to every Pod of the cluster.
When set, this overrides the operator's default PodSecurityContext for the cluster.
If omitted, the operator defaults are used.
This field doesn't have any effect if SecurityContextConstraints are present. | | | | -| `securityContext` *[SecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#securitycontext-v1-core)* | Override the SecurityContext applied to every Container in the Pod of the cluster.
When set, this overrides the operator's default Container SecurityContext.
If omitted, the operator defaults are used. | | | | -| `tablespaces` *[TablespaceConfiguration](#tablespaceconfiguration) array* | The tablespaces configuration | | | | -| `enablePDB` *boolean* | 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 any
`PodDisruptionBudget` 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. | | true | | -| `plugins` *[PluginConfiguration](#pluginconfiguration) array* | The plugins configuration, containing
any plugin to be loaded with the corresponding configuration | | | | -| `probes` *[ProbesConfiguration](#probesconfiguration)* | The configuration of the probes to be injected
in the PostgreSQL Pods. | | | | -| `primaryLease` *[PrimaryLeaseConfiguration](#primaryleaseconfiguration)* | Configuration of the Kubernetes `Lease` used to coordinate safe primary
election within the cluster. When omitted, the operator applies built-in
defaults; tune these values only if you understand the consequences for
failover timing. | | | | - -#### ClusterStatus - -ClusterStatus defines the observed state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *integer* | The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods. | | | | -| `readyInstances` *integer* | The total number of ready instances in the cluster. It is equal to the number of ready instance pods. | | | | -| `selector` *string* | Selector is the serialized form of the label selector that identifies
the pods managed by this cluster. Populated by the operator and exposed
through the scale sub-resource so an autoscaler (such as HPA or VPA)
can discover the managed instance pods. | | | | -| `instancesStatus` *object (keys:[PodStatus](#podstatus), values:string array)* | InstancesStatus indicates in which status the instances are | | | | -| `instancesReportedState` *object (keys:[PodName](#podname), values:[InstanceReportedState](#instancereportedstate))* | The reported state of the instances during the last reconciliation loop | | | | -| `managedRolesStatus` *[ManagedRoles](#managedroles)* | ManagedRolesStatus reports the state of the managed roles in the cluster | | | | -| `tablespacesStatus` *[TablespaceState](#tablespacestate) array* | TablespacesStatus reports the state of the declarative tablespaces in the cluster | | | | -| `podSelectorRefs` *[PodSelectorRefStatus](#podselectorrefstatus) array* | PodSelectorRefs contains the resolved pod IPs for each named selector
defined in spec.podSelectorRefs. | | | | -| `timelineID` *integer* | The timeline of the Postgres cluster | | | | -| `topology` *[Topology](#topology)* | Instances topology. | | | | -| `latestGeneratedNode` *integer* | ID of the latest generated node (used to avoid node name clashing)
Deprecated: this field is not set anymore | | | | -| `currentPrimary` *string* | Current primary instance | | | | -| `targetPrimary` *string* | Target primary instance, this is different from the previous one
during a switchover or a failover | | | | -| `lastPromotionToken` *string* | LastPromotionToken is the last verified promotion token that
was used to promote a replica cluster | | | | -| `pvcCount` *integer* | How many PVCs have been created by this cluster | | | | -| `jobCount` *integer* | How many Jobs have been created by this cluster | | | | -| `danglingPVC` *string array* | List of all the PVCs created by this cluster and still available
which are not attached to a Pod | | | | -| `resizingPVC` *string array* | List of all the PVCs that have ResizingPVC condition. | | | | -| `initializingPVC` *string array* | List of all the PVCs that are being initialized by this cluster | | | | -| `healthyPVC` *string array* | List of all the PVCs not dangling nor initializing | | | | -| `unusablePVC` *string array* | List of all the PVCs that are unusable because another PVC is missing | | | | -| `licenseStatus` *Status* | Status of the license | | | | -| `writeService` *string* | Current write pod | | | | -| `readService` *string* | Current list of read pods | | | | -| `phase` *string* | Current phase of the cluster | | | | -| `phaseReason` *string* | Reason for the current phase | | | | -| `secretsResourceVersion` *[SecretsResourceVersion](#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` *[ConfigMapResourceVersion](#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` *[CertificatesStatus](#certificatesstatus)* | The configuration for the CA and related certificates, initialized with defaults. | | | | -| `firstRecoverabilityPoint` *string* | The first recoverability point, stored as a date in RFC3339 format.
This field is calculated from the content of FirstRecoverabilityPointByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `firstRecoverabilityPointByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | The first recoverability point, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackup` *string* | Last successful backup, stored as a date in RFC3339 format.
This field is calculated from the content of LastSuccessfulBackupByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackupByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | Last successful backup, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastFailedBackup` *string* | Last failed backup, stored as a date in RFC3339 format.
Deprecated: the field is not set for backup plugins. | | | | -| `cloudNativePostgresqlCommitHash` *string* | The commit hash number of which this operator running | | | | -| `currentPrimaryTimestamp` *string* | The timestamp when the last actual promotion to primary has occurred | | | | -| `currentPrimaryFailingSinceTimestamp` *string* | The timestamp when the primary was detected to be unhealthy
This field is reported when `.spec.failoverDelay` is populated or during online upgrades | | | | -| `targetPrimaryTimestamp` *string* | The timestamp when the last request for a new primary has occurred | | | | -| `poolerIntegrations` *[PoolerIntegrations](#poolerintegrations)* | The integration needed by poolers referencing the cluster | | | | -| `cloudNativePostgresqlOperatorHash` *string* | The hash of the binary of the operator | | | | -| `operatorCertificateFingerprint` *string* | OperatorCertificateFingerprint is the SHA256 fingerprint of the operator's
in-memory client certificate public key. The instance manager pins this
fingerprint to authenticate requests from the operator. | | | | -| `availableArchitectures` *[AvailableArchitecture](#availablearchitecture) array* | AvailableArchitectures reports the available architectures of a cluster | | | | -| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for cluster object | | | | -| `instanceNames` *string array* | List of instance names in the cluster | | | | -| `onlineUpdateEnabled` *boolean* | OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster | | | | -| `image` *string* | Image contains the image name used by the pods | | | | -| `pgDataImageInfo` *[ImageInfo](#imageinfo)* | PGDataImageInfo contains the details of the latest image that has run on the current data directory. | | | | -| `targetPgDataImageInfo` *[ImageInfo](#imageinfo)* | TargetPGDataImageInfo contains the details of the target image for an
in-progress major upgrade. It is set before the upgrade Job is created,
and cleared on successful completion or when the upgrade is rolled back. | | | | -| `pluginStatus` *[PluginStatus](#pluginstatus) array* | PluginStatus is the status of the loaded plugins | | | | -| `switchReplicaClusterStatus` *[SwitchReplicaClusterStatus](#switchreplicaclusterstatus)* | SwitchReplicaClusterStatus is the status of the switch to replica cluster | | | | -| `demotionToken` *string* | DemotionToken is a JSON token containing the information
from pg_controldata such as Database system identifier, Latest checkpoint's
TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO
WAL file, and Time of latest checkpoint | | | | -| `systemID` *string* | SystemID is the latest detected PostgreSQL SystemID | | | | - -#### ConfigMapResourceVersion - -ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metrics` *object (keys:string, values:string)* | 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 | | | | - -#### DataDurabilityLevel - -*Underlying type:* *string* - -DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are `required` or `preferred`. - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -| Field | Description | -| ----------- | ----------------------------------------------------------------------------------------------------------------------- | -| `required` | DataDurabilityLevelRequired means that data durability is strictly enforced
| -| `preferred` | DataDurabilityLevelPreferred means that data durability is enforced
only when healthy replicas are available
| - -#### DataSource - -DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `storage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage of the instances | True | | | -| `walStorage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `tablespaceStorage` *object (keys:string, values:[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core))* | Configuration of the storage for PostgreSQL tablespaces | | | | - -#### Database - -Database is the Schema for the databases API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Database` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[DatabaseSpec](#databasespec)* | Specification of the desired Database.
More info: | True | | | -| `status` *[DatabaseStatus](#databasestatus)* | Most recently observed status of the Database. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### DatabaseObjectSpec - -DatabaseObjectSpec contains the fields which are common to every -database object - -*Appears in:* - -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| - -#### DatabaseObjectStatus - -DatabaseObjectStatus is the status of the managed database objects - -*Appears in:* - -- [DatabaseStatus](#databasestatus) - -| Field | Description | Required | Default | Validation | -| ------------------- | ----------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the object | True | | | -| `applied` *boolean* | True of the object has been installed successfully in
the database | True | | | -| `message` *string* | Message is the object reconciliation message | | | | - -#### DatabaseReclaimPolicy - -*Underlying type:* *string* - -DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases. - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | DatabaseReclaimDelete means the database will be deleted from its PostgreSQL Cluster on release
from its claim.
| -| `retain` | DatabaseReclaimRetain means the database will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### DatabaseRole - -DatabaseRole is the Schema for the databaseroles API - -*Appears in:* - -- [DatabaseRoleList](#databaserolelist) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `DatabaseRole` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[DatabaseRoleSpec](#databaserolespec)* | Specification of the desired DatabaseRole.
More info: | True | | | -| `status` *[DatabaseRoleStatus](#databaserolestatus)* | Most recently observed status of the DatabaseRole. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### DatabaseRoleList - -DatabaseRoleList contains a list of DatabaseRoles - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `DatabaseRoleList` | True | | | -| `metadata` *[ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#listmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `items` *[DatabaseRole](#databaserole) array* | | True | | | - -#### DatabaseRoleReclaimPolicy - -*Underlying type:* *string* - -DatabaseRoleReclaimPolicy describes a policy for end-of-life maintenance of Roles. - -*Appears in:* - -- [DatabaseRoleSpec](#databaserolespec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | DatabaseRoleReclaimDelete means the Role will be deleted from Kubernetes on release
from its claim.
| -| `retain` | DatabaseRoleReclaimRetain means the Role will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### DatabaseRoleRef - -DatabaseRoleRef is a reference an a role available inside PostgreSQL - -*Appears in:* - -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------- | ----------- | -------- | ------- | ---------- | -| `name` *string* | | | | | - -#### DatabaseRoleSpec - -DatabaseRoleSpec represents a role in Postgres - -*Appears in:* - -- [DatabaseRole](#databaserole) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the role | True | | | -| `comment` *string* | Description of the role | | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the role is `present` or `absent` - defaults to "present" | | present | Enum: [present absent]
| -| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present).
If null, the password will be ignored unless DisablePassword is set.
When set, the secret must follow the `kubernetes.io/basic-auth` format
and contain both a `username` and a `password` field. | | | | -| `connectionLimit` *integer* | If the role can log in, this specifies how many concurrent
connections the role can make. `-1` (the default) means no limit. | | -1 | | -| `validUntil` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Date and time after which the role's password is no longer valid.
When omitted, the password will never expire (default). | | | | -| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty.
Changes to the list are applied to an existing role through
`GRANT` and `REVOKE` statements, not only at role creation. | | | | -| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Default is `true`. | | true | | -| `disablePassword` *boolean* | DisablePassword indicates that a role's password should be set to NULL in Postgres | | | | -| `superuser` *boolean* | 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`. | | | | -| `createdb` *boolean* | 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. | | | | -| `createrole` *boolean* | 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`. | | | | -| `login` *boolean* | 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`. | | | | -| `replication` *boolean* | 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`. | | | | -| `bypassrls` *boolean* | Whether a role bypasses every row-level security (RLS) policy.
Default is `false`. | | | | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The corresponding cluster | True | | | -| `databaseRoleReclaimPolicy` *[DatabaseRoleReclaimPolicy](#databaserolereclaimpolicy)* | The policy for end-of-life maintenance of this role | | retain | Enum: [delete retain]
| -| `clientCertificate` *[ClientCertificateConfiguration](#clientcertificateconfiguration)* | ClientCertificate configures the operator to generate and renew a TLS client
certificate for this role, signed by the cluster's client CA. The certificate
is stored in a Secret named `-client-cert`.
Requires login to be true. | | | | - -#### DatabaseRoleStatus - -DatabaseRoleStatus defines the observed state of a DatabaseRole - -*Appears in:* - -- [DatabaseRole](#databaserole) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the role was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation error message | | | | -| `secretResourceVersion` *string* | SecretResourceVersion is the resource version of the password secret
last applied to the role; a change to it triggers reconciliation. | | | | -| `clientCertificate` *[ClientCertificateState](#clientcertificatestate)* | ClientCertificate holds the observed state of the generated TLS client
certificate, when client certificate issuance is enabled. | | | | -| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for the DatabaseRole object | | | | - -#### DatabaseSpec - -DatabaseSpec is the specification of a Postgresql Database, built around the -`CREATE DATABASE`, `ALTER DATABASE`, and `DROP DATABASE` SQL commands of -PostgreSQL. - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster hosting the database. | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the PostgreSQL database is `present` or `absent` - defaults to "present". | | present | Enum: [present absent]
| -| `name` *string* | The name of the database to create inside PostgreSQL. This setting cannot be changed. | True | | | -| `owner` *string* | Maps to the `OWNER` parameter of `CREATE DATABASE`.
Maps to the `OWNER TO` command of `ALTER DATABASE`.
The role name of the user who owns the database inside PostgreSQL. | True | | | -| `template` *string* | Maps to the `TEMPLATE` parameter of `CREATE DATABASE`. This setting
cannot be changed. The name of the template from which to create
this database. | | | | -| `encoding` *string* | Maps to the `ENCODING` parameter of `CREATE DATABASE`. This setting
cannot be changed. Character set encoding to use in the database. | | | | -| `locale` *string* | Maps to the `LOCALE` parameter of `CREATE DATABASE`. This setting
cannot be changed. Sets the default collation order and character
classification in the new database. | | | | -| `localeProvider` *string* | Maps to the `LOCALE_PROVIDER` parameter of `CREATE DATABASE`. This
setting cannot be changed. This option sets the locale provider for
databases created in the new cluster. Available from PostgreSQL 16. | | | | -| `localeCollate` *string* | Maps to the `LC_COLLATE` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `localeCType` *string* | Maps to the `LC_CTYPE` parameter of `CREATE DATABASE`. This setting
cannot be changed. | | | | -| `icuLocale` *string* | Maps to the `ICU_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the ICU locale when the ICU
provider is used. This option requires `localeProvider` to be set to
`icu`. Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Maps to the `ICU_RULES` parameter of `CREATE DATABASE`. This setting
cannot be changed. Specifies additional collation rules to customize
the behavior of the default collation. This option requires
`localeProvider` to be set to `icu`. Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Maps to the `BUILTIN_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the locale name when the
builtin provider is used. This option requires `localeProvider` to
be set to `builtin`. Available from PostgreSQL 17. | | | | -| `collationVersion` *string* | Maps to the `COLLATION_VERSION` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `isTemplate` *boolean* | Maps to the `IS_TEMPLATE` parameter of `CREATE DATABASE` and `ALTER
DATABASE`. If true, this database is considered a template and can
be cloned by any user with `CREATEDB` privileges. | | | | -| `allowConnections` *boolean* | Maps to the `ALLOW_CONNECTIONS` parameter of `CREATE DATABASE` and
`ALTER DATABASE`. If false then no one can connect to this database. | | | | -| `connectionLimit` *integer* | Maps to the `CONNECTION LIMIT` clause of `CREATE DATABASE` and
`ALTER DATABASE`. How many concurrent connections can be made to
this database. -1 (the default) means no limit. | | | | -| `tablespace` *string* | Maps to the `TABLESPACE` parameter of `CREATE DATABASE`.
Maps to the `SET TABLESPACE` command of `ALTER DATABASE`.
The name of the tablespace (in PostgreSQL) that will be associated
with the new database. This tablespace will be the default
tablespace used for objects created in this database. | | | | -| `databaseReclaimPolicy` *[DatabaseReclaimPolicy](#databasereclaimpolicy)* | The policy for end-of-life maintenance of this database. | | retain | Enum: [delete retain]
| -| `schemas` *[SchemaSpec](#schemaspec) array* | The list of schemas to be managed in the database | | | | -| `extensions` *[ExtensionSpec](#extensionspec) array* | The list of extensions to be managed in the database | | | | -| `fdws` *[FDWSpec](#fdwspec) array* | The list of foreign data wrappers to be managed in the database | | | | -| `servers` *[ServerSpec](#serverspec) array* | The list of foreign servers to be managed in the database | | | | - -#### DatabaseStatus - -DatabaseStatus defines the observed state of Database - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the database was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | -| `schemas` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Schemas is the status of the managed schemas | | | | -| `extensions` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Extensions is the status of the managed extensions | | | | -| `fdws` *[DatabaseObjectStatus](#databaseobjectstatus) array* | FDWs is the status of the managed FDWs | | | | -| `servers` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Servers is the status of the managed servers | | | | - -#### EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `audit` *boolean* | If true enables edb_audit logging | | | | -| `tde` *[TDEConfiguration](#tdeconfiguration)* | TDE configuration | | | | - -#### EmbeddedObjectMetadata - -EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `labels` *object (keys:string, values:string)* | | | | | -| `annotations` *object (keys:string, values:string)* | | | | | - -#### EnsureOption - -*Underlying type:* *string* - -EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance - -*Appears in:* - -- [DatabaseObjectSpec](#databaseobjectspec) -- [DatabaseRoleSpec](#databaserolespec) -- [DatabaseSpec](#databasespec) -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [OptionSpec](#optionspec) -- [RoleConfiguration](#roleconfiguration) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | -| --------- | ----------- | -| `present` | | -| `absent` | | - -#### EphemeralVolumesSizeLimitConfiguration - -EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------ | -------- | ------- | ---------- | -| `shm` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Shm is the size limit of the shared memory volume | | | | -| `temporaryData` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | TemporaryData is the size limit of the temporary data volume | | | | - -#### ExtensionConfiguration - -ExtensionConfiguration is the configuration used to add -PostgreSQL extensions to the Cluster. - -*Appears in:* - -- [CatalogImage](#catalogimage) -- [ImageInfo](#imageinfo) -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------------------------------------------------------------------- | -| `name` *string* | The name of the extension, required. The limit of 59 characters
leaves room for the prefix the operator adds when deriving the
extension's Kubernetes Volume name (capped at 63 characters). | True | | MaxLength: 59
MinLength: 1
Pattern: `^[a-z0-9]([-a-z0-9_]*[a-z0-9])?$`
| -| `image` *[ImageVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#imagevolumesource-v1-core)* | The image containing the extension. | | | | -| `extension_control_path` *string array* | The list of directories inside the image which should be added to extension_control_path.
If not defined, defaults to "/share". | | | | -| `dynamic_library_path` *string array* | The list of directories inside the image which should be added to dynamic_library_path.
If not defined, defaults to "/lib". | | | | -| `ld_library_path` *string array* | The list of directories inside the image which should be added to ld_library_path. | | | | -| `bin_path` *string array* | A list of directories within the image to be appended to the
PostgreSQL process's `PATH` environment variable. | | | | -| `env` *[ExtensionEnvVar](#extensionenvvar) array* | Env is a list of custom environment variables to be set in the
PostgreSQL process for this extension. It is the responsibility of the
cluster administrator to ensure the variables are correct for the
specific extension. Note that changes to these variables require
a manual cluster restart to take effect. | | | | - -#### ExtensionEnvVar - -ExtensionEnvVar defines an environment variable for a specific extension -image volume. - -*Appears in:* - -- [ExtensionConfiguration](#extensionconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------------------------------- | -| `name` *string* | Name of the environment variable to be injected into the
PostgreSQL process. | True | | MinLength: 1
Pattern: `^[a-zA-Z_][a-zA-Z0-9_]*$`
| -| `value` *string* | Value of the environment variable. {{name.ln}} performs a direct
replacement of this value, with support for placeholder expansion.
The ${`image_root`} placeholder resolves to the absolute mount path
of the extension's volume (e.g., `/extensions/my-extension`). This
is particularly useful for allowing applications or libraries to
locate specific directories within the mounted image.
Unrecognized placeholders are rejected. To include a literal ${...}
in the value, escape it as $${...}. | True | | MinLength: 1
| - -#### ExtensionSpec - -ExtensionSpec configures an extension in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `version` *string* | The version of the extension to install. If empty, the operator will
install the default version (whatever is specified in the
extension's control file) | True | | | -| `schema` *string* | The name of the schema in which to install the extension's objects,
in case the extension allows its contents to be relocated. If not
specified (default), and the extension's control file does not
specify a schema either, the current default object creation schema
is used. | True | | | - -#### ExternalCluster - -ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The server name, required | True | | | -| `connectionParameters` *object (keys:string, values:string)* | The list of connection parameters, such as dbname, host, username, etc | | | | -| `sslCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL certificate to be used to connect to this
instance | | | | -| `sslKey` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL private key to be used to connect to this
instance | | | | -| `sslRootCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL CA public key to be used to connect to this
instance | | | | -| `password` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the password to be used to connect to the server.
If a password is provided, {{name.ln}} 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. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `plugin` *[PluginConfiguration](#pluginconfiguration)* | The configuration of the plugin that is taking care
of WAL archiving and backups for this external cluster | True | | | - -#### FDWSpec - -FDWSpec configures an Foreign Data Wrapper in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `handler` *string* | Name of the handler function (e.g., "postgres_fdw_handler").
This will be empty if no handler is specified. In that case,
the default handler is registered when the FDW extension is created. | | | | -| `validator` *string* | Name of the validator function (e.g., "postgres_fdw_validator").
This will be empty if no validator is specified. In that case,
the default validator is registered when the FDW extension is created. | | | | -| `owner` *string* | Owner specifies the database role that will own the Foreign Data Wrapper.
The role must have superuser privileges in the target database. | | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the FDW. | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the FDW are granted or revoked. | | | | - -#### FailoverQuorum - -FailoverQuorum contains the information about the current failover -quorum status of a PG cluster. It is updated by the instance manager -of the primary node and reset to zero by the operator to trigger -an update. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `FailoverQuorum` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `status` *[FailoverQuorumStatus](#failoverquorumstatus)* | Most recently observed status of the failover quorum. | | | | - -#### FailoverQuorumStatus - -FailoverQuorumStatus is the latest observed status of the failover -quorum of the PG cluster. - -*Appears in:* - -- [FailoverQuorum](#failoverquorum) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | --------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `method` *string* | Contains the latest reported Method value. | | | | -| `standbyNames` *string array* | StandbyNames is the list of potentially synchronous
instance names. | | | | -| `standbyNumber` *integer* | StandbyNumber is the number of synchronous standbys that transactions
need to wait for replies from. | | | | -| `primary` *string* | Primary is the name of the primary instance that updated
this object the latest time. | | | | - -#### ImageCatalog - -ImageCatalog is the Schema for the imagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ImageCatalog.
More info: | True | | | - -#### ImageCatalogComponentRef - -ImageCatalogComponentRef identifies a named image within the componentImages list of an -ImageCatalog or ClusterImageCatalog. - -*Appears in:* - -- [PgBouncerSpec](#pgbouncerspec) - -| Field | Description | Required | Default | Validation | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------------------------------------------- | -| `apiGroup` *string* | APIGroup is the group for the resource being referenced.
If APIGroup is not specified, the specified Kind must be in the core API group.
For any other third-party types, APIGroup is required. | | | | -| `kind` *string* | Kind is the type of resource being referenced | True | | | -| `name` *string* | Name is the name of resource being referenced | True | | | -| `key` *string* | Key identifies the entry within the catalog's componentImages list. | True | | MaxLength: 63
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| - -#### ImageCatalogRef - -ImageCatalogRef defines the reference to a major version in an ImageCatalog - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiGroup` *string* | APIGroup is the group for the resource being referenced.
If APIGroup is not specified, the specified Kind must be in the core API group.
For any other third-party types, APIGroup is required. | | | | -| `kind` *string* | Kind is the type of resource being referenced | True | | | -| `name` *string* | Name is the name of resource being referenced | True | | | -| `major` *integer* | The major version of PostgreSQL we want to use from the ImageCatalog | True | | | - -#### ImageCatalogSpec - -ImageCatalogSpec defines the desired ImageCatalog - -*Appears in:* - -- [ClusterImageCatalog](#clusterimagecatalog) -- [ImageCatalog](#imagecatalog) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------ | -| `images` *[CatalogImage](#catalogimage) array* | List of CatalogImages available in the catalog | True | | MaxItems: 8
MinItems: 1
| -| `componentImages` *[CatalogComponentImage](#catalogcomponentimage) array* | ComponentImages is a list of named images for components other than PostgreSQL
(e.g. pgbouncer). Keys must be unique within a catalog. | | | MaxItems: 32
| - -#### ImageInfo - -ImageInfo contains the information about a PostgreSQL image - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `image` *string* | Image is the image name | True | | | -| `majorVersion` *integer* | MajorVersion is the major version of the image | True | | | -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | Extensions contains the container image extensions available for the current Image | | | | - -#### Import - -Import contains the configuration to init a database from a logic snapshot of an externalCluster - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------ | -| `source` *[ImportSource](#importsource)* | The source of the import | True | | | -| `type` *[SnapshotType](#snapshottype)* | The import type. Can be `microservice` or `monolith`. | True | | Enum: [microservice monolith]
| -| `databases` *string array* | The databases to import | True | | | -| `roles` *string array* | The roles to import | | | | -| `postImportApplicationSQL` *string array* | 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. | | | | -| `schemaOnly` *boolean* | When set to true, only the `pre-data` and `post-data` sections of
`pg_restore` are invoked, avoiding data import. Default: `false`. | | | | -| `pgDumpExtraOptions` *string array* | List of custom options to pass to the `pg_dump` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreExtraOptions` *string array* | List of custom options to pass to the `pg_restore` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePredataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `pre-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreDataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePostdataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `post-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | - -#### ImportSource - -ImportSource describes the source for the logical snapshot - -*Appears in:* - -- [Import](#import) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ----------------------------------------------- | -------- | ------- | ---------- | -| `externalCluster` *string* | The name of the externalCluster used for import | True | | | - -#### InstanceID - -InstanceID contains the information to identify an instance - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `podName` *string* | The pod name | | | | -| `ContainerID` *string* | The container ID | | | | -| `sessionID` *string* | The instance manager session ID. This is a unique identifier generated at instance manager
startup and changes on every restart (including container reboots). Used to detect if
the instance manager was restarted during long-running operations like backups, which
would terminate any running backup process. | | | | - -#### InstanceReportedState - -InstanceReportedState describes the last reported state of an instance during a reconciliation loop - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------- | -------- | ------- | ---------- | -| `isPrimary` *boolean* | indicates if an instance is the primary one | True | | | -| `timeLineID` *integer* | indicates on which TimelineId the instance is | | | | -| `ip` *string* | IP address of the instance | True | | | - -#### IsolationCheckConfiguration - -IsolationCheckConfiguration contains the configuration for the isolation check -functionality in the liveness probe - -*Appears in:* - -- [LivenessProbe](#livenessprobe) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Whether primary isolation checking is enabled for the liveness probe | | true | | -| `requestTimeout` *integer* | Timeout in milliseconds for requests during the primary isolation check | | 1000 | | -| `connectionTimeout` *integer* | Timeout in milliseconds for connections during the primary isolation check | | 1000 | | - -#### LDAPBindAsAuth - -LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ----------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `prefix` *string* | Prefix for the bind authentication option | | | | -| `suffix` *string* | Suffix for the bind authentication option | | | | - -#### LDAPBindSearchAuth - -LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | -------- | ------- | ---------- | -| `baseDN` *string* | Root DN to begin the user search | | | | -| `bindDN` *string* | DN of the user to bind to the directory | | | | -| `bindPassword` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Secret with the password for the user to bind to the directory | | | | -| `searchAttribute` *string* | Attribute to match against the username | | | | -| `searchFilter` *string* | Search filter to use when doing the search+bind authentication | | | | - -#### LDAPConfig - -LDAPConfig contains the parameters needed for LDAP authentication - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ------------------------- | -| `server` *string* | LDAP hostname or IP address | | | | -| `port` *integer* | LDAP server port | | | | -| `scheme` *[LDAPScheme](#ldapscheme)* | LDAP schema to be used, possible options are `ldap` and `ldaps` | | | Enum: [ldap ldaps]
| -| `bindAsAuth` *[LDAPBindAsAuth](#ldapbindasauth)* | Bind as authentication configuration | | | | -| `bindSearchAuth` *[LDAPBindSearchAuth](#ldapbindsearchauth)* | Bind+Search authentication configuration | | | | -| `tls` *boolean* | Set to 'true' to enable LDAP over TLS. 'false' is default | | | | - -#### LDAPScheme - -*Underlying type:* *string* - -LDAPScheme defines the possible schemes for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | -| ------- | ----------- | -| `ldap` | | -| `ldaps` | | - -#### LivenessProbe - -LivenessProbe is the configuration of the liveness probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `isolationCheck` *[IsolationCheckConfiguration](#isolationcheckconfiguration)* | Configure the feature that extends the liveness probe for a primary
instance. In addition to the basic checks, this verifies whether the
primary is isolated from the Kubernetes API server and from its
replicas, ensuring that it can be safely shut down if network
partition or API unavailability is detected. Enabled by default. | | | | - -#### ManagedConfiguration - -ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------- | --------------------------------------- | -------- | ------- | ---------- | -| `roles` *[RoleConfiguration](#roleconfiguration) array* | Database roles managed by the `Cluster` | | | | -| `services` *[ManagedServices](#managedservices)* | Services roles managed by the `Cluster` | | | | - -#### ManagedRoles - -ManagedRoles tracks the status of a cluster's managed roles - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `byStatus` *object (keys:[RoleStatus](#rolestatus), values:string array)* | ByStatus gives the list of roles in each state | | | | -| `cannotReconcile` *object (keys:string, values:string array)* | CannotReconcile lists roles that cannot be reconciled, with an
explanation of the cause. Failures may originate in PostgreSQL
(e.g. dropping a role that owns objects) or in Kubernetes (e.g.
the referenced password Secret cannot be fetched). | | | | -| `passwordStatus` *object (keys:string, values:[PasswordState](#passwordstate))* | PasswordStatus gives the last transaction id and password secret version for each managed role | | | | - -#### ManagedService - -ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification. - -*Appears in:* - -- [ManagedServices](#managedservices) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `selectorType` *[ServiceSelectorType](#serviceselectortype)* | SelectorType specifies the type of selectors that the service will have.
Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services. | True | | Enum: [rw r ro]
| -| `updateStrategy` *[ServiceUpdateStrategy](#serviceupdatestrategy)* | UpdateStrategy describes how the service differences should be reconciled | | patch | Enum: [patch replace]
| -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | ServiceTemplate is the template specification for the service. | True | | | - -#### ManagedServices - -ManagedServices represents the services managed by the cluster. - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------- | -| `disabledDefaultServices` *[ServiceSelectorType](#serviceselectortype) array* | DisabledDefaultServices is a list of service types that are disabled by default.
Valid values are "r", and "ro", representing read, and read-only services. | | | Enum: [rw r ro]
| -| `additional` *[ManagedService](#managedservice) array* | Additional is a list of additional managed services specified by the user. | | | | - -#### 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. - -*Appears in:* - -- [PodTemplateSpec](#podtemplatespec) -- [ServiceAccountTemplate](#serviceaccounttemplate) -- [ServiceTemplateSpec](#servicetemplatespec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the resource. Only supported for certain types | | | | -| `labels` *object (keys:string, values:string)* | 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: | | | | -| `annotations` *object (keys:string, values:string)* | 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: | | | | - -#### MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `disableDefaultQueries` *boolean* | 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. | | false | | -| `customQueriesConfigMap` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | The list of config maps containing the custom queries | | | | -| `customQueriesSecret` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | The list of secrets containing the custom queries | | | | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor`
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | false | | -| `tls` *[ClusterMonitoringTLSConfiguration](#clustermonitoringtlsconfiguration)* | Configure TLS communication for the metrics endpoint.
Changing tls.enabled option will force a rollout of all instances. | | | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `metricsQueriesTTL` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | The interval during which metrics computed from queries are considered current.
Once it is exceeded, a new scrape will trigger a rerun
of the queries.
If not set, defaults to 30 seconds, in line with Prometheus scraping defaults.
Setting this to zero disables the caching mechanism and can cause heavy load on the PostgreSQL server. | | | | - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `reusePVC` *boolean* | Reuse the existing PVC (wait for the node to come
up again) or not (recreate it elsewhere - when `instances` >1) | | true | | -| `inProgress` *boolean* | Is there a node maintenance activity in progress? | | false | | - -#### OnlineConfiguration - -OnlineConfiguration contains the configuration parameters for the online volume snapshot - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `waitForArchive` *boolean* | 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. | | true | | -| `immediateCheckpoint` *boolean* | 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. | | | | - -#### OptionSpec - -OptionSpec holds the name, value and the ensure field for an option - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the option | True | | | -| `value` *string* | Value of the option | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an option should be present or absent in
the database. If set to `present`, the option will be
created if it does not exist. If set to `absent`, the
option will be removed if it exists. | | present | Enum: [present absent]
| - -#### PasswordState - -PasswordState represents the state of the password of a managed RoleConfiguration - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ------------------------------------------------------------------- | -------- | ------- | ---------- | -| `transactionID` *integer* | the last transaction ID to affect the role definition in PostgreSQL | | | | -| `resourceVersion` *string* | the resource version of the password secret | | | | - -#### PgBouncerIntegrationStatus - -PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster - -*Appears in:* - -- [PoolerIntegrations](#poolerintegrations) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------- | -------- | ------- | ---------- | -| `secrets` *string array* | | | | | - -#### PgBouncerPoolMode - -*Underlying type:* *string* - -PgBouncerPoolMode is the mode of PgBouncer - -*Validation:* - -- Enum: [session transaction] - -*Appears in:* - -- [PgBouncerSpec](#pgbouncerspec) - -#### PgBouncerSecrets - -PgBouncerSecrets contains the versions of the secrets used -by pgbouncer - -*Appears in:* - -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | ----------------------------- | -------- | ------- | ---------- | -| `authQuery` *[SecretVersion](#secretversion)* | The auth query secret version | | | | - -#### PgBouncerSpec - -PgBouncerSpec defines how to configure PgBouncer - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------------- | -| `poolMode` *[PgBouncerPoolMode](#pgbouncerpoolmode)* | The pool mode. Default: `session`. | | session | Enum: [session transaction]
| -| `serverTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerTLSSecret, when pointing to a TLS secret, provides pgbouncer's
`server_tls_key_file` and `server_tls_cert_file`, used when
authenticating against PostgreSQL. | | | | -| `serverCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerCASecret provides PgBouncer’s server_tls_ca_file, the root
CA for validating PostgreSQL certificates | | | | -| `clientCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientCASecret provides PgBouncer’s client_tls_ca_file, the root
CA for validating client certificates | | | | -| `clientTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientTLSSecret provides PgBouncer’s client_tls_key_file (private key)
and client_tls_cert_file (certificate) used to accept client connections | | | | -| `authQuerySecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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.
Deprecated. | | | | -| `authQuery` *string* | 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. | | | | -| `parameters` *object (keys:string, values:string)* | Additional parameters to be passed to PgBouncer - please check
the CNP documentation for a list of options you can configure | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file) | | | | -| `paused` *boolean* | 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. | | false | | -| `image` *string* | Image is the pgbouncer container image to use. When set, it takes
precedence over ImageCatalogRef and the operator default, but is
overridden by an explicit image set in the pod template. | | | | -| `imageCatalogRef` *[ImageCatalogComponentRef](#imagecatalogcomponentref)* | ImageCatalogRef points to an entry in an ImageCatalog or ClusterImageCatalog.
Mutually exclusive with Image. | | | | - -#### PluginConfiguration - -PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [ExternalCluster](#externalcluster) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the plugin name | True | | | -| `enabled` *boolean* | Enabled is true if this plugin will be used | | true | | -| `isWALArchiver` *boolean* | Marks the plugin as the WAL archiver. At most one plugin can be
designated as a WAL archiver. This cannot be enabled if the
`.spec.backup.barmanObjectStore` configuration is present. | | false | | -| `parameters` *object (keys:string, values:string)* | Parameters is the configuration of the plugin | | | | - -#### PluginStatus - -PluginStatus is the status of a loaded plugin - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin | True | | | -| `version` *string* | Version is the version of the plugin loaded by the
latest reconciliation loop | True | | | -| `capabilities` *string array* | Capabilities are the list of capabilities of the
plugin | | | | -| `operatorCapabilities` *string array* | OperatorCapabilities are the list of capabilities of the
plugin regarding the reconciler | | | | -| `walCapabilities` *string array* | WALCapabilities are the list of capabilities of the
plugin regarding the WAL management | | | | -| `backupCapabilities` *string array* | BackupCapabilities are the list of capabilities of the
plugin regarding the Backup management | | | | -| `restoreJobHookCapabilities` *string array* | RestoreJobHookCapabilities are the list of capabilities of the
plugin regarding the RestoreJobHook management | | | | -| `status` *string* | Status contain the status reported by the plugin through the SetStatusInCluster interface | | | | - -#### PodName - -*Underlying type:* *string* - -PodName is the name of a Pod - -*Appears in:* - -- [ClusterStatus](#clusterstatus) -- [Topology](#topology) - -#### PodSelectorRef - -PodSelectorRef defines a named pod label selector for use in pg_hba rules. -Pods matching the selector in the Cluster's namespace will have their IPs -resolved and made available for pg_hba address expansion via the -`${podselector:NAME}` syntax. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------------------------------------ | -| `name` *string* | Name is the identifier used to reference this selector in pg_hba rules
via the ${podselector:NAME} syntax in the address field. | True | | MinLength: 1
Pattern: `^[a-z]([a-z0-9_-]*[a-z0-9])?$`
| -| `selector` *[LabelSelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#labelselector-v1-meta)* | Selector is a label selector that identifies the pods whose IPs
should be resolved. Only pods in the Cluster's namespace are considered. | True | | | - -#### PodSelectorRefStatus - -PodSelectorRefStatus contains the resolved pod IPs for a named selector. - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| -------------------- | ------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name corresponds to the name in the spec's PodSelectorRef. | True | | | -| `ips` *string array* | IPs is the list of pod IPs matching the selector.
Each IP is a single address (no CIDR notation). | | | | - -#### PodStatus - -*Underlying type:* *string* - -PodStatus represent the possible status of pods - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -#### 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: - - - - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[PodSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podspec-v1-core)* | Specification of the desired behavior of the pod.
More info: | | | | - -#### PodTopologyLabels - -*Underlying type:* *object* - -PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue - -*Appears in:* - -- [Topology](#topology) - -#### Pooler - -Pooler is the Schema for the poolers API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Pooler` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PoolerSpec](#poolerspec)* | Specification of the desired behavior of the Pooler.
More info: | True | | | -| `status` *[PoolerStatus](#poolerstatus)* | Most recently observed status of the Pooler. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `pgBouncerIntegration` *[PgBouncerIntegrationStatus](#pgbouncerintegrationstatus)* | | | | | - -#### 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. - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor`
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | false | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `tls` *[PoolerMonitoringTLSConfiguration](#poolermonitoringtlsconfiguration)* | Configure TLS communication for the metrics endpoint.
Changing tls.enabled option will force a rollout of all instances. | | | | - -#### PoolerMonitoringTLSConfiguration - -PoolerMonitoringTLSConfiguration is the type containing the TLS configuration -for the pooler monitoring - -*Appears in:* - -- [PoolerMonitoringConfiguration](#poolermonitoringconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------- | -------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Enable TLS for the monitoring endpoint.
Changing this option will force a rollout of all instances. | | false | | - -#### PoolerPhase - -*Underlying type:* *string* - -PoolerPhase represents the lifecycle phase of a Pooler. - -*Validation:* - -- Enum: [active paused inactive failed] - -*Appears in:* - -- [PoolerStatus](#poolerstatus) - -| Field | Description | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `active` | PoolerPhaseActive means the pooler is running normally and serving traffic.
| -| `paused` | PoolerPhasePaused means PgBouncer is up and running but holding new client
connections in the queue because spec.pgbouncer.paused is true. The Deployment
keeps reconciling; lifting the pause transitions back to Active.
| -| `inactive` | PoolerPhaseInactive means the pooler cannot make progress because a
prerequisite resource is missing (cluster, secret, certificate). The
controller retries periodically until the prerequisite shows up. Check
status.phaseReason for the specific cause.
| -| `failed` | PoolerPhaseFailed means the pooler cannot be reconciled due to a
configuration error. Check status.phaseReason for details.
| - -#### PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -*Appears in:* - -- [PoolerStatus](#poolerstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------- | -------------------------------------------- | -------- | ------- | ---------- | -| `clientTLS` *[SecretVersion](#secretversion)* | The client TLS secret version | | | | -| `serverTLS` *[SecretVersion](#secretversion)* | The server TLS secret version | | | | -| `serverCA` *[SecretVersion](#secretversion)* | The server CA secret version | | | | -| `clientCA` *[SecretVersion](#secretversion)* | The client CA secret version | | | | -| `pgBouncerSecrets` *[PgBouncerSecrets](#pgbouncersecrets)* | The version of the secrets used by PgBouncer | | | | - -#### PoolerSpec - -PoolerSpec defines the desired state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------------------------------------------------- | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | This is the cluster reference on which the Pooler will work.
Pooler name should never match with any cluster name within the same namespace. | True | | | -| `type` *[PoolerType](#poolertype)* | Type of service to forward traffic to. Default: `rw`. | | rw | Enum: [rw ro r]
| -| `instances` *integer* | The number of replicas we want. Default: 1. | | 1 | | -| `template` *[PodTemplateSpec](#podtemplatespec)* | The template of the Pod to be created | | | | -| `pgbouncer` *[PgBouncerSpec](#pgbouncerspec)* | The PgBouncer configuration | True | | | -| `deploymentStrategy` *[DeploymentStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#deploymentstrategy-v1-apps)* | The deployment strategy to use for pgbouncer to replace existing pods with new ones | | | | -| `monitoring` *[PoolerMonitoringConfiguration](#poolermonitoringconfiguration)* | The configuration of the monitoring infrastructure of this pooler. | | | | -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | Template for the Service to be created | | | | -| `serviceAccountName` *string* | Name of an existing ServiceAccount in the same namespace to use for the pooler.
When specified, the operator will not create a new ServiceAccount
but will use the provided one. This is useful for sharing a single
ServiceAccount across multiple poolers (e.g., for cloud IAM configurations).
If not specified, a ServiceAccount will be created with the pooler name. | | | MaxLength: 253
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| - -#### PoolerStatus - -PoolerStatus defines the observed state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | -------------------------------------------- | -| `secrets` *[PoolerSecrets](#poolersecrets)* | The resource version of the config object | | | | -| `instances` *integer* | The number of pods trying to be scheduled | | | | -| `phase` *[PoolerPhase](#poolerphase)* | Phase summarizes the overall lifecycle state of the Pooler. | | | Enum: [active paused inactive failed]
| -| `phaseReason` *string* | PhaseReason is a human-readable explanation of the current Phase. | | | | -| `image` *string* | Image is the resolved pgbouncer container image that the operator is
using for this Pooler, including any override coming from spec.template.
While Phase is Active or Paused this field reflects what the Deployment
actually runs; while Phase is Inactive or Failed it may carry the last
successfully resolved value (or be empty if the Pooler has never reconciled
successfully). | | | | -| `error` *string* | Error is the latest admission validation error | | | | - -#### PoolerType - -*Underlying type:* *string* - -PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are `rw` and `ro`. - -*Validation:* - -- Enum: [rw ro r] - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -#### PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `parameters` *object (keys:string, values:string)* | PostgreSQL configuration options (postgresql.conf) | | | | -| `synchronous` *[SynchronousReplicaConfiguration](#synchronousreplicaconfiguration)* | Configuration of the PostgreSQL synchronous replication feature | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file).
Use the ${podselector:NAME} syntax to reference a pod selector;
the rule will be expanded for each Pod IP matching that selector. | | | | -| `pg_ident` *string array* | PostgreSQL User Name Maps rules (lines to be appended
to the pg_ident.conf file) | | | | -| `epas` *[EPASConfiguration](#epasconfiguration)* | EDB Postgres Advanced Server specific configurations | | | | -| `syncReplicaElectionConstraint` *[SyncReplicaElectionConstraints](#syncreplicaelectionconstraints)* | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be
set up. | | | | -| `shared_preload_libraries` *string array* | Lists of shared preload libraries to add to the default ones | | | | -| `ldap` *[LDAPConfig](#ldapconfig)* | Options to specify LDAP configuration | | | | -| `promotionTimeout` *integer* | 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 | | | | -| `enableAlterSystem` *boolean* | If this parameter is true, the user will be able to invoke `ALTER SYSTEM`
on this {{name.ln}} Cluster.
This should only be used for debugging and troubleshooting.
Defaults to false. | | | | -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | - -#### PrimaryLeaseConfiguration - -PrimaryLeaseConfiguration configures the timings of the Kubernetes `Lease` -that the primary instance holds and renews to coordinate a safe primary -election. These values map directly onto the underlying Kubernetes -leader-election parameters. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------- | -| `leaseDurationSeconds` *integer* | How long, in seconds, the primary lease is considered valid before it
expires and another instance may acquire it. It must be greater than
`renewDeadlineSeconds`.
Defaults to 15. | | 15 | Minimum: 1
| -| `renewDeadlineSeconds` *integer* | How long, in seconds, the current primary keeps retrying to renew the
lease before giving up and stopping. It must be smaller than
`leaseDurationSeconds`.
Defaults to 10. | | 10 | Minimum: 1
| -| `retryPeriodSeconds` *integer* | How frequently, in seconds, a non-holder instance retries acquiring or
renewing the lease.
Defaults to 2. | | 2 | Minimum: 1
| -| `releasedLeaseDurationSeconds` *integer* | The TTL, in seconds, written when the primary explicitly releases the
lease on a clean shutdown, allowing a replica to promote without waiting
for the full lease duration to expire.
Defaults to 1. | | 1 | Minimum: 1
| - -#### PrimaryUpdateMethod - -*Underlying type:* *string* - -PrimaryUpdateMethod defines the method to use when upgrading -the primary instance of the cluster as part of rolling updates. -The default method is "restart" - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `switchover` | PrimaryUpdateMethodSwitchover means that the operator will switchover to another updated
replica when it needs to upgrade the primary instance.
Note: when using this method, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process.
| -| `restart` | PrimaryUpdateMethodRestart means that the operator will restart the primary instance in-place
when it needs to upgrade it
| - -#### PrimaryUpdateStrategy - -*Underlying type:* *string* - -PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `supervised` | PrimaryUpdateStrategySupervised means that the operator need to wait for the
user to manually issue a switchover request before updating the primary
server (`supervised`)
| -| `unsupervised` | PrimaryUpdateStrategyUnsupervised means that the operator will proceed with the
selected PrimaryUpdateMethod to another updated replica and then automatically update
the primary server (`unsupervised`, default)
| - -#### Probe - -Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic. - -*Appears in:* - -- [LivenessProbe](#livenessprobe) -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | - -#### ProbeStrategyType - -*Underlying type:* *string* - -ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready - -*Appears in:* - -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `pg_isready` | ProbeStrategyPgIsReady means that the pg_isready tool is used to determine
whether PostgreSQL is started up
| -| `streaming` | ProbeStrategyStreaming means that pg_isready is positive and the replica is
connected via streaming replication to the current primary and the lag is, if specified,
within the limit.
| -| `query` | ProbeStrategyQuery means that the server is able to connect to the superuser database
and able to execute a simple query like "-- ping"
| - -#### ProbeWithStrategy - -ProbeWithStrategy is the configuration of the startup probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------------------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `type` *[ProbeStrategyType](#probestrategytype)* | The probe strategy | | | Enum: [pg_isready streaming query]
| -| `maximumLag` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Lag limit. Used only for `streaming` strategy | | | | - -#### ProbesConfiguration - -ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `startup` *[ProbeWithStrategy](#probewithstrategy)* | The startup probe configuration | True | | | -| `liveness` *[LivenessProbe](#livenessprobe)* | The liveness probe configuration | True | | | -| `readiness` *[ProbeWithStrategy](#probewithstrategy)* | The readiness probe configuration | True | | | - -#### Publication - -Publication is the Schema for the publications API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Publication` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PublicationSpec](#publicationspec)* | | True | | | -| `status` *[PublicationStatus](#publicationstatus)* | | True | | | - -#### PublicationReclaimPolicy - -*Underlying type:* *string* - -PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications. - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | PublicationReclaimDelete means the publication will be deleted from Kubernetes on release
from its claim.
| -| `retain` | PublicationReclaimRetain means the publication will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### PublicationSpec - -PublicationSpec defines the desired state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "publisher" | True | | | -| `name` *string* | The name of the publication inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "publisher" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Publication parameters part of the `WITH` clause as expected by
PostgreSQL `CREATE PUBLICATION` command | | | | -| `target` *[PublicationTarget](#publicationtarget)* | Target of the publication as expected by PostgreSQL `CREATE PUBLICATION` command | True | | | -| `publicationReclaimPolicy` *[PublicationReclaimPolicy](#publicationreclaimpolicy)* | The policy for end-of-life maintenance of this publication | | retain | Enum: [delete retain]
| - -#### PublicationStatus - -PublicationStatus defines the observed state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the publication was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### PublicationTarget - -PublicationTarget is what this publication should publish - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------- | -| `allTables` *boolean* | Marks the publication as one that replicates changes for all tables
in the database, including tables created in the future.
Corresponding to `FOR ALL TABLES` in PostgreSQL. | | | | -| `objects` *[PublicationTargetObject](#publicationtargetobject) array* | Just the following schema objects | | | MaxItems: 100000
| - -#### PublicationTargetObject - -PublicationTargetObject is an object to publish - -*Appears in:* - -- [PublicationTarget](#publicationtarget) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `tablesInSchema` *string* | Marks the publication as one that replicates changes for all tables
in the specified list of schemas, including tables created in the
future. Corresponding to `FOR TABLES IN SCHEMA` in PostgreSQL. | | | | -| `table` *[PublicationTargetTable](#publicationtargettable)* | Specifies a list of tables to add to the publication. Corresponding
to `FOR TABLE` in PostgreSQL. | | | | - -#### PublicationTargetTable - -PublicationTargetTable is a table to publish - -*Appears in:* - -- [PublicationTargetObject](#publicationtargetobject) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `only` *boolean* | Whether to limit to the table only or include all its descendants | | | | -| `name` *string* | The table name | True | | | -| `schema` *string* | The schema name | | | | -| `columns` *string array* | The columns to publish | | | | - -#### RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backupID` *string* | 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. | | | | -| `targetTLI` *string* | The target timeline ("latest" or a positive integer) | | | | -| `targetXID` *string* | The target transaction ID | | | | -| `targetName` *string* | The target name (to be previously created
with `pg_create_restore_point`) | | | | -| `targetLSN` *string* | The target LSN (Log Sequence Number) | | | | -| `targetTime` *string* | The target time as a timestamp in RFC3339 format or PostgreSQL timestamp format.
Timestamps without an explicit timezone are interpreted as UTC. | | | | -| `targetImmediate` *boolean* | End recovery as soon as a consistent state is reached | | | | -| `exclusive` *boolean* | Set the target to be exclusive. If omitted, defaults to false, so that
in Postgres, `recovery_target_inclusive` will be true | | | | - -#### ReplicaClusterConfiguration - -ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------- | -| `self` *string* | Self defines the name of this cluster. It is used to determine if this is a primary
or a replica cluster, comparing it with `primary` | | | | -| `primary` *string* | Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the
topology specified in externalClusters | | | | -| `source` *string* | The name of the external cluster which is the replication origin | True | | MinLength: 1
| -| `enabled` *boolean* | 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. | | | | -| `promotionToken` *string* | A demotion token generated by an external cluster used to
check if the promotion requirements are met. | | | | -| `minApplyDelay` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | When replica mode is enabled, this parameter allows you to replay
transactions only when the system time is at least the configured
time past the commit time. This provides an opportunity to correct
data loss errors. Note that when this parameter is set, a promotion
token cannot be used. | | | | - -#### ReplicationSlotsConfiguration - -ReplicationSlotsConfiguration encapsulates the configuration -of replication slots - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------- | -| `highAvailability` *[ReplicationSlotsHAConfiguration](#replicationslotshaconfiguration)* | Replication slots for high availability configuration | | | | -| `updateInterval` *integer* | Standby will update the status of the local replication slots
every `updateInterval` seconds (default 30). | | | Minimum: 1
| -| `synchronizeReplicas` *[SynchronizeReplicasConfiguration](#synchronizereplicasconfiguration)* | Configures the synchronization of the user defined physical replication slots | | | | - -#### 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. - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------ | -| `enabled` *boolean* | 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. | | | | -| `slotPrefix` *string* | 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_`. | | | Pattern: `^[0-9a-z_]*$`
| -| `synchronizeLogicalDecoding` *boolean* | When enabled, the operator automatically manages synchronization of logical
decoding (replication) slots across high-availability clusters.
Requires one of the following conditions:
- PostgreSQL version 17 or later
- PostgreSQL version < 17 with pg_failover_slots extension enabled | | | | - -#### 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: - -*Appears in:* - -- [DatabaseRoleSpec](#databaserolespec) -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the role | True | | | -| `comment` *string* | Description of the role | | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the role is `present` or `absent` - defaults to "present" | | present | Enum: [present absent]
| -| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present).
If null, the password will be ignored unless DisablePassword is set.
When set, the secret must follow the `kubernetes.io/basic-auth` format
and contain both a `username` and a `password` field. | | | | -| `connectionLimit` *integer* | If the role can log in, this specifies how many concurrent
connections the role can make. `-1` (the default) means no limit. | | -1 | | -| `validUntil` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Date and time after which the role's password is no longer valid.
When omitted, the password will never expire (default). | | | | -| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty.
Changes to the list are applied to an existing role through
`GRANT` and `REVOKE` statements, not only at role creation. | | | | -| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Default is `true`. | | true | | -| `disablePassword` *boolean* | DisablePassword indicates that a role's password should be set to NULL in Postgres | | | | -| `superuser` *boolean* | 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`. | | | | -| `createdb` *boolean* | 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. | | | | -| `createrole` *boolean* | 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`. | | | | -| `login` *boolean* | 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`. | | | | -| `replication` *boolean* | 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`. | | | | -| `bypassrls` *boolean* | Whether a role bypasses every row-level security (RLS) policy.
Default is `false`. | | | | - -#### RoleStatus - -*Underlying type:* *string* - -RoleStatus represents the status of a managed role in the cluster - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | -| ------------------------ | ----------------------------------------------------------------------------------------------------- | -| `reconciled` | RoleStatusReconciled indicates the role in DB matches the Spec
| -| `not-managed` | RoleStatusNotManaged indicates the role is not in the Spec, therefore not managed
| -| `pending-reconciliation` | RoleStatusPendingReconciliation indicates the role in Spec requires updated/creation in DB
| -| `reserved` | RoleStatusReserved indicates this is one of the roles reserved by the operator. E.g. `postgres`
| - -#### SQLRefs - -SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------- | ------- | ---------- | -| `secretRefs` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | SecretRefs holds a list of references to Secrets | | | | -| `configMapRefs` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | ConfigMapRefs holds a list of references to ConfigMaps | | | | - -#### ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ScheduledBackup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ScheduledBackupSpec](#scheduledbackupspec)* | Specification of the desired behavior of the ScheduledBackup.
More info: | True | | | -| `status` *[ScheduledBackupStatus](#scheduledbackupstatus)* | Most recently observed status of the ScheduledBackup. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `suspend` *boolean* | If this backup is suspended or not | | | | -| `immediate` *boolean* | If the first backup has to be immediately start after creation or not | | | | -| `schedule` *string* | The schedule does not follow the same format used in Kubernetes CronJobs
as it includes an additional seconds specifier,
see | True | | | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `backupOwnerReference` *string* | 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
| | none | Enum: [none self cluster]
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `lastCheckTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | The latest time the schedule | | | | -| `lastScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Information when was the last time that backup was successfully scheduled. | | | | -| `nextScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Next time we will run a backup | | | | -| `error` *string* | Error is the latest admission validation error | | | | - -#### SchemaSpec - -SchemaSpec configures a schema in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `owner` *string* | The role name of the user who owns the schema inside PostgreSQL.
It maps to the `AUTHORIZATION` parameter of `CREATE SCHEMA` and the
`OWNER TO` command of `ALTER SCHEMA`. | True | | | - -#### SecretVersion - -SecretVersion contains a secret name and its ResourceVersion - -*Appears in:* - -- [PgBouncerSecrets](#pgbouncersecrets) -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| ------------------ | --------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the secret | | | | -| `version` *string* | The ResourceVersion of the secret | | | | - -#### SecretsResourceVersion - -SecretsResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `superuserSecretVersion` *string* | The resource version of the "postgres" user secret | | | | -| `replicationSecretVersion` *string* | The resource version of the "streaming_replica" user secret | | | | -| `applicationSecretVersion` *string* | The resource version of the "app" user secret | | | | -| `managedRoleSecretVersion` *object (keys:string, values:string)* | The resource versions of the managed roles secrets | | | | -| `caSecretVersion` *string* | Unused. Retained for compatibility with old versions. | | | | -| `clientCaSecretVersion` *string* | The resource version of the PostgreSQL client-side CA secret version | | | | -| `serverCaSecretVersion` *string* | The resource version of the PostgreSQL server-side CA secret version | | | | -| `serverSecretVersion` *string* | The resource version of the PostgreSQL server-side secret version | | | | -| `barmanEndpointCA` *string* | The resource version of the Barman Endpoint CA if provided | | | | -| `externalClusterSecretVersion` *object (keys:string, values:string)* | The resource versions of the external cluster secrets | | | | -| `metrics` *object (keys:string, values:string)* | A map with the versions of all the secrets used to pass metrics.
Map keys are the secret names, map values are the versions | | | | - -#### ServerSpec - -ServerSpec configures a server of a foreign data wrapper - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `fdw` *string* | The name of the Foreign Data Wrapper (FDW) | True | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the server
(key is the option name, value is the option value). | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the server are granted or revoked. | | | | - -#### ServiceAccountTemplate - -ServiceAccountTemplate contains the template needed to generate the service accounts - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | - -#### ServiceSelectorType - -*Underlying type:* *string* - -ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only - -*Validation:* - -- Enum: [rw r ro] - -*Appears in:* - -- [ManagedService](#managedservice) -- [ManagedServices](#managedservices) - -| Field | Description | -| ----- | ----------------------------------------------------------- | -| `rw` | ServiceSelectorTypeRW selects the read-write service.
| -| `r` | ServiceSelectorTypeR selects the read service.
| -| `ro` | ServiceSelectorTypeRO selects the read-only service.
| - -#### ServiceTemplateSpec - -ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation. - -*Appears in:* - -- [ManagedService](#managedservice) -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[ServiceSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#servicespec-v1-core)* | Specification of the desired behavior of the service.
More info: | | | | - -#### ServiceUpdateStrategy - -*Underlying type:* *string* - -ServiceUpdateStrategy describes how the changes to the managed service should be handled - -*Validation:* - -- Enum: [patch replace] - -*Appears in:* - -- [ManagedService](#managedservice) - -#### SnapshotOwnerReference - -*Underlying type:* *string* - -SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to. - -*Appears in:* - -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | -| --------- | ------------------------------------------------------------------------------------------------- | -| `none` | SnapshotOwnerReferenceNone indicates that the snapshot does not have any owner reference.
| -| `backup` | SnapshotOwnerReferenceBackup indicates that the snapshot is owned by the backup resource.
| -| `cluster` | SnapshotOwnerReferenceCluster indicates that the snapshot is owned by the cluster resource.
| - -#### SnapshotType - -*Underlying type:* *string* - -SnapshotType is a type of allowed import - -*Appears in:* - -- [Import](#import) - -| Field | Description | -| -------------- | ----------------------------------------------------------------------------------- | -| `monolith` | MonolithSnapshotType indicates to execute the monolith clone typology
| -| `microservice` | MicroserviceSnapshotType indicates to execute the microservice clone typology
| - -#### StorageConfiguration - -StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `storageClass` *string* | 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` *string* | 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. | | | | -| `resizeInUseVolumes` *boolean* | Resize existent PVCs, defaults to true | | true | | -| `pvcTemplate` *[PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#persistentvolumeclaimspec-v1-core)* | Template to be used to generate the Persistent Volume Claim | | | | - -#### Subscription - -Subscription is the Schema for the subscriptions API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Subscription` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[SubscriptionSpec](#subscriptionspec)* | | True | | | -| `status` *[SubscriptionStatus](#subscriptionstatus)* | | True | | | - -#### SubscriptionReclaimPolicy - -*Underlying type:* *string* - -SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions. - -*Appears in:* - -- [SubscriptionSpec](#subscriptionspec) - -| Field | Description | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `delete` | SubscriptionReclaimDelete means the subscription will be deleted from Kubernetes on release
from its claim.
| -| `retain` | SubscriptionReclaimRetain means the subscription will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### SubscriptionSpec - -SubscriptionSpec defines the desired state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "subscriber" | True | | | -| `name` *string* | The name of the subscription inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "subscriber" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Subscription parameters included in the `WITH` clause of the PostgreSQL
`CREATE SUBSCRIPTION` command. Most parameters cannot be changed
after the subscription is created and will be ignored if modified
later, except for a limited set documented at:
| | | | -| `publicationName` *string* | The name of the publication inside the PostgreSQL database in the
"publisher" | True | | | -| `publicationDBName` *string* | The name of the database containing the publication on the external
cluster. Defaults to the one in the external cluster definition. | | | | -| `externalClusterName` *string* | The name of the external cluster with the publication ("publisher") | True | | | -| `subscriptionReclaimPolicy` *[SubscriptionReclaimPolicy](#subscriptionreclaimpolicy)* | The policy for end-of-life maintenance of this subscription | | retain | Enum: [delete retain]
| - -#### SubscriptionStatus - -SubscriptionStatus defines the observed state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the subscription was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### SwitchReplicaClusterStatus - -SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `inProgress` *boolean* | InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster. | | | | - -#### 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. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `nodeLabelsAntiAffinity` *string array* | A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not | | | | -| `enabled` *boolean* | This flag enables the constraints for sync replicas | True | | | - -#### SynchronizeReplicasConfiguration - -SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | When set to true, every replication slot that is on the primary is synchronized on each standby | True | | | -| `excludePatterns` *string array* | List of regular expression patterns to match the names of replication slots to be excluded (by default empty) | | | | - -#### SynchronousReplicaConfiguration - -SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also `.spec.minSyncReplicas` and `.spec.maxSyncReplicas` -need to be considered. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------- | -| `method` *[SynchronousReplicaConfigurationMethod](#synchronousreplicaconfigurationmethod)* | Method to select synchronous replication standbys from the listed
servers, accepting 'any' (quorum-based synchronous replication) or
'first' (priority-based synchronous replication) as values. | True | | Enum: [any first]
| -| `number` *integer* | Specifies the number of synchronous standby servers that
transactions must wait for responses from. | True | | | -| `maxStandbyNamesFromCluster` *integer* | Specifies the maximum number of local cluster pods that can be
automatically included in the `synchronous_standby_names` option in
PostgreSQL. | | | | -| `standbyNamesPre` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` before local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `standbyNamesPost` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` after local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `dataDurability` *[DataDurabilityLevel](#datadurabilitylevel)* | If set to "required", data durability is strictly enforced. Write operations
with synchronous commit settings (`on`, `remote_write`, or `remote_apply`) will
block if there are insufficient healthy replicas, ensuring data persistence.
If set to "preferred", data durability is maintained when healthy replicas
are available, but the required number of instances will adjust dynamically
if replicas become unavailable. This setting relaxes strict durability enforcement
to allow for operational continuity. This setting is only applicable if both
`standbyNamesPre` and `standbyNamesPost` are unset (empty). | | | Enum: [required preferred]
| -| `failoverQuorum` *boolean* | FailoverQuorum enables a quorum-based check before failover, improving
data durability and safety during failover events in {{name.ln}}-managed
PostgreSQL clusters. | | | | - -#### SynchronousReplicaConfigurationMethod - -*Underlying type:* *string* - -SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -#### TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -*Appears in:* - -- [EPASConfiguration](#epasconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | True if we want to have TDE enabled | | | | -| `secretKeyRef` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Reference to the secret that contains the encryption key | | | | -| `wrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | WrapCommand is the encrypt command provided by the user | | | | -| `unwrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | UnwrapCommand is the decryption command provided by the user | | | | -| `passphraseCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | PassphraseCommand is the command executed to get the passphrase that will be
passed to the OpenSSL command to encrypt and decrypt | | | | - -#### TablespaceConfiguration - -TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the tablespace | True | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | The storage configuration for the tablespace | True | | | -| `owner` *[DatabaseRoleRef](#databaseroleref)* | Owner is the PostgreSQL user owning the tablespace | | | | -| `temporary` *boolean* | When set to true, the tablespace will be added as a `temp_tablespaces`
entry 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. | | false | | - -#### TablespaceState - -TablespaceState represents the state of a tablespace in a cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | -------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the tablespace | True | | | -| `owner` *string* | Owner is the PostgreSQL user owning the tablespace | | | | -| `state` *[TablespaceStatus](#tablespacestatus)* | State is the latest reconciliation state | True | | | -| `error` *string* | Error is the reconciliation error, if any | | | | - -#### TablespaceStatus - -*Underlying type:* *string* - -TablespaceStatus represents the status of a tablespace in the cluster - -*Appears in:* - -- [TablespaceState](#tablespacestate) - -| Field | Description | -| ------------ | -------------------------------------------------------------------------------------------------------- | -| `reconciled` | TablespaceStatusReconciled indicates the tablespace in DB matches the Spec
| -| `pending` | TablespaceStatusPendingReconciliation indicates the tablespace in Spec requires creation in the DB
| - -#### Topology - -Topology contains the cluster topology - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *object (keys:[PodName](#podname), values:[PodTopologyLabels](#podtopologylabels))* | Instances contains the pod topology of the instances | | | | -| `nodesUsed` *integer* | 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` *boolean* | SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors
in synchronous replica election in case of failures | | | | - -#### UsageSpec - -UsageSpec configures a usage for a foreign data wrapper - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------- | -------- | ------- | --------------------------- | -| `name` *string* | Name of the usage | True | | | -| `type` *[UsageSpecType](#usagespectype)* | The type of usage | | grant | Enum: [grant revoke]
| - -#### UsageSpecType - -*Underlying type:* *string* - -UsageSpecType describes the type of usage specified in the `usage` field of the -`Database` object. - -*Appears in:* - -- [UsageSpec](#usagespec) - -| Field | Description | -| -------- | -------------------------------------------------------------------------------------------------------- | -| `grant` | GrantUsageSpecType indicates a grant usage permission.
The default usage permission is grant.
| -| `revoke` | RevokeUsageSpecType indicates a revoke usage permission.
| - -#### VolumeSnapshotConfiguration - -VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups. - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------- | ---------------------------------- | -| `labels` *object (keys:string, values:string)* | Labels are key-value pairs that will be added to .metadata.labels snapshot resources. | | | | -| `annotations` *object (keys:string, values:string)* | Annotations key-value pairs that will be added to .metadata.annotations snapshot resources. | | | | -| `className` *string* | 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` *string* | WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim. | | | | -| `tablespaceClassName` *object (keys:string, values:string)* | TablespaceClassName specifies the Snapshot Class to be used for the tablespaces.
defaults to the PGDATA Snapshot Class, if set | | | | -| `snapshotOwnerReference` *[SnapshotOwnerReference](#snapshotownerreference)* | SnapshotOwnerReference indicates the type of owner reference the snapshot should have | | none | Enum: [none cluster backup]
| -| `online` *boolean* | Whether the default type of backup with volume snapshots is
online/hot (`true`, default) or offline/cold (`false`) | | true | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots | | { immediateCheckpoint:false waitForArchive:true } | | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.6.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.6.0.mdx deleted file mode 100644 index 33e74c97c07..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.6.0.mdx +++ /dev/null @@ -1,344 +0,0 @@ ---- -title: 'API Reference - v0.6.0' -navTitle: v0.6.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1alpha1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - - - -- [Backup](#backup) -- [BackupList](#backuplist) -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [AffinityConfiguration](#affinityconfiguration) -- [BackupConfiguration](#backupconfiguration) -- [BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) -- [BootstrapConfiguration](#bootstrapconfiguration) -- [BootstrapInitDB](#bootstrapinitdb) -- [BootstrapRecovery](#bootstraprecovery) -- [Cluster](#cluster) -- [ClusterList](#clusterlist) -- [ClusterSpec](#clusterspec) -- [ClusterStatus](#clusterstatus) -- [DataBackupConfiguration](#databackupconfiguration) -- [NodeMaintenanceWindow](#nodemaintenancewindow) -- [PostgresConfiguration](#postgresconfiguration) -- [RecoveryTarget](#recoverytarget) -- [RollingUpdateStatus](#rollingupdatestatus) -- [S3Credentials](#s3credentials) -- [StorageConfiguration](#storageconfiguration) -- [WalBackupConfiguration](#walbackupconfiguration) -- [ScheduledBackup](#scheduledbackup) -- [ScheduledBackupList](#scheduledbackuplist) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [ScheduledBackupStatus](#scheduledbackupstatus) - -## Backup - -Backup is the Schema for the backups API - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the backup. More info: | [BackupSpec](#backupspec) | false | -| status | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#backupstatus) | false | - -## BackupList - -BackupList contains a list of Backup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of backups | [][Backup](#backup) | true | - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Field | Description | Scheme | Required | -| ------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| encryption | Encryption method required to S3 API | string | false | -| backupId | The ID of the Barman backup | string | false | -| phase | The last backup status | BackupPhase | false | -| startedAt | When the backup was started | \*metav1.Time | false | -| stoppedAt | When the backup was terminated | \*metav1.Time | false | -| error | The detected error | string | false | -| commandOutput | The backup command output | string | false | -| commandError | The backup command output | string | false | - -## AffinityConfiguration - -AffinityConfiguration contains the info we need to create the affinity rules for Pods - -| Field | Description | Scheme | Required | -| --------------------- | ----------------------------------------------------------------------------------------------- | ------ | -------- | -| enablePodAntiAffinity | Should we enable anti affinity or not? | bool | true | -| topologyKey | TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that | string | true | - -## 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 - -| Field | Description | Scheme | Required | -| ----------------- | ------------------------------------------------- | ------------------------------------------------------------------- | -------- | -| barmanObjectStore | The configuration for the barman-cloud tool suite | \*[BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) | false | - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Field | Description | Scheme | Required | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| 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. | \*[WalBackupConfiguration](#walbackupconfiguration) | false | -| 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. | \*[DataBackupConfiguration](#databackupconfiguration) | false | - -## 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. - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------- | ----------------------------------------- | -------- | -| initdb | Bootstrap the cluster via initdb | \*[BootstrapInitDB](#bootstrapinitdb) | false | -| recovery | Bootstrap the cluster from a backup | \*[BootstrapRecovery](#bootstraprecovery) | false | - -## BootstrapInitDB - -BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------- | -| database | Name of the database used by the application. Default: `app`. | string | true | -| owner | Name of the owner of the database in the instance to be used by applications. Defaults to the value of the `database` key. | string | true | -| 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 | \*corev1.LocalObjectReference | false | -| redwood | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | false | -| options | The list of options that must be passed to initdb when creating the cluster | \[]string | false | - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -------- | -| backup | The backup we need to restore | corev1.LocalObjectReference | true | -| recoveryTarget | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | \*[RecoveryTarget](#recoverytarget) | false | - -## Cluster - -Cluster is the Schema for the postgresql API - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#clusterspec) | false | -| status | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#clusterstatus) | false | - -## ClusterList - -ClusterList contains a list of Cluster - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][Cluster](#cluster) | true | - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Field | Description | Scheme | Required | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- | -------- | -| description | Description of this PostgreSQL cluster | string | false | -| imageName | Name of the container image | string | false | -| postgresUID | The UID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| postgresGID | The GID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| instances | Number of instances required in the cluster | int32 | true | -| minSyncReplicas | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | false | -| 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. | int32 | false | -| postgresql | Configuration of the PostgreSQL server | [PostgresConfiguration](#postgresconfiguration) | false | -| bootstrap | Instructions to bootstrap this cluster | \*[BootstrapConfiguration](#bootstrapconfiguration) | false | -| superuserSecret | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | \*corev1.LocalObjectReference | false | -| imagePullSecrets | 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. | \[]corev1.LocalObjectReference | false | -| storage | Configuration of the storage of the instances | [StorageConfiguration](#storageconfiguration) | false | -| startDelay | The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 30) | int32 | false | -| stopDelay | The time in seconds that is allowed for a PostgreSQL instance node to gracefully shutdown (default 30) | int32 | false | -| affinity | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#affinityconfiguration) | false | -| resources | Resources requirements of every generated Pod. Please refer to for more information. | corev1.ResourceRequirements | false | -| primaryUpdateStrategy | 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 | false | -| backup | The configuration to be used for backups | \*[BackupConfiguration](#backupconfiguration) | false | -| nodeMaintenanceWindow | Define a maintenance window for the Kubernetes nodes | \*[NodeMaintenanceWindow](#nodemaintenancewindow) | false | -| licenseKey | 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. | string | false | - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------- | -------- | -| instances | Total number of instances in the cluster | int32 | false | -| readyInstances | Total number of ready instances in the cluster | int32 | false | -| instancesStatus | Instances status | map[utils.PodStatus][]string | false | -| latestGeneratedNode | ID of the latest generated node (used to avoid node name clashing) | int32 | false | -| currentPrimary | Current primary instance | string | false | -| targetPrimary | Target primary instance, this is different from the previous one during a switchover or a failover | string | false | -| pvcCount | How many PVCs have been created by this cluster | int32 | false | -| jobCount | How many Jobs have been created by this cluster | int32 | false | -| danglingPVC | List of all the PVCs created by this cluster and still available which are not attached to a Pod | \[]string | false | -| licenseStatus | Status of the license | licensekey.Status | false | -| writeService | Current write pod | string | false | -| readService | Current list of read pods | string | false | -| phase | Current phase of the cluster | string | false | -| phaseReason | Reason for the current phase | string | false | - -## DataBackupConfiguration - -DataBackupConfiguration is the configuration of the backup of the data directory - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| 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` or `bzip2`. | CompressionType | false | -| 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 | false | -| 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 | false | -| jobs | The number of parallel jobs to be used to upload the backup, defaults to 2 | \*int32 | false | - -## NodeMaintenanceWindow - -NodeMaintenanceWindow contains information that the operator will use while upgrading the underlying node. - -This option is only useful when using local storage, as the Pods can't be freely moved between nodes in that configuration. - -| Field | Description | Scheme | Required | -| ---------- | ------------------------------------------------------------------------------------------ | ------ | -------- | -| inProgress | Is there a node maintenance activity in progress? | bool | true | -| reusePVC | Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere) | \*bool | true | - -## PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -| Field | Description | Scheme | Required | -| ---------- | ----------------------------------------------------------------------------------------- | ----------------- | -------- | -| parameters | PostgreSQL configuration options (postgresql.conf) | map[string]string | false | -| pg_hba | PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) | \[]string | false | - -## RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive. - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------- | ------ | -------- | -| targetTLI | The target timeline (\\"latest\\", \\"current\\" or a positive integer) | string | false | -| targetXID | The target transaction ID | string | false | -| targetName | The target name (to be previously created with `pg_create_restore_point`) | string | false | -| targetLSN | The target LSN (Log Sequence Number) | string | false | -| targetTime | The target time, in any unambiguous representation allowed by PostgreSQL | string | false | -| targetImmediate | End recovery as soon as a consistent state is reached | \*bool | false | -| exclusive | Set the target to be exclusive (defaults to true) | \*bool | false | - -## RollingUpdateStatus - -RollingUpdateStatus contains the information about an instance which is being updated - -| Field | Description | Scheme | Required | -| --------- | ----------------------------------- | ----------- | -------- | -| imageName | The image which we put into the Pod | string | true | -| startedAt | When the update has been started | metav1.Time | false | - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Field | Description | Scheme | Required | -| --------------- | -------------------------------------- | ------------------------ | -------- | -| accessKeyId | The reference to the access key id | corev1.SecretKeySelector | true | -| secretAccessKey | The reference to the secret access key | corev1.SecretKeySelector | true | - -## StorageConfiguration - -StorageConfiguration is the configuration of the storage of the PostgreSQL instances - -| Field | Description | Scheme | Required | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------- | -------- | -| 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 | false | -| size | Size of the storage. Required if not already specified in the PVC template. | string | true | -| pvcTemplate | Template to be used to generate the Persistent Volume Claim | \*corev1.PersistentVolumeClaimSpec | false | - -## WalBackupConfiguration - -WalBackupConfiguration is the configuration of the backup of the WAL stream - -| Field | Description | Scheme | Required | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| compression | Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), `gzip` or `bzip2`. | CompressionType | false | -| 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 | false | - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#scheduledbackupspec) | false | -| status | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#scheduledbackupstatus) | false | - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][ScheduledBackup](#scheduledbackup) | true | - -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| suspend | If this backup is suspended of not | \*bool | false | -| schedule | The schedule in Cron format, see . | string | true | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Field | Description | Scheme | Required | -| ---------------- | -------------------------------------------------------------------------- | ------------- | -------- | -| lastCheckTime | The latest time the schedule | \*metav1.Time | false | -| lastScheduleTime | Information when was the last time that backup was successfully scheduled. | \*metav1.Time | false | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.7.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.7.0.mdx deleted file mode 100644 index 534240c3fe8..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.7.0.mdx +++ /dev/null @@ -1,345 +0,0 @@ ---- -title: 'API Reference - v0.7.0' -navTitle: v0.7.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1alpha1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - - - -- [Backup](#backup) -- [BackupList](#backuplist) -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [AffinityConfiguration](#affinityconfiguration) -- [BackupConfiguration](#backupconfiguration) -- [BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) -- [BootstrapConfiguration](#bootstrapconfiguration) -- [BootstrapInitDB](#bootstrapinitdb) -- [BootstrapRecovery](#bootstraprecovery) -- [Cluster](#cluster) -- [ClusterList](#clusterlist) -- [ClusterSpec](#clusterspec) -- [ClusterStatus](#clusterstatus) -- [DataBackupConfiguration](#databackupconfiguration) -- [NodeMaintenanceWindow](#nodemaintenancewindow) -- [PostgresConfiguration](#postgresconfiguration) -- [RecoveryTarget](#recoverytarget) -- [RollingUpdateStatus](#rollingupdatestatus) -- [S3Credentials](#s3credentials) -- [StorageConfiguration](#storageconfiguration) -- [WalBackupConfiguration](#walbackupconfiguration) -- [ScheduledBackup](#scheduledbackup) -- [ScheduledBackupList](#scheduledbackuplist) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [ScheduledBackupStatus](#scheduledbackupstatus) - -## Backup - -Backup is the Schema for the backups API - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the backup. More info: | [BackupSpec](#backupspec) | false | -| status | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#backupstatus) | false | - -## BackupList - -BackupList contains a list of Backup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of backups | [][Backup](#backup) | true | - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Field | Description | Scheme | Required | -| ------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| encryption | Encryption method required to S3 API | string | false | -| backupId | The ID of the Barman backup | string | false | -| phase | The last backup status | BackupPhase | false | -| startedAt | When the backup was started | \*metav1.Time | false | -| stoppedAt | When the backup was terminated | \*metav1.Time | false | -| error | The detected error | string | false | -| commandOutput | The backup command output | string | false | -| commandError | The backup command output | string | false | - -## AffinityConfiguration - -AffinityConfiguration contains the info we need to create the affinity rules for Pods - -| Field | Description | Scheme | Required | -| --------------------- | ----------------------------------------------------------------------------------------------- | ------ | -------- | -| enablePodAntiAffinity | Should we enable anti affinity or not? | bool | true | -| topologyKey | TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that | string | true | - -## 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 - -| Field | Description | Scheme | Required | -| ----------------- | ------------------------------------------------- | ------------------------------------------------------------------- | -------- | -| barmanObjectStore | The configuration for the barman-cloud tool suite | \*[BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) | false | - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Field | Description | Scheme | Required | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| 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. | \*[WalBackupConfiguration](#walbackupconfiguration) | false | -| 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. | \*[DataBackupConfiguration](#databackupconfiguration) | false | - -## 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. - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------- | ----------------------------------------- | -------- | -| initdb | Bootstrap the cluster via initdb | \*[BootstrapInitDB](#bootstrapinitdb) | false | -| recovery | Bootstrap the cluster from a backup | \*[BootstrapRecovery](#bootstraprecovery) | false | - -## BootstrapInitDB - -BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------- | -| database | Name of the database used by the application. Default: `app`. | string | true | -| owner | Name of the owner of the database in the instance to be used by applications. Defaults to the value of the `database` key. | string | true | -| 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 | \*corev1.LocalObjectReference | false | -| redwood | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | false | -| options | The list of options that must be passed to initdb when creating the cluster | \[]string | false | - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -------- | -| backup | The backup we need to restore | corev1.LocalObjectReference | true | -| recoveryTarget | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | \*[RecoveryTarget](#recoverytarget) | false | - -## Cluster - -Cluster is the Schema for the postgresql API - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#clusterspec) | false | -| status | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#clusterstatus) | false | - -## ClusterList - -ClusterList contains a list of Cluster - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][Cluster](#cluster) | true | - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Field | Description | Scheme | Required | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- | -------- | -| description | Description of this PostgreSQL cluster | string | false | -| imageName | Name of the container image | string | false | -| postgresUID | The UID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| postgresGID | The GID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| instances | Number of instances required in the cluster | int32 | true | -| minSyncReplicas | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | false | -| 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. | int32 | false | -| postgresql | Configuration of the PostgreSQL server | [PostgresConfiguration](#postgresconfiguration) | false | -| bootstrap | Instructions to bootstrap this cluster | \*[BootstrapConfiguration](#bootstrapconfiguration) | false | -| superuserSecret | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | \*corev1.LocalObjectReference | false | -| imagePullSecrets | 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. | \[]corev1.LocalObjectReference | false | -| storage | Configuration of the storage of the instances | [StorageConfiguration](#storageconfiguration) | false | -| startDelay | The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 30) | int32 | false | -| stopDelay | The time in seconds that is allowed for a PostgreSQL instance node to gracefully shutdown (default 30) | int32 | false | -| affinity | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#affinityconfiguration) | false | -| resources | Resources requirements of every generated Pod. Please refer to for more information. | corev1.ResourceRequirements | false | -| primaryUpdateStrategy | 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 | false | -| backup | The configuration to be used for backups | \*[BackupConfiguration](#backupconfiguration) | false | -| nodeMaintenanceWindow | Define a maintenance window for the Kubernetes nodes | \*[NodeMaintenanceWindow](#nodemaintenancewindow) | false | -| licenseKey | 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. | string | false | - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------- | -------- | -| instances | Total number of instances in the cluster | int32 | false | -| readyInstances | Total number of ready instances in the cluster | int32 | false | -| instancesStatus | Instances status | map[utils.PodStatus][]string | false | -| latestGeneratedNode | ID of the latest generated node (used to avoid node name clashing) | int32 | false | -| currentPrimary | Current primary instance | string | false | -| targetPrimary | Target primary instance, this is different from the previous one during a switchover or a failover | string | false | -| pvcCount | How many PVCs have been created by this cluster | int32 | false | -| jobCount | How many Jobs have been created by this cluster | int32 | false | -| danglingPVC | List of all the PVCs created by this cluster and still available which are not attached to a Pod | \[]string | false | -| licenseStatus | Status of the license | licensekey.Status | false | -| writeService | Current write pod | string | false | -| readService | Current list of read pods | string | false | -| phase | Current phase of the cluster | string | false | -| phaseReason | Reason for the current phase | string | false | - -## DataBackupConfiguration - -DataBackupConfiguration is the configuration of the backup of the data directory - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| 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` or `bzip2`. | CompressionType | false | -| 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 | false | -| 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 | false | -| jobs | The number of parallel jobs to be used to upload the backup, defaults to 2 | \*int32 | false | - -## NodeMaintenanceWindow - -NodeMaintenanceWindow contains information that the operator will use while upgrading the underlying node. - -This option is only useful when using local storage, as the Pods can't be freely moved between nodes in that configuration. - -| Field | Description | Scheme | Required | -| ---------- | ------------------------------------------------------------------------------------------ | ------ | -------- | -| inProgress | Is there a node maintenance activity in progress? | bool | true | -| reusePVC | Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere) | \*bool | true | - -## PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -| Field | Description | Scheme | Required | -| ---------- | ----------------------------------------------------------------------------------------- | ----------------- | -------- | -| parameters | PostgreSQL configuration options (postgresql.conf) | map[string]string | false | -| pg_hba | PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) | \[]string | false | - -## RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive. - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------- | ------ | -------- | -| targetTLI | The target timeline (\\"latest\\", \\"current\\" or a positive integer) | string | false | -| targetXID | The target transaction ID | string | false | -| targetName | The target name (to be previously created with `pg_create_restore_point`) | string | false | -| targetLSN | The target LSN (Log Sequence Number) | string | false | -| targetTime | The target time, in any unambiguous representation allowed by PostgreSQL | string | false | -| targetImmediate | End recovery as soon as a consistent state is reached | \*bool | false | -| exclusive | Set the target to be exclusive (defaults to true) | \*bool | false | - -## RollingUpdateStatus - -RollingUpdateStatus contains the information about an instance which is being updated - -| Field | Description | Scheme | Required | -| --------- | ----------------------------------- | ----------- | -------- | -| imageName | The image which we put into the Pod | string | true | -| startedAt | When the update has been started | metav1.Time | false | - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Field | Description | Scheme | Required | -| --------------- | -------------------------------------- | ------------------------ | -------- | -| accessKeyId | The reference to the access key id | corev1.SecretKeySelector | true | -| secretAccessKey | The reference to the secret access key | corev1.SecretKeySelector | true | - -## StorageConfiguration - -StorageConfiguration is the configuration of the storage of the PostgreSQL instances - -| Field | Description | Scheme | Required | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------- | -------- | -| 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 | false | -| 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 | true | -| resizeInUseVolumes | Resize existent PVCs, defaults to true | \*bool | false | -| pvcTemplate | Template to be used to generate the Persistent Volume Claim | \*corev1.PersistentVolumeClaimSpec | false | - -## WalBackupConfiguration - -WalBackupConfiguration is the configuration of the backup of the WAL stream - -| Field | Description | Scheme | Required | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| compression | Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), `gzip` or `bzip2`. | CompressionType | false | -| 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 | false | - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#scheduledbackupspec) | false | -| status | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#scheduledbackupstatus) | false | - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][ScheduledBackup](#scheduledbackup) | true | - -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| suspend | If this backup is suspended of not | \*bool | false | -| schedule | The schedule in Cron format, see . | string | true | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Field | Description | Scheme | Required | -| ---------------- | -------------------------------------------------------------------------- | ------------- | -------- | -| lastCheckTime | The latest time the schedule | \*metav1.Time | false | -| lastScheduleTime | Information when was the last time that backup was successfully scheduled. | \*metav1.Time | false | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.8.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.8.0.mdx deleted file mode 100644 index bedb31ad456..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v0.8.0.mdx +++ /dev/null @@ -1,347 +0,0 @@ ---- -title: 'API Reference - v0.8.0' -navTitle: v0.8.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - - - -- [Backup](#backup) -- [BackupList](#backuplist) -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [AffinityConfiguration](#affinityconfiguration) -- [BackupConfiguration](#backupconfiguration) -- [BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) -- [BootstrapConfiguration](#bootstrapconfiguration) -- [BootstrapInitDB](#bootstrapinitdb) -- [BootstrapRecovery](#bootstraprecovery) -- [Cluster](#cluster) -- [ClusterList](#clusterlist) -- [ClusterSpec](#clusterspec) -- [ClusterStatus](#clusterstatus) -- [DataBackupConfiguration](#databackupconfiguration) -- [NodeMaintenanceWindow](#nodemaintenancewindow) -- [PostgresConfiguration](#postgresconfiguration) -- [RecoveryTarget](#recoverytarget) -- [RollingUpdateStatus](#rollingupdatestatus) -- [S3Credentials](#s3credentials) -- [StorageConfiguration](#storageconfiguration) -- [WalBackupConfiguration](#walbackupconfiguration) -- [ScheduledBackup](#scheduledbackup) -- [ScheduledBackupList](#scheduledbackuplist) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [ScheduledBackupStatus](#scheduledbackupstatus) - -## Backup - -Backup is the Schema for the backups API - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the backup. More info: | [BackupSpec](#backupspec) | false | -| status | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#backupstatus) | false | - -## BackupList - -BackupList contains a list of Backup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of backups | [][Backup](#backup) | true | - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Field | Description | Scheme | Required | -| ------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| encryption | Encryption method required to S3 API | string | false | -| backupId | The ID of the Barman backup | string | false | -| phase | The last backup status | BackupPhase | false | -| startedAt | When the backup was started | \*metav1.Time | false | -| stoppedAt | When the backup was terminated | \*metav1.Time | false | -| error | The detected error | string | false | -| commandOutput | The backup command output | string | false | -| commandError | The backup command output | string | false | - -## AffinityConfiguration - -AffinityConfiguration contains the info we need to create the affinity rules for Pods - -| Field | Description | Scheme | Required | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------- | -| enablePodAntiAffinity | Activates anti-affinity for the pods. The operator will define pods anti-affinity unless this field is explicitly set to false | \*bool | false | -| topologyKey | TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that | string | true | -| nodeSelector | NodeSelector is map of key-value pairs used to define the nodes on which the pods can run. More info: | map[string]string | false | - -## 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 - -| Field | Description | Scheme | Required | -| ----------------- | ------------------------------------------------- | ------------------------------------------------------------------- | -------- | -| barmanObjectStore | The configuration for the barman-cloud tool suite | \*[BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) | false | - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Field | Description | Scheme | Required | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| 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. | \*[WalBackupConfiguration](#walbackupconfiguration) | false | -| 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. | \*[DataBackupConfiguration](#databackupconfiguration) | false | - -## 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. - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------- | ----------------------------------------- | -------- | -| initdb | Bootstrap the cluster via initdb | \*[BootstrapInitDB](#bootstrapinitdb) | false | -| recovery | Bootstrap the cluster from a backup | \*[BootstrapRecovery](#bootstraprecovery) | false | - -## BootstrapInitDB - -BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------- | -| database | Name of the database used by the application. Default: `app`. | string | true | -| owner | Name of the owner of the database in the instance to be used by applications. Defaults to the value of the `database` key. | string | true | -| 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 | \*corev1.LocalObjectReference | false | -| redwood | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | false | -| options | The list of options that must be passed to initdb when creating the cluster | \[]string | false | - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -------- | -| backup | The backup we need to restore | corev1.LocalObjectReference | true | -| recoveryTarget | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | \*[RecoveryTarget](#recoverytarget) | false | - -## Cluster - -Cluster is the Schema for the PostgreSQL API - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#clusterspec) | false | -| status | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#clusterstatus) | false | - -## ClusterList - -ClusterList contains a list of Cluster - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][Cluster](#cluster) | true | - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Field | Description | Scheme | Required | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- | -------- | -| description | Description of this PostgreSQL cluster | string | false | -| imageName | Name of the container image | string | false | -| postgresUID | The UID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| postgresGID | The GID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| instances | Number of instances required in the cluster | int32 | true | -| minSyncReplicas | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | false | -| 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. | int32 | false | -| postgresql | Configuration of the PostgreSQL server | [PostgresConfiguration](#postgresconfiguration) | false | -| bootstrap | Instructions to bootstrap this cluster | \*[BootstrapConfiguration](#bootstrapconfiguration) | false | -| superuserSecret | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | \*corev1.LocalObjectReference | false | -| imagePullSecrets | 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. | \[]corev1.LocalObjectReference | false | -| storage | Configuration of the storage of the instances | [StorageConfiguration](#storageconfiguration) | false | -| startDelay | The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 30) | int32 | false | -| stopDelay | The time in seconds that is allowed for a PostgreSQL instance node to gracefully shutdown (default 30) | int32 | false | -| affinity | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#affinityconfiguration) | false | -| resources | Resources requirements of every generated Pod. Please refer to for more information. | corev1.ResourceRequirements | false | -| primaryUpdateStrategy | 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 | false | -| backup | The configuration to be used for backups | \*[BackupConfiguration](#backupconfiguration) | false | -| nodeMaintenanceWindow | Define a maintenance window for the Kubernetes nodes | \*[NodeMaintenanceWindow](#nodemaintenancewindow) | false | -| licenseKey | 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. | string | false | - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------- | -------- | -| instances | Total number of instances in the cluster | int32 | false | -| readyInstances | Total number of ready instances in the cluster | int32 | false | -| instancesStatus | Instances status | map[utils.PodStatus][]string | false | -| latestGeneratedNode | ID of the latest generated node (used to avoid node name clashing) | int32 | false | -| currentPrimary | Current primary instance | string | false | -| targetPrimary | Target primary instance, this is different from the previous one during a switchover or a failover | string | false | -| pvcCount | How many PVCs have been created by this cluster | int32 | false | -| jobCount | How many Jobs have been created by this cluster | int32 | false | -| danglingPVC | List of all the PVCs created by this cluster and still available which are not attached to a Pod | \[]string | false | -| licenseStatus | Status of the license | licensekey.Status | false | -| writeService | Current write pod | string | false | -| readService | Current list of read pods | string | false | -| phase | Current phase of the cluster | string | false | -| phaseReason | Reason for the current phase | string | false | - -## DataBackupConfiguration - -DataBackupConfiguration is the configuration of the backup of the data directory - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| 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` or `bzip2`. | CompressionType | false | -| 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 | false | -| 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 | false | -| jobs | The number of parallel jobs to be used to upload the backup, defaults to 2 | \*int32 | false | - -## 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. - -| Field | Description | Scheme | Required | -| ---------- | ------------------------------------------------------------------------------------------ | ------ | -------- | -| inProgress | Is there a node maintenance activity in progress? | bool | true | -| reusePVC | Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere) | \*bool | true | - -## PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -| Field | Description | Scheme | Required | -| ---------- | ----------------------------------------------------------------------------------------- | ----------------- | -------- | -| parameters | PostgreSQL configuration options (postgresql.conf) | map[string]string | false | -| pg_hba | PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) | \[]string | false | - -## RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive. - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------- | ------ | -------- | -| targetTLI | The target timeline (\\"latest\\", \\"current\\" or a positive integer) | string | false | -| targetXID | The target transaction ID | string | false | -| targetName | The target name (to be previously created with `pg_create_restore_point`) | string | false | -| targetLSN | The target LSN (Log Sequence Number) | string | false | -| targetTime | The target time, in any unambiguous representation allowed by PostgreSQL | string | false | -| targetImmediate | End recovery as soon as a consistent state is reached | \*bool | false | -| exclusive | Set the target to be exclusive (defaults to true) | \*bool | false | - -## RollingUpdateStatus - -RollingUpdateStatus contains the information about an instance which is being updated - -| Field | Description | Scheme | Required | -| --------- | ----------------------------------- | ----------- | -------- | -| imageName | The image which we put into the Pod | string | true | -| startedAt | When the update has been started | metav1.Time | false | - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Field | Description | Scheme | Required | -| --------------- | -------------------------------------- | ------------------------ | -------- | -| accessKeyId | The reference to the access key id | corev1.SecretKeySelector | true | -| secretAccessKey | The reference to the secret access key | corev1.SecretKeySelector | true | - -## StorageConfiguration - -StorageConfiguration is the configuration of the storage of the PostgreSQL instances - -| Field | Description | Scheme | Required | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------- | -------- | -| 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 | false | -| 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 | true | -| resizeInUseVolumes | Resize existent PVCs, defaults to true | \*bool | false | -| pvcTemplate | Template to be used to generate the Persistent Volume Claim | \*corev1.PersistentVolumeClaimSpec | false | - -## WalBackupConfiguration - -WalBackupConfiguration is the configuration of the backup of the WAL stream - -| Field | Description | Scheme | Required | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| compression | Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), `gzip` or `bzip2`. | CompressionType | false | -| 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 | false | - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#scheduledbackupspec) | false | -| status | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#scheduledbackupstatus) | false | - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][ScheduledBackup](#scheduledbackup) | true | - -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| suspend | If this backup is suspended of not | \*bool | false | -| schedule | The schedule in Cron format, see . | string | true | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Field | Description | Scheme | Required | -| ---------------- | -------------------------------------------------------------------------- | ------------- | -------- | -| lastCheckTime | The latest time the schedule | \*metav1.Time | false | -| lastScheduleTime | Information when was the last time that backup was successfully scheduled. | \*metav1.Time | false | -| nextScheduleTime | Next time we will run a backup | \*metav1.Time | false | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.0.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.0.0.mdx deleted file mode 100644 index 0288033898f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.0.0.mdx +++ /dev/null @@ -1,347 +0,0 @@ ---- -title: 'API Reference - v1.0.0' -navTitle: v1.0.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - - - -- [Backup](#backup) -- [BackupList](#backuplist) -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [AffinityConfiguration](#affinityconfiguration) -- [BackupConfiguration](#backupconfiguration) -- [BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) -- [BootstrapConfiguration](#bootstrapconfiguration) -- [BootstrapInitDB](#bootstrapinitdb) -- [BootstrapRecovery](#bootstraprecovery) -- [Cluster](#cluster) -- [ClusterList](#clusterlist) -- [ClusterSpec](#clusterspec) -- [ClusterStatus](#clusterstatus) -- [DataBackupConfiguration](#databackupconfiguration) -- [NodeMaintenanceWindow](#nodemaintenancewindow) -- [PostgresConfiguration](#postgresconfiguration) -- [RecoveryTarget](#recoverytarget) -- [RollingUpdateStatus](#rollingupdatestatus) -- [S3Credentials](#s3credentials) -- [StorageConfiguration](#storageconfiguration) -- [WalBackupConfiguration](#walbackupconfiguration) -- [ScheduledBackup](#scheduledbackup) -- [ScheduledBackupList](#scheduledbackuplist) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [ScheduledBackupStatus](#scheduledbackupstatus) - -## Backup - -Backup is the Schema for the backups API - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the backup. More info: | [BackupSpec](#backupspec) | false | -| status | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#backupstatus) | false | - -## BackupList - -BackupList contains a list of Backup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of backups | [][Backup](#backup) | true | - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Field | Description | Scheme | Required | -| ------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| encryption | Encryption method required to S3 API | string | false | -| backupId | The ID of the Barman backup | string | false | -| phase | The last backup status | BackupPhase | false | -| startedAt | When the backup was started | \*metav1.Time | false | -| stoppedAt | When the backup was terminated | \*metav1.Time | false | -| error | The detected error | string | false | -| commandOutput | The backup command output | string | false | -| commandError | The backup command output | string | false | - -## AffinityConfiguration - -AffinityConfiguration contains the info we need to create the affinity rules for Pods - -| Field | Description | Scheme | Required | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------- | -| enablePodAntiAffinity | Activates anti-affinity for the pods. The operator will define pods anti-affinity unless this field is explicitly set to false | \*bool | false | -| topologyKey | TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that | string | true | -| nodeSelector | NodeSelector is map of key-value pairs used to define the nodes on which the pods can run. More info: | map[string]string | false | - -## 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 - -| Field | Description | Scheme | Required | -| ----------------- | ------------------------------------------------- | ------------------------------------------------------------------- | -------- | -| barmanObjectStore | The configuration for the barman-cloud tool suite | \*[BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) | false | - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Field | Description | Scheme | Required | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| 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. | \*[WalBackupConfiguration](#walbackupconfiguration) | false | -| 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. | \*[DataBackupConfiguration](#databackupconfiguration) | false | - -## 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. - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------- | ----------------------------------------- | -------- | -| initdb | Bootstrap the cluster via initdb | \*[BootstrapInitDB](#bootstrapinitdb) | false | -| recovery | Bootstrap the cluster from a backup | \*[BootstrapRecovery](#bootstraprecovery) | false | - -## BootstrapInitDB - -BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------- | -| database | Name of the database used by the application. Default: `app`. | string | true | -| owner | Name of the owner of the database in the instance to be used by applications. Defaults to the value of the `database` key. | string | true | -| 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 | \*corev1.LocalObjectReference | false | -| redwood | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | false | -| options | The list of options that must be passed to initdb when creating the cluster | \[]string | false | - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -------- | -| backup | The backup we need to restore | corev1.LocalObjectReference | true | -| recoveryTarget | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | \*[RecoveryTarget](#recoverytarget) | false | - -## Cluster - -Cluster is the Schema for the PostgreSQL API - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#clusterspec) | false | -| status | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#clusterstatus) | false | - -## ClusterList - -ClusterList contains a list of Cluster - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][Cluster](#cluster) | true | - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Field | Description | Scheme | Required | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- | -------- | -| description | Description of this PostgreSQL cluster | string | false | -| imageName | Name of the container image | string | false | -| postgresUID | The UID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| postgresGID | The GID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| instances | Number of instances required in the cluster | int32 | true | -| minSyncReplicas | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | false | -| 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. | int32 | false | -| postgresql | Configuration of the PostgreSQL server | [PostgresConfiguration](#postgresconfiguration) | false | -| bootstrap | Instructions to bootstrap this cluster | \*[BootstrapConfiguration](#bootstrapconfiguration) | false | -| superuserSecret | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | \*corev1.LocalObjectReference | false | -| imagePullSecrets | 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. | \[]corev1.LocalObjectReference | false | -| storage | Configuration of the storage of the instances | [StorageConfiguration](#storageconfiguration) | false | -| startDelay | The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 30) | int32 | false | -| stopDelay | The time in seconds that is allowed for a PostgreSQL instance node to gracefully shutdown (default 30) | int32 | false | -| affinity | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#affinityconfiguration) | false | -| resources | Resources requirements of every generated Pod. Please refer to for more information. | corev1.ResourceRequirements | false | -| primaryUpdateStrategy | 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 | false | -| backup | The configuration to be used for backups | \*[BackupConfiguration](#backupconfiguration) | false | -| nodeMaintenanceWindow | Define a maintenance window for the Kubernetes nodes | \*[NodeMaintenanceWindow](#nodemaintenancewindow) | false | -| licenseKey | 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. | string | false | - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------- | -------- | -| instances | Total number of instances in the cluster | int32 | false | -| readyInstances | Total number of ready instances in the cluster | int32 | false | -| instancesStatus | Instances status | map[utils.PodStatus][]string | false | -| latestGeneratedNode | ID of the latest generated node (used to avoid node name clashing) | int32 | false | -| currentPrimary | Current primary instance | string | false | -| targetPrimary | Target primary instance, this is different from the previous one during a switchover or a failover | string | false | -| pvcCount | How many PVCs have been created by this cluster | int32 | false | -| jobCount | How many Jobs have been created by this cluster | int32 | false | -| danglingPVC | List of all the PVCs created by this cluster and still available which are not attached to a Pod | \[]string | false | -| licenseStatus | Status of the license | licensekey.Status | false | -| writeService | Current write pod | string | false | -| readService | Current list of read pods | string | false | -| phase | Current phase of the cluster | string | false | -| phaseReason | Reason for the current phase | string | false | - -## DataBackupConfiguration - -DataBackupConfiguration is the configuration of the backup of the data directory - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| 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` or `bzip2`. | CompressionType | false | -| 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 | false | -| 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 | false | -| jobs | The number of parallel jobs to be used to upload the backup, defaults to 2 | \*int32 | false | - -## 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. - -| Field | Description | Scheme | Required | -| ---------- | ------------------------------------------------------------------------------------------ | ------ | -------- | -| inProgress | Is there a node maintenance activity in progress? | bool | true | -| reusePVC | Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere) | \*bool | true | - -## PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -| Field | Description | Scheme | Required | -| ---------- | ----------------------------------------------------------------------------------------- | ----------------- | -------- | -| parameters | PostgreSQL configuration options (postgresql.conf) | map[string]string | false | -| pg_hba | PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) | \[]string | false | - -## RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive. - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------- | ------ | -------- | -| targetTLI | The target timeline (\\"latest\\", \\"current\\" or a positive integer) | string | false | -| targetXID | The target transaction ID | string | false | -| targetName | The target name (to be previously created with `pg_create_restore_point`) | string | false | -| targetLSN | The target LSN (Log Sequence Number) | string | false | -| targetTime | The target time, in any unambiguous representation allowed by PostgreSQL | string | false | -| targetImmediate | End recovery as soon as a consistent state is reached | \*bool | false | -| exclusive | Set the target to be exclusive (defaults to true) | \*bool | false | - -## RollingUpdateStatus - -RollingUpdateStatus contains the information about an instance which is being updated - -| Field | Description | Scheme | Required | -| --------- | ----------------------------------- | ----------- | -------- | -| imageName | The image which we put into the Pod | string | true | -| startedAt | When the update has been started | metav1.Time | false | - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Field | Description | Scheme | Required | -| --------------- | -------------------------------------- | ------------------------ | -------- | -| accessKeyId | The reference to the access key id | corev1.SecretKeySelector | true | -| secretAccessKey | The reference to the secret access key | corev1.SecretKeySelector | true | - -## StorageConfiguration - -StorageConfiguration is the configuration of the storage of the PostgreSQL instances - -| Field | Description | Scheme | Required | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------- | -------- | -| 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 | false | -| 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 | true | -| resizeInUseVolumes | Resize existent PVCs, defaults to true | \*bool | false | -| pvcTemplate | Template to be used to generate the Persistent Volume Claim | \*corev1.PersistentVolumeClaimSpec | false | - -## WalBackupConfiguration - -WalBackupConfiguration is the configuration of the backup of the WAL stream - -| Field | Description | Scheme | Required | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| compression | Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), `gzip` or `bzip2`. | CompressionType | false | -| 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 | false | - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#scheduledbackupspec) | false | -| status | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#scheduledbackupstatus) | false | - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][ScheduledBackup](#scheduledbackup) | true | - -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| suspend | If this backup is suspended of not | \*bool | false | -| schedule | The schedule in Cron format, see . | string | true | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Field | Description | Scheme | Required | -| ---------------- | -------------------------------------------------------------------------- | ------------- | -------- | -| lastCheckTime | The latest time the schedule | \*metav1.Time | false | -| lastScheduleTime | Information when was the last time that backup was successfully scheduled. | \*metav1.Time | false | -| nextScheduleTime | Next time we will run a backup | \*metav1.Time | false | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.1.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.1.0.mdx deleted file mode 100644 index ccca8df96bb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.1.0.mdx +++ /dev/null @@ -1,347 +0,0 @@ ---- -title: 'API Reference - v1.1.0' -navTitle: v1.1.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - - - -- [Backup](#backup) -- [BackupList](#backuplist) -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [AffinityConfiguration](#affinityconfiguration) -- [BackupConfiguration](#backupconfiguration) -- [BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) -- [BootstrapConfiguration](#bootstrapconfiguration) -- [BootstrapInitDB](#bootstrapinitdb) -- [BootstrapRecovery](#bootstraprecovery) -- [Cluster](#cluster) -- [ClusterList](#clusterlist) -- [ClusterSpec](#clusterspec) -- [ClusterStatus](#clusterstatus) -- [DataBackupConfiguration](#databackupconfiguration) -- [NodeMaintenanceWindow](#nodemaintenancewindow) -- [PostgresConfiguration](#postgresconfiguration) -- [RecoveryTarget](#recoverytarget) -- [RollingUpdateStatus](#rollingupdatestatus) -- [S3Credentials](#s3credentials) -- [StorageConfiguration](#storageconfiguration) -- [WalBackupConfiguration](#walbackupconfiguration) -- [ScheduledBackup](#scheduledbackup) -- [ScheduledBackupList](#scheduledbackuplist) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [ScheduledBackupStatus](#scheduledbackupstatus) - -## Backup - -Backup is the Schema for the backups API - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the backup. More info: | [BackupSpec](#backupspec) | false | -| status | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#backupstatus) | false | - -## BackupList - -BackupList contains a list of Backup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of backups | [][Backup](#backup) | true | - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Field | Description | Scheme | Required | -| ------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| encryption | Encryption method required to S3 API | string | false | -| backupId | The ID of the Barman backup | string | false | -| phase | The last backup status | BackupPhase | false | -| startedAt | When the backup was started | \*metav1.Time | false | -| stoppedAt | When the backup was terminated | \*metav1.Time | false | -| error | The detected error | string | false | -| commandOutput | The backup command output | string | false | -| commandError | The backup command output | string | false | - -## AffinityConfiguration - -AffinityConfiguration contains the info we need to create the affinity rules for Pods - -| Field | Description | Scheme | Required | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------- | -| enablePodAntiAffinity | Activates anti-affinity for the pods. The operator will define pods anti-affinity unless this field is explicitly set to false | \*bool | false | -| topologyKey | TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that | string | true | -| nodeSelector | NodeSelector is map of key-value pairs used to define the nodes on which the pods can run. More info: | map[string]string | false | - -## 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 - -| Field | Description | Scheme | Required | -| ----------------- | ------------------------------------------------- | ------------------------------------------------------------------- | -------- | -| barmanObjectStore | The configuration for the barman-cloud tool suite | \*[BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) | false | - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Field | Description | Scheme | Required | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| 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. | \*[WalBackupConfiguration](#walbackupconfiguration) | false | -| 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. | \*[DataBackupConfiguration](#databackupconfiguration) | false | - -## 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. - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------- | ----------------------------------------- | -------- | -| initdb | Bootstrap the cluster via initdb | \*[BootstrapInitDB](#bootstrapinitdb) | false | -| recovery | Bootstrap the cluster from a backup | \*[BootstrapRecovery](#bootstraprecovery) | false | - -## BootstrapInitDB - -BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------- | -| database | Name of the database used by the application. Default: `app`. | string | true | -| owner | Name of the owner of the database in the instance to be used by applications. Defaults to the value of the `database` key. | string | true | -| 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 | \*corev1.LocalObjectReference | false | -| redwood | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | false | -| options | The list of options that must be passed to initdb when creating the cluster | \[]string | false | - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -------- | -| backup | The backup we need to restore | corev1.LocalObjectReference | true | -| recoveryTarget | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | \*[RecoveryTarget](#recoverytarget) | false | - -## Cluster - -Cluster is the Schema for the PostgreSQL API - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#clusterspec) | false | -| status | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#clusterstatus) | false | - -## ClusterList - -ClusterList contains a list of Cluster - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][Cluster](#cluster) | true | - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Field | Description | Scheme | Required | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- | -------- | -| description | Description of this PostgreSQL cluster | string | false | -| imageName | Name of the container image | string | false | -| postgresUID | The UID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| postgresGID | The GID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| instances | Number of instances required in the cluster | int32 | true | -| minSyncReplicas | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | false | -| 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. | int32 | false | -| postgresql | Configuration of the PostgreSQL server | [PostgresConfiguration](#postgresconfiguration) | false | -| bootstrap | Instructions to bootstrap this cluster | \*[BootstrapConfiguration](#bootstrapconfiguration) | false | -| superuserSecret | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | \*corev1.LocalObjectReference | false | -| imagePullSecrets | 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. | \[]corev1.LocalObjectReference | false | -| storage | Configuration of the storage of the instances | [StorageConfiguration](#storageconfiguration) | false | -| startDelay | The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 30) | int32 | false | -| stopDelay | The time in seconds that is allowed for a PostgreSQL instance node to gracefully shutdown (default 30) | int32 | false | -| affinity | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#affinityconfiguration) | false | -| resources | Resources requirements of every generated Pod. Please refer to for more information. | corev1.ResourceRequirements | false | -| primaryUpdateStrategy | 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 | false | -| backup | The configuration to be used for backups | \*[BackupConfiguration](#backupconfiguration) | false | -| nodeMaintenanceWindow | Define a maintenance window for the Kubernetes nodes | \*[NodeMaintenanceWindow](#nodemaintenancewindow) | false | -| licenseKey | 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. | string | false | - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------- | -------- | -| instances | Total number of instances in the cluster | int32 | false | -| readyInstances | Total number of ready instances in the cluster | int32 | false | -| instancesStatus | Instances status | map[utils.PodStatus][]string | false | -| latestGeneratedNode | ID of the latest generated node (used to avoid node name clashing) | int32 | false | -| currentPrimary | Current primary instance | string | false | -| targetPrimary | Target primary instance, this is different from the previous one during a switchover or a failover | string | false | -| pvcCount | How many PVCs have been created by this cluster | int32 | false | -| jobCount | How many Jobs have been created by this cluster | int32 | false | -| danglingPVC | List of all the PVCs created by this cluster and still available which are not attached to a Pod | \[]string | false | -| licenseStatus | Status of the license | licensekey.Status | false | -| writeService | Current write pod | string | false | -| readService | Current list of read pods | string | false | -| phase | Current phase of the cluster | string | false | -| phaseReason | Reason for the current phase | string | false | - -## DataBackupConfiguration - -DataBackupConfiguration is the configuration of the backup of the data directory - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| 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` or `bzip2`. | CompressionType | false | -| 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 | false | -| 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 | false | -| jobs | The number of parallel jobs to be used to upload the backup, defaults to 2 | \*int32 | false | - -## 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. - -| Field | Description | Scheme | Required | -| ---------- | ------------------------------------------------------------------------------------------ | ------ | -------- | -| inProgress | Is there a node maintenance activity in progress? | bool | true | -| reusePVC | Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere) | \*bool | true | - -## PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -| Field | Description | Scheme | Required | -| ---------- | ----------------------------------------------------------------------------------------- | ----------------- | -------- | -| parameters | PostgreSQL configuration options (postgresql.conf) | map[string]string | false | -| pg_hba | PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) | \[]string | false | - -## RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive. - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------- | ------ | -------- | -| targetTLI | The target timeline (\\"latest\\", \\"current\\" or a positive integer) | string | false | -| targetXID | The target transaction ID | string | false | -| targetName | The target name (to be previously created with `pg_create_restore_point`) | string | false | -| targetLSN | The target LSN (Log Sequence Number) | string | false | -| targetTime | The target time, in any unambiguous representation allowed by PostgreSQL | string | false | -| targetImmediate | End recovery as soon as a consistent state is reached | \*bool | false | -| exclusive | Set the target to be exclusive (defaults to true) | \*bool | false | - -## RollingUpdateStatus - -RollingUpdateStatus contains the information about an instance which is being updated - -| Field | Description | Scheme | Required | -| --------- | ----------------------------------- | ----------- | -------- | -| imageName | The image which we put into the Pod | string | true | -| startedAt | When the update has been started | metav1.Time | false | - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Field | Description | Scheme | Required | -| --------------- | -------------------------------------- | ------------------------ | -------- | -| accessKeyId | The reference to the access key id | corev1.SecretKeySelector | true | -| secretAccessKey | The reference to the secret access key | corev1.SecretKeySelector | true | - -## StorageConfiguration - -StorageConfiguration is the configuration of the storage of the PostgreSQL instances - -| Field | Description | Scheme | Required | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------- | -------- | -| 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 | false | -| 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 | true | -| resizeInUseVolumes | Resize existent PVCs, defaults to true | \*bool | false | -| pvcTemplate | Template to be used to generate the Persistent Volume Claim | \*corev1.PersistentVolumeClaimSpec | false | - -## WalBackupConfiguration - -WalBackupConfiguration is the configuration of the backup of the WAL stream - -| Field | Description | Scheme | Required | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| compression | Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), `gzip` or `bzip2`. | CompressionType | false | -| 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 | false | - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#scheduledbackupspec) | false | -| status | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#scheduledbackupstatus) | false | - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | [][ScheduledBackup](#scheduledbackup) | true | - -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| suspend | If this backup is suspended of not | \*bool | false | -| schedule | The schedule in Cron format, see . | string | true | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Field | Description | Scheme | Required | -| ---------------- | -------------------------------------------------------------------------- | ------------- | -------- | -| lastCheckTime | The latest time the schedule | \*metav1.Time | false | -| lastScheduleTime | Information when was the last time that backup was successfully scheduled. | \*metav1.Time | false | -| nextScheduleTime | Next time we will run a backup | \*metav1.Time | false | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.10.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.10.0.mdx deleted file mode 100644 index 65cde47b35f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.10.0.mdx +++ /dev/null @@ -1,788 +0,0 @@ ---- -title: 'API Reference - v1.10.0' -navTitle: v1.10.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [InstanceID](#InstanceID) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to use to upload data in Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - - - -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | The hash of the binary of the operator | string | -| `onlineUpdateEnabled ` | OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster | bool | - - - -## 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` or `bzip2`. | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | - - - -## 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. Default: false. | \*bool | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - - - -## 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) - *mandatory* | \*bool | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -Name | Description | Type --------- \| \| ------------------------------------------------------------------------------------------------------------ -`metadata` \| \| [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) -`spec ` \| \| [PoolerSpec](#PoolerSpec) -`status ` \| \| [PoolerStatus](#PoolerStatus) - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -Name | Description | Type --------------------- \| \| --------------------------------------------------------- -`pgBouncerIntegration` \| \| [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) - - - -## PoolerList - -PoolerList contains a list of Pooler - -Name | Description | Type --------- \| \| -------------------------------------------------------------------------------------------------------- -`metadata` \| \| [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) -`items ` \| - *mandatory* \| [\[\]Pooler](#Pooler) - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| --------- | ----------------------------------------- | --------------------------------- | -| `secrets` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `promotionTimeout ` | Specifies the maximum number of seconds to wait when promoting an instance to primary | int32 | -| `shared_preload_libraries` | Lists of shared preload libraries to add to the default ones | \[]string | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.11.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.11.0.mdx deleted file mode 100644 index 7b698aba2cb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.11.0.mdx +++ /dev/null @@ -1,796 +0,0 @@ ---- -title: 'API Reference - v1.11.0' -navTitle: v1.11.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [InstanceID](#InstanceID) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to use to upload data in Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - - - -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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` or `bzip2`. | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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) - *mandatory* | \*bool | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -Name | Description | Type --------- \| \| ------------------------------------------------------------------------------------------------------------ -`metadata` \| \| [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) -`spec ` \| \| [PoolerSpec](#PoolerSpec) -`status ` \| \| [PoolerStatus](#PoolerStatus) - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -Name | Description | Type --------------------- \| \| --------------------------------------------------------- -`pgBouncerIntegration` \| \| [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) - - - -## PoolerList - -PoolerList contains a list of Pooler - -Name | Description | Type --------- \| \| -------------------------------------------------------------------------------------------------------- -`metadata` \| \| [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) -`items ` \| - *mandatory* \| [\[\]Pooler](#Pooler) - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.12.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.12.0.mdx deleted file mode 100644 index f9ab6ecbaf6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.12.0.mdx +++ /dev/null @@ -1,810 +0,0 @@ ---- -title: 'API Reference - v1.12.0' -navTitle: v1.12.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [InstanceID](#InstanceID) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to use to upload data in Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - - - -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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` or `bzip2`. | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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) - *mandatory* | \*bool | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -Name | Description | Type --------- \| \| ------------------------------------------------------------------------------------------------------------ -`metadata` \| \| [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) -`spec ` \| \| [PoolerSpec](#PoolerSpec) -`status ` \| \| [PoolerStatus](#PoolerStatus) - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -Name | Description | Type --------------------- \| \| --------------------------------------------------------- -`pgBouncerIntegration` \| \| [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) - - - -## PoolerList - -PoolerList contains a list of Pooler - -Name | Description | Type --------- \| \| -------------------------------------------------------------------------------------------------------- -`metadata` \| \| [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) -`items ` \| - *mandatory* \| [\[\]Pooler](#Pooler) - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.13.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.13.0.mdx deleted file mode 100644 index f852c6c0dca..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.13.0.mdx +++ /dev/null @@ -1,828 +0,0 @@ ---- -title: 'API Reference - v1.13.0' -navTitle: v1.13.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterCondition](#ClusterCondition) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [InstanceID](#InstanceID) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to use to upload data in Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterCondition - -ClusterCondition describes the state of a cluster object at a certain point - -| Name | Description | Type | -| -------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `type ` | Type of the condition. | ClusterConditionType | -| `status ` | Status of the condition, one of True, False, Unknown. | ConditionStatus | -| `lastTransitionTime` | Last time the condition transitioned from one status to another. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `reason ` | The reason for the condition's last transition. | string | -| `message ` | A human readable message indicating details about the transition. | string | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | [\[\]ClusterCondition](#ClusterCondition) | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.14.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.14.0.mdx deleted file mode 100644 index 6e806b35224..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.14.0.mdx +++ /dev/null @@ -1,847 +0,0 @@ ---- -title: 'API Reference - v1.14.0' -navTitle: v1.14.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterCondition](#ClusterCondition) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [InstanceID](#InstanceID) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterCondition - -ClusterCondition describes the state of a cluster object at a certain point - -| Name | Description | Type | -| -------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `type ` | Type of the condition. | ClusterConditionType | -| `status ` | Status of the condition, one of True, False, Unknown. | ConditionStatus | -| `lastTransitionTime` | Last time the condition transitioned from one status to another. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `reason ` | The reason for the condition's last transition. | string | -| `message ` | A human readable message indicating details about the transition. | string | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | [\[\]ClusterCondition](#ClusterCondition) | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.0.mdx deleted file mode 100644 index 625998660b1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.0.mdx +++ /dev/null @@ -1,893 +0,0 @@ ---- -title: 'API Reference - v1.15.0' -navTitle: v1.15.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterCondition](#ClusterCondition) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [InstanceID](#InstanceID) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterCondition - -ClusterCondition describes the state of a cluster object at a certain point - -| Name | Description | Type | -| -------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `type ` | Type of the condition. | ClusterConditionType | -| `status ` | Status of the condition, one of True, False, Unknown. | ConditionStatus | -| `lastTransitionTime` | Last time the condition transitioned from one status to another. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `reason ` | The reason for the condition's last transition. | string | -| `message ` | A human readable message indicating details about the transition. | string | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | [\[\]ClusterCondition](#ClusterCondition) | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 1 to enable LDAP over TLS | bool | -| `bindAsAuth ` | Bind as authentication configuration | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.1.mdx deleted file mode 100644 index 243104bb2a5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.1.mdx +++ /dev/null @@ -1,897 +0,0 @@ ---- -title: 'API Reference - v1.15.1' -navTitle: v1.15.1 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterCondition](#ClusterCondition) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [InstanceID](#InstanceID) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterCondition - -ClusterCondition describes the state of a cluster object at a certain point - -| Name | Description | Type | -| -------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `type ` | Type of the condition. | ClusterConditionType | -| `status ` | Status of the condition, one of True, False, Unknown. | ConditionStatus | -| `lastTransitionTime` | Last time the condition transitioned from one status to another. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `reason ` | The reason for the condition's last transition. | string | -| `message ` | A human readable message indicating details about the transition. | string | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | int | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | [\[\]ClusterCondition](#ClusterCondition) | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 1 to enable LDAP over TLS | bool | -| `bindAsAuth ` | Bind as authentication configuration | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.2.mdx deleted file mode 100644 index 12cb9e10300..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.2.mdx +++ /dev/null @@ -1,898 +0,0 @@ ---- -title: 'API Reference - v1.15.2' -navTitle: v1.15.2 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterCondition](#ClusterCondition) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [InstanceID](#InstanceID) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterCondition - -ClusterCondition describes the state of a cluster object at a certain point - -| Name | Description | Type | -| -------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `type ` | Type of the condition. | ClusterConditionType | -| `status ` | Status of the condition, one of True, False, Unknown. | ConditionStatus | -| `lastTransitionTime` | Last time the condition transitioned from one status to another. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `reason ` | The reason for the condition's last transition. | string | -| `message ` | A human readable message indicating details about the transition. | string | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | int | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | [\[\]ClusterCondition](#ClusterCondition) | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 1 to enable LDAP over TLS | bool | -| `bindAsAuth ` | Bind as authentication configuration | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.3.mdx deleted file mode 100644 index ed2ab91b392..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.3.mdx +++ /dev/null @@ -1,898 +0,0 @@ ---- -title: 'API Reference - v1.15.3' -navTitle: v1.15.3 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterCondition](#ClusterCondition) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [InstanceID](#InstanceID) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterCondition - -ClusterCondition describes the state of a cluster object at a certain point - -| Name | Description | Type | -| -------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `type ` | Type of the condition. | ClusterConditionType | -| `status ` | Status of the condition, one of True, False, Unknown. | ConditionStatus | -| `lastTransitionTime` | Last time the condition transitioned from one status to another. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `reason ` | The reason for the condition's last transition. | string | -| `message ` | A human readable message indicating details about the transition. | string | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | int | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | [\[\]ClusterCondition](#ClusterCondition) | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 1 to enable LDAP over TLS | bool | -| `bindAsAuth ` | Bind as authentication configuration | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.4.mdx deleted file mode 100644 index 937da810f51..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.4.mdx +++ /dev/null @@ -1,898 +0,0 @@ ---- -title: 'API Reference - v1.15.4' -navTitle: v1.15.4 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterCondition](#ClusterCondition) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [InstanceID](#InstanceID) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterCondition - -ClusterCondition describes the state of a cluster object at a certain point - -| Name | Description | Type | -| -------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `type ` | Type of the condition. | ClusterConditionType | -| `status ` | Status of the condition, one of True, False, Unknown. | ConditionStatus | -| `lastTransitionTime` | Last time the condition transitioned from one status to another. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `reason ` | The reason for the condition's last transition. | string | -| `message ` | A human readable message indicating details about the transition. | string | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | int | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | [\[\]ClusterCondition](#ClusterCondition) | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.5.mdx deleted file mode 100644 index 787696eedfb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.15.5.mdx +++ /dev/null @@ -1,898 +0,0 @@ ---- -title: 'API Reference - v1.15.5' -navTitle: v1.15.5 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterCondition](#ClusterCondition) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [InstanceID](#InstanceID) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterCondition - -ClusterCondition describes the state of a cluster object at a certain point - -| Name | Description | Type | -| -------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `type ` | Type of the condition. | ClusterConditionType | -| `status ` | Status of the condition, one of True, False, Unknown. | ConditionStatus | -| `lastTransitionTime` | Last time the condition transitioned from one status to another. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `reason ` | The reason for the condition's last transition. | string | -| `message ` | A human readable message indicating details about the transition. | string | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | int | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | [\[\]ClusterCondition](#ClusterCondition) | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## InstanceID - -InstanceID contains the information to identify an instance - -| Name | Description | Type | -| ------------- | ---------------- | ------ | -| `podName ` | The pod name | string | -| `ContainerID` | The container ID | string | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.0.mdx deleted file mode 100644 index 4ee6f7cb962..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.0.mdx +++ /dev/null @@ -1,947 +0,0 @@ ---- -title: 'API Reference - v1.16.0' -navTitle: v1.16.0 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `googleCredentials` | The credentials to use to upload data to Google Cloud Storage | [\*GoogleCredentials](#GoogleCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | int | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 1 to enable LDAP over TLS | bool | -| `bindAsAuth ` | Bind as authentication configuration | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.1.mdx deleted file mode 100644 index ae7fb13097a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.1.mdx +++ /dev/null @@ -1,968 +0,0 @@ ---- -title: 'API Reference - v1.16.1' -navTitle: v1.16.1 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 1 to enable LDAP over TLS | bool | -| `bindAsAuth ` | Bind as authentication configuration | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.2.mdx deleted file mode 100644 index f95308e709f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.2.mdx +++ /dev/null @@ -1,968 +0,0 @@ ---- -title: 'API Reference - v1.16.2' -navTitle: v1.16.2 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.3.mdx deleted file mode 100644 index cab3dd36280..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.3.mdx +++ /dev/null @@ -1,968 +0,0 @@ ---- -title: 'API Reference - v1.16.3' -navTitle: v1.16.3 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.4.mdx deleted file mode 100644 index ffc1aa1982b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.4.mdx +++ /dev/null @@ -1,968 +0,0 @@ ---- -title: 'API Reference - v1.16.4' -navTitle: v1.16.4 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.5.mdx deleted file mode 100644 index 1ab18858838..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.16.5.mdx +++ /dev/null @@ -1,968 +0,0 @@ ---- -title: 'API Reference - v1.16.5' -navTitle: v1.16.5 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `instances` | The number of pods trying to be scheduled | int32 | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.0.mdx deleted file mode 100644 index ed8f3959763..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.0.mdx +++ /dev/null @@ -1,983 +0,0 @@ ---- -title: 'API Reference - v1.17.0' -navTitle: v1.17.0 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.1.mdx deleted file mode 100644 index 2d5152be44b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.1.mdx +++ /dev/null @@ -1,983 +0,0 @@ ---- -title: 'API Reference - v1.17.1' -navTitle: v1.17.1 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 follows the same format used in Kubernetes CronJobs, see - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.2.mdx deleted file mode 100644 index f6face11793..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.2.mdx +++ /dev/null @@ -1,983 +0,0 @@ ---- -title: 'API Reference - v1.17.2' -navTitle: v1.17.2 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.3.mdx deleted file mode 100644 index d368c95ae67..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.3.mdx +++ /dev/null @@ -1,983 +0,0 @@ ---- -title: 'API Reference - v1.17.3' -navTitle: v1.17.3 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.4.mdx deleted file mode 100644 index 1184f3d0bfa..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.4.mdx +++ /dev/null @@ -1,983 +0,0 @@ ---- -title: 'API Reference - v1.17.4' -navTitle: v1.17.4 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.5.mdx deleted file mode 100644 index c731fbc935e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.17.5.mdx +++ /dev/null @@ -1,984 +0,0 @@ ---- -title: 'API Reference - v1.17.5' -navTitle: v1.17.5 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | - - - -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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 enabled 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.0.mdx deleted file mode 100644 index e65325e8487..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.0.mdx +++ /dev/null @@ -1,1009 +0,0 @@ ---- -title: 'API Reference - v1.18.0' -navTitle: v1.18.0 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodMeta](#PodMeta) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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 | - - - -## PodMeta - -PodMeta 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: | 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: | map[string]string | - - - -## 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| `metadata` | Standard object's metadata. More info: | [PodMeta](#PodMeta) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | - - - -## 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 | -| `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 | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.1.mdx deleted file mode 100644 index 7d74190d5ec..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.1.mdx +++ /dev/null @@ -1,1022 +0,0 @@ ---- -title: 'API Reference - v1.18.1' -navTitle: v1.18.1 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy ` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, warning, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.10.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.10.mdx deleted file mode 100644 index 3e793c41c4c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.10.mdx +++ /dev/null @@ -1,4069 +0,0 @@ ---- -title: 'API Reference - v1.18.10' -navTitle: v1.18.10 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

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

-
topologyKey
-string -		 -

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

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

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

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

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

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

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

-
storageSasToken
-SecretKeySelector -		 -

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

-
inheritFromAzureAD
-bool -		 -

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

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

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

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

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

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

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

-
- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

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

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

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

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

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

-
historyTags
-map[string]string -		 -

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

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

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

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

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

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

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

-
encoding
-string -		 -

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

-
localeCollate
-string -		 -

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

-
localeCType
-string -		 -

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

-
walSegmentSize
-int -		 -

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

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

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

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

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

-
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

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

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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
-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
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

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

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

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

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

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

-
imageName
-string -		 -

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

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

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

-
postgresGID
-int64 -		 -

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

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

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

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

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

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

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

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

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

-
startDelay
-int32 -		 -

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

-
stopDelay
-int32 -		 -

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

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

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

-
resources
-core/v1.ResourceRequirements -		 -

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

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default) or in-place (restart)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

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

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

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

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

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

-
env
-[]core/v1.EnvVar -		 -

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

-
envFrom
-[]core/v1.EnvFromSource -		 -

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

-
seccompProfile
-core/v1.SeccompProfile -		 -

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

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

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

-
readyInstances
-int -		 -

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

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

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

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

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

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

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

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

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

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

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

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

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

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
targetPrimaryTimestamp
-string -		 -

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

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled [Required]
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled [Required]
-bool -		 -

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

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs [Required]
-int32 -		 -

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

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

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

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

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

-
sslCert
-core/v1.SecretKeySelector -		 -

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

-
sslKey
-core/v1.SecretKeySelector -		 -

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

-
sslRootCert
-core/v1.SecretKeySelector -		 -

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

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials [Required]
-SecretKeySelector -		 -

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

-
gkeEnvironment
-bool -		 -

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

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

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

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

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

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

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

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls [Required]
-bool -		 -

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

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

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

-
inProgress [Required]
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

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

-
pg_hba
-[]string -		 -

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

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

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

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

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

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

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

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

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

-
pg_ident
-[]string -		 -

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

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

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

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

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

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

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

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

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

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

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

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

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

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

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

-
serverCaSecretVersion
-string -		 -

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

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

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

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

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

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

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

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

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

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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 [Required]
-bool -		 -

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

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.11.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.11.mdx deleted file mode 100644 index 3846909e521..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.11.mdx +++ /dev/null @@ -1,4147 +0,0 @@ ---- -title: 'API Reference - v1.18.11' -navTitle: v1.18.11 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

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

-
topologyKey
-string -		 -

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

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

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

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

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

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

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

-
storageSasToken
-SecretKeySelector -		 -

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

-
inheritFromAzureAD
-bool -		 -

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

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

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

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

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

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

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

-
- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

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

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

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

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

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

-
historyTags
-map[string]string -		 -

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

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

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

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

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

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

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

-
encoding
-string -		 -

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

-
localeCollate
-string -		 -

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

-
localeCType
-string -		 -

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

-
walSegmentSize
-int -		 -

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

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

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

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

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

-
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

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

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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
-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
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

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

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

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

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

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

-
imageName
-string -		 -

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

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

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

-
postgresGID
-int64 -		 -

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

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

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

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

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

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

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

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

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

-
startDelay
-int32 -		 -

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

-
stopDelay
-int32 -		 -

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

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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

-
switchoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

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

-
resources
-core/v1.ResourceRequirements -		 -

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

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default) or in-place (restart)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

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

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

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

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

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

-
env
-[]core/v1.EnvVar -		 -

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

-
envFrom
-[]core/v1.EnvFromSource -		 -

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

-
seccompProfile
-core/v1.SeccompProfile -		 -

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

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

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

-
readyInstances
-int -		 -

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

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

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

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

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

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

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

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

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

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

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

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

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

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
targetPrimaryTimestamp
-string -		 -

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

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled [Required]
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled [Required]
-bool -		 -

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

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs [Required]
-int32 -		 -

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

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

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

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

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

-
sslCert
-core/v1.SecretKeySelector -		 -

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

-
sslKey
-core/v1.SecretKeySelector -		 -

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

-
sslRootCert
-core/v1.SecretKeySelector -		 -

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

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials [Required]
-SecretKeySelector -		 -

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

-
gkeEnvironment
-bool -		 -

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

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

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

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

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

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

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

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls [Required]
-bool -		 -

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

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

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

-
inProgress [Required]
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

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

-
pg_hba
-[]string -		 -

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

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

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

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

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

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

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

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

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

-
pg_ident
-[]string -		 -

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

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

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

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

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

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

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

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

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

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

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

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

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

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

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

-
serverCaSecretVersion
-string -		 -

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

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

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

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

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

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

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

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

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

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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 [Required]
-bool -		 -

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

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.12.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.12.mdx deleted file mode 100644 index 2b90557d07d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.12.mdx +++ /dev/null @@ -1,5023 +0,0 @@ ---- -title: 'API Reference - v1.18.12' -navTitle: v1.18.12 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

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

-
topologyKey
-string -		 -

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

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

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

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

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

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

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

-
storageSasToken
-SecretKeySelector -		 -

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

-
inheritFromAzureAD
-bool -		 -

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

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups. -Only available in 1.22 or later

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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. -Only available in 1.22 or later

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

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

-
tablespaceName [Required]
-string -		 -

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

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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. -Only available in 1.22 or later

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore. -Only available in 1.22 or later

-
online
-bool -		 -

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' -Only available in 1.22 or later

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza -Only available in 1.22 or later

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

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

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

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

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups -Only available in 1.22 or later

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups -Only available in 1.22 or later

-
instanceID
-InstanceID -		 -

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

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup -Only available in 1.22 or later

-
method
-BackupMethod -		 -

The backup method being used -Only available in 1.22 or later

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false) -Only available in 1.22 or later

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

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

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

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

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

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

-
historyTags
-map[string]string -		 -

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

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

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

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

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

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

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

-
encoding
-string -		 -

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

-
localeCollate
-string -		 -

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

-
localeCType
-string -		 -

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

-
walSegmentSize
-int -		 -

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

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

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

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

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

-
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

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

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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. -Only available in 1.22 or later

-
recoveryTarget
-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
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

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

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

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

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

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

-
imageName
-string -		 -

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

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

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

-
postgresGID
-int64 -		 -

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

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

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

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

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

-
enableSuperuserAccess
-bool -		 -

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 before 1.22. Disabled by default in 1.22 or later.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

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

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

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

-
startDelay
-int32 -		 -

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

-
stopDelay
-int32 -		 -

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

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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). -Only available in 1.22 or later

-
switchoverDelay
-int32 -		 -

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

-
failoverDelay
-int32 -		 -

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 -Only available in 1.22 or later

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

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

-
resources
-core/v1.ResourceRequirements -		 -

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

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

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

-
priorityClassName
-string -		 -

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 -Only available in 1.22 or later

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default before 1.22) -or in-place (restart - default in 1.22 or later)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

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

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

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

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

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

-
env
-[]core/v1.EnvVar -		 -

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

-
envFrom
-[]core/v1.EnvFromSource -		 -

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

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager -Only available in 1.22 or later

-
seccompProfile
-core/v1.SeccompProfile -		 -

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

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration -Only available in 1.22 or later

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

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

-
readyInstances
-int -		 -

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

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster -Only available in 1.22 or later

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster -Only available in 1.22 or later

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

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

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

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

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

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

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

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

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

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

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

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

-
firstRecoverabilityPoint
-string -		 -

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

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type -Only available in 1.22 or later

-
lastSuccessfulBackup
-string -		 -

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

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type -Only available in 1.22 or later

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades -Only available in 1.22 or later

-
targetPrimaryTimestamp
-string -		 -

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

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster -Only available in 1.22 or later

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

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

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

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

-
immediateCheckpoint
-bool -		 -

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
-[]string -		 -

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. -Only available in 1.22 or later

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

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

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces -Only available in 1.22 or later

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

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

-
sslCert
-core/v1.SecretKeySelector -		 -

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

-
sslKey
-core/v1.SecretKeySelector -		 -

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

-
sslRootCert
-core/v1.SecretKeySelector -		 -

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

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

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

-
gkeEnvironment
-bool -		 -

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

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

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

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

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

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

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

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

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

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

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

-
passwordStatus
-map[string]PasswordState -		 -

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

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

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

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

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

-
pg_hba
-[]string -		 -

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

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

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

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

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

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

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

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

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

-
pg_ident
-[]string -		 -

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

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

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

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Default to true before 1.22. Defaults to false in 1.22 or later.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

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

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

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

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

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

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

If enabled (default in 1.22 or later), 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 before 1.22), 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.

-
slotPrefix
-string -		 -

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

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

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

-
passwordSecret
-LocalObjectReference -		 -

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

-
connectionLimit
-int64 -		 -

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

-
validUntil
-meta/v1.Time -		 -

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

-
inRoles
-[]string -		 -

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

-
inherit
-bool -		 -

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

-
disablePassword
-bool -		 -

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

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

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

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

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

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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. -Only available in 1.22 or later

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore. -Only available in 1.22 or later

-
online
-bool -		 -

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' -Only available in 1.22 or later

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza -Only available in 1.22 or later

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

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

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets -Only available in 1.22 or later

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

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

-
serverCaSecretVersion
-string -		 -

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

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

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

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

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

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

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

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

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

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

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

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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

-
annotations
-map[string]string -		 -

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

-
className
-string -		 -

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
-string -		 -

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

-
tablespaceClassName
-map[string]string -		 -

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

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

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

-
onlineConfiguration
-OnlineConfiguration -		 -

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

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.13.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.13.mdx deleted file mode 100644 index aafc102588d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.13.mdx +++ /dev/null @@ -1,5033 +0,0 @@ ---- -title: 'API Reference - v1.18.13' -navTitle: v1.18.13 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

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

-
topologyKey
-string -		 -

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

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

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

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

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

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

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

-
storageSasToken
-SecretKeySelector -		 -

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

-
inheritFromAzureAD
-bool -		 -

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

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups. -Only available in 1.22 or later

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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. -Only available in 1.22 or later

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

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

-
tablespaceName [Required]
-string -		 -

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

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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. -Only available in 1.22 or later

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore. -Only available in 1.22 or later

-
online
-bool -		 -

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' -Only available in 1.22 or later

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza -Only available in 1.22 or later

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

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

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

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

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups -Only available in 1.22 or later

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups -Only available in 1.22 or later

-
instanceID
-InstanceID -		 -

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

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup -Only available in 1.22 or later

-
method
-BackupMethod -		 -

The backup method being used -Only available in 1.22 or later

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false) -Only available in 1.22 or later

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

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

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

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

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

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

-
historyTags
-map[string]string -		 -

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

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

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

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

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

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

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

-
encoding
-string -		 -

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

-
localeCollate
-string -		 -

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

-
localeCType
-string -		 -

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

-
walSegmentSize
-int -		 -

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

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

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

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

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

-
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

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

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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. -Only available in 1.22 or later

-
recoveryTarget
-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
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

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

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

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

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

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

-
imageName
-string -		 -

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

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

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

-
postgresGID
-int64 -		 -

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

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

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

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

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

-
enableSuperuserAccess
-bool -		 -

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 before 1.22. Disabled by default in 1.22 or later.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

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

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

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

-
startDelay
-int32 -		 -

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

-
stopDelay
-int32 -		 -

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

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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). -Only available in 1.22 or later

-
switchoverDelay
-int32 -		 -

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

-
failoverDelay
-int32 -		 -

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 -Only available in 1.22 or later

-
livenessProbeTimeout
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

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

-
resources
-core/v1.ResourceRequirements -		 -

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

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

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

-
priorityClassName
-string -		 -

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 -Only available in 1.22 or later

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default before 1.22) -or in-place (restart - default in 1.22 or later)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

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

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

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

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

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

-
env
-[]core/v1.EnvVar -		 -

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

-
envFrom
-[]core/v1.EnvFromSource -		 -

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

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager -Only available in 1.22 or later

-
seccompProfile
-core/v1.SeccompProfile -		 -

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

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration -Only available in 1.22 or later

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

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

-
readyInstances
-int -		 -

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

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster -Only available in 1.22 or later

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster -Only available in 1.22 or later

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

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

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

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

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

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

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

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

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

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

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

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

-
firstRecoverabilityPoint
-string -		 -

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

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type -Only available in 1.22 or later

-
lastSuccessfulBackup
-string -		 -

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

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type -Only available in 1.22 or later

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades -Only available in 1.22 or later

-
targetPrimaryTimestamp
-string -		 -

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

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster -Only available in 1.22 or later

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

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

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

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

-
immediateCheckpoint
-bool -		 -

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
-[]string -		 -

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. -Only available in 1.22 or later

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

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

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces -Only available in 1.22 or later

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

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

-
sslCert
-core/v1.SecretKeySelector -		 -

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

-
sslKey
-core/v1.SecretKeySelector -		 -

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

-
sslRootCert
-core/v1.SecretKeySelector -		 -

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

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

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

-
gkeEnvironment
-bool -		 -

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

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

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

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

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

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

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

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

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

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

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

-
passwordStatus
-map[string]PasswordState -		 -

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

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

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

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

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

-
pg_hba
-[]string -		 -

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

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

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

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

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

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

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

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

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

-
pg_ident
-[]string -		 -

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

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

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

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Default to true before 1.22. Defaults to false in 1.22 or later.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

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

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

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

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

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

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

If enabled (default in 1.22 or later), 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 before 1.22), 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.

-
slotPrefix
-string -		 -

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

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

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

-
passwordSecret
-LocalObjectReference -		 -

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

-
connectionLimit
-int64 -		 -

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

-
validUntil
-meta/v1.Time -		 -

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

-
inRoles
-[]string -		 -

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

-
inherit
-bool -		 -

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

-
disablePassword
-bool -		 -

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

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

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

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

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

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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. -Only available in 1.22 or later

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore. -Only available in 1.22 or later

-
online
-bool -		 -

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' -Only available in 1.22 or later

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza -Only available in 1.22 or later

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

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

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets -Only available in 1.22 or later

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

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

-
serverCaSecretVersion
-string -		 -

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

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

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

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

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

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

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

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

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

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

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

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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

-
annotations
-map[string]string -		 -

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

-
className
-string -		 -

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
-string -		 -

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

-
tablespaceClassName
-map[string]string -		 -

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

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

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

-
onlineConfiguration
-OnlineConfiguration -		 -

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

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.2.mdx deleted file mode 100644 index 44fea134e09..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.2.mdx +++ /dev/null @@ -1,1025 +0,0 @@ ---- -title: 'API Reference - v1.18.2' -navTitle: v1.18.2 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy ` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.3.mdx deleted file mode 100644 index 656323c9680..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.3.mdx +++ /dev/null @@ -1,1042 +0,0 @@ ---- -title: 'API Reference - v1.18.3' -navTitle: v1.18.3 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy ` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| -------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef` | Reference to the secret that contains the encryption key | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.4.mdx deleted file mode 100644 index 7205013050a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.4.mdx +++ /dev/null @@ -1,1046 +0,0 @@ ---- -title: 'API Reference - v1.18.4' -navTitle: v1.18.4 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy ` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.5.mdx deleted file mode 100644 index a4eff37a5e7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.5.mdx +++ /dev/null @@ -1,1077 +0,0 @@ ---- -title: 'API Reference - v1.18.5' -navTitle: v1.18.5 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [DataSource](#DataSource) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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`. | [\*BackupSource](#BackupSource) | -| `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 {{name.ln}}, 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`. | [\*DataSource](#DataSource) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | 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: | 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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `topologySpreadConstraints` | TopologySpreadConstraints specifies how to spread matching pods among the given topology. More info: | \[]corev1.TopologySpreadConstraint | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## 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 | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer ` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | -| `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. | [\*PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.6.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.6.mdx deleted file mode 100644 index 7ef7c8e877a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.6.mdx +++ /dev/null @@ -1,1078 +0,0 @@ ---- -title: 'API Reference - v1.18.6' -navTitle: v1.18.6 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [DataSource](#DataSource) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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`. | [\*BackupSource](#BackupSource) | -| `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 {{name.ln}}, 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`. | [\*DataSource](#DataSource) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | 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: | 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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `topologySpreadConstraints` | TopologySpreadConstraints specifies how to spread matching pods among the given topology. More info: | \[]corev1.TopologySpreadConstraint | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## 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 | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer ` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | -| `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. | [\*PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.7.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.7.mdx deleted file mode 100644 index 0cc4c9bd1dc..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.7.mdx +++ /dev/null @@ -1,4003 +0,0 @@ ---- -title: 'API Reference - v1.18.7' -navTitle: v1.18.7 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

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

-
topologyKey
-string -		 -

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

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

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

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

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

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

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

-
storageSasToken
-SecretKeySelector -		 -

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

-
inheritFromAzureAD
-bool -		 -

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

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

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

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

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

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

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

-
- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

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

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

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

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

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

-
historyTags
-map[string]string -		 -

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

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

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

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

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

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

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

-
encoding
-string -		 -

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

-
localeCollate
-string -		 -

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

-
localeCType
-string -		 -

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

-
walSegmentSize
-int -		 -

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

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

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

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

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

-
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

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

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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
-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
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

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

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

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

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

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

-
imageName
-string -		 -

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

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

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

-
postgresGID
-int64 -		 -

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

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

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

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

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

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

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

-
startDelay
-int32 -		 -

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

-
stopDelay
-int32 -		 -

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

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

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

-
resources
-core/v1.ResourceRequirements -		 -

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

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default) or in-place (restart)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

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

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

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

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

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

-
env
-[]core/v1.EnvVar -		 -

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

-
envFrom
-[]core/v1.EnvFromSource -		 -

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

-
seccompProfile
-core/v1.SeccompProfile -		 -

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

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

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

-
readyInstances
-int -		 -

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

-
instancesStatus
-map[github.com/EnterpriseDB/cloud-native-postgres/pkg/utils.PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodName]github.com/EnterpriseDB/cloud-native-postgres/api/v1.InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

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

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

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

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

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

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

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

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

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

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

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

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
targetPrimaryTimestamp
-string -		 -

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

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled [Required]
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled [Required]
-bool -		 -

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

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs [Required]
-int32 -		 -

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

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

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

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

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

-
sslCert
-core/v1.SecretKeySelector -		 -

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

-
sslKey
-core/v1.SecretKeySelector -		 -

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

-
sslRootCert
-core/v1.SecretKeySelector -		 -

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

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials [Required]
-SecretKeySelector -		 -

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

-
gkeEnvironment
-bool -		 -

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

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

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

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

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

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

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

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls [Required]
-bool -		 -

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

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

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

-
inProgress [Required]
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

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

-
pg_hba
-[]string -		 -

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

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

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

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

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

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

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

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

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

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

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

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

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

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

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

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

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

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

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

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

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

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

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

-
serverCaSecretVersion
-string -		 -

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

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
metrics
-map[string]string -		 -

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

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

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

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

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

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

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

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodName]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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 [Required]
-bool -		 -

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

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.8.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.8.mdx deleted file mode 100644 index 2a8c420b625..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.8.mdx +++ /dev/null @@ -1,4003 +0,0 @@ ---- -title: 'API Reference - v1.18.8' -navTitle: v1.18.8 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

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

-
topologyKey
-string -		 -

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

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

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

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

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

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

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

-
storageSasToken
-SecretKeySelector -		 -

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

-
inheritFromAzureAD
-bool -		 -

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

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

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

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

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

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

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

-
- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

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

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

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

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

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

-
historyTags
-map[string]string -		 -

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

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

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

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

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

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

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

-
encoding
-string -		 -

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

-
localeCollate
-string -		 -

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

-
localeCType
-string -		 -

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

-
walSegmentSize
-int -		 -

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

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

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

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

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

-
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

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

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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
-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
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

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

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

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

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

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

-
imageName
-string -		 -

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

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

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

-
postgresGID
-int64 -		 -

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

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

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

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

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

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

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

-
startDelay
-int32 -		 -

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

-
stopDelay
-int32 -		 -

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

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

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

-
resources
-core/v1.ResourceRequirements -		 -

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

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default) or in-place (restart)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

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

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

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

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

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

-
env
-[]core/v1.EnvVar -		 -

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

-
envFrom
-[]core/v1.EnvFromSource -		 -

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

-
seccompProfile
-core/v1.SeccompProfile -		 -

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

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

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

-
readyInstances
-int -		 -

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

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

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

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

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

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

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

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

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

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

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

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

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

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
targetPrimaryTimestamp
-string -		 -

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

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled [Required]
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled [Required]
-bool -		 -

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

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs [Required]
-int32 -		 -

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

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

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

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

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

-
sslCert
-core/v1.SecretKeySelector -		 -

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

-
sslKey
-core/v1.SecretKeySelector -		 -

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

-
sslRootCert
-core/v1.SecretKeySelector -		 -

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

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials [Required]
-SecretKeySelector -		 -

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

-
gkeEnvironment
-bool -		 -

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

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

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

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

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

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

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

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls [Required]
-bool -		 -

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

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

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

-
inProgress [Required]
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

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

-
pg_hba
-[]string -		 -

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

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

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

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

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

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

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

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

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

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

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

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

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

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

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

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

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

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

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

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

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

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

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

-
serverCaSecretVersion
-string -		 -

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

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
metrics
-map[string]string -		 -

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

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

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

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

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

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

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

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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 [Required]
-bool -		 -

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

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.9.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.9.mdx deleted file mode 100644 index d07bfecf901..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.18.9.mdx +++ /dev/null @@ -1,4054 +0,0 @@ ---- -title: 'API Reference - v1.18.9' -navTitle: v1.18.9 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

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

-
topologyKey
-string -		 -

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

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

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

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

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

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

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

-
storageSasToken
-SecretKeySelector -		 -

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

-
inheritFromAzureAD
-bool -		 -

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

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

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

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

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

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

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

-
- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

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

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

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

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

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

-
historyTags
-map[string]string -		 -

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

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

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

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

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

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

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

-
encoding
-string -		 -

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

-
localeCollate
-string -		 -

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

-
localeCType
-string -		 -

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

-
walSegmentSize
-int -		 -

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

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

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

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

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

-
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

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

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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
-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
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

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

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

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

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

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

-
imageName
-string -		 -

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

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

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

-
postgresGID
-int64 -		 -

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

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

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

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

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

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

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

-
startDelay
-int32 -		 -

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

-
stopDelay
-int32 -		 -

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

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

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

-
resources
-core/v1.ResourceRequirements -		 -

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

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default) or in-place (restart)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

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

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

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

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

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

-
env
-[]core/v1.EnvVar -		 -

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

-
envFrom
-[]core/v1.EnvFromSource -		 -

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

-
seccompProfile
-core/v1.SeccompProfile -		 -

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

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

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

-
readyInstances
-int -		 -

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

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

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

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

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

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

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

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

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

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

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

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

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

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
targetPrimaryTimestamp
-string -		 -

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

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled [Required]
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled [Required]
-bool -		 -

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

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs [Required]
-int32 -		 -

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

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

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

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

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

-
sslCert
-core/v1.SecretKeySelector -		 -

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

-
sslKey
-core/v1.SecretKeySelector -		 -

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

-
sslRootCert
-core/v1.SecretKeySelector -		 -

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

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials [Required]
-SecretKeySelector -		 -

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

-
gkeEnvironment
-bool -		 -

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

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

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

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

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

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

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

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls [Required]
-bool -		 -

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

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

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

-
inProgress [Required]
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

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

-
pg_hba
-[]string -		 -

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

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

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

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

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

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

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

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

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

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

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

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

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

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

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

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

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

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

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

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

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

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

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

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

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

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

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

-
serverCaSecretVersion
-string -		 -

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

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

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

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

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

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

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

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

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

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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 [Required]
-bool -		 -

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

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.0.mdx deleted file mode 100644 index 4919a3d0eb3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.0.mdx +++ /dev/null @@ -1,1041 +0,0 @@ ---- -title: 'API Reference - v1.19.0' -navTitle: v1.19.0 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 `primary` 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: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy ` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash ` | 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 only when spec.failoverDelay is populated | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | string | -| `poolerIntegrations ` | The integration needed by poolers referencing the cluster | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash ` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP documentation for a list of options you can configure | map[string]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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| string | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| -------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef` | Reference to the secret that contains the encryption key | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.1.mdx deleted file mode 100644 index 9fb6492af80..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.1.mdx +++ /dev/null @@ -1,1047 +0,0 @@ ---- -title: 'API Reference - v1.19.1' -navTitle: v1.19.1 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 `primary` 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: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `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, which will default to `primary` 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 | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy ` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int | -| `readyInstances ` | Total number of ready instances in the cluster | 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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | 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 | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash ` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| 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, which will default to `primary` 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 | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| -------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef` | Reference to the secret that contains the encryption key | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.2.mdx deleted file mode 100644 index ade3034b69a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.2.mdx +++ /dev/null @@ -1,1051 +0,0 @@ ---- -title: 'API Reference - v1.19.2' -navTitle: v1.19.2 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 `primary` 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: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `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, which will default to `primary` 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 | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy ` | 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | 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 | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash ` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| 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, which will default to `primary` 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 | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.3.mdx deleted file mode 100644 index 11c956152bc..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.3.mdx +++ /dev/null @@ -1,1082 +0,0 @@ ---- -title: 'API Reference - v1.19.3' -navTitle: v1.19.3 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [DataSource](#DataSource) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 `primary` 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: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `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, which will default to `primary` 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 | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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`. | [\*BackupSource](#BackupSource) | -| `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 {{name.ln}}, 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`. | [\*DataSource](#DataSource) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | 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: | 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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | [AffinityConfiguration](#AffinityConfiguration) | -| `topologySpreadConstraints` | TopologySpreadConstraints specifies how to spread matching pods among the given topology. More info: | \[]corev1.TopologySpreadConstraint | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | 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 | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash ` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## 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 | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer ` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | -| `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. | [\*PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| 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, which will default to `primary` 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 | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.4.mdx deleted file mode 100644 index ded2535c517..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.4.mdx +++ /dev/null @@ -1,1084 +0,0 @@ ---- -title: 'API Reference - v1.19.4' -navTitle: v1.19.4 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [DataSource](#DataSource) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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 `primary` 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: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `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, which will default to `primary` 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 | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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`. | [\*BackupSource](#BackupSource) | -| `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 {{name.ln}}, 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`. | [\*DataSource](#DataSource) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | 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: | 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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | [AffinityConfiguration](#AffinityConfiguration) | -| `topologySpreadConstraints` | TopologySpreadConstraints specifies how to spread matching pods among the given topology. More info: | \[]corev1.TopologySpreadConstraint | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#resourcerequirements-v1-core) | -| `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 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` - default) or in-place (`restart`) | PrimaryUpdateMethod | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | 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 | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash ` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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 | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | - - - -## 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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## 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 | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer ` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | -| `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. | [\*PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| 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, which will default to `primary` 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 | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | - - - -## 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 | -| `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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.5.mdx deleted file mode 100644 index 577f0155e67..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.5.mdx +++ /dev/null @@ -1,4084 +0,0 @@ ---- -title: 'API Reference - v1.19.5' -navTitle: v1.19.5 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

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

-
topologyKey
-string -		 -

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

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

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

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

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

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

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

-
storageSasToken
-SecretKeySelector -		 -

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

-
inheritFromAzureAD
-bool -		 -

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

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

The policy to decide which instance should perform backups. Available -options are empty string, which will default to primary policy, primary -to have backups run always on primary instances, prefer-standby to have -backups run preferably on the most updated standby, if available.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

The policy to decide which instance should perform this backup. If empty, -it defaults to cluster.spec.backup.target. -Available options are empty string, which will default to primary -policy, primary to have backups run always on primary instances, -prefer-standby to have backups run preferably on the most updated -standby, if available.

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

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

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

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

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

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

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

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

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

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

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

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

-
historyTags
-map[string]string -		 -

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

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

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

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

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

-
owner
-string -		 -

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

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default) or in-place (restart)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[github.com/EnterpriseDB/cloud-native-postgres/pkg/utils.PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodName]github.com/EnterpriseDB/cloud-native-postgres/api/v1.InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

The policy to decide which instance should perform this backup. If empty, -it defaults to cluster.spec.backup.target. -Available options are empty string, which will default to primary -policy, primary to have backups run always on primary instances, -prefer-standby to have backups run preferably on the most updated -standby, if available.

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodName]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.6.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.6.mdx deleted file mode 100644 index e1cb052cda4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.19.6.mdx +++ /dev/null @@ -1,4084 +0,0 @@ ---- -title: 'API Reference - v1.19.6' -navTitle: v1.19.6 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

The policy to decide which instance should perform backups. Available -options are empty string, which will default to primary policy, primary -to have backups run always on primary instances, prefer-standby to have -backups run preferably on the most updated standby, if available.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

The policy to decide which instance should perform this backup. If empty, -it defaults to cluster.spec.backup.target. -Available options are empty string, which will default to primary -policy, primary to have backups run always on primary instances, -prefer-standby to have backups run preferably on the most updated -standby, if available.

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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 - default) or in-place (restart)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

The policy to decide which instance should perform this backup. If empty, -it defaults to cluster.spec.backup.target. -Available options are empty string, which will default to primary -policy, primary to have backups run always on primary instances, -prefer-standby to have backups run preferably on the most updated -standby, if available.

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.2.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.2.0.mdx deleted file mode 100644 index 77daeb7e781..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.2.0.mdx +++ /dev/null @@ -1,359 +0,0 @@ ---- -title: 'API Reference - v1.2.0' -navTitle: v1.2.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - - - -- [Backup](#backup) -- [BackupList](#backuplist) -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [AffinityConfiguration](#affinityconfiguration) -- [BackupConfiguration](#backupconfiguration) -- [BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) -- [BootstrapConfiguration](#bootstrapconfiguration) -- [BootstrapInitDB](#bootstrapinitdb) -- [BootstrapRecovery](#bootstraprecovery) -- [Cluster](#cluster) -- [ClusterList](#clusterlist) -- [ClusterSpec](#clusterspec) -- [ClusterStatus](#clusterstatus) -- [DataBackupConfiguration](#databackupconfiguration) -- [MonitoringConfiguration](#monitoringconfiguration) -- [NodeMaintenanceWindow](#nodemaintenancewindow) -- [PostgresConfiguration](#postgresconfiguration) -- [RecoveryTarget](#recoverytarget) -- [RollingUpdateStatus](#rollingupdatestatus) -- [S3Credentials](#s3credentials) -- [StorageConfiguration](#storageconfiguration) -- [WalBackupConfiguration](#walbackupconfiguration) -- [ScheduledBackup](#scheduledbackup) -- [ScheduledBackupList](#scheduledbackuplist) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [ScheduledBackupStatus](#scheduledbackupstatus) - -## Backup - -Backup is the Schema for the backups API - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the backup. More info: | [BackupSpec](#backupspec) | false | -| status | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#backupstatus) | false | - -## BackupList - -BackupList contains a list of Backup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of backups | \[][Backup](#backup) | true | - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Field | Description | Scheme | Required | -| ------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| encryption | Encryption method required to S3 API | string | false | -| backupId | The ID of the Barman backup | string | false | -| phase | The last backup status | BackupPhase | false | -| startedAt | When the backup was started | \*metav1.Time | false | -| stoppedAt | When the backup was terminated | \*metav1.Time | false | -| error | The detected error | string | false | -| commandOutput | The backup command output | string | false | -| commandError | The backup command output | string | false | - -## AffinityConfiguration - -AffinityConfiguration contains the info we need to create the affinity rules for Pods - -| Field | Description | Scheme | Required | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------- | -| enablePodAntiAffinity | Activates anti-affinity for the pods. The operator will define pods anti-affinity unless this field is explicitly set to false | \*bool | false | -| topologyKey | TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that | string | true | -| nodeSelector | NodeSelector is map of key-value pairs used to define the nodes on which the pods can run. More info: | map[string]string | false | - -## 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 - -| Field | Description | Scheme | Required | -| ----------------- | ------------------------------------------------- | ------------------------------------------------------------------- | -------- | -| barmanObjectStore | The configuration for the barman-cloud tool suite | \*[BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) | false | - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Field | Description | Scheme | Required | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| 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. | \*[WalBackupConfiguration](#walbackupconfiguration) | false | -| 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. | \*[DataBackupConfiguration](#databackupconfiguration) | false | - -## 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. - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------- | ----------------------------------------- | -------- | -| initdb | Bootstrap the cluster via initdb | \*[BootstrapInitDB](#bootstrapinitdb) | false | -| recovery | Bootstrap the cluster from a backup | \*[BootstrapRecovery](#bootstraprecovery) | false | - -## BootstrapInitDB - -BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------- | -| database | Name of the database used by the application. Default: `app`. | string | true | -| owner | Name of the owner of the database in the instance to be used by applications. Defaults to the value of the `database` key. | string | true | -| 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 | \*corev1.LocalObjectReference | false | -| redwood | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | false | -| options | The list of options that must be passed to initdb when creating the cluster | \[]string | false | - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -------- | -| backup | The backup we need to restore | corev1.LocalObjectReference | true | -| recoveryTarget | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | \*[RecoveryTarget](#recoverytarget) | false | - -## Cluster - -Cluster is the Schema for the PostgreSQL API - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#clusterspec) | false | -| status | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#clusterstatus) | false | - -## ClusterList - -ClusterList contains a list of Cluster - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | \[][Cluster](#cluster) | true | - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Field | Description | Scheme | Required | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| description | Description of this PostgreSQL cluster | string | false | -| imageName | Name of the container image | string | false | -| postgresUID | The UID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| postgresGID | The GID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| instances | Number of instances required in the cluster | int32 | true | -| minSyncReplicas | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | false | -| 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. | int32 | false | -| postgresql | Configuration of the PostgreSQL server | [PostgresConfiguration](#postgresconfiguration) | false | -| bootstrap | Instructions to bootstrap this cluster | \*[BootstrapConfiguration](#bootstrapconfiguration) | false | -| superuserSecret | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | \*corev1.LocalObjectReference | false | -| imagePullSecrets | 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. | \[]corev1.LocalObjectReference | false | -| storage | Configuration of the storage of the instances | [StorageConfiguration](#storageconfiguration) | false | -| startDelay | The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 30) | int32 | false | -| stopDelay | The time in seconds that is allowed for a PostgreSQL instance node to gracefully shutdown (default 30) | int32 | false | -| affinity | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#affinityconfiguration) | false | -| resources | Resources requirements of every generated Pod. Please refer to for more information. | corev1.ResourceRequirements | false | -| primaryUpdateStrategy | 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 | false | -| backup | The configuration to be used for backups | \*[BackupConfiguration](#backupconfiguration) | false | -| nodeMaintenanceWindow | Define a maintenance window for the Kubernetes nodes | \*[NodeMaintenanceWindow](#nodemaintenancewindow) | false | -| licenseKey | 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. | string | false | -| monitoring | The configuration of the monitoring infrastructure of this cluster | \*[MonitoringConfiguration](#monitoringconfiguration) | false | - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------- | -------- | -| instances | Total number of instances in the cluster | int32 | false | -| readyInstances | Total number of ready instances in the cluster | int32 | false | -| instancesStatus | Instances status | map[utils.PodStatus][]string | false | -| latestGeneratedNode | ID of the latest generated node (used to avoid node name clashing) | int32 | false | -| currentPrimary | Current primary instance | string | false | -| targetPrimary | Target primary instance, this is different from the previous one during a switchover or a failover | string | false | -| pvcCount | How many PVCs have been created by this cluster | int32 | false | -| jobCount | How many Jobs have been created by this cluster | int32 | false | -| danglingPVC | List of all the PVCs created by this cluster and still available which are not attached to a Pod | \[]string | false | -| initializingPVC | List of all the PVCs that are being initialized by this cluster | \[]string | false | -| licenseStatus | Status of the license | licensekey.Status | false | -| writeService | Current write pod | string | false | -| readService | Current list of read pods | string | false | -| phase | Current phase of the cluster | string | false | -| phaseReason | Reason for the current phase | string | false | - -## DataBackupConfiguration - -DataBackupConfiguration is the configuration of the backup of the data directory - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| 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` or `bzip2`. | CompressionType | false | -| 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 | false | -| 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 | false | -| jobs | The number of parallel jobs to be used to upload the backup, defaults to 2 | \*int32 | false | - -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Field | Description | Scheme | Required | -| ---------------------- | ----------------------------------------------------- | ------------------------------ | -------- | -| customQueriesConfigMap | The list of config maps containing the custom queries | \[]corev1.ConfigMapKeySelector | false | -| customQueriesSecret | The list of secrets containing the custom queries | \[]corev1.SecretKeySelector | false | - -## 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. - -| Field | Description | Scheme | Required | -| ---------- | ------------------------------------------------------------------------------------------ | ------ | -------- | -| inProgress | Is there a node maintenance activity in progress? | bool | true | -| reusePVC | Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere) | \*bool | true | - -## PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -| Field | Description | Scheme | Required | -| ---------- | ----------------------------------------------------------------------------------------- | ----------------- | -------- | -| parameters | PostgreSQL configuration options (postgresql.conf) | map[string]string | false | -| pg_hba | PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) | \[]string | false | - -## RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive. - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------- | ------ | -------- | -| targetTLI | The target timeline (\\"latest\\", \\"current\\" or a positive integer) | string | false | -| targetXID | The target transaction ID | string | false | -| targetName | The target name (to be previously created with `pg_create_restore_point`) | string | false | -| targetLSN | The target LSN (Log Sequence Number) | string | false | -| targetTime | The target time, in any unambiguous representation allowed by PostgreSQL | string | false | -| targetImmediate | End recovery as soon as a consistent state is reached | \*bool | false | -| exclusive | Set the target to be exclusive (defaults to true) | \*bool | false | - -## RollingUpdateStatus - -RollingUpdateStatus contains the information about an instance which is being updated - -| Field | Description | Scheme | Required | -| --------- | ----------------------------------- | ----------- | -------- | -| imageName | The image which we put into the Pod | string | true | -| startedAt | When the update has been started | metav1.Time | false | - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Field | Description | Scheme | Required | -| --------------- | -------------------------------------- | ------------------------ | -------- | -| accessKeyId | The reference to the access key id | corev1.SecretKeySelector | true | -| secretAccessKey | The reference to the secret access key | corev1.SecretKeySelector | true | - -## StorageConfiguration - -StorageConfiguration is the configuration of the storage of the PostgreSQL instances - -| Field | Description | Scheme | Required | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------- | -------- | -| 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 | false | -| 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 | true | -| resizeInUseVolumes | Resize existent PVCs, defaults to true | \*bool | false | -| pvcTemplate | Template to be used to generate the Persistent Volume Claim | \*corev1.PersistentVolumeClaimSpec | false | - -## WalBackupConfiguration - -WalBackupConfiguration is the configuration of the backup of the WAL stream - -| Field | Description | Scheme | Required | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| compression | Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), `gzip` or `bzip2`. | CompressionType | false | -| 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 | false | - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#scheduledbackupspec) | false | -| status | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#scheduledbackupstatus) | false | - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | \[][ScheduledBackup](#scheduledbackup) | true | - -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| suspend | If this backup is suspended of not | \*bool | false | -| schedule | The schedule in Cron format, see . | string | true | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Field | Description | Scheme | Required | -| ---------------- | -------------------------------------------------------------------------- | ------------- | -------- | -| lastCheckTime | The latest time the schedule | \*metav1.Time | false | -| lastScheduleTime | Information when was the last time that backup was successfully scheduled. | \*metav1.Time | false | -| nextScheduleTime | Next time we will run a backup | \*metav1.Time | false | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.2.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.2.1.mdx deleted file mode 100644 index 9ac47701765..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.2.1.mdx +++ /dev/null @@ -1,359 +0,0 @@ ---- -title: 'API Reference - v1.2.1' -navTitle: v1.2.1 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - - - -- [Backup](#backup) -- [BackupList](#backuplist) -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [AffinityConfiguration](#affinityconfiguration) -- [BackupConfiguration](#backupconfiguration) -- [BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) -- [BootstrapConfiguration](#bootstrapconfiguration) -- [BootstrapInitDB](#bootstrapinitdb) -- [BootstrapRecovery](#bootstraprecovery) -- [Cluster](#cluster) -- [ClusterList](#clusterlist) -- [ClusterSpec](#clusterspec) -- [ClusterStatus](#clusterstatus) -- [DataBackupConfiguration](#databackupconfiguration) -- [MonitoringConfiguration](#monitoringconfiguration) -- [NodeMaintenanceWindow](#nodemaintenancewindow) -- [PostgresConfiguration](#postgresconfiguration) -- [RecoveryTarget](#recoverytarget) -- [RollingUpdateStatus](#rollingupdatestatus) -- [S3Credentials](#s3credentials) -- [StorageConfiguration](#storageconfiguration) -- [WalBackupConfiguration](#walbackupconfiguration) -- [ScheduledBackup](#scheduledbackup) -- [ScheduledBackupList](#scheduledbackuplist) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [ScheduledBackupStatus](#scheduledbackupstatus) - -## Backup - -Backup is the Schema for the backups API - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the backup. More info: | [BackupSpec](#backupspec) | false | -| status | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#backupstatus) | false | - -## BackupList - -BackupList contains a list of Backup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of backups | \[][Backup](#backup) | true | - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Field | Description | Scheme | Required | -| ------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| encryption | Encryption method required to S3 API | string | false | -| backupId | The ID of the Barman backup | string | false | -| phase | The last backup status | BackupPhase | false | -| startedAt | When the backup was started | \*metav1.Time | false | -| stoppedAt | When the backup was terminated | \*metav1.Time | false | -| error | The detected error | string | false | -| commandOutput | The backup command output | string | false | -| commandError | The backup command output | string | false | - -## AffinityConfiguration - -AffinityConfiguration contains the info we need to create the affinity rules for Pods - -| Field | Description | Scheme | Required | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------- | -| enablePodAntiAffinity | Activates anti-affinity for the pods. The operator will define pods anti-affinity unless this field is explicitly set to false | \*bool | false | -| topologyKey | TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that | string | true | -| nodeSelector | NodeSelector is map of key-value pairs used to define the nodes on which the pods can run. More info: | map[string]string | false | - -## 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 - -| Field | Description | Scheme | Required | -| ----------------- | ------------------------------------------------- | ------------------------------------------------------------------- | -------- | -| barmanObjectStore | The configuration for the barman-cloud tool suite | \*[BarmanObjectStoreConfiguration](#barmanobjectstoreconfiguration) | false | - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Field | Description | Scheme | Required | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| s3Credentials | The credentials to use to upload data to S3 | [S3Credentials](#s3credentials) | true | -| endpointURL | Endpoint to be used to upload data to the cloud, overriding the automatic endpoint discovery | string | false | -| 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 | string | true | -| serverName | The server name on S3, the cluster name is used if this parameter is omitted | string | false | -| 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. | \*[WalBackupConfiguration](#walbackupconfiguration) | false | -| 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. | \*[DataBackupConfiguration](#databackupconfiguration) | false | - -## 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. - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------- | ----------------------------------------- | -------- | -| initdb | Bootstrap the cluster via initdb | \*[BootstrapInitDB](#bootstrapinitdb) | false | -| recovery | Bootstrap the cluster from a backup | \*[BootstrapRecovery](#bootstraprecovery) | false | - -## BootstrapInitDB - -BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------- | -| database | Name of the database used by the application. Default: `app`. | string | true | -| owner | Name of the owner of the database in the instance to be used by applications. Defaults to the value of the `database` key. | string | true | -| 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 | \*corev1.LocalObjectReference | false | -| redwood | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | false | -| options | The list of options that must be passed to initdb when creating the cluster | \[]string | false | - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Field | Description | Scheme | Required | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | -------- | -| backup | The backup we need to restore | corev1.LocalObjectReference | true | -| recoveryTarget | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | \*[RecoveryTarget](#recoverytarget) | false | - -## Cluster - -Cluster is the Schema for the PostgreSQL API - -| Field | Description | Scheme | Required | -| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#clusterspec) | false | -| status | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#clusterstatus) | false | - -## ClusterList - -ClusterList contains a list of Cluster - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | \[][Cluster](#cluster) | true | - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Field | Description | Scheme | Required | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------- | -| description | Description of this PostgreSQL cluster | string | false | -| imageName | Name of the container image | string | false | -| postgresUID | The UID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| postgresGID | The GID of the `postgres` user inside the image, defaults to `26` | int64 | false | -| instances | Number of instances required in the cluster | int32 | true | -| minSyncReplicas | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | false | -| 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. | int32 | false | -| postgresql | Configuration of the PostgreSQL server | [PostgresConfiguration](#postgresconfiguration) | false | -| bootstrap | Instructions to bootstrap this cluster | \*[BootstrapConfiguration](#bootstrapconfiguration) | false | -| superuserSecret | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | \*corev1.LocalObjectReference | false | -| imagePullSecrets | 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. | \[]corev1.LocalObjectReference | false | -| storage | Configuration of the storage of the instances | [StorageConfiguration](#storageconfiguration) | false | -| startDelay | The time in seconds that is allowed for a PostgreSQL instance to successfully start up (default 30) | int32 | false | -| stopDelay | The time in seconds that is allowed for a PostgreSQL instance node to gracefully shutdown (default 30) | int32 | false | -| affinity | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#affinityconfiguration) | false | -| resources | Resources requirements of every generated Pod. Please refer to for more information. | corev1.ResourceRequirements | false | -| primaryUpdateStrategy | 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 | false | -| backup | The configuration to be used for backups | \*[BackupConfiguration](#backupconfiguration) | false | -| nodeMaintenanceWindow | Define a maintenance window for the Kubernetes nodes | \*[NodeMaintenanceWindow](#nodemaintenancewindow) | false | -| licenseKey | 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. | string | false | -| monitoring | The configuration of the monitoring infrastructure of this cluster | \*[MonitoringConfiguration](#monitoringconfiguration) | false | - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------- | -------- | -| instances | Total number of instances in the cluster | int32 | false | -| readyInstances | Total number of ready instances in the cluster | int32 | false | -| instancesStatus | Instances status | map[utils.PodStatus][]string | false | -| latestGeneratedNode | ID of the latest generated node (used to avoid node name clashing) | int32 | false | -| currentPrimary | Current primary instance | string | false | -| targetPrimary | Target primary instance, this is different from the previous one during a switchover or a failover | string | false | -| pvcCount | How many PVCs have been created by this cluster | int32 | false | -| jobCount | How many Jobs have been created by this cluster | int32 | false | -| danglingPVC | List of all the PVCs created by this cluster and still available which are not attached to a Pod | \[]string | false | -| initializingPVC | List of all the PVCs that are being initialized by this cluster | \[]string | false | -| licenseStatus | Status of the license | licensekey.Status | false | -| writeService | Current write pod | string | false | -| readService | Current list of read pods | string | false | -| phase | Current phase of the cluster | string | false | -| phaseReason | Reason for the current phase | string | false | - -## DataBackupConfiguration - -DataBackupConfiguration is the configuration of the backup of the data directory - -| Field | Description | Scheme | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| 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` or `bzip2`. | CompressionType | false | -| 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 | false | -| 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 | false | -| jobs | The number of parallel jobs to be used to upload the backup, defaults to 2 | \*int32 | false | - -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Field | Description | Scheme | Required | -| ---------------------- | ----------------------------------------------------- | ------------------------------ | -------- | -| customQueriesConfigMap | The list of config maps containing the custom queries | \[]corev1.ConfigMapKeySelector | false | -| customQueriesSecret | The list of secrets containing the custom queries | \[]corev1.SecretKeySelector | false | - -## 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. - -| Field | Description | Scheme | Required | -| ---------- | ------------------------------------------------------------------------------------------ | ------ | -------- | -| inProgress | Is there a node maintenance activity in progress? | bool | true | -| reusePVC | Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere) | \*bool | true | - -## PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -| Field | Description | Scheme | Required | -| ---------- | ----------------------------------------------------------------------------------------- | ----------------- | -------- | -| parameters | PostgreSQL configuration options (postgresql.conf) | map[string]string | false | -| pg_hba | PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) | \[]string | false | - -## RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive. - -| Field | Description | Scheme | Required | -| --------------- | ------------------------------------------------------------------------- | ------ | -------- | -| targetTLI | The target timeline (\\"latest\\", \\"current\\" or a positive integer) | string | false | -| targetXID | The target transaction ID | string | false | -| targetName | The target name (to be previously created with `pg_create_restore_point`) | string | false | -| targetLSN | The target LSN (Log Sequence Number) | string | false | -| targetTime | The target time, in any unambiguous representation allowed by PostgreSQL | string | false | -| targetImmediate | End recovery as soon as a consistent state is reached | \*bool | false | -| exclusive | Set the target to be exclusive (defaults to true) | \*bool | false | - -## RollingUpdateStatus - -RollingUpdateStatus contains the information about an instance which is being updated - -| Field | Description | Scheme | Required | -| --------- | ----------------------------------- | ----------- | -------- | -| imageName | The image which we put into the Pod | string | true | -| startedAt | When the update has been started | metav1.Time | false | - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Field | Description | Scheme | Required | -| --------------- | -------------------------------------- | ------------------------ | -------- | -| accessKeyId | The reference to the access key id | corev1.SecretKeySelector | true | -| secretAccessKey | The reference to the secret access key | corev1.SecretKeySelector | true | - -## StorageConfiguration - -StorageConfiguration is the configuration of the storage of the PostgreSQL instances - -| Field | Description | Scheme | Required | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------- | -------- | -| 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 | false | -| 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 | true | -| resizeInUseVolumes | Resize existent PVCs, defaults to true | \*bool | false | -| pvcTemplate | Template to be used to generate the Persistent Volume Claim | \*corev1.PersistentVolumeClaimSpec | false | - -## WalBackupConfiguration - -WalBackupConfiguration is the configuration of the backup of the WAL stream - -| Field | Description | Scheme | Required | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- | -| compression | Compress a WAL file before sending it to the object store. Available options are empty string (no compression, default), `gzip` or `bzip2`. | CompressionType | false | -| 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 | false | - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| metadata | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#objectmeta-v1-meta) | false | -| spec | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#scheduledbackupspec) | false | -| status | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#scheduledbackupstatus) | false | - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------- | -| metadata | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#listmeta-v1-meta) | false | -| items | List of clusters | \[][ScheduledBackup](#scheduledbackup) | true | - -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Field | Description | Scheme | Required | -| -------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- | -| suspend | If this backup is suspended of not | \*bool | false | -| schedule | The schedule in Cron format, see . | string | true | -| cluster | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#localobjectreference-v1-core) | false | - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Field | Description | Scheme | Required | -| ---------------- | -------------------------------------------------------------------------- | ------------- | -------- | -| lastCheckTime | The latest time the schedule | \*metav1.Time | false | -| lastScheduleTime | Information when was the last time that backup was successfully scheduled. | \*metav1.Time | false | -| nextScheduleTime | Next time we will run a backup | \*metav1.Time | false | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.0.mdx deleted file mode 100644 index d77b690bb63..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.0.mdx +++ /dev/null @@ -1,1116 +0,0 @@ ---- -title: 'API Reference - v1.20.0' -navTitle: v1.20.0 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [ManagedConfiguration](#ManagedConfiguration) -- [ManagedRoles](#ManagedRoles) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PasswordState](#PasswordState) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RoleConfiguration](#RoleConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*BackupSource](#BackupSource) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy ` | 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 | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | [\*ManagedConfiguration](#ManagedConfiguration) | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `managedRolesStatus ` | ManagedRolesStatus reports the state of the managed roles in the cluster | [ManagedRoles](#ManagedRoles) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | 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 | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash ` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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` | [\[\]RoleConfiguration](#RoleConfiguration) | - - - -## 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 | [map\[string\]PasswordState](#PasswordState) | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -| Name | Description | Type | -| ------------------ | -------------------------------------------- | --------------------------------------- | -| `serverTLS ` | The server TLS secret version | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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: - -| 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) | [\*LocalObjectReference](#LocalObjectReference) | -| `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). | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| 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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.1.mdx deleted file mode 100644 index 8e05a086ab1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.1.mdx +++ /dev/null @@ -1,1148 +0,0 @@ ---- -title: 'API Reference - v1.20.1' -navTitle: v1.20.1 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [DataSource](#DataSource) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [ManagedConfiguration](#ManagedConfiguration) -- [ManagedRoles](#ManagedRoles) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PasswordState](#PasswordState) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RoleConfiguration](#RoleConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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`. | [\*BackupSource](#BackupSource) | -| `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 {{name.ln}}, 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`. | [\*DataSource](#DataSource) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | 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: | 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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | [AffinityConfiguration](#AffinityConfiguration) | -| `topologySpreadConstraints` | TopologySpreadConstraints specifies how to spread matching pods among the given topology. More info: | \[]corev1.TopologySpreadConstraint | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcerequirements-v1-core) | -| `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 | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | [\*ManagedConfiguration](#ManagedConfiguration) | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `managedRolesStatus ` | ManagedRolesStatus reports the state of the managed roles in the cluster | [ManagedRoles](#ManagedRoles) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | 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 | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash ` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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` | [\[\]RoleConfiguration](#RoleConfiguration) | - - - -## 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 | [map\[string\]PasswordState](#PasswordState) | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## 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 | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer ` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | -| `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. | [\*PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 (defaults to 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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: - -| 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `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). | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| 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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta) | - - - -## 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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.2.mdx deleted file mode 100644 index c1430a0235e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.2.mdx +++ /dev/null @@ -1,1150 +0,0 @@ ---- -title: 'API Reference - v1.20.2' -navTitle: v1.20.2 -pdfExclude: true ---- - -{{name.ln}} extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [Pooler](#pooler) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSource](#BackupSource) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanCredentials](#BarmanCredentials) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [DataSource](#DataSource) -- [EPASConfiguration](#EPASConfiguration) -- [EmbeddedObjectMetadata](#EmbeddedObjectMetadata) -- [ExternalCluster](#ExternalCluster) -- [GoogleCredentials](#GoogleCredentials) -- [Import](#Import) -- [ImportSource](#ImportSource) -- [InstanceID](#InstanceID) -- [InstanceReportedState](#InstanceReportedState) -- [LDAPBindAsAuth](#LDAPBindAsAuth) -- [LDAPBindSearchAuth](#LDAPBindSearchAuth) -- [LDAPConfig](#LDAPConfig) -- [LocalObjectReference](#LocalObjectReference) -- [ManagedConfiguration](#ManagedConfiguration) -- [ManagedRoles](#ManagedRoles) -- [Metadata](#Metadata) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PasswordState](#PasswordState) -- [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) -- [PgBouncerSecrets](#PgBouncerSecrets) -- [PgBouncerSpec](#PgBouncerSpec) -- [PodTemplateSpec](#PodTemplateSpec) -- [Pooler](#Pooler) -- [PoolerIntegrations](#PoolerIntegrations) -- [PoolerList](#PoolerList) -- [PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) -- [PoolerSecrets](#PoolerSecrets) -- [PoolerSpec](#PoolerSpec) -- [PoolerStatus](#PoolerStatus) -- [PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) -- [ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) -- [RoleConfiguration](#RoleConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretVersion](#SecretVersion) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [ServiceAccountTemplate](#ServiceAccountTemplate) -- [StorageConfiguration](#StorageConfiguration) -- [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) -- [TDEConfiguration](#TDEConfiguration) -- [Topology](#Topology) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `nodeAffinity ` | NodeAffinity describes node affinity scheduling rules for the pod. More info: | \*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: | \[]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: | 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | -| `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: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## 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. | [\*SecretKeySelector](#SecretKeySelector) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `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. | [\*SecretKeySelector](#SecretKeySelector) | -| `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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `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 | [\*InstanceID](#InstanceID) | - - - -## 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 | [\*GoogleCredentials](#GoogleCredentials) | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials ` | The credentials to use to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | -| `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `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`) | [\*Import](#Import) | -| `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) | [\*PostInitApplicationSQLRefs](#PostInitApplicationSQLRefs) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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`. | [\*BackupSource](#BackupSource) | -| `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 {{name.ln}}, 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`. | [\*DataSource](#DataSource) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | -| `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 | [\*LocalObjectReference](#LocalObjectReference) | - - - -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## 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 | [\*EmbeddedObjectMetadata](#EmbeddedObjectMetadata) | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | 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: | 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 | [PostgresConfiguration](#PostgresConfiguration) | -| `replicationSlots ` | Replication slots management configuration | [\*ReplicationSlotsConfiguration](#ReplicationSlotsConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `serviceAccountTemplate ` | Configure the generation of the service account | [\*ServiceAccountTemplate](#ServiceAccountTemplate) | -| `walStorage ` | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | [\*StorageConfiguration](#StorageConfiguration) | -| `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 | [AffinityConfiguration](#AffinityConfiguration) | -| `topologySpreadConstraints` | TopologySpreadConstraints specifies how to spread matching pods among the given topology. More info: | \[]corev1.TopologySpreadConstraint | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#resourcerequirements-v1-core) | -| `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 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 | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow ` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `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 | [\*ManagedConfiguration](#ManagedConfiguration) | -| `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 | [map\[PodName\]InstanceReportedState](#InstanceReportedState) | -| `managedRolesStatus ` | ManagedRolesStatus reports the state of the managed roles in the cluster | [ManagedRoles](#ManagedRoles) | -| `timelineID ` | The timeline of the Postgres cluster | int | -| `topology ` | Instances topology. | [Topology](#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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `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 | -| `cloudNativePostgresqlCommitHash ` | 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 | [\*PoolerIntegrations](#PoolerIntegrations) | -| `cloudNativePostgresqlOperatorHash ` | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | --------------------------------------- | -| `audit` | If true enables edb_audit logging | bool | -| `tde ` | TDE configuration | [\*TDEConfiguration](#TDEConfiguration) | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | - - - -## 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* | [ImportSource](#ImportSource) | -| `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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `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 | [\*LDAPBindAsAuth](#LDAPBindAsAuth) | -| `bindSearchAuth` | Bind+Search authentication configuration | [\*LDAPBindSearchAuth](#LDAPBindSearchAuth) | - - - -## 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` | [\[\]RoleConfiguration](#RoleConfiguration) | - - - -## 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 | [map\[string\]PasswordState](#PasswordState) | - - - -## 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: | 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: | 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 | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | -| `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 | [SecretVersion](#SecretVersion) | - - - -## 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 CNP Cluster integration will be triggered. | [\*LocalObjectReference](#LocalObjectReference) | -| `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 CNP Cluster integration will be triggered. | string | -| `parameters ` | Additional parameters to be passed to PgBouncer - please check the CNP 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: - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | -| `metadata` | Standard object's metadata. More info: | [Metadata](#Metadata) | -| `spec ` | Specification of the desired behavior of the pod. More info: | corev1.PodSpec | - - - -## Pooler - -Pooler is the Schema for the poolers API - -| Name | Description | Type | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta) | -| `spec ` | | [PoolerSpec](#PoolerSpec) | -| `status ` | | [PoolerStatus](#PoolerStatus) | - - - -## PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -| Name | Description | Type | -| ---------------------- | ----------- | --------------------------------------------------------- | -| `pgBouncerIntegration` | | [PgBouncerIntegrationStatus](#PgBouncerIntegrationStatus) | - - - -## PoolerList - -PoolerList contains a list of Pooler - -| Name | Description | Type | -| ---------- | ------------- | -------------------------------------------------------------------------------------------------------- | -| `metadata` | | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta) | -| `items ` | - *mandatory* | [\[\]Pooler](#Pooler) | - - - -## 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 | [SecretVersion](#SecretVersion) | -| `serverCA ` | The server CA secret version | [SecretVersion](#SecretVersion) | -| `clientCA ` | The client CA secret version | [SecretVersion](#SecretVersion) | -| `pgBouncerSecrets` | The version of the secrets used by PgBouncer | [\*PgBouncerSecrets](#PgBouncerSecrets) | - - - -## 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* | [LocalObjectReference](#LocalObjectReference) | -| `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 | [\*PodTemplateSpec](#PodTemplateSpec) | -| `pgbouncer ` | The PgBouncer configuration - *mandatory* | [\*PgBouncerSpec](#PgBouncerSpec) | -| `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. | [\*PoolerMonitoringConfiguration](#PoolerMonitoringConfiguration) | - - - -## PoolerStatus - -PoolerStatus defines the observed state of Pooler - -| Name | Description | Type | -| ----------- | ----------------------------------------- | --------------------------------- | -| `secrets ` | The resource version of the config object | [\*PoolerSecrets](#PoolerSecrets) | -| `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 | [\[\]SecretKeySelector](#SecretKeySelector) | -| `configMapRefs` | ConfigMapRefs holds a list of references to ConfigMaps | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `syncReplicaElectionConstraint` | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be set up. | [SyncReplicaElectionConstraints](#SyncReplicaElectionConstraints) | -| `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 | [\*LDAPConfig](#LDAPConfig) | - - - -## 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 | [\*ReplicationSlotsHAConfiguration](#ReplicationSlotsHAConfiguration) | -| `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 `_cnp_`. | 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: - -| 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `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). | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | - - - -## 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 | [\*SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey ` | The reference to the secret access key | [\*SecretKeySelector](#SecretKeySelector) | -| `region ` | The reference to the secret containing the region name | [\*SecretKeySelector](#SecretKeySelector) | -| `sessionToken ` | The references to the session key | [\*SecretKeySelector](#SecretKeySelector) | -| `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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | -| `backupOwnerReference` | 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
| 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 | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta) | - - - -## 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* | [Metadata](#Metadata) | - - - -## 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 | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#persistentvolumeclaim-v1-core) | - - - -## 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 | - - - -## TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -| Name | Description | Type | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| `enabled ` | True if we want to have TDE enabled | bool | -| `secretKeyRef ` | Reference to the secret that contains the encryption key | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `wrapCommand ` | WrapCommand is the encrypt command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `unwrapCommand ` | UnwrapCommand is the decryption command provided by the user | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | -| `passphraseCommand` | PassphraseCommand is the command executed to get the passphrase that will be passed to the OpenSSL command to encrypt and decrypt | [\*v1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#secretkeyselector-v1-core) | - - - -## 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.3.mdx deleted file mode 100644 index c11087a0562..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.3.mdx +++ /dev/null @@ -1,4367 +0,0 @@ ---- -title: 'API Reference - v1.20.3' -navTitle: v1.20.3 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey [Required]
-string -		 -

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.

-
licenseKeySecret [Required]
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[github.com/EnterpriseDB/cloud-native-postgres/pkg/utils.PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodName]github.com/EnterpriseDB/cloud-native-postgres/api/v1.InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus [Required]
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodName]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.4.mdx deleted file mode 100644 index f65301e8180..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.4.mdx +++ /dev/null @@ -1,4367 +0,0 @@ ---- -title: 'API Reference - v1.20.4' -navTitle: v1.20.4 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey [Required]
-string -		 -

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.

-
licenseKeySecret [Required]
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus [Required]
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.5.mdx deleted file mode 100644 index e16a092cff8..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.5.mdx +++ /dev/null @@ -1,4418 +0,0 @@ ---- -title: 'API Reference - v1.20.5' -navTitle: v1.20.5 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey [Required]
-string -		 -

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.

-
licenseKeySecret [Required]
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus [Required]
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.6.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.6.mdx deleted file mode 100644 index c71d93540b2..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.20.6.mdx +++ /dev/null @@ -1,4433 +0,0 @@ ---- -title: 'API Reference - v1.20.6' -navTitle: v1.20.6 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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

- - - - - - - - - - - - - - - - -
FieldDescription
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

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 - smartStopDelay).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey [Required]
-string -		 -

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.

-
licenseKeySecret [Required]
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus [Required]
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.0.mdx deleted file mode 100644 index fa7043a8f6e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.0.mdx +++ /dev/null @@ -1,4393 +0,0 @@ ---- -title: 'API Reference - v1.21.0' -navTitle: v1.21.0 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA and PG_WAL

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[github.com/EnterpriseDB/cloud-native-postgres/pkg/utils.PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodName]github.com/EnterpriseDB/cloud-native-postgres/api/v1.InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodName]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.1.mdx deleted file mode 100644 index 507de91eb34..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.1.mdx +++ /dev/null @@ -1,4509 +0,0 @@ ---- -title: 'API Reference - v1.21.1' -navTitle: v1.21.1 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA and PG_WAL

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format

-
lastSuccessfulBackup
-string -		 -

Stored as a date in RFC3339 format

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.2.mdx deleted file mode 100644 index 90351f5c457..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.2.mdx +++ /dev/null @@ -1,4576 +0,0 @@ ---- -title: 'API Reference - v1.21.2' -navTitle: v1.21.2 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA and PG_WAL

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.3.mdx deleted file mode 100644 index 77e04e930eb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.3.mdx +++ /dev/null @@ -1,4591 +0,0 @@ ---- -title: 'API Reference - v1.21.3' -navTitle: v1.21.3 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA and PG_WAL

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.4.mdx deleted file mode 100644 index 57852a0dfbf..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.4.mdx +++ /dev/null @@ -1,4653 +0,0 @@ ---- -title: 'API Reference - v1.21.4' -navTitle: v1.21.4 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA and PG_WAL

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.5.mdx deleted file mode 100644 index 134234e9892..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.5.mdx +++ /dev/null @@ -1,4668 +0,0 @@ ---- -title: 'API Reference - v1.21.5' -navTitle: v1.21.5 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA and PG_WAL

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.6.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.6.mdx deleted file mode 100644 index b61a0e69380..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.21.6.mdx +++ /dev/null @@ -1,4678 +0,0 @@ ---- -title: 'API Reference - v1.21.6' -navTitle: v1.21.6 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA and PG_WAL

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to true.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

StorageConfiguration is the configuration of the storage of the PostgreSQL instances

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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

-
size
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.0.mdx deleted file mode 100644 index 4f8530a8224..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.0.mdx +++ /dev/null @@ -1,4742 +0,0 @@ ---- -title: 'API Reference - v1.22.0' -navTitle: v1.22.0 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.1.mdx deleted file mode 100644 index b6a27befd64..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.1.mdx +++ /dev/null @@ -1,4757 +0,0 @@ ---- -title: 'API Reference - v1.22.1' -navTitle: v1.22.1 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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 CNP Cluster integration will be triggered.

-
authQuery
-string -		 -

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 CNP Cluster integration will be triggered.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.2.mdx deleted file mode 100644 index 6c71f3ec7ca..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.2.mdx +++ /dev/null @@ -1,4819 +0,0 @@ ---- -title: 'API Reference - v1.22.2' -navTitle: v1.22.2 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.3.mdx deleted file mode 100644 index c977ad20150..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.3.mdx +++ /dev/null @@ -1,4834 +0,0 @@ ---- -title: 'API Reference - v1.22.3' -navTitle: v1.22.3 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.4.mdx deleted file mode 100644 index 4b9d6c0d306..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.4.mdx +++ /dev/null @@ -1,4844 +0,0 @@ ---- -title: 'API Reference - v1.22.4' -navTitle: v1.22.4 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.5.mdx deleted file mode 100644 index b325c44c017..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.5.mdx +++ /dev/null @@ -1,4844 +0,0 @@ ---- -title: 'API Reference - v1.22.5' -navTitle: v1.22.5 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.6.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.6.mdx deleted file mode 100644 index ef12ecbb8ff..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.6.mdx +++ /dev/null @@ -1,4843 +0,0 @@ ---- -title: 'API Reference - v1.22.6' -navTitle: v1.22.6 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.7.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.7.mdx deleted file mode 100644 index f64c5bff4ae..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.7.mdx +++ /dev/null @@ -1,4278 +0,0 @@ ---- -title: 'API Reference - v1.22.7' -navTitle: v1.22.7 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.8.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.8.mdx deleted file mode 100644 index 29bcae1ecce..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.8.mdx +++ /dev/null @@ -1,5905 +0,0 @@ ---- -title: API Reference - v1.22.8 -navTitle: v1.22.8 -pdfExclude: true - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Database - -

Database is the Schema for the databases API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Database
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-DatabaseSpec -		 -

Specification of the desired Database. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
status
-DatabaseStatus -		 -

Most recently observed status of the Database. 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

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## Publication - -

Publication is the Schema for the publications API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Publication
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PublicationSpec -		 - No description provided.
status [Required]
-PublicationStatus -		 - No description provided.
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## Subscription - -

Subscription is the Schema for the subscriptions API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Subscription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-SubscriptionSpec -		 - No description provided.
status [Required]
-SubscriptionStatus -		 - No description provided.
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup -Only available in 1.25 or later

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
pluginMetadata
-map[string]string -		 -

A map containing the plugin metadata

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
locale
-string -		 -

Sets the default collation order and character classification in the new database. -Only available in 1.25 or later

-
localeProvider
-string -		 -

This option sets the locale provider for databases created in the new cluster. -Available from PostgreSQL 16. -Only available in 1.25 or later

-
icuLocale
-string -		 -

Specifies the ICU locale when the ICU provider is used. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 15. -Only available in 1.25 or later

-
icuRules
-string -		 -

Specifies additional collation rules to customize the behavior of the default collation. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 16. -Only available in 1.25 or later

-
builtinLocale
-string -		 -

Specifies the locale name when the builtin provider is used. -This option requires localeProvider to be set to builtin. -Available from PostgreSQL 17. -Only available in 1.25 or later

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty) -Only available in 1.25 or later

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty) -Only available in 1.25 or later

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog -Only available in 1.25 or later

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-ExternalClusterList -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration -Only available in 1.25 or later

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataDurabilityLevel - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are required or preferred.

- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases.

- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## DatabaseSpec - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseSpec is the specification of a Postgresql Database, built around the -CREATE DATABASE, ALTER DATABASE, and DROP DATABASE SQL commands of -PostgreSQL.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster hosting the database.

-
ensure
-EnsureOption -		 -

Ensure the PostgreSQL database is present or absent - defaults to "present".

-
name [Required]
-string -		 -

The name of the database to create inside PostgreSQL. This setting cannot be changed.

-
owner [Required]
-string -		 -

Maps to the OWNER parameter of CREATE DATABASE. -Maps to the OWNER TO command of ALTER DATABASE. -The role name of the user who owns the database inside PostgreSQL.

-
template
-string -		 -

Maps to the TEMPLATE parameter of CREATE DATABASE. This setting -cannot be changed. The name of the template from which to create -this database.

-
encoding
-string -		 -

Maps to the ENCODING parameter of CREATE DATABASE. This setting -cannot be changed. Character set encoding to use in the database.

-
locale
-string -		 -

Maps to the LOCALE parameter of CREATE DATABASE. This setting -cannot be changed. Sets the default collation order and character -classification in the new database.

-
localeProvider
-string -		 -

Maps to the LOCALE_PROVIDER parameter of CREATE DATABASE. This -setting cannot be changed. This option sets the locale provider for -databases created in the new cluster. Available from PostgreSQL 16.

-
localeCollate
-string -		 -

Maps to the LC_COLLATE parameter of CREATE DATABASE. This -setting cannot be changed.

-
localeCType
-string -		 -

Maps to the LC_CTYPE parameter of CREATE DATABASE. This setting -cannot be changed.

-
icuLocale
-string -		 -

Maps to the ICU_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the ICU locale when the ICU -provider is used. This option requires localeProvider to be set to -icu. Available from PostgreSQL 15.

-
icuRules
-string -		 -

Maps to the ICU_RULES parameter of CREATE DATABASE. This setting -cannot be changed. Specifies additional collation rules to customize -the behavior of the default collation. This option requires -localeProvider to be set to icu. Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Maps to the BUILTIN_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the locale name when the -builtin provider is used. This option requires localeProvider to -be set to builtin. Available from PostgreSQL 17.

-
collationVersion
-string -		 -

Maps to the COLLATION_VERSION parameter of CREATE DATABASE. This -setting cannot be changed.

-
isTemplate
-bool -		 -

Maps to the IS_TEMPLATE parameter of CREATE DATABASE and ALTER DATABASE. If true, this database is considered a template and can -be cloned by any user with CREATEDB privileges.

-
allowConnections
-bool -		 -

Maps to the ALLOW_CONNECTIONS parameter of CREATE DATABASE and -ALTER DATABASE. If false then no one can connect to this database.

-
connectionLimit
-int -		 -

Maps to the CONNECTION LIMIT clause of CREATE DATABASE and -ALTER DATABASE. How many concurrent connections can be made to -this database. -1 (the default) means no limit.

-
tablespace
-string -		 -

Maps to the TABLESPACE parameter of CREATE DATABASE. -Maps to the SET TABLESPACE command of ALTER DATABASE. -The name of the tablespace (in PostgreSQL) that will be associated -with the new database. This tablespace will be the default -tablespace used for objects created in this database.

-
databaseReclaimPolicy
-DatabaseReclaimPolicy -		 -

The policy for end-of-life maintenance of this database.

-
- -
- -## DatabaseStatus - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseStatus defines the observed state of Database

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the database was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalClusterList - -(Alias of `[]github.com/EnterpriseDB/cloud-native-postgres/api/v1.ExternalCluster`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalClusterList is a list of external clusters

- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
pgDumpExtraOptions
-[]string -		 -

List of custom options to pass to the pg_dump command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design. -Only available in 1.25 or later

-
pgRestoreExtraOptions
-[]string -		 -

List of custom options to pass to the pg_restore command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design. -Only available in 1.25 or later

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster -Only available in 1.25 or later

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types -Only available in 1.25 or later

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances. -Only available in 1.25 or later

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
enabled
-bool -		 -

Enabled is true if this plugin will be used

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginConfigurationList - -(Alias of `[]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PluginConfiguration`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PluginConfigurationList represent a set of plugin with their -configuration parameters

- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
restoreJobHookCapabilities
-[]string -		 -

RestoreJobHookCapabilities are the list of capabilities of the -plugin regarding the RestoreJobHook management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created -Only available in 1.25 or later

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature -Only available in 1.25 or later

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-Probe -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-Probe -		 -

The readiness probe configuration

-
- -
- -## PublicationReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications.

- -
- -## PublicationSpec - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationSpec defines the desired state of Publication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "publisher"

-
name [Required]
-string -		 -

The name of the publication inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "publisher" cluster

-
parameters
-map[string]string -		 -

Publication parameters part of the WITH clause as expected by -PostgreSQL CREATE PUBLICATION command

-
target [Required]
-PublicationTarget -		 -

Target of the publication as expected by PostgreSQL CREATE PUBLICATION command

-
publicationReclaimPolicy
-PublicationReclaimPolicy -		 -

The policy for end-of-life maintenance of this publication

-
- -
- -## PublicationStatus - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationStatus defines the observed state of Publication

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the publication was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## PublicationTarget - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationTarget is what this publication should publish

- - - - - - - - - - - -
FieldDescription
allTables
-bool -		 -

Marks the publication as one that replicates changes for all tables -in the database, including tables created in the future. -Corresponding to FOR ALL TABLES in PostgreSQL.

-
objects
-[]PublicationTargetObject -		 -

Just the following schema objects

-
- -
- -## PublicationTargetObject - -**Appears in:** - -- [PublicationTarget](#postgresql-k8s-enterprisedb-io-v1-PublicationTarget) - -

PublicationTargetObject is an object to publish

- - - - - - - - - - - -
FieldDescription
tablesInSchema
-string -		 -

Marks the publication as one that replicates changes for all tables -in the specified list of schemas, including tables created in the -future. Corresponding to FOR TABLES IN SCHEMA in PostgreSQL.

-
table
-PublicationTargetTable -		 -

Specifies a list of tables to add to the publication. Corresponding -to FOR TABLE in PostgreSQL.

-
- -
- -## PublicationTargetTable - -**Appears in:** - -- [PublicationTargetObject](#postgresql-k8s-enterprisedb-io-v1-PublicationTargetObject) - -

PublicationTargetTable is a table to publish

- - - - - - - - - - - - - - - - - -
FieldDescription
only
-bool -		 -

Whether to limit to the table only or include all its descendants

-
name [Required]
-string -		 -

The table name

-
schema
-string -		 -

The schema name

-
columns
-[]string -		 -

The columns to publish

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary -Only available in 1.25 or later

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters -Only available in 1.25 or later

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met. -Only available in 1.25 or later

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used. -Only available in 1.25 or later

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots -Only available in 1.25 or later

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup -Only available in 1.25 or later

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SubscriptionReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [SubscriptionSpec](#postgresql-k8s-enterprisedb-io-v1-SubscriptionSpec) - -

SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions.

- -
- -## SubscriptionSpec - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionSpec defines the desired state of Subscription

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "subscriber"

-
name [Required]
-string -		 -

The name of the subscription inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "subscriber" cluster

-
parameters
-map[string]string -		 -

Subscription parameters part of the WITH clause as expected by -PostgreSQL CREATE SUBSCRIPTION command

-
publicationName [Required]
-string -		 -

The name of the publication inside the PostgreSQL database in the -"publisher"

-
publicationDBName
-string -		 -

The name of the database containing the publication on the external -cluster. Defaults to the one in the external cluster definition.

-
externalClusterName [Required]
-string -		 -

The name of the external cluster with the publication ("publisher")

-
subscriptionReclaimPolicy
-SubscriptionReclaimPolicy -		 -

The policy for end-of-life maintenance of this subscription

-
- -
- -## SubscriptionStatus - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionStatus defines the observed state of Subscription

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the subscription was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
dataDurability
-DataDurabilityLevel -		 -

If set to "required", data durability is strictly enforced. Write operations -with synchronous commit settings (on, remote_write, or remote_apply) will -block if there are insufficient healthy replicas, ensuring data persistence. -If set to "preferred", data durability is maintained when healthy replicas -are available, but the required number of instances will adjust dynamically -if replicas become unavailable. This setting relaxes strict durability enforcement -to allow for operational continuity. This setting is only applicable if both -standbyNamesPre and standbyNamesPost are unset (empty).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.9.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.9.mdx deleted file mode 100644 index 7753c416b3e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.22.9.mdx +++ /dev/null @@ -1,5905 +0,0 @@ ---- -title: API Reference - v1.22.9 -navTitle: v1.22.9 -pdfExclude: true - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Database - -

Database is the Schema for the databases API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Database
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-DatabaseSpec -		 -

Specification of the desired Database. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
status
-DatabaseStatus -		 -

Most recently observed status of the Database. 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

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## Publication - -

Publication is the Schema for the publications API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Publication
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PublicationSpec -		 - No description provided.
status [Required]
-PublicationStatus -		 - No description provided.
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## Subscription - -

Subscription is the Schema for the subscriptions API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Subscription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-SubscriptionSpec -		 - No description provided.
status [Required]
-SubscriptionStatus -		 - No description provided.
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup -Only available in 1.25 or later

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
pluginMetadata
-map[string]string -		 -

A map containing the plugin metadata

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
locale
-string -		 -

Sets the default collation order and character classification in the new database. -Only available in 1.25 or later

-
localeProvider
-string -		 -

This option sets the locale provider for databases created in the new cluster. -Available from PostgreSQL 16. -Only available in 1.25 or later

-
icuLocale
-string -		 -

Specifies the ICU locale when the ICU provider is used. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 15. -Only available in 1.25 or later

-
icuRules
-string -		 -

Specifies additional collation rules to customize the behavior of the default collation. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 16. -Only available in 1.25 or later

-
builtinLocale
-string -		 -

Specifies the locale name when the builtin provider is used. -This option requires localeProvider to be set to builtin. -Available from PostgreSQL 17. -Only available in 1.25 or later

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty) -Only available in 1.25 or later

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty) -Only available in 1.25 or later

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog -Only available in 1.25 or later

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-ExternalClusterList -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration -Only available in 1.25 or later

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataDurabilityLevel - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are required or preferred.

- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases.

- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## DatabaseSpec - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseSpec is the specification of a Postgresql Database, built around the -CREATE DATABASE, ALTER DATABASE, and DROP DATABASE SQL commands of -PostgreSQL.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster hosting the database.

-
ensure
-EnsureOption -		 -

Ensure the PostgreSQL database is present or absent - defaults to "present".

-
name [Required]
-string -		 -

The name of the database to create inside PostgreSQL. This setting cannot be changed.

-
owner [Required]
-string -		 -

Maps to the OWNER parameter of CREATE DATABASE. -Maps to the OWNER TO command of ALTER DATABASE. -The role name of the user who owns the database inside PostgreSQL.

-
template
-string -		 -

Maps to the TEMPLATE parameter of CREATE DATABASE. This setting -cannot be changed. The name of the template from which to create -this database.

-
encoding
-string -		 -

Maps to the ENCODING parameter of CREATE DATABASE. This setting -cannot be changed. Character set encoding to use in the database.

-
locale
-string -		 -

Maps to the LOCALE parameter of CREATE DATABASE. This setting -cannot be changed. Sets the default collation order and character -classification in the new database.

-
localeProvider
-string -		 -

Maps to the LOCALE_PROVIDER parameter of CREATE DATABASE. This -setting cannot be changed. This option sets the locale provider for -databases created in the new cluster. Available from PostgreSQL 16.

-
localeCollate
-string -		 -

Maps to the LC_COLLATE parameter of CREATE DATABASE. This -setting cannot be changed.

-
localeCType
-string -		 -

Maps to the LC_CTYPE parameter of CREATE DATABASE. This setting -cannot be changed.

-
icuLocale
-string -		 -

Maps to the ICU_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the ICU locale when the ICU -provider is used. This option requires localeProvider to be set to -icu. Available from PostgreSQL 15.

-
icuRules
-string -		 -

Maps to the ICU_RULES parameter of CREATE DATABASE. This setting -cannot be changed. Specifies additional collation rules to customize -the behavior of the default collation. This option requires -localeProvider to be set to icu. Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Maps to the BUILTIN_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the locale name when the -builtin provider is used. This option requires localeProvider to -be set to builtin. Available from PostgreSQL 17.

-
collationVersion
-string -		 -

Maps to the COLLATION_VERSION parameter of CREATE DATABASE. This -setting cannot be changed.

-
isTemplate
-bool -		 -

Maps to the IS_TEMPLATE parameter of CREATE DATABASE and ALTER DATABASE. If true, this database is considered a template and can -be cloned by any user with CREATEDB privileges.

-
allowConnections
-bool -		 -

Maps to the ALLOW_CONNECTIONS parameter of CREATE DATABASE and -ALTER DATABASE. If false then no one can connect to this database.

-
connectionLimit
-int -		 -

Maps to the CONNECTION LIMIT clause of CREATE DATABASE and -ALTER DATABASE. How many concurrent connections can be made to -this database. -1 (the default) means no limit.

-
tablespace
-string -		 -

Maps to the TABLESPACE parameter of CREATE DATABASE. -Maps to the SET TABLESPACE command of ALTER DATABASE. -The name of the tablespace (in PostgreSQL) that will be associated -with the new database. This tablespace will be the default -tablespace used for objects created in this database.

-
databaseReclaimPolicy
-DatabaseReclaimPolicy -		 -

The policy for end-of-life maintenance of this database.

-
- -
- -## DatabaseStatus - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseStatus defines the observed state of Database

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the database was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalClusterList - -(Alias of `[]github.com/EnterpriseDB/cloud-native-postgres/api/v1.ExternalCluster`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalClusterList is a list of external clusters

- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
pgDumpExtraOptions
-[]string -		 -

List of custom options to pass to the pg_dump command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design. -Only available in 1.25 or later

-
pgRestoreExtraOptions
-[]string -		 -

List of custom options to pass to the pg_restore command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design. -Only available in 1.25 or later

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster -Only available in 1.25 or later

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types -Only available in 1.25 or later

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances. -Only available in 1.25 or later

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
enabled
-bool -		 -

Enabled is true if this plugin will be used

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginConfigurationList - -(Alias of `[]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PluginConfiguration`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PluginConfigurationList represent a set of plugin with their -configuration parameters

- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
restoreJobHookCapabilities
-[]string -		 -

RestoreJobHookCapabilities are the list of capabilities of the -plugin regarding the RestoreJobHook management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created -Only available in 1.25 or later

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature -Only available in 1.25 or later

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-Probe -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-Probe -		 -

The readiness probe configuration

-
- -
- -## PublicationReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications.

- -
- -## PublicationSpec - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationSpec defines the desired state of Publication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "publisher"

-
name [Required]
-string -		 -

The name of the publication inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "publisher" cluster

-
parameters
-map[string]string -		 -

Publication parameters part of the WITH clause as expected by -PostgreSQL CREATE PUBLICATION command

-
target [Required]
-PublicationTarget -		 -

Target of the publication as expected by PostgreSQL CREATE PUBLICATION command

-
publicationReclaimPolicy
-PublicationReclaimPolicy -		 -

The policy for end-of-life maintenance of this publication

-
- -
- -## PublicationStatus - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationStatus defines the observed state of Publication

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the publication was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## PublicationTarget - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationTarget is what this publication should publish

- - - - - - - - - - - -
FieldDescription
allTables
-bool -		 -

Marks the publication as one that replicates changes for all tables -in the database, including tables created in the future. -Corresponding to FOR ALL TABLES in PostgreSQL.

-
objects
-[]PublicationTargetObject -		 -

Just the following schema objects

-
- -
- -## PublicationTargetObject - -**Appears in:** - -- [PublicationTarget](#postgresql-k8s-enterprisedb-io-v1-PublicationTarget) - -

PublicationTargetObject is an object to publish

- - - - - - - - - - - -
FieldDescription
tablesInSchema
-string -		 -

Marks the publication as one that replicates changes for all tables -in the specified list of schemas, including tables created in the -future. Corresponding to FOR TABLES IN SCHEMA in PostgreSQL.

-
table
-PublicationTargetTable -		 -

Specifies a list of tables to add to the publication. Corresponding -to FOR TABLE in PostgreSQL.

-
- -
- -## PublicationTargetTable - -**Appears in:** - -- [PublicationTargetObject](#postgresql-k8s-enterprisedb-io-v1-PublicationTargetObject) - -

PublicationTargetTable is a table to publish

- - - - - - - - - - - - - - - - - -
FieldDescription
only
-bool -		 -

Whether to limit to the table only or include all its descendants

-
name [Required]
-string -		 -

The table name

-
schema
-string -		 -

The schema name

-
columns
-[]string -		 -

The columns to publish

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary -Only available in 1.25 or later

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters -Only available in 1.25 or later

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met. -Only available in 1.25 or later

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used. -Only available in 1.25 or later

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots -Only available in 1.25 or later

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup -Only available in 1.25 or later

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SubscriptionReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [SubscriptionSpec](#postgresql-k8s-enterprisedb-io-v1-SubscriptionSpec) - -

SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions.

- -
- -## SubscriptionSpec - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionSpec defines the desired state of Subscription

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "subscriber"

-
name [Required]
-string -		 -

The name of the subscription inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "subscriber" cluster

-
parameters
-map[string]string -		 -

Subscription parameters part of the WITH clause as expected by -PostgreSQL CREATE SUBSCRIPTION command

-
publicationName [Required]
-string -		 -

The name of the publication inside the PostgreSQL database in the -"publisher"

-
publicationDBName
-string -		 -

The name of the database containing the publication on the external -cluster. Defaults to the one in the external cluster definition.

-
externalClusterName [Required]
-string -		 -

The name of the external cluster with the publication ("publisher")

-
subscriptionReclaimPolicy
-SubscriptionReclaimPolicy -		 -

The policy for end-of-life maintenance of this subscription

-
- -
- -## SubscriptionStatus - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionStatus defines the observed state of Subscription

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the subscription was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
dataDurability
-DataDurabilityLevel -		 -

If set to "required", data durability is strictly enforced. Write operations -with synchronous commit settings (on, remote_write, or remote_apply) will -block if there are insufficient healthy replicas, ensuring data persistence. -If set to "preferred", data durability is maintained when healthy replicas -are available, but the required number of instances will adjust dynamically -if replicas become unavailable. This setting relaxes strict durability enforcement -to allow for operational continuity. This setting is only applicable if both -standbyNamesPre and standbyNamesPost are unset (empty).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.0.mdx deleted file mode 100644 index beb5d2a0868..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.0.mdx +++ /dev/null @@ -1,5225 +0,0 @@ ---- -title: 'API Reference - v1.23.0' -navTitle: v1.23.0 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins [Required]
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus [Required]
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities [Required]
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities [Required]
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities [Required]
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities [Required]
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.1.mdx deleted file mode 100644 index c7a7b2a7b51..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.1.mdx +++ /dev/null @@ -1,5225 +0,0 @@ ---- -title: 'API Reference - v1.23.1' -navTitle: v1.23.1 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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

-
affinity
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins [Required]
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus [Required]
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities [Required]
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities [Required]
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities [Required]
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities [Required]
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]*github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.2.mdx deleted file mode 100644 index ed941527aa2..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.2.mdx +++ /dev/null @@ -1,5235 +0,0 @@ ---- -title: 'API Reference - v1.23.2' -navTitle: v1.23.2 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins [Required]
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus [Required]
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities [Required]
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities [Required]
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities [Required]
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities [Required]
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore -and volumeSnapshot. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.3.mdx deleted file mode 100644 index f8f61032e76..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.3.mdx +++ /dev/null @@ -1,5235 +0,0 @@ ---- -title: 'API Reference - v1.23.3' -navTitle: v1.23.3 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins [Required]
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus [Required]
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities [Required]
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities [Required]
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities [Required]
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities [Required]
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.4.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.4.mdx deleted file mode 100644 index 0ceb44bc77d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.4.mdx +++ /dev/null @@ -1,5235 +0,0 @@ ---- -title: 'API Reference - v1.23.4' -navTitle: v1.23.4 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins [Required]
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus [Required]
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities [Required]
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities [Required]
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities [Required]
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities [Required]
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [PostInitApplicationSQLRefs](#postgresql-k8s-enterprisedb-io-v1-PostInitApplicationSQLRefs) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.5.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.5.mdx deleted file mode 100644 index 3b5d5f62d86..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.5.mdx +++ /dev/null @@ -1,4670 +0,0 @@ ---- -title: 'API Reference - v1.23.5' -navTitle: v1.23.5 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins [Required]
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus [Required]
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities [Required]
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities [Required]
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities [Required]
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities [Required]
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.6.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.6.mdx deleted file mode 100644 index 06afe68f276..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.23.6.mdx +++ /dev/null @@ -1,4806 +0,0 @@ ---- -title: API Reference - v1.23.6 -navTitle: v1.23.6 -pdfExclude: true - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

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)

-
postInitApplicationSQL
-[]string -		 -

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)

-
postInitTemplateSQL
-[]string -		 -

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)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfigurationList - -(Alias of `[]github.com/EnterpriseDB/cloud-native-postgres/api/v1.PluginConfiguration`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PluginConfigurationList represent a set of plugin with their -configuration parameters

- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostInitApplicationSQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

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

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-Probe -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-Probe -		 -

The readiness probe configuration

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.0.mdx deleted file mode 100644 index 845cfe9b1ec..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.0.mdx +++ /dev/null @@ -1,5587 +0,0 @@ ---- -title: 'API Reference - v1.24.0' -navTitle: v1.24.0 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## AzureCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
connectionString
-SecretKeySelector -		 -

The connection string to be used

-
storageAccount
-SecretKeySelector -		 -

The storage account where to upload data

-
storageKey
-SecretKeySelector -		 -

The storage account key to be used in conjunction -with the storage account name

-
storageSasToken
-SecretKeySelector -		 -

A shared-access-signature to be used in conjunction with -the storage account name

-
inheritFromAzureAD
-bool -		 -

Use the Azure AD based authentication without providing explicitly the keys.

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BarmanCredentials - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

BarmanCredentials an object containing the potential credentials for each cloud provider

- - - - - - - - - - - - - - -
FieldDescription
googleCredentials
-GoogleCredentials -		 -

The credentials to use to upload data to Google Cloud Storage

-
s3Credentials
-S3Credentials -		 -

The credentials to use to upload data to S3

-
azureCredentials
-AzureCredentials -		 -

The credentials to use to upload data to Azure Blob Storage

-
- -
- -## BarmanObjectStoreConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

BarmanObjectStoreConfiguration contains the backup configuration -using Barman against an S3-compatible object storage

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointURL
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
endpointCA
-SecretKeySelector -		 -

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 [Required]
-string -		 -

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

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
wal
-WalBackupConfiguration -		 -

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
-DataBackupConfiguration -		 -

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
-map[string]string -		 -

Tags is a list of key value pairs that will be passed to the -Barman --tags option.

-
historyTags
-map[string]string -		 -

HistoryTags is a list of key value pairs that will be passed to the -Barman --history-tags option.

-
- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins [Required]
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken [Required]
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus [Required]
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## CompressionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

CompressionType encapsulates the available types of compression

- -
- -## ConfigMapKeySelector - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [SQLRefs](#postgresql-k8s-enterprisedb-io-v1-SQLRefs) - -

ConfigMapKeySelector contains enough information to let you locate -the key of a ConfigMap

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

DataBackupConfiguration is the configuration of the backup of -the data directory

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

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.

-
encryption
-EncryptionType -		 -

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

-
jobs
-int32 -		 -

The number of parallel jobs to be used to upload the backup, defaults -to 2

-
immediateCheckpoint
-bool -		 -

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 [Required]
-[]string -		 -

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.

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EncryptionType - -(Alias of `string`) - -**Appears in:** - -- [DataBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-DataBackupConfiguration) - -- [WalBackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-WalBackupConfiguration) - -

EncryptionType encapsulated the available types of encryption

- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## GoogleCredentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

GoogleCredentials is the type for the Google Cloud Storage credentials. -This needs to be specified even if we run inside a GKE environment.

- - - - - - - - - - - -
FieldDescription
applicationCredentials
-SecretKeySelector -		 -

The secret containing the Google Cloud Storage JSON file with the credentials

-
gkeEnvironment
-bool -		 -

If set to true, will presume that it's running inside a GKE environment, -default to false.

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LocalObjectReference - -**Appears in:** - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -- [BootstrapPgBaseBackup](#postgresql-k8s-enterprisedb-io-v1-BootstrapPgBaseBackup) - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ConfigMapKeySelector](#postgresql-k8s-enterprisedb-io-v1-ConfigMapKeySelector) - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [SecretKeySelector](#postgresql-k8s-enterprisedb-io-v1-SecretKeySelector) - -

LocalObjectReference contains enough information to let you locate a -local object with a known type inside the same namespace

- - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the referent.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy [Required]
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional [Required]
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities [Required]
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities [Required]
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities [Required]
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities [Required]
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
status [Required]
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self [Required]
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary [Required]
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
promotionToken [Required]
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay [Required]
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## S3Credentials - -**Appears in:** - -- [BarmanCredentials](#postgresql-k8s-enterprisedb-io-v1-BarmanCredentials) - -

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

    -
    • -
- - - - - - - - - - - - - - - - - - - - -
FieldDescription
accessKeyId
-SecretKeySelector -		 -

The reference to the access key id

-
secretAccessKey
-SecretKeySelector -		 -

The reference to the secret access key

-
region
-SecretKeySelector -		 -

The reference to the secret containing the region name

-
sessionToken
-SecretKeySelector -		 -

The references to the session key

-
inheritFromIAMRole
-bool -		 -

Use the role based authentication without providing explicitly the keys.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretKeySelector - -**Appears in:** - -- [AzureCredentials](#postgresql-k8s-enterprisedb-io-v1-AzureCredentials) - -- [BackupSource](#postgresql-k8s-enterprisedb-io-v1-BackupSource) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -- [GoogleCredentials](#postgresql-k8s-enterprisedb-io-v1-GoogleCredentials) - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -- [S3Credentials](#postgresql-k8s-enterprisedb-io-v1-S3Credentials) - -- [SQLRefs](#postgresql-k8s-enterprisedb-io-v1-SQLRefs) - -

SecretKeySelector contains enough information to let you locate -the key of a Secret

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) -

The name of the secret in the pod's namespace to select from.

-
key [Required]
-string -		 -

The key to select

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
- -
- -## WalBackupConfiguration - -**Appears in:** - -- [BarmanObjectStoreConfiguration](#postgresql-k8s-enterprisedb-io-v1-BarmanObjectStoreConfiguration) - -

WalBackupConfiguration is the configuration of the backup of the -WAL stream

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
compression
-CompressionType -		 -

Compress a WAL file before sending it to the object store. Available -options are empty string (no compression, default), gzip, bzip2 or snappy.

-
encryption
-EncryptionType -		 -

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

-
maxParallel
-int -		 -

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.

-
archiveAdditionalCommandArgs [Required]
-[]string -		 -

Additional arguments that can be appended to the 'barman-cloud-wal-archive' -command-line invocation. These arguments provide flexibility to customize -the WAL archive 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-wal-archive' command, to avoid potential errors or unintended -behavior during execution.

-
restoreAdditionalCommandArgs [Required]
-[]string -		 -

Additional arguments that can be appended to the 'barman-cloud-wal-restore' -command-line invocation. These arguments provide flexibility to customize -the WAL restore 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-wal-restore' command, to avoid potential errors or unintended -behavior during execution.

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.1.mdx deleted file mode 100644 index 0f5294b3cd5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.1.mdx +++ /dev/null @@ -1,4990 +0,0 @@ ---- -title: 'API Reference - v1.24.1' -navTitle: v1.24.1 -pdfExclude: true ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName [Required]
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online [Required]
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit [Required]
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins [Required]
-PluginConfigurationList -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken [Required]
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus [Required]
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData [Required]
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy [Required]
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional [Required]
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities [Required]
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities [Required]
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities [Required]
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities [Required]
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
status [Required]
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self [Required]
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary [Required]
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled [Required]
-bool -		 -

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.

-
promotionToken [Required]
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay [Required]
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.2.mdx deleted file mode 100644 index e5f21cfaefb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.2.mdx +++ /dev/null @@ -1,5142 +0,0 @@ ---- -title: API Reference - v1.24.2 -navTitle: v1.24.2 -pdfExclude: true - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-[]PluginConfiguration -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-Probe -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-Probe -		 -

The readiness probe configuration

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.3.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.3.mdx deleted file mode 100644 index de07fddd18a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.24.3.mdx +++ /dev/null @@ -1,5150 +0,0 @@ ---- -title: API Reference - v1.24.3 -navTitle: v1.24.3 -pdfExclude: true - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-[]PluginConfiguration -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
isWALArchiver
-bool -		 -

Only one plugin can be declared as WALArchiver. -Cannot be active if ".spec.backup.barmanObjectStore" configuration is present.

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-Probe -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-Probe -		 -

The readiness probe configuration

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.25.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.25.0.mdx deleted file mode 100644 index c5fd4d93a8d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.25.0.mdx +++ /dev/null @@ -1,5944 +0,0 @@ ---- -title: API Reference - v1.25.0 -navTitle: v1.25.0 -pdfExclude: true - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Database - -

Database is the Schema for the databases API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Database
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-DatabaseSpec -		 -

Specification of the desired Database. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
status
-DatabaseStatus -		 -

Most recently observed status of the Database. 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

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## Publication - -

Publication is the Schema for the publications API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Publication
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PublicationSpec -		 - No description provided.
status [Required]
-PublicationStatus -		 - No description provided.
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## Subscription - -

Subscription is the Schema for the subscriptions API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Subscription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-SubscriptionSpec -		 - No description provided.
status [Required]
-SubscriptionStatus -		 - No description provided.
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
pluginMetadata
-map[string]string -		 -

A map containing the plugin metadata

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
locale
-string -		 -

Sets the default collation order and character classification in the new database.

-
localeProvider
-string -		 -

This option sets the locale provider for databases created in the new cluster. -Available from PostgreSQL 16.

-
icuLocale
-string -		 -

Specifies the ICU locale when the ICU provider is used. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 15.

-
icuRules
-string -		 -

Specifies additional collation rules to customize the behavior of the default collation. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Specifies the locale name when the builtin provider is used. -This option requires localeProvider to be set to builtin. -Available from PostgreSQL 17.

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-[]PluginConfiguration -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataDurabilityLevel - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are required or preferred.

- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases.

- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## DatabaseSpec - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseSpec is the specification of a Postgresql Database, built around the -CREATE DATABASE, ALTER DATABASE, and DROP DATABASE SQL commands of -PostgreSQL.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster hosting the database.

-
ensure
-EnsureOption -		 -

Ensure the PostgreSQL database is present or absent - defaults to "present".

-
name [Required]
-string -		 -

The name of the database to create inside PostgreSQL. This setting cannot be changed.

-
owner [Required]
-string -		 -

Maps to the OWNER parameter of CREATE DATABASE. -Maps to the OWNER TO command of ALTER DATABASE. -The role name of the user who owns the database inside PostgreSQL.

-
template
-string -		 -

Maps to the TEMPLATE parameter of CREATE DATABASE. This setting -cannot be changed. The name of the template from which to create -this database.

-
encoding
-string -		 -

Maps to the ENCODING parameter of CREATE DATABASE. This setting -cannot be changed. Character set encoding to use in the database.

-
locale
-string -		 -

Maps to the LOCALE parameter of CREATE DATABASE. This setting -cannot be changed. Sets the default collation order and character -classification in the new database.

-
localeProvider
-string -		 -

Maps to the LOCALE_PROVIDER parameter of CREATE DATABASE. This -setting cannot be changed. This option sets the locale provider for -databases created in the new cluster. Available from PostgreSQL 16.

-
localeCollate
-string -		 -

Maps to the LC_COLLATE parameter of CREATE DATABASE. This -setting cannot be changed.

-
localeCType
-string -		 -

Maps to the LC_CTYPE parameter of CREATE DATABASE. This setting -cannot be changed.

-
icuLocale
-string -		 -

Maps to the ICU_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the ICU locale when the ICU -provider is used. This option requires localeProvider to be set to -icu. Available from PostgreSQL 15.

-
icuRules
-string -		 -

Maps to the ICU_RULES parameter of CREATE DATABASE. This setting -cannot be changed. Specifies additional collation rules to customize -the behavior of the default collation. This option requires -localeProvider to be set to icu. Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Maps to the BUILTIN_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the locale name when the -builtin provider is used. This option requires localeProvider to -be set to builtin. Available from PostgreSQL 17.

-
collationVersion
-string -		 -

Maps to the COLLATION_VERSION parameter of CREATE DATABASE. This -setting cannot be changed.

-
isTemplate
-bool -		 -

Maps to the IS_TEMPLATE parameter of CREATE DATABASE and ALTER DATABASE. If true, this database is considered a template and can -be cloned by any user with CREATEDB privileges.

-
allowConnections
-bool -		 -

Maps to the ALLOW_CONNECTIONS parameter of CREATE DATABASE and -ALTER DATABASE. If false then no one can connect to this database.

-
connectionLimit
-int -		 -

Maps to the CONNECTION LIMIT clause of CREATE DATABASE and -ALTER DATABASE. How many concurrent connections can be made to -this database. -1 (the default) means no limit.

-
tablespace
-string -		 -

Maps to the TABLESPACE parameter of CREATE DATABASE. -Maps to the SET TABLESPACE command of ALTER DATABASE. -The name of the tablespace (in PostgreSQL) that will be associated -with the new database. This tablespace will be the default -tablespace used for objects created in this database.

-
databaseReclaimPolicy
-DatabaseReclaimPolicy -		 -

The policy for end-of-life maintenance of this database.

-
- -
- -## DatabaseStatus - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseStatus defines the observed state of Database

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the database was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
plugin [Required]
-PluginConfiguration -		 -

The configuration of the plugin that is taking care -of WAL archiving and backups for this external cluster

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
pgDumpExtraOptions
-[]string -		 -

List of custom options to pass to the pg_dump command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
pgRestoreExtraOptions
-[]string -		 -

List of custom options to pass to the pg_restore command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
enabled
-bool -		 -

Enabled is true if this plugin will be used

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
restoreJobHookCapabilities
-[]string -		 -

RestoreJobHookCapabilities are the list of capabilities of the -plugin regarding the RestoreJobHook management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-Probe -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-Probe -		 -

The readiness probe configuration

-
- -
- -## PublicationReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications.

- -
- -## PublicationSpec - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationSpec defines the desired state of Publication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "publisher"

-
name [Required]
-string -		 -

The name of the publication inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "publisher" cluster

-
parameters
-map[string]string -		 -

Publication parameters part of the WITH clause as expected by -PostgreSQL CREATE PUBLICATION command

-
target [Required]
-PublicationTarget -		 -

Target of the publication as expected by PostgreSQL CREATE PUBLICATION command

-
publicationReclaimPolicy
-PublicationReclaimPolicy -		 -

The policy for end-of-life maintenance of this publication

-
- -
- -## PublicationStatus - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationStatus defines the observed state of Publication

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the publication was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## PublicationTarget - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationTarget is what this publication should publish

- - - - - - - - - - - -
FieldDescription
allTables
-bool -		 -

Marks the publication as one that replicates changes for all tables -in the database, including tables created in the future. -Corresponding to FOR ALL TABLES in PostgreSQL.

-
objects
-[]PublicationTargetObject -		 -

Just the following schema objects

-
- -
- -## PublicationTargetObject - -**Appears in:** - -- [PublicationTarget](#postgresql-k8s-enterprisedb-io-v1-PublicationTarget) - -

PublicationTargetObject is an object to publish

- - - - - - - - - - - -
FieldDescription
tablesInSchema
-string -		 -

Marks the publication as one that replicates changes for all tables -in the specified list of schemas, including tables created in the -future. Corresponding to FOR TABLES IN SCHEMA in PostgreSQL.

-
table
-PublicationTargetTable -		 -

Specifies a list of tables to add to the publication. Corresponding -to FOR TABLE in PostgreSQL.

-
- -
- -## PublicationTargetTable - -**Appears in:** - -- [PublicationTargetObject](#postgresql-k8s-enterprisedb-io-v1-PublicationTargetObject) - -

PublicationTargetTable is a table to publish

- - - - - - - - - - - - - - - - - -
FieldDescription
only
-bool -		 -

Whether to limit to the table only or include all its descendants

-
name [Required]
-string -		 -

The table name

-
schema
-string -		 -

The schema name

-
columns
-[]string -		 -

The columns to publish

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SubscriptionReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [SubscriptionSpec](#postgresql-k8s-enterprisedb-io-v1-SubscriptionSpec) - -

SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions.

- -
- -## SubscriptionSpec - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionSpec defines the desired state of Subscription

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "subscriber"

-
name [Required]
-string -		 -

The name of the subscription inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "subscriber" cluster

-
parameters
-map[string]string -		 -

Subscription parameters part of the WITH clause as expected by -PostgreSQL CREATE SUBSCRIPTION command

-
publicationName [Required]
-string -		 -

The name of the publication inside the PostgreSQL database in the -"publisher"

-
publicationDBName
-string -		 -

The name of the database containing the publication on the external -cluster. Defaults to the one in the external cluster definition.

-
externalClusterName [Required]
-string -		 -

The name of the external cluster with the publication ("publisher")

-
subscriptionReclaimPolicy
-SubscriptionReclaimPolicy -		 -

The policy for end-of-life maintenance of this subscription

-
- -
- -## SubscriptionStatus - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionStatus defines the observed state of Subscription

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the subscription was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
dataDurability
-DataDurabilityLevel -		 -

If set to "required", data durability is strictly enforced. Write operations -with synchronous commit settings (on, remote_write, or remote_apply) will -block if there are insufficient healthy replicas, ensuring data persistence. -If set to "preferred", data durability is maintained when healthy replicas -are available, but the required number of instances will adjust dynamically -if replicas become unavailable. This setting relaxes strict durability enforcement -to allow for operational continuity. This setting is only applicable if both -standbyNamesPre and standbyNamesPost are unset (empty).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.25.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.25.1.mdx deleted file mode 100644 index 9e363611dfd..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.25.1.mdx +++ /dev/null @@ -1,5952 +0,0 @@ ---- -title: API Reference - v1.25.1 -navTitle: v1.25.1 -pdfExclude: true - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -
- -## Backup - -

Backup is the Schema for the backups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Database - -

Database is the Schema for the databases API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Database
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-DatabaseSpec -		 -

Specification of the desired Database. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
status
-DatabaseStatus -		 -

Most recently observed status of the Database. 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

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## Publication - -

Publication is the Schema for the publications API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Publication
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PublicationSpec -		 - No description provided.
status [Required]
-PublicationStatus -		 - No description provided.
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## Subscription - -

Subscription is the Schema for the subscriptions API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Subscription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-SubscriptionSpec -		 - No description provided.
status [Required]
-SubscriptionStatus -		 - No description provided.
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
pluginMetadata
-map[string]string -		 -

A map containing the plugin metadata

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
locale
-string -		 -

Sets the default collation order and character classification in the new database.

-
localeProvider
-string -		 -

This option sets the locale provider for databases created in the new cluster. -Available from PostgreSQL 16.

-
icuLocale
-string -		 -

Specifies the ICU locale when the ICU provider is used. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 15.

-
icuRules
-string -		 -

Specifies additional collation rules to customize the behavior of the default collation. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Specifies the locale name when the builtin provider is used. -This option requires localeProvider to be set to builtin. -Available from PostgreSQL 17.

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-[]PluginConfiguration -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
azurePVCUpdateEnabled
-bool -		 -

AzurePVCUpdateEnabled shows if the PVC online upgrade is enabled for this cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataDurabilityLevel - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are required or preferred.

- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases.

- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## DatabaseSpec - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseSpec is the specification of a Postgresql Database, built around the -CREATE DATABASE, ALTER DATABASE, and DROP DATABASE SQL commands of -PostgreSQL.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster hosting the database.

-
ensure
-EnsureOption -		 -

Ensure the PostgreSQL database is present or absent - defaults to "present".

-
name [Required]
-string -		 -

The name of the database to create inside PostgreSQL. This setting cannot be changed.

-
owner [Required]
-string -		 -

Maps to the OWNER parameter of CREATE DATABASE. -Maps to the OWNER TO command of ALTER DATABASE. -The role name of the user who owns the database inside PostgreSQL.

-
template
-string -		 -

Maps to the TEMPLATE parameter of CREATE DATABASE. This setting -cannot be changed. The name of the template from which to create -this database.

-
encoding
-string -		 -

Maps to the ENCODING parameter of CREATE DATABASE. This setting -cannot be changed. Character set encoding to use in the database.

-
locale
-string -		 -

Maps to the LOCALE parameter of CREATE DATABASE. This setting -cannot be changed. Sets the default collation order and character -classification in the new database.

-
localeProvider
-string -		 -

Maps to the LOCALE_PROVIDER parameter of CREATE DATABASE. This -setting cannot be changed. This option sets the locale provider for -databases created in the new cluster. Available from PostgreSQL 16.

-
localeCollate
-string -		 -

Maps to the LC_COLLATE parameter of CREATE DATABASE. This -setting cannot be changed.

-
localeCType
-string -		 -

Maps to the LC_CTYPE parameter of CREATE DATABASE. This setting -cannot be changed.

-
icuLocale
-string -		 -

Maps to the ICU_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the ICU locale when the ICU -provider is used. This option requires localeProvider to be set to -icu. Available from PostgreSQL 15.

-
icuRules
-string -		 -

Maps to the ICU_RULES parameter of CREATE DATABASE. This setting -cannot be changed. Specifies additional collation rules to customize -the behavior of the default collation. This option requires -localeProvider to be set to icu. Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Maps to the BUILTIN_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the locale name when the -builtin provider is used. This option requires localeProvider to -be set to builtin. Available from PostgreSQL 17.

-
collationVersion
-string -		 -

Maps to the COLLATION_VERSION parameter of CREATE DATABASE. This -setting cannot be changed.

-
isTemplate
-bool -		 -

Maps to the IS_TEMPLATE parameter of CREATE DATABASE and ALTER DATABASE. If true, this database is considered a template and can -be cloned by any user with CREATEDB privileges.

-
allowConnections
-bool -		 -

Maps to the ALLOW_CONNECTIONS parameter of CREATE DATABASE and -ALTER DATABASE. If false then no one can connect to this database.

-
connectionLimit
-int -		 -

Maps to the CONNECTION LIMIT clause of CREATE DATABASE and -ALTER DATABASE. How many concurrent connections can be made to -this database. -1 (the default) means no limit.

-
tablespace
-string -		 -

Maps to the TABLESPACE parameter of CREATE DATABASE. -Maps to the SET TABLESPACE command of ALTER DATABASE. -The name of the tablespace (in PostgreSQL) that will be associated -with the new database. This tablespace will be the default -tablespace used for objects created in this database.

-
databaseReclaimPolicy
-DatabaseReclaimPolicy -		 -

The policy for end-of-life maintenance of this database.

-
- -
- -## DatabaseStatus - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseStatus defines the observed state of Database

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the database was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
plugin [Required]
-PluginConfiguration -		 -

The configuration of the plugin that is taking care -of WAL archiving and backups for this external cluster

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
pgDumpExtraOptions
-[]string -		 -

List of custom options to pass to the pg_dump command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
pgRestoreExtraOptions
-[]string -		 -

List of custom options to pass to the pg_restore command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
enabled
-bool -		 -

Enabled is true if this plugin will be used

-
isWALArchiver
-bool -		 -

Only one plugin can be declared as WALArchiver. -Cannot be active if ".spec.backup.barmanObjectStore" configuration is present.

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
restoreJobHookCapabilities
-[]string -		 -

RestoreJobHookCapabilities are the list of capabilities of the -plugin regarding the RestoreJobHook management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-Probe -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-Probe -		 -

The readiness probe configuration

-
- -
- -## PublicationReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications.

- -
- -## PublicationSpec - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationSpec defines the desired state of Publication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "publisher"

-
name [Required]
-string -		 -

The name of the publication inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "publisher" cluster

-
parameters
-map[string]string -		 -

Publication parameters part of the WITH clause as expected by -PostgreSQL CREATE PUBLICATION command

-
target [Required]
-PublicationTarget -		 -

Target of the publication as expected by PostgreSQL CREATE PUBLICATION command

-
publicationReclaimPolicy
-PublicationReclaimPolicy -		 -

The policy for end-of-life maintenance of this publication

-
- -
- -## PublicationStatus - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationStatus defines the observed state of Publication

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the publication was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## PublicationTarget - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationTarget is what this publication should publish

- - - - - - - - - - - -
FieldDescription
allTables
-bool -		 -

Marks the publication as one that replicates changes for all tables -in the database, including tables created in the future. -Corresponding to FOR ALL TABLES in PostgreSQL.

-
objects
-[]PublicationTargetObject -		 -

Just the following schema objects

-
- -
- -## PublicationTargetObject - -**Appears in:** - -- [PublicationTarget](#postgresql-k8s-enterprisedb-io-v1-PublicationTarget) - -

PublicationTargetObject is an object to publish

- - - - - - - - - - - -
FieldDescription
tablesInSchema
-string -		 -

Marks the publication as one that replicates changes for all tables -in the specified list of schemas, including tables created in the -future. Corresponding to FOR TABLES IN SCHEMA in PostgreSQL.

-
table
-PublicationTargetTable -		 -

Specifies a list of tables to add to the publication. Corresponding -to FOR TABLE in PostgreSQL.

-
- -
- -## PublicationTargetTable - -**Appears in:** - -- [PublicationTargetObject](#postgresql-k8s-enterprisedb-io-v1-PublicationTargetObject) - -

PublicationTargetTable is a table to publish

- - - - - - - - - - - - - - - - - -
FieldDescription
only
-bool -		 -

Whether to limit to the table only or include all its descendants

-
name [Required]
-string -		 -

The table name

-
schema
-string -		 -

The schema name

-
columns
-[]string -		 -

The columns to publish

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SubscriptionReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [SubscriptionSpec](#postgresql-k8s-enterprisedb-io-v1-SubscriptionSpec) - -

SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions.

- -
- -## SubscriptionSpec - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionSpec defines the desired state of Subscription

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "subscriber"

-
name [Required]
-string -		 -

The name of the subscription inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "subscriber" cluster

-
parameters
-map[string]string -		 -

Subscription parameters part of the WITH clause as expected by -PostgreSQL CREATE SUBSCRIPTION command

-
publicationName [Required]
-string -		 -

The name of the publication inside the PostgreSQL database in the -"publisher"

-
publicationDBName
-string -		 -

The name of the database containing the publication on the external -cluster. Defaults to the one in the external cluster definition.

-
externalClusterName [Required]
-string -		 -

The name of the external cluster with the publication ("publisher")

-
subscriptionReclaimPolicy
-SubscriptionReclaimPolicy -		 -

The policy for end-of-life maintenance of this subscription

-
- -
- -## SubscriptionStatus - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionStatus defines the observed state of Subscription

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the subscription was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
dataDurability
-DataDurabilityLevel -		 -

If set to "required", data durability is strictly enforced. Write operations -with synchronous commit settings (on, remote_write, or remote_apply) will -block if there are insufficient healthy replicas, ensuring data persistence. -If set to "preferred", data durability is maintained when healthy replicas -are available, but the required number of instances will adjust dynamically -if replicas become unavailable. This setting relaxes strict durability enforcement -to allow for operational continuity. This setting is only applicable if both -standbyNamesPre and standbyNamesPost are unset (empty).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.26.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.26.0.mdx deleted file mode 100644 index 2da27a30088..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.26.0.mdx +++ /dev/null @@ -1,6220 +0,0 @@ ---- -title: API Reference - v1.26.0 -navTitle: v1.26.0 -pdfExclude: 'true' - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -
- -## Backup - -

A Backup resource is a request for a PostgreSQL backup by the user.

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Database - -

Database is the Schema for the databases API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Database
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-DatabaseSpec -		 -

Specification of the desired Database. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
status
-DatabaseStatus -		 -

Most recently observed status of the Database. 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

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## Publication - -

Publication is the Schema for the publications API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Publication
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PublicationSpec -		 - No description provided.
status [Required]
-PublicationStatus -		 - No description provided.
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## Subscription - -

Subscription is the Schema for the subscriptions API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Subscription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-SubscriptionSpec -		 - No description provided.
status [Required]
-SubscriptionStatus -		 - No description provided.
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
pluginMetadata
-map[string]string -		 -

A map containing the plugin metadata

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
locale
-string -		 -

Sets the default collation order and character classification in the new database.

-
localeProvider
-string -		 -

This option sets the locale provider for databases created in the new cluster. -Available from PostgreSQL 16.

-
icuLocale
-string -		 -

Specifies the ICU locale when the ICU provider is used. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 15.

-
icuRules
-string -		 -

Specifies additional collation rules to customize the behavior of the default collation. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Specifies the locale name when the builtin provider is used. -This option requires localeProvider to be set to builtin. -Available from PostgreSQL 17.

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-[]PluginConfiguration -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format -This field is calculated from the content of LastSuccessfulBackupByMethod

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type

-
lastFailedBackup
-string -		 -

Stored as a date in RFC3339 format

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pgDataImageInfo
-ImageInfo -		 -

PGDataImageInfo contains the details of the latest image that has run on the current data directory.

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataDurabilityLevel - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are required or preferred.

- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseObjectSpec - -**Appears in:** - -- [ExtensionSpec](#postgresql-k8s-enterprisedb-io-v1-ExtensionSpec) - -- [SchemaSpec](#postgresql-k8s-enterprisedb-io-v1-SchemaSpec) - -

DatabaseObjectSpec contains the fields which are common to every -database object

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the extension/schema

-
ensure
-EnsureOption -		 -

Specifies whether an extension/schema should be present or absent in -the database. If set to present, the extension/schema will be -created if it does not exist. If set to absent, the -extension/schema will be removed if it exists.

-
- -
- -## DatabaseObjectStatus - -**Appears in:** - -- [DatabaseStatus](#postgresql-k8s-enterprisedb-io-v1-DatabaseStatus) - -

DatabaseObjectStatus is the status of the managed database objects

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the object

-
applied [Required]
-bool -		 -

True of the object has been installed successfully in -the database

-
message
-string -		 -

Message is the object reconciliation message

-
- -
- -## DatabaseReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases.

- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## DatabaseSpec - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseSpec is the specification of a Postgresql Database, built around the -CREATE DATABASE, ALTER DATABASE, and DROP DATABASE SQL commands of -PostgreSQL.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster hosting the database.

-
ensure
-EnsureOption -		 -

Ensure the PostgreSQL database is present or absent - defaults to "present".

-
name [Required]
-string -		 -

The name of the database to create inside PostgreSQL. This setting cannot be changed.

-
owner [Required]
-string -		 -

Maps to the OWNER parameter of CREATE DATABASE. -Maps to the OWNER TO command of ALTER DATABASE. -The role name of the user who owns the database inside PostgreSQL.

-
template
-string -		 -

Maps to the TEMPLATE parameter of CREATE DATABASE. This setting -cannot be changed. The name of the template from which to create -this database.

-
encoding
-string -		 -

Maps to the ENCODING parameter of CREATE DATABASE. This setting -cannot be changed. Character set encoding to use in the database.

-
locale
-string -		 -

Maps to the LOCALE parameter of CREATE DATABASE. This setting -cannot be changed. Sets the default collation order and character -classification in the new database.

-
localeProvider
-string -		 -

Maps to the LOCALE_PROVIDER parameter of CREATE DATABASE. This -setting cannot be changed. This option sets the locale provider for -databases created in the new cluster. Available from PostgreSQL 16.

-
localeCollate
-string -		 -

Maps to the LC_COLLATE parameter of CREATE DATABASE. This -setting cannot be changed.

-
localeCType
-string -		 -

Maps to the LC_CTYPE parameter of CREATE DATABASE. This setting -cannot be changed.

-
icuLocale
-string -		 -

Maps to the ICU_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the ICU locale when the ICU -provider is used. This option requires localeProvider to be set to -icu. Available from PostgreSQL 15.

-
icuRules
-string -		 -

Maps to the ICU_RULES parameter of CREATE DATABASE. This setting -cannot be changed. Specifies additional collation rules to customize -the behavior of the default collation. This option requires -localeProvider to be set to icu. Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Maps to the BUILTIN_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the locale name when the -builtin provider is used. This option requires localeProvider to -be set to builtin. Available from PostgreSQL 17.

-
collationVersion
-string -		 -

Maps to the COLLATION_VERSION parameter of CREATE DATABASE. This -setting cannot be changed.

-
isTemplate
-bool -		 -

Maps to the IS_TEMPLATE parameter of CREATE DATABASE and ALTER DATABASE. If true, this database is considered a template and can -be cloned by any user with CREATEDB privileges.

-
allowConnections
-bool -		 -

Maps to the ALLOW_CONNECTIONS parameter of CREATE DATABASE and -ALTER DATABASE. If false then no one can connect to this database.

-
connectionLimit
-int -		 -

Maps to the CONNECTION LIMIT clause of CREATE DATABASE and -ALTER DATABASE. How many concurrent connections can be made to -this database. -1 (the default) means no limit.

-
tablespace
-string -		 -

Maps to the TABLESPACE parameter of CREATE DATABASE. -Maps to the SET TABLESPACE command of ALTER DATABASE. -The name of the tablespace (in PostgreSQL) that will be associated -with the new database. This tablespace will be the default -tablespace used for objects created in this database.

-
databaseReclaimPolicy
-DatabaseReclaimPolicy -		 -

The policy for end-of-life maintenance of this database.

-
schemas
-[]SchemaSpec -		 -

The list of schemas to be managed in the database

-
extensions
-[]ExtensionSpec -		 -

The list of extensions to be managed in the database

-
- -
- -## DatabaseStatus - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseStatus defines the observed state of Database

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the database was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
schemas
-[]DatabaseObjectStatus -		 -

Schemas is the status of the managed schemas

-
extensions
-[]DatabaseObjectStatus -		 -

Extensions is the status of the managed extensions

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [DatabaseObjectSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseObjectSpec) - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExtensionSpec - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

ExtensionSpec configures an extension in a database

- - - - - - - - - - - - - - -
FieldDescription
DatabaseObjectSpec
-DatabaseObjectSpec -		(Members of DatabaseObjectSpec are embedded into this type.) -

Common fields

-
version [Required]
-string -		 -

The version of the extension to install. If empty, the operator will -install the default version (whatever is specified in the -extension's control file)

-
schema [Required]
-string -		 -

The name of the schema in which to install the extension's objects, -in case the extension allows its contents to be relocated. If not -specified (default), and the extension's control file does not -specify a schema either, the current default object creation schema -is used.

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
plugin [Required]
-PluginConfiguration -		 -

The configuration of the plugin that is taking care -of WAL archiving and backups for this external cluster

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## ImageInfo - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ImageInfo contains the information about a PostgreSQL image

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

Image is the image name

-
majorVersion [Required]
-int -		 -

MajorVersion is the major version of the image

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
pgDumpExtraOptions
-[]string -		 -

List of custom options to pass to the pg_dump command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
pgRestoreExtraOptions
-[]string -		 -

List of custom options to pass to the pg_restore command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
ip [Required]
-string -		 -

IP address of the instance

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
enabled
-bool -		 -

Enabled is true if this plugin will be used

-
isWALArchiver
-bool -		 -

Only one plugin can be declared as WALArchiver. -Cannot be active if ".spec.backup.barmanObjectStore" configuration is present.

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
restoreJobHookCapabilities
-[]string -		 -

RestoreJobHookCapabilities are the list of capabilities of the -plugin regarding the RestoreJobHook management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbeWithStrategy](#postgresql-k8s-enterprisedb-io-v1-ProbeWithStrategy) - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbeStrategyType - -(Alias of `string`) - -**Appears in:** - -- [ProbeWithStrategy](#postgresql-k8s-enterprisedb-io-v1-ProbeWithStrategy) - -

ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready

- -
- -## ProbeWithStrategy - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

ProbeWithStrategy is the configuration of the startup probe

- - - - - - - - - - - - - - -
FieldDescription
Probe
-Probe -		(Members of Probe are embedded into this type.) -

Probe is the standard probe configuration

-
type
-ProbeStrategyType -		 -

The probe strategy

-
maximumLag
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Lag limit. Used only for streaming strategy

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-ProbeWithStrategy -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-ProbeWithStrategy -		 -

The readiness probe configuration

-
- -
- -## PublicationReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications.

- -
- -## PublicationSpec - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationSpec defines the desired state of Publication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "publisher"

-
name [Required]
-string -		 -

The name of the publication inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "publisher" cluster

-
parameters
-map[string]string -		 -

Publication parameters part of the WITH clause as expected by -PostgreSQL CREATE PUBLICATION command

-
target [Required]
-PublicationTarget -		 -

Target of the publication as expected by PostgreSQL CREATE PUBLICATION command

-
publicationReclaimPolicy
-PublicationReclaimPolicy -		 -

The policy for end-of-life maintenance of this publication

-
- -
- -## PublicationStatus - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationStatus defines the observed state of Publication

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the publication was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## PublicationTarget - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationTarget is what this publication should publish

- - - - - - - - - - - -
FieldDescription
allTables
-bool -		 -

Marks the publication as one that replicates changes for all tables -in the database, including tables created in the future. -Corresponding to FOR ALL TABLES in PostgreSQL.

-
objects
-[]PublicationTargetObject -		 -

Just the following schema objects

-
- -
- -## PublicationTargetObject - -**Appears in:** - -- [PublicationTarget](#postgresql-k8s-enterprisedb-io-v1-PublicationTarget) - -

PublicationTargetObject is an object to publish

- - - - - - - - - - - -
FieldDescription
tablesInSchema
-string -		 -

Marks the publication as one that replicates changes for all tables -in the specified list of schemas, including tables created in the -future. Corresponding to FOR TABLES IN SCHEMA in PostgreSQL.

-
table
-PublicationTargetTable -		 -

Specifies a list of tables to add to the publication. Corresponding -to FOR TABLE in PostgreSQL.

-
- -
- -## PublicationTargetTable - -**Appears in:** - -- [PublicationTargetObject](#postgresql-k8s-enterprisedb-io-v1-PublicationTargetObject) - -

PublicationTargetTable is a table to publish

- - - - - - - - - - - - - - - - - -
FieldDescription
only
-bool -		 -

Whether to limit to the table only or include all its descendants

-
name [Required]
-string -		 -

The table name

-
schema
-string -		 -

The schema name

-
columns
-[]string -		 -

The columns to publish

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SchemaSpec - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

SchemaSpec configures a schema in a database

- - - - - - - - - - - -
FieldDescription
DatabaseObjectSpec
-DatabaseObjectSpec -		(Members of DatabaseObjectSpec are embedded into this type.) -

Common fields

-
owner [Required]
-string -		 -

The role name of the user who owns the schema inside PostgreSQL. -It maps to the AUTHORIZATION parameter of CREATE SCHEMA and the -OWNER TO command of ALTER SCHEMA.

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SubscriptionReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [SubscriptionSpec](#postgresql-k8s-enterprisedb-io-v1-SubscriptionSpec) - -

SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions.

- -
- -## SubscriptionSpec - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionSpec defines the desired state of Subscription

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "subscriber"

-
name [Required]
-string -		 -

The name of the subscription inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "subscriber" cluster

-
parameters
-map[string]string -		 -

Subscription parameters part of the WITH clause as expected by -PostgreSQL CREATE SUBSCRIPTION command

-
publicationName [Required]
-string -		 -

The name of the publication inside the PostgreSQL database in the -"publisher"

-
publicationDBName
-string -		 -

The name of the database containing the publication on the external -cluster. Defaults to the one in the external cluster definition.

-
externalClusterName [Required]
-string -		 -

The name of the external cluster with the publication ("publisher")

-
subscriptionReclaimPolicy
-SubscriptionReclaimPolicy -		 -

The policy for end-of-life maintenance of this subscription

-
- -
- -## SubscriptionStatus - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionStatus defines the observed state of Subscription

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the subscription was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
dataDurability
-DataDurabilityLevel -		 -

If set to "required", data durability is strictly enforced. Write operations -with synchronous commit settings (on, remote_write, or remote_apply) will -block if there are insufficient healthy replicas, ensuring data persistence. -If set to "preferred", data durability is maintained when healthy replicas -are available, but the required number of instances will adjust dynamically -if replicas become unavailable. This setting relaxes strict durability enforcement -to allow for operational continuity. This setting is only applicable if both -standbyNamesPre and standbyNamesPost are unset (empty).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.26.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.26.1.mdx deleted file mode 100644 index 2787accce0b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.26.1.mdx +++ /dev/null @@ -1,6235 +0,0 @@ ---- -title: API Reference - v1.26.1 -navTitle: v1.26.1 -pdfExclude: 'true' - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -
- -## Backup - -

A Backup resource is a request for a PostgreSQL backup by the user.

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Database - -

Database is the Schema for the databases API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Database
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-DatabaseSpec -		 -

Specification of the desired Database. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
status
-DatabaseStatus -		 -

Most recently observed status of the Database. 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

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## Publication - -

Publication is the Schema for the publications API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Publication
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PublicationSpec -		 - No description provided.
status [Required]
-PublicationStatus -		 - No description provided.
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## Subscription - -

Subscription is the Schema for the subscriptions API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Subscription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-SubscriptionSpec -		 - No description provided.
status [Required]
-SubscriptionStatus -		 - No description provided.
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
pluginMetadata
-map[string]string -		 -

A map containing the plugin metadata

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
locale
-string -		 -

Sets the default collation order and character classification in the new database.

-
localeProvider
-string -		 -

This option sets the locale provider for databases created in the new cluster. -Available from PostgreSQL 16.

-
icuLocale
-string -		 -

Specifies the ICU locale when the ICU provider is used. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 15.

-
icuRules
-string -		 -

Specifies additional collation rules to customize the behavior of the default collation. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Specifies the locale name when the builtin provider is used. -This option requires localeProvider to be set to builtin. -Available from PostgreSQL 17.

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-[]PluginConfiguration -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod.

-

Deprecated: the field is not set for backup plugins.

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type.

-

Deprecated: the field is not set for backup plugins.

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format. -This field is calculated from the content of LastSuccessfulBackupByMethod.

-

Deprecated: the field is not set for backup plugins.

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type.

-

Deprecated: the field is not set for backup plugins.

-
lastFailedBackup
-string -		 -

Last failed backup, stored as a date in RFC3339 format.

-

Deprecated: the field is not set for backup plugins.

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pgDataImageInfo
-ImageInfo -		 -

PGDataImageInfo contains the details of the latest image that has run on the current data directory.

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
systemID
-string -		 -

SystemID is the latest detected PostgreSQL SystemID

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataDurabilityLevel - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are required or preferred.

- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseObjectSpec - -**Appears in:** - -- [ExtensionSpec](#postgresql-k8s-enterprisedb-io-v1-ExtensionSpec) - -- [SchemaSpec](#postgresql-k8s-enterprisedb-io-v1-SchemaSpec) - -

DatabaseObjectSpec contains the fields which are common to every -database object

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the extension/schema

-
ensure
-EnsureOption -		 -

Specifies whether an extension/schema should be present or absent in -the database. If set to present, the extension/schema will be -created if it does not exist. If set to absent, the -extension/schema will be removed if it exists.

-
- -
- -## DatabaseObjectStatus - -**Appears in:** - -- [DatabaseStatus](#postgresql-k8s-enterprisedb-io-v1-DatabaseStatus) - -

DatabaseObjectStatus is the status of the managed database objects

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the object

-
applied [Required]
-bool -		 -

True of the object has been installed successfully in -the database

-
message
-string -		 -

Message is the object reconciliation message

-
- -
- -## DatabaseReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases.

- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## DatabaseSpec - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseSpec is the specification of a Postgresql Database, built around the -CREATE DATABASE, ALTER DATABASE, and DROP DATABASE SQL commands of -PostgreSQL.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster hosting the database.

-
ensure
-EnsureOption -		 -

Ensure the PostgreSQL database is present or absent - defaults to "present".

-
name [Required]
-string -		 -

The name of the database to create inside PostgreSQL. This setting cannot be changed.

-
owner [Required]
-string -		 -

Maps to the OWNER parameter of CREATE DATABASE. -Maps to the OWNER TO command of ALTER DATABASE. -The role name of the user who owns the database inside PostgreSQL.

-
template
-string -		 -

Maps to the TEMPLATE parameter of CREATE DATABASE. This setting -cannot be changed. The name of the template from which to create -this database.

-
encoding
-string -		 -

Maps to the ENCODING parameter of CREATE DATABASE. This setting -cannot be changed. Character set encoding to use in the database.

-
locale
-string -		 -

Maps to the LOCALE parameter of CREATE DATABASE. This setting -cannot be changed. Sets the default collation order and character -classification in the new database.

-
localeProvider
-string -		 -

Maps to the LOCALE_PROVIDER parameter of CREATE DATABASE. This -setting cannot be changed. This option sets the locale provider for -databases created in the new cluster. Available from PostgreSQL 16.

-
localeCollate
-string -		 -

Maps to the LC_COLLATE parameter of CREATE DATABASE. This -setting cannot be changed.

-
localeCType
-string -		 -

Maps to the LC_CTYPE parameter of CREATE DATABASE. This setting -cannot be changed.

-
icuLocale
-string -		 -

Maps to the ICU_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the ICU locale when the ICU -provider is used. This option requires localeProvider to be set to -icu. Available from PostgreSQL 15.

-
icuRules
-string -		 -

Maps to the ICU_RULES parameter of CREATE DATABASE. This setting -cannot be changed. Specifies additional collation rules to customize -the behavior of the default collation. This option requires -localeProvider to be set to icu. Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Maps to the BUILTIN_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the locale name when the -builtin provider is used. This option requires localeProvider to -be set to builtin. Available from PostgreSQL 17.

-
collationVersion
-string -		 -

Maps to the COLLATION_VERSION parameter of CREATE DATABASE. This -setting cannot be changed.

-
isTemplate
-bool -		 -

Maps to the IS_TEMPLATE parameter of CREATE DATABASE and ALTER DATABASE. If true, this database is considered a template and can -be cloned by any user with CREATEDB privileges.

-
allowConnections
-bool -		 -

Maps to the ALLOW_CONNECTIONS parameter of CREATE DATABASE and -ALTER DATABASE. If false then no one can connect to this database.

-
connectionLimit
-int -		 -

Maps to the CONNECTION LIMIT clause of CREATE DATABASE and -ALTER DATABASE. How many concurrent connections can be made to -this database. -1 (the default) means no limit.

-
tablespace
-string -		 -

Maps to the TABLESPACE parameter of CREATE DATABASE. -Maps to the SET TABLESPACE command of ALTER DATABASE. -The name of the tablespace (in PostgreSQL) that will be associated -with the new database. This tablespace will be the default -tablespace used for objects created in this database.

-
databaseReclaimPolicy
-DatabaseReclaimPolicy -		 -

The policy for end-of-life maintenance of this database.

-
schemas
-[]SchemaSpec -		 -

The list of schemas to be managed in the database

-
extensions
-[]ExtensionSpec -		 -

The list of extensions to be managed in the database

-
- -
- -## DatabaseStatus - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseStatus defines the observed state of Database

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the database was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
schemas
-[]DatabaseObjectStatus -		 -

Schemas is the status of the managed schemas

-
extensions
-[]DatabaseObjectStatus -		 -

Extensions is the status of the managed extensions

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [DatabaseObjectSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseObjectSpec) - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExtensionSpec - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

ExtensionSpec configures an extension in a database

- - - - - - - - - - - - - - -
FieldDescription
DatabaseObjectSpec
-DatabaseObjectSpec -		(Members of DatabaseObjectSpec are embedded into this type.) -

Common fields

-
version [Required]
-string -		 -

The version of the extension to install. If empty, the operator will -install the default version (whatever is specified in the -extension's control file)

-
schema [Required]
-string -		 -

The name of the schema in which to install the extension's objects, -in case the extension allows its contents to be relocated. If not -specified (default), and the extension's control file does not -specify a schema either, the current default object creation schema -is used.

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
plugin [Required]
-PluginConfiguration -		 -

The configuration of the plugin that is taking care -of WAL archiving and backups for this external cluster

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## ImageInfo - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ImageInfo contains the information about a PostgreSQL image

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

Image is the image name

-
majorVersion [Required]
-int -		 -

MajorVersion is the major version of the image

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
pgDumpExtraOptions
-[]string -		 -

List of custom options to pass to the pg_dump command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
pgRestoreExtraOptions
-[]string -		 -

List of custom options to pass to the pg_restore command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
ip [Required]
-string -		 -

IP address of the instance

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
enabled
-bool -		 -

Enabled is true if this plugin will be used

-
isWALArchiver
-bool -		 -

Only one plugin can be declared as WALArchiver. -Cannot be active if ".spec.backup.barmanObjectStore" configuration is present.

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
restoreJobHookCapabilities
-[]string -		 -

RestoreJobHookCapabilities are the list of capabilities of the -plugin regarding the RestoreJobHook management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [ProbeWithStrategy](#postgresql-k8s-enterprisedb-io-v1-ProbeWithStrategy) - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbeStrategyType - -(Alias of `string`) - -**Appears in:** - -- [ProbeWithStrategy](#postgresql-k8s-enterprisedb-io-v1-ProbeWithStrategy) - -

ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready

- -
- -## ProbeWithStrategy - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

ProbeWithStrategy is the configuration of the startup probe

- - - - - - - - - - - - - - -
FieldDescription
Probe
-Probe -		(Members of Probe are embedded into this type.) -

Probe is the standard probe configuration

-
type
-ProbeStrategyType -		 -

The probe strategy

-
maximumLag
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Lag limit. Used only for streaming strategy

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-ProbeWithStrategy -		 -

The startup probe configuration

-
liveness [Required]
-Probe -		 -

The liveness probe configuration

-
readiness [Required]
-ProbeWithStrategy -		 -

The readiness probe configuration

-
- -
- -## PublicationReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications.

- -
- -## PublicationSpec - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationSpec defines the desired state of Publication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "publisher"

-
name [Required]
-string -		 -

The name of the publication inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "publisher" cluster

-
parameters
-map[string]string -		 -

Publication parameters part of the WITH clause as expected by -PostgreSQL CREATE PUBLICATION command

-
target [Required]
-PublicationTarget -		 -

Target of the publication as expected by PostgreSQL CREATE PUBLICATION command

-
publicationReclaimPolicy
-PublicationReclaimPolicy -		 -

The policy for end-of-life maintenance of this publication

-
- -
- -## PublicationStatus - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationStatus defines the observed state of Publication

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the publication was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## PublicationTarget - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationTarget is what this publication should publish

- - - - - - - - - - - -
FieldDescription
allTables
-bool -		 -

Marks the publication as one that replicates changes for all tables -in the database, including tables created in the future. -Corresponding to FOR ALL TABLES in PostgreSQL.

-
objects
-[]PublicationTargetObject -		 -

Just the following schema objects

-
- -
- -## PublicationTargetObject - -**Appears in:** - -- [PublicationTarget](#postgresql-k8s-enterprisedb-io-v1-PublicationTarget) - -

PublicationTargetObject is an object to publish

- - - - - - - - - - - -
FieldDescription
tablesInSchema
-string -		 -

Marks the publication as one that replicates changes for all tables -in the specified list of schemas, including tables created in the -future. Corresponding to FOR TABLES IN SCHEMA in PostgreSQL.

-
table
-PublicationTargetTable -		 -

Specifies a list of tables to add to the publication. Corresponding -to FOR TABLE in PostgreSQL.

-
- -
- -## PublicationTargetTable - -**Appears in:** - -- [PublicationTargetObject](#postgresql-k8s-enterprisedb-io-v1-PublicationTargetObject) - -

PublicationTargetTable is a table to publish

- - - - - - - - - - - - - - - - - -
FieldDescription
only
-bool -		 -

Whether to limit to the table only or include all its descendants

-
name [Required]
-string -		 -

The table name

-
schema
-string -		 -

The schema name

-
columns
-[]string -		 -

The columns to publish

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SchemaSpec - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

SchemaSpec configures a schema in a database

- - - - - - - - - - - -
FieldDescription
DatabaseObjectSpec
-DatabaseObjectSpec -		(Members of DatabaseObjectSpec are embedded into this type.) -

Common fields

-
owner [Required]
-string -		 -

The role name of the user who owns the schema inside PostgreSQL. -It maps to the AUTHORIZATION parameter of CREATE SCHEMA and the -OWNER TO command of ALTER SCHEMA.

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SubscriptionReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [SubscriptionSpec](#postgresql-k8s-enterprisedb-io-v1-SubscriptionSpec) - -

SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions.

- -
- -## SubscriptionSpec - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionSpec defines the desired state of Subscription

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "subscriber"

-
name [Required]
-string -		 -

The name of the subscription inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "subscriber" cluster

-
parameters
-map[string]string -		 -

Subscription parameters included in the WITH clause of the PostgreSQL -CREATE SUBSCRIPTION command. Most parameters cannot be changed -after the subscription is created and will be ignored if modified -later, except for a limited set documented at: -https://www.postgresql.org/docs/current/sql-altersubscription.html#SQL-ALTERSUBSCRIPTION-PARAMS-SET

-
publicationName [Required]
-string -		 -

The name of the publication inside the PostgreSQL database in the -"publisher"

-
publicationDBName
-string -		 -

The name of the database containing the publication on the external -cluster. Defaults to the one in the external cluster definition.

-
externalClusterName [Required]
-string -		 -

The name of the external cluster with the publication ("publisher")

-
subscriptionReclaimPolicy
-SubscriptionReclaimPolicy -		 -

The policy for end-of-life maintenance of this subscription

-
- -
- -## SubscriptionStatus - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionStatus defines the observed state of Subscription

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the subscription was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
dataDurability
-DataDurabilityLevel -		 -

If set to "required", data durability is strictly enforced. Write operations -with synchronous commit settings (on, remote_write, or remote_apply) will -block if there are insufficient healthy replicas, ensuring data persistence. -If set to "preferred", data durability is maintained when healthy replicas -are available, but the required number of instances will adjust dynamically -if replicas become unavailable. This setting relaxes strict durability enforcement -to allow for operational continuity. This setting is only applicable if both -standbyNamesPre and standbyNamesPost are unset (empty).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.27.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.27.0.mdx deleted file mode 100644 index fa0fd04d847..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.27.0.mdx +++ /dev/null @@ -1,6462 +0,0 @@ ---- -title: API Reference - v1.27.0 -navTitle: v1.27.0 -pdfExclude: 'true' - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) -- [FailoverQuorum](#postgresql-k8s-enterprisedb-io-v1-FailoverQuorum) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -
- -## Backup - -

A Backup resource is a request for a PostgreSQL backup by the user.

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster is the Schema for the PostgreSQL API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Database - -

Database is the Schema for the databases API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Database
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-DatabaseSpec -		 -

Specification of the desired Database. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
status
-DatabaseStatus -		 -

Most recently observed status of the Database. 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

-
- -
- -## FailoverQuorum - -**Appears in:** - -

FailoverQuorum contains the information about the current failover -quorum status of a PG cluster. It is updated by the instance manager -of the primary node and reset to zero by the operator to trigger -an update.

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		FailoverQuorum
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
status
-FailoverQuorumStatus -		 -

Most recently observed status of the failover quorum.

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## Publication - -

Publication is the Schema for the publications API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Publication
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PublicationSpec -		 - No description provided.
status [Required]
-PublicationStatus -		 - No description provided.
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## Subscription - -

Subscription is the Schema for the subscriptions API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Subscription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-SubscriptionSpec -		 - No description provided.
status [Required]
-SubscriptionStatus -		 - No description provided.
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
pluginMetadata
-map[string]string -		 -

A map containing the plugin metadata

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
locale
-string -		 -

Sets the default collation order and character classification in the new database.

-
localeProvider
-string -		 -

This option sets the locale provider for databases created in the new cluster. -Available from PostgreSQL 16.

-
icuLocale
-string -		 -

Specifies the ICU locale when the ICU provider is used. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 15.

-
icuRules
-string -		 -

Specifies additional collation rules to customize the behavior of the default collation. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Specifies the locale name when the builtin provider is used. -This option requires localeProvider to be set to builtin. -Available from PostgreSQL 17.

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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).

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-[]PluginConfiguration -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of Cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod.

-

Deprecated: the field is not set for backup plugins.

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type.

-

Deprecated: the field is not set for backup plugins.

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format. -This field is calculated from the content of LastSuccessfulBackupByMethod.

-

Deprecated: the field is not set for backup plugins.

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type.

-

Deprecated: the field is not set for backup plugins.

-
lastFailedBackup
-string -		 -

Last failed backup, stored as a date in RFC3339 format.

-

Deprecated: the field is not set for backup plugins.

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pgDataImageInfo
-ImageInfo -		 -

PGDataImageInfo contains the details of the latest image that has run on the current data directory.

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
systemID
-string -		 -

SystemID is the latest detected PostgreSQL SystemID

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataDurabilityLevel - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are required or preferred.

- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseObjectSpec - -**Appears in:** - -- [ExtensionSpec](#postgresql-k8s-enterprisedb-io-v1-ExtensionSpec) - -- [SchemaSpec](#postgresql-k8s-enterprisedb-io-v1-SchemaSpec) - -

DatabaseObjectSpec contains the fields which are common to every -database object

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the extension/schema

-
ensure
-EnsureOption -		 -

Specifies whether an extension/schema should be present or absent in -the database. If set to present, the extension/schema will be -created if it does not exist. If set to absent, the -extension/schema will be removed if it exists.

-
- -
- -## DatabaseObjectStatus - -**Appears in:** - -- [DatabaseStatus](#postgresql-k8s-enterprisedb-io-v1-DatabaseStatus) - -

DatabaseObjectStatus is the status of the managed database objects

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the object

-
applied [Required]
-bool -		 -

True of the object has been installed successfully in -the database

-
message
-string -		 -

Message is the object reconciliation message

-
- -
- -## DatabaseReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases.

- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## DatabaseSpec - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseSpec is the specification of a Postgresql Database, built around the -CREATE DATABASE, ALTER DATABASE, and DROP DATABASE SQL commands of -PostgreSQL.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster hosting the database.

-
ensure
-EnsureOption -		 -

Ensure the PostgreSQL database is present or absent - defaults to "present".

-
name [Required]
-string -		 -

The name of the database to create inside PostgreSQL. This setting cannot be changed.

-
owner [Required]
-string -		 -

Maps to the OWNER parameter of CREATE DATABASE. -Maps to the OWNER TO command of ALTER DATABASE. -The role name of the user who owns the database inside PostgreSQL.

-
template
-string -		 -

Maps to the TEMPLATE parameter of CREATE DATABASE. This setting -cannot be changed. The name of the template from which to create -this database.

-
encoding
-string -		 -

Maps to the ENCODING parameter of CREATE DATABASE. This setting -cannot be changed. Character set encoding to use in the database.

-
locale
-string -		 -

Maps to the LOCALE parameter of CREATE DATABASE. This setting -cannot be changed. Sets the default collation order and character -classification in the new database.

-
localeProvider
-string -		 -

Maps to the LOCALE_PROVIDER parameter of CREATE DATABASE. This -setting cannot be changed. This option sets the locale provider for -databases created in the new cluster. Available from PostgreSQL 16.

-
localeCollate
-string -		 -

Maps to the LC_COLLATE parameter of CREATE DATABASE. This -setting cannot be changed.

-
localeCType
-string -		 -

Maps to the LC_CTYPE parameter of CREATE DATABASE. This setting -cannot be changed.

-
icuLocale
-string -		 -

Maps to the ICU_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the ICU locale when the ICU -provider is used. This option requires localeProvider to be set to -icu. Available from PostgreSQL 15.

-
icuRules
-string -		 -

Maps to the ICU_RULES parameter of CREATE DATABASE. This setting -cannot be changed. Specifies additional collation rules to customize -the behavior of the default collation. This option requires -localeProvider to be set to icu. Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Maps to the BUILTIN_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the locale name when the -builtin provider is used. This option requires localeProvider to -be set to builtin. Available from PostgreSQL 17.

-
collationVersion
-string -		 -

Maps to the COLLATION_VERSION parameter of CREATE DATABASE. This -setting cannot be changed.

-
isTemplate
-bool -		 -

Maps to the IS_TEMPLATE parameter of CREATE DATABASE and ALTER DATABASE. If true, this database is considered a template and can -be cloned by any user with CREATEDB privileges.

-
allowConnections
-bool -		 -

Maps to the ALLOW_CONNECTIONS parameter of CREATE DATABASE and -ALTER DATABASE. If false then no one can connect to this database.

-
connectionLimit
-int -		 -

Maps to the CONNECTION LIMIT clause of CREATE DATABASE and -ALTER DATABASE. How many concurrent connections can be made to -this database. -1 (the default) means no limit.

-
tablespace
-string -		 -

Maps to the TABLESPACE parameter of CREATE DATABASE. -Maps to the SET TABLESPACE command of ALTER DATABASE. -The name of the tablespace (in PostgreSQL) that will be associated -with the new database. This tablespace will be the default -tablespace used for objects created in this database.

-
databaseReclaimPolicy
-DatabaseReclaimPolicy -		 -

The policy for end-of-life maintenance of this database.

-
schemas
-[]SchemaSpec -		 -

The list of schemas to be managed in the database

-
extensions
-[]ExtensionSpec -		 -

The list of extensions to be managed in the database

-
- -
- -## DatabaseStatus - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseStatus defines the observed state of Database

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the database was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
schemas
-[]DatabaseObjectStatus -		 -

Schemas is the status of the managed schemas

-
extensions
-[]DatabaseObjectStatus -		 -

Extensions is the status of the managed extensions

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [DatabaseObjectSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseObjectSpec) - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExtensionConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

ExtensionConfiguration is the configuration used to add -PostgreSQL extensions to the Cluster.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the extension, required

-
image [Required]
-core/v1.ImageVolumeSource -		 -

The image containing the extension, required

-
extension_control_path
-[]string -		 -

The list of directories inside the image which should be added to extension_control_path. -If not defined, defaults to "/share".

-
dynamic_library_path
-[]string -		 -

The list of directories inside the image which should be added to dynamic_library_path. -If not defined, defaults to "/lib".

-
ld_library_path
-[]string -		 -

The list of directories inside the image which should be added to ld_library_path.

-
- -
- -## ExtensionSpec - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

ExtensionSpec configures an extension in a database

- - - - - - - - - - - - - - -
FieldDescription
DatabaseObjectSpec
-DatabaseObjectSpec -		(Members of DatabaseObjectSpec are embedded into this type.) -

Common fields

-
version [Required]
-string -		 -

The version of the extension to install. If empty, the operator will -install the default version (whatever is specified in the -extension's control file)

-
schema [Required]
-string -		 -

The name of the schema in which to install the extension's objects, -in case the extension allows its contents to be relocated. If not -specified (default), and the extension's control file does not -specify a schema either, the current default object creation schema -is used.

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
plugin [Required]
-PluginConfiguration -		 -

The configuration of the plugin that is taking care -of WAL archiving and backups for this external cluster

-
- -
- -## FailoverQuorumStatus - -**Appears in:** - -- [FailoverQuorum](#postgresql-k8s-enterprisedb-io-v1-FailoverQuorum) - -

FailoverQuorumStatus is the latest observed status of the failover -quorum of the PG cluster.

- - - - - - - - - - - - - - - - - -
FieldDescription
method
-string -		 -

Contains the latest reported Method value.

-
standbyNames
-[]string -		 -

StandbyNames is the list of potentially synchronous -instance names.

-
standbyNumber
-int -		 -

StandbyNumber is the number of synchronous standbys that transactions -need to wait for replies from.

-
primary
-string -		 -

Primary is the name of the primary instance that updated -this object the latest time.

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## ImageInfo - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ImageInfo contains the information about a PostgreSQL image

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

Image is the image name

-
majorVersion [Required]
-int -		 -

MajorVersion is the major version of the image

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
pgDumpExtraOptions
-[]string -		 -

List of custom options to pass to the pg_dump command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
pgRestoreExtraOptions
-[]string -		 -

List of custom options to pass to the pg_restore command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
ip [Required]
-string -		 -

IP address of the instance

-
- -
- -## IsolationCheckConfiguration - -**Appears in:** - -- [LivenessProbe](#postgresql-k8s-enterprisedb-io-v1-LivenessProbe) - -

IsolationCheckConfiguration contains the configuration for the isolation check -functionality in the liveness probe

- - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

Whether primary isolation checking is enabled for the liveness probe

-
requestTimeout
-int -		 -

Timeout in milliseconds for requests during the primary isolation check

-
connectionTimeout
-int -		 -

Timeout in milliseconds for connections during the primary isolation check

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LivenessProbe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

LivenessProbe is the configuration of the liveness probe

- - - - - - - - - - - -
FieldDescription
Probe
-Probe -		(Members of Probe are embedded into this type.) -

Probe is the standard probe configuration

-
isolationCheck
-IsolationCheckConfiguration -		 -

Configure the feature that extends the liveness probe for a primary -instance. In addition to the basic checks, this verifies whether the -primary is isolated from the Kubernetes API server and from its -replicas, ensuring that it can be safely shut down if network -partition or API unavailability is detected. Enabled by default.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
enabled
-bool -		 -

Enabled is true if this plugin will be used

-
isWALArchiver
-bool -		 -

Only one plugin can be declared as WALArchiver. -Cannot be active if ".spec.backup.barmanObjectStore" configuration is present.

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
restoreJobHookCapabilities
-[]string -		 -

RestoreJobHookCapabilities are the list of capabilities of the -plugin regarding the RestoreJobHook management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
extensions
-[]ExtensionConfiguration -		 -

The configuration of the extensions to be added

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [LivenessProbe](#postgresql-k8s-enterprisedb-io-v1-LivenessProbe) - -- [ProbeWithStrategy](#postgresql-k8s-enterprisedb-io-v1-ProbeWithStrategy) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbeStrategyType - -(Alias of `string`) - -**Appears in:** - -- [ProbeWithStrategy](#postgresql-k8s-enterprisedb-io-v1-ProbeWithStrategy) - -

ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready

- -
- -## ProbeWithStrategy - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

ProbeWithStrategy is the configuration of the startup probe

- - - - - - - - - - - - - - -
FieldDescription
Probe
-Probe -		(Members of Probe are embedded into this type.) -

Probe is the standard probe configuration

-
type
-ProbeStrategyType -		 -

The probe strategy

-
maximumLag
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Lag limit. Used only for streaming strategy

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-ProbeWithStrategy -		 -

The startup probe configuration

-
liveness [Required]
-LivenessProbe -		 -

The liveness probe configuration

-
readiness [Required]
-ProbeWithStrategy -		 -

The readiness probe configuration

-
- -
- -## PublicationReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications.

- -
- -## PublicationSpec - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationSpec defines the desired state of Publication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "publisher"

-
name [Required]
-string -		 -

The name of the publication inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "publisher" cluster

-
parameters
-map[string]string -		 -

Publication parameters part of the WITH clause as expected by -PostgreSQL CREATE PUBLICATION command

-
target [Required]
-PublicationTarget -		 -

Target of the publication as expected by PostgreSQL CREATE PUBLICATION command

-
publicationReclaimPolicy
-PublicationReclaimPolicy -		 -

The policy for end-of-life maintenance of this publication

-
- -
- -## PublicationStatus - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationStatus defines the observed state of Publication

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the publication was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## PublicationTarget - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationTarget is what this publication should publish

- - - - - - - - - - - -
FieldDescription
allTables
-bool -		 -

Marks the publication as one that replicates changes for all tables -in the database, including tables created in the future. -Corresponding to FOR ALL TABLES in PostgreSQL.

-
objects
-[]PublicationTargetObject -		 -

Just the following schema objects

-
- -
- -## PublicationTargetObject - -**Appears in:** - -- [PublicationTarget](#postgresql-k8s-enterprisedb-io-v1-PublicationTarget) - -

PublicationTargetObject is an object to publish

- - - - - - - - - - - -
FieldDescription
tablesInSchema
-string -		 -

Marks the publication as one that replicates changes for all tables -in the specified list of schemas, including tables created in the -future. Corresponding to FOR TABLES IN SCHEMA in PostgreSQL.

-
table
-PublicationTargetTable -		 -

Specifies a list of tables to add to the publication. Corresponding -to FOR TABLE in PostgreSQL.

-
- -
- -## PublicationTargetTable - -**Appears in:** - -- [PublicationTargetObject](#postgresql-k8s-enterprisedb-io-v1-PublicationTargetObject) - -

PublicationTargetTable is a table to publish

- - - - - - - - - - - - - - - - - -
FieldDescription
only
-bool -		 -

Whether to limit to the table only or include all its descendants

-
name [Required]
-string -		 -

The table name

-
schema
-string -		 -

The schema name

-
columns
-[]string -		 -

The columns to publish

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
synchronizeLogicalDecoding
-bool -		 -

When enabled, the operator automatically manages synchronization of logical -decoding (replication) slots across high-availability clusters.

-

Requires one of the following conditions:

-
    -
  • PostgreSQL version 17 or later
    • -
  • PostgreSQL version < 17 with pg_failover_slots extension enabled
    • -
-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SchemaSpec - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

SchemaSpec configures a schema in a database

- - - - - - - - - - - -
FieldDescription
DatabaseObjectSpec
-DatabaseObjectSpec -		(Members of DatabaseObjectSpec are embedded into this type.) -

Common fields

-
owner [Required]
-string -		 -

The role name of the user who owns the schema inside PostgreSQL. -It maps to the AUTHORIZATION parameter of CREATE SCHEMA and the -OWNER TO command of ALTER SCHEMA.

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SubscriptionReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [SubscriptionSpec](#postgresql-k8s-enterprisedb-io-v1-SubscriptionSpec) - -

SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions.

- -
- -## SubscriptionSpec - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionSpec defines the desired state of Subscription

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "subscriber"

-
name [Required]
-string -		 -

The name of the subscription inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "subscriber" cluster

-
parameters
-map[string]string -		 -

Subscription parameters included in the WITH clause of the PostgreSQL -CREATE SUBSCRIPTION command. Most parameters cannot be changed -after the subscription is created and will be ignored if modified -later, except for a limited set documented at: -https://www.postgresql.org/docs/current/sql-altersubscription.html#SQL-ALTERSUBSCRIPTION-PARAMS-SET

-
publicationName [Required]
-string -		 -

The name of the publication inside the PostgreSQL database in the -"publisher"

-
publicationDBName
-string -		 -

The name of the database containing the publication on the external -cluster. Defaults to the one in the external cluster definition.

-
externalClusterName [Required]
-string -		 -

The name of the external cluster with the publication ("publisher")

-
subscriptionReclaimPolicy
-SubscriptionReclaimPolicy -		 -

The policy for end-of-life maintenance of this subscription

-
- -
- -## SubscriptionStatus - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionStatus defines the observed state of Subscription

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the subscription was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
dataDurability
-DataDurabilityLevel -		 -

If set to "required", data durability is strictly enforced. Write operations -with synchronous commit settings (on, remote_write, or remote_apply) will -block if there are insufficient healthy replicas, ensuring data persistence. -If set to "preferred", data durability is maintained when healthy replicas -are available, but the required number of instances will adjust dynamically -if replicas become unavailable. This setting relaxes strict durability enforcement -to allow for operational continuity. This setting is only applicable if both -standbyNamesPre and standbyNamesPost are unset (empty).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.27.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.27.1.mdx deleted file mode 100644 index 8c2fd03ef07..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.27.1.mdx +++ /dev/null @@ -1,6482 +0,0 @@ ---- -title: API Reference - v1.27.1 -navTitle: v1.27.1 -pdfExclude: 'true' - ---- - -

Package v1 contains API Schema definitions for the postgresql v1 API group

- -## Resource Types - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) -- [FailoverQuorum](#postgresql-k8s-enterprisedb-io-v1-FailoverQuorum) -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -
- -## Backup - -

A Backup resource is a request for a PostgreSQL backup by the user.

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Backup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-BackupSpec -		 -

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
-BackupStatus -		 -

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

-
- -
- -## Cluster - -

Cluster defines the API schema for a highly available PostgreSQL database cluster -managed by {{name.ln}}.

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Cluster
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ClusterSpec -		 -

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
-ClusterStatus -		 -

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

-
- -
- -## ClusterImageCatalog - -

ClusterImageCatalog is the Schema for the clusterimagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ClusterImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ClusterImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Database - -

Database is the Schema for the databases API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Database
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-DatabaseSpec -		 -

Specification of the desired Database. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
status
-DatabaseStatus -		 -

Most recently observed status of the Database. 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

-
- -
- -## FailoverQuorum - -**Appears in:** - -

FailoverQuorum contains the information about the current failover -quorum status of a PG cluster. It is updated by the instance manager -of the primary node and reset to zero by the operator to trigger -an update.

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		FailoverQuorum
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
status
-FailoverQuorumStatus -		 -

Most recently observed status of the failover quorum.

-
- -
- -## ImageCatalog - -

ImageCatalog is the Schema for the imagecatalogs API

- - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ImageCatalog
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ImageCatalogSpec -		 -

Specification of the desired behavior of the ImageCatalog. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## Pooler - -

Pooler is the Schema for the poolers API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Pooler
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PoolerSpec -		 -

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

-
status
-PoolerStatus -		 -

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

-
- -
- -## Publication - -

Publication is the Schema for the publications API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Publication
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-PublicationSpec -		 - No description provided.
status [Required]
-PublicationStatus -		 - No description provided.
- -
- -## ScheduledBackup - -

ScheduledBackup is the Schema for the scheduledbackups API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		ScheduledBackup
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-ScheduledBackupSpec -		 -

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
-ScheduledBackupStatus -		 -

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

-
- -
- -## Subscription - -

Subscription is the Schema for the subscriptions API

- - - - - - - - - - - - - - - - -
FieldDescription
apiVersion [Required]
string		postgresql.k8s.enterprisedb.io/v1
kind [Required]
string		Subscription
metadata [Required]
-meta/v1.ObjectMeta -		 - No description provided.Refer to the Kubernetes API documentation for the fields of the metadata field.
spec [Required]
-SubscriptionSpec -		 - No description provided.
status [Required]
-SubscriptionStatus -		 - No description provided.
- -
- -## AffinityConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

AffinityConfiguration contains the info we need to create the -affinity rules for Pods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
enablePodAntiAffinity
-bool -		 -

Activates anti-affinity for the pods. The operator will define pods -anti-affinity unless this field is explicitly set to false

-
topologyKey
-string -		 -

TopologyKey to use for anti-affinity configuration. See k8s documentation -for more info on that

-
nodeSelector
-map[string]string -		 -

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
-core/v1.NodeAffinity -		 -

NodeAffinity describes node affinity scheduling rules for the pod. -More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity

-
tolerations
-[]core/v1.Toleration -		 -

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
-string -		 -

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
-core/v1.PodAntiAffinity -		 -

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
-core/v1.PodAffinity -		 -

AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods.

-
- -
- -## AvailableArchitecture - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

AvailableArchitecture represents the state of a cluster's architecture

- - - - - - - - - - - -
FieldDescription
goArch [Required]
-string -		 -

GoArch is the name of the executable architecture

-
hash [Required]
-string -		 -

Hash is the hash of the executable

-
- -
- -## BackupConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation

- - - - - - - - - - - - - - - - - -
FieldDescription
volumeSnapshot
-VolumeSnapshotConfiguration -		 -

VolumeSnapshot provides the configuration for the execution of volume snapshot backups.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
retentionPolicy
-string -		 -

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.

-
target
-BackupTarget -		 -

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.

-
- -
- -## BackupMethod - -(Alias of `string`) - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance

- -
- -## BackupPhase - -(Alias of `string`) - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupPhase is the phase of the backup

- -
- -## BackupPluginConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupPluginConfiguration contains the backup configuration used by -the backup plugin

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin managing this backup

-
parameters
-map[string]string -		 -

Parameters are the configuration parameters passed to the backup -plugin for this backup

-
- -
- -## BackupSnapshotElementStatus - -**Appears in:** - -- [BackupSnapshotStatus](#postgresql-k8s-enterprisedb-io-v1-BackupSnapshotStatus) - -

BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the snapshot resource name

-
type [Required]
-string -		 -

Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE

-
tablespaceName
-string -		 -

TablespaceName is the name of the snapshotted tablespace. Only set -when type is PG_TABLESPACE

-
- -
- -## BackupSnapshotStatus - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup

- - - - - - - - -
FieldDescription
elements
-[]BackupSnapshotElementStatus -		 -

The elements list, populated with the gathered volume snapshots

-
- -
- -## BackupSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it.

- - - - - - - - - - - -
FieldDescription
LocalObjectReference
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		(Members of LocalObjectReference are embedded into this type.) - No description provided.
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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 - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupSpec defines the desired state of Backup

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## BackupStatus - -**Appears in:** - -- [Backup](#postgresql-k8s-enterprisedb-io-v1-Backup) - -

BackupStatus defines the observed state of Backup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
BarmanCredentials
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanCredentials -		(Members of BarmanCredentials are embedded into this type.) -

The potential credentials for each cloud provider

-
majorVersion [Required]
-int -		 -

The PostgreSQL major version that was running when the -backup was taken.

-
endpointCA
-github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

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
-string -		 -

Endpoint to be used to upload data to the cloud, -overriding the automatic endpoint discovery

-
destinationPath
-string -		 -

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.

-
serverName
-string -		 -

The server name on S3, the cluster name is used if this -parameter is omitted

-
encryption
-string -		 -

Encryption method required to S3 API

-
backupId
-string -		 -

The ID of the Barman backup

-
backupName
-string -		 -

The Name of the Barman backup

-
phase
-BackupPhase -		 -

The last backup status

-
startedAt
-meta/v1.Time -		 -

When the backup was started

-
stoppedAt
-meta/v1.Time -		 -

When the backup was terminated

-
beginWal
-string -		 -

The starting WAL

-
endWal
-string -		 -

The ending WAL

-
beginLSN
-string -		 -

The starting xlog

-
endLSN
-string -		 -

The ending xlog

-
error
-string -		 -

The detected error

-
commandOutput
-string -		 -

Unused. Retained for compatibility with old versions.

-
commandError
-string -		 -

The backup command output in case of error

-
backupLabelFile
-[]byte -		 -

Backup label file content as returned by Postgres in case of online (hot) backups

-
tablespaceMapFile
-[]byte -		 -

Tablespace map file content as returned by Postgres in case of online (hot) backups

-
instanceID
-InstanceID -		 -

Information to identify the instance where the backup has been taken from

-
snapshotBackupStatus
-BackupSnapshotStatus -		 -

Status of the volumeSnapshot backup

-
method
-BackupMethod -		 -

The backup method being used

-
online
-bool -		 -

Whether the backup was online/hot (true) or offline/cold (false)

-
pluginMetadata
-map[string]string -		 -

A map containing the plugin metadata

-
- -
- -## BackupTarget - -(Alias of `string`) - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -

BackupTarget describes the preferred targets for a backup

- -
- -## BootstrapConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
initdb
-BootstrapInitDB -		 -

Bootstrap the cluster via initdb

-
recovery
-BootstrapRecovery -		 -

Bootstrap the cluster from a backup

-
pg_basebackup
-BootstrapPgBaseBackup -		 -

Bootstrap the cluster taking a physical backup of another compatible -PostgreSQL instance

-
- -
- -## BootstrapInitDB - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapInitDB is the configuration of the bootstrap process when -initdb is used -Refer to the Bootstrap page of the documentation for more information.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
redwood
-bool -		 -

If we need to enable/disable Redwood compatibility. Requires -EPAS and for EPAS defaults to true

-
options
-[]string -		 -

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.

-
dataChecksums
-bool -		 -

Whether the -k option should be passed to initdb, -enabling checksums on data pages (default: false)

-
encoding
-string -		 -

The value to be passed as option --encoding for initdb (default:UTF8)

-
localeCollate
-string -		 -

The value to be passed as option --lc-collate for initdb (default:C)

-
localeCType
-string -		 -

The value to be passed as option --lc-ctype for initdb (default:C)

-
locale
-string -		 -

Sets the default collation order and character classification in the new database.

-
localeProvider
-string -		 -

This option sets the locale provider for databases created in the new cluster. -Available from PostgreSQL 16.

-
icuLocale
-string -		 -

Specifies the ICU locale when the ICU provider is used. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 15.

-
icuRules
-string -		 -

Specifies additional collation rules to customize the behavior of the default collation. -This option requires localeProvider to be set to icu. -Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Specifies the locale name when the builtin provider is used. -This option requires localeProvider to be set to builtin. -Available from PostgreSQL 17.

-
walSegmentSize
-int -		 -

The value in megabytes (1 to 1024) to be passed to the --wal-segsize -option for initdb (default: empty, resulting in PostgreSQL default: 16MB)

-
postInitSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the postgres -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitApplicationSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the application -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
postInitTemplateSQL
-[]string -		 -

List of SQL queries to be executed as a superuser in the template1 -database right after the cluster has been created - to be used with extreme care -(by default empty)

-
import
-Import -		 -

Bootstraps the new cluster by importing data from an existing PostgreSQL -instance using logical backup (pg_dump and pg_restore)

-
postInitApplicationSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the application database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitTemplateSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the template1 database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
postInitSQLRefs
-SQLRefs -		 -

List of references to ConfigMaps or Secrets containing SQL files -to be executed as a superuser in the postgres database right after -the cluster has been created. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. -(by default empty)

-
- -
- -## BootstrapPgBaseBackup - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-string -		 -

The name of the server of which we need to take a physical backup

-
database
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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 - -**Appears in:** - -- [BootstrapConfiguration](#postgresql-k8s-enterprisedb-io-v1-BootstrapConfiguration) - -

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.
    2. -
- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backup
-BackupSource -		 -

The backup object containing the physical base backup from which to -initiate the recovery procedure. -Mutually exclusive with source and volumeSnapshots.

-
source
-string -		 -

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.

-
volumeSnapshots
-DataSource -		 -

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 {{name.ln}}, 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.

-
recoveryTarget
-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
-string -		 -

Name of the database used by the application. Default: app.

-
owner
-string -		 -

Name of the owner of the database in the instance to be used -by applications. Defaults to the value of the database key.

-
secret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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

-
- -
- -## CatalogImage - -**Appears in:** - -- [ImageCatalogSpec](#postgresql-k8s-enterprisedb-io-v1-ImageCatalogSpec) - -

CatalogImage defines the image and major version

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

The image reference

-
major [Required]
-int -		 -

The PostgreSQL major version of the image. Must be unique within the catalog.

-
- -
- -## CertificatesConfiguration - -**Appears in:** - -- [CertificatesStatus](#postgresql-k8s-enterprisedb-io-v1-CertificatesStatus) - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

CertificatesConfiguration contains the needed configurations to handle server certificates.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
serverCASecret
-string -		 -

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.
    • -
-
serverTLSSecret
-string -		 -

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.

-
replicationTLSSecret
-string -		 -

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.

-
clientCASecret
-string -		 -

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.
    • -
-
serverAltDNSNames
-[]string -		 -

The list of the server alternative DNS names to be added to the generated server TLS certificates, when required.

-
- -
- -## CertificatesStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

CertificatesStatus contains configuration certificates and related expiration dates.

- - - - - - - - - - - -
FieldDescription
CertificatesConfiguration
-CertificatesConfiguration -		(Members of CertificatesConfiguration are embedded into this type.) -

Needed configurations to handle server certificates, initialized with default values, if needed.

-
expirations
-map[string]string -		 -

Expiration dates for all certificates.

-
- -
- -## ClusterMonitoringTLSConfiguration - -**Appears in:** - -- [MonitoringConfiguration](#postgresql-k8s-enterprisedb-io-v1-MonitoringConfiguration) - -

ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring

- - - - - - - - -
FieldDescription
enabled
-bool -		 -

Enable TLS for the monitoring endpoint. -Changing this option will force a rollout of all instances.

-
- -
- -## ClusterSpec - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterSpec defines the desired state of a PostgreSQL cluster managed by -{{name.ln}}.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
description
-string -		 -

Description of this PostgreSQL cluster

-
inheritedMetadata
-EmbeddedObjectMetadata -		 -

Metadata that will be inherited by all objects related to the Cluster

-
imageName
-string -		 -

Name of the container image, supporting both tags (<image>:<tag>) -and digests for deterministic and repeatable deployments -(<image>:<tag>@sha256:<digestValue>)

-
imageCatalogRef
-ImageCatalogRef -		 -

Defines the major PostgreSQL version we want to use within an ImageCatalog

-
imagePullPolicy
-core/v1.PullPolicy -		 -

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

-
schedulerName
-string -		 -

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/

-
postgresUID
-int64 -		 -

The UID of the postgres user inside the image, defaults to 26

-
postgresGID
-int64 -		 -

The GID of the postgres user inside the image, defaults to 26

-
instances [Required]
-int -		 -

Number of instances required in the cluster

-
minSyncReplicas
-int -		 -

Minimum number of instances required in synchronous replication with the -primary. Undefined or 0 allow writes to complete when no standby is -available.

-
maxSyncReplicas
-int -		 -

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.

-
postgresql
-PostgresConfiguration -		 -

Configuration of the PostgreSQL server

-
replicationSlots
-ReplicationSlotsConfiguration -		 -

Replication slots management configuration

-
bootstrap
-BootstrapConfiguration -		 -

Instructions to bootstrap this cluster

-
replica
-ReplicaClusterConfiguration -		 -

Replica cluster configuration

-
superuserSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The secret containing the superuser password. If not defined a new -secret will be created with a randomly generated password

-
enableSuperuserAccess
-bool -		 -

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. Disabled by default.

-
certificates
-CertificatesConfiguration -		 -

The configuration for the CA and related certificates

-
imagePullSecrets
-[]github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
storage
-StorageConfiguration -		 -

Configuration of the storage of the instances

-
serviceAccountTemplate
-ServiceAccountTemplate -		 -

Configure the generation of the service account

-
walStorage
-StorageConfiguration -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
ephemeralVolumeSource
-core/v1.EphemeralVolumeSource -		 -

EphemeralVolumeSource allows the user to configure the source of ephemeral volumes.

-
startDelay
-int32 -		 -

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).

-
stopDelay
-int32 -		 -

The time in seconds that is allowed for a PostgreSQL instance to -gracefully shutdown (default 1800)

-
smartStopDelay
-int32 -		 -

Deprecated: please use SmartShutdownTimeout instead

-
smartShutdownTimeout
-int32 -		 -

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). Default is 180 seconds.

-
switchoverDelay
-int32 -		 -

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).

-
failoverDelay
-int32 -		 -

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
-int32 -		 -

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
-AffinityConfiguration -		 -

Affinity/Anti-affinity rules for Pods

-
topologySpreadConstraints
-[]core/v1.TopologySpreadConstraint -		 -

TopologySpreadConstraints specifies how to spread matching pods among the given topology. -More info: -https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

-
resources
-core/v1.ResourceRequirements -		 -

Resources requirements of every generated Pod. Please refer to -https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ -for more information.

-
ephemeralVolumesSizeLimit
-EphemeralVolumesSizeLimitConfiguration -		 -

EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral -volumes

-
priorityClassName
-string -		 -

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

-
primaryUpdateStrategy
-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)

-
primaryUpdateMethod
-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)

-
backup
-BackupConfiguration -		 -

The configuration to be used for backups

-
nodeMaintenanceWindow
-NodeMaintenanceWindow -		 -

Define a maintenance window for the Kubernetes nodes

-
licenseKey
-string -		 -

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.

-
licenseKeySecret
-core/v1.SecretKeySelector -		 -

The reference to the license key. When this is set it take precedence over LicenseKey.

-
monitoring
-MonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this cluster

-
externalClusters
-[]ExternalCluster -		 -

The list of external clusters which are used in the configuration

-
logLevel
-string -		 -

The instances' log level, one of the following values: error, warning, info (default), debug, trace

-
projectedVolumeTemplate
-core/v1.ProjectedVolumeSource -		 -

Template to be used to define projected volumes, projected volumes will be mounted -under /projected base folder

-
env
-[]core/v1.EnvVar -		 -

Env follows the Env format to pass environment variables -to the pods created in the cluster

-
envFrom
-[]core/v1.EnvFromSource -		 -

EnvFrom follows the EnvFrom format to pass environment variables -sources to the pods to be used by Env

-
managed
-ManagedConfiguration -		 -

The configuration that is used by the portions of PostgreSQL that are managed by the instance manager

-
seccompProfile
-core/v1.SeccompProfile -		 -

The SeccompProfile applied to every Pod and Container. -Defaults to: RuntimeDefault

-
tablespaces
-[]TablespaceConfiguration -		 -

The tablespaces configuration

-
enablePDB
-bool -		 -

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 any -PodDisruptionBudget 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.

-
plugins
-[]PluginConfiguration -		 -

The plugins configuration, containing -any plugin to be loaded with the corresponding configuration

-
probes
-ProbesConfiguration -		 -

The configuration of the probes to be injected -in the PostgreSQL Pods.

-
- -
- -## ClusterStatus - -**Appears in:** - -- [Cluster](#postgresql-k8s-enterprisedb-io-v1-Cluster) - -

ClusterStatus defines the observed state of a PostgreSQL cluster managed by -{{name.ln}}.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
instances
-int -		 -

The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods.

-
readyInstances
-int -		 -

The total number of ready instances in the cluster. It is equal to the number of ready instance pods.

-
instancesStatus
-map[PodStatus][]string -		 -

InstancesStatus indicates in which status the instances are

-
instancesReportedState
-map[PodName]InstanceReportedState -		 -

The reported state of the instances during the last reconciliation loop

-
managedRolesStatus
-ManagedRoles -		 -

ManagedRolesStatus reports the state of the managed roles in the cluster

-
tablespacesStatus
-[]TablespaceState -		 -

TablespacesStatus reports the state of the declarative tablespaces in the cluster

-
timelineID
-int -		 -

The timeline of the Postgres cluster

-
topology
-Topology -		 -

Instances topology.

-
latestGeneratedNode
-int -		 -

ID of the latest generated node (used to avoid node name clashing)

-
currentPrimary
-string -		 -

Current primary instance

-
targetPrimary
-string -		 -

Target primary instance, this is different from the previous one -during a switchover or a failover

-
lastPromotionToken
-string -		 -

LastPromotionToken is the last verified promotion token that -was used to promote a replica cluster

-
pvcCount
-int32 -		 -

How many PVCs have been created by this cluster

-
jobCount
-int32 -		 -

How many Jobs have been created by this cluster

-
danglingPVC
-[]string -		 -

List of all the PVCs created by this cluster and still available -which are not attached to a Pod

-
resizingPVC
-[]string -		 -

List of all the PVCs that have ResizingPVC condition.

-
initializingPVC
-[]string -		 -

List of all the PVCs that are being initialized by this cluster

-
healthyPVC
-[]string -		 -

List of all the PVCs not dangling nor initializing

-
unusablePVC
-[]string -		 -

List of all the PVCs that are unusable because another PVC is missing

-
licenseStatus
-github.com/EnterpriseDB/cloud-native-postgres/pkg/licensekey.Status -		 -

Status of the license

-
writeService
-string -		 -

Current write pod

-
readService
-string -		 -

Current list of read pods

-
phase
-string -		 -

Current phase of the cluster

-
phaseReason
-string -		 -

Reason for the current phase

-
secretsResourceVersion
-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
-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
-CertificatesStatus -		 -

The configuration for the CA and related certificates, initialized with defaults.

-
firstRecoverabilityPoint
-string -		 -

The first recoverability point, stored as a date in RFC3339 format. -This field is calculated from the content of FirstRecoverabilityPointByMethod.

-

Deprecated: the field is not set for backup plugins.

-
firstRecoverabilityPointByMethod
-map[BackupMethod]meta/v1.Time -		 -

The first recoverability point, stored as a date in RFC3339 format, per backup method type.

-

Deprecated: the field is not set for backup plugins.

-
lastSuccessfulBackup
-string -		 -

Last successful backup, stored as a date in RFC3339 format. -This field is calculated from the content of LastSuccessfulBackupByMethod.

-

Deprecated: the field is not set for backup plugins.

-
lastSuccessfulBackupByMethod
-map[BackupMethod]meta/v1.Time -		 -

Last successful backup, stored as a date in RFC3339 format, per backup method type.

-

Deprecated: the field is not set for backup plugins.

-
lastFailedBackup
-string -		 -

Last failed backup, stored as a date in RFC3339 format.

-

Deprecated: the field is not set for backup plugins.

-
cloudNativePostgresqlCommitHash
-string -		 -

The commit hash number of which this operator running

-
currentPrimaryTimestamp
-string -		 -

The timestamp when the last actual promotion to primary has occurred

-
currentPrimaryFailingSinceTimestamp
-string -		 -

The timestamp when the primary was detected to be unhealthy -This field is reported when .spec.failoverDelay is populated or during online upgrades

-
targetPrimaryTimestamp
-string -		 -

The timestamp when the last request for a new primary has occurred

-
poolerIntegrations
-PoolerIntegrations -		 -

The integration needed by poolers referencing the cluster

-
cloudNativePostgresqlOperatorHash
-string -		 -

The hash of the binary of the operator

-
availableArchitectures
-[]AvailableArchitecture -		 -

AvailableArchitectures reports the available architectures of a cluster

-
conditions
-[]meta/v1.Condition -		 -

Conditions for cluster object

-
instanceNames
-[]string -		 -

List of instance names in the cluster

-
onlineUpdateEnabled
-bool -		 -

OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster

-
image
-string -		 -

Image contains the image name used by the pods

-
pgDataImageInfo
-ImageInfo -		 -

PGDataImageInfo contains the details of the latest image that has run on the current data directory.

-
pluginStatus
-[]PluginStatus -		 -

PluginStatus is the status of the loaded plugins

-
switchReplicaClusterStatus
-SwitchReplicaClusterStatus -		 -

SwitchReplicaClusterStatus is the status of the switch to replica cluster

-
demotionToken
-string -		 -

DemotionToken is a JSON token containing the information -from pg_controldata such as Database system identifier, Latest checkpoint's -TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO -WAL file, and Time of latest checkpoint

-
systemID
-string -		 -

SystemID is the latest detected PostgreSQL SystemID

-
- -
- -## ConfigMapResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - -
FieldDescription
metrics
-map[string]string -		 -

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

-
- -
- -## DataDurabilityLevel - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are required or preferred.

- -
- -## DataSource - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage

- - - - - - - - - - - - - - -
FieldDescription
storage [Required]
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage of the instances

-
walStorage
-core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL WAL (Write-Ahead Log)

-
tablespaceStorage
-map[string]core/v1.TypedLocalObjectReference -		 -

Configuration of the storage for PostgreSQL tablespaces

-
- -
- -## DatabaseObjectSpec - -**Appears in:** - -- [ExtensionSpec](#postgresql-k8s-enterprisedb-io-v1-ExtensionSpec) - -- [SchemaSpec](#postgresql-k8s-enterprisedb-io-v1-SchemaSpec) - -

DatabaseObjectSpec contains the fields which are common to every -database object

- - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the extension/schema

-
ensure
-EnsureOption -		 -

Specifies whether an extension/schema should be present or absent in -the database. If set to present, the extension/schema will be -created if it does not exist. If set to absent, the -extension/schema will be removed if it exists.

-
- -
- -## DatabaseObjectStatus - -**Appears in:** - -- [DatabaseStatus](#postgresql-k8s-enterprisedb-io-v1-DatabaseStatus) - -

DatabaseObjectStatus is the status of the managed database objects

- - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the object

-
applied [Required]
-bool -		 -

True of the object has been installed successfully in -the database

-
message
-string -		 -

Message is the object reconciliation message

-
- -
- -## DatabaseReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases.

- -
- -## DatabaseRoleRef - -**Appears in:** - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

DatabaseRoleRef is a reference an a role available inside PostgreSQL

- - - - - - - - -
FieldDescription
name
-string -		 - No description provided.
- -
- -## DatabaseSpec - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseSpec is the specification of a Postgresql Database, built around the -CREATE DATABASE, ALTER DATABASE, and DROP DATABASE SQL commands of -PostgreSQL.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster hosting the database.

-
ensure
-EnsureOption -		 -

Ensure the PostgreSQL database is present or absent - defaults to "present".

-
name [Required]
-string -		 -

The name of the database to create inside PostgreSQL. This setting cannot be changed.

-
owner [Required]
-string -		 -

Maps to the OWNER parameter of CREATE DATABASE. -Maps to the OWNER TO command of ALTER DATABASE. -The role name of the user who owns the database inside PostgreSQL.

-
template
-string -		 -

Maps to the TEMPLATE parameter of CREATE DATABASE. This setting -cannot be changed. The name of the template from which to create -this database.

-
encoding
-string -		 -

Maps to the ENCODING parameter of CREATE DATABASE. This setting -cannot be changed. Character set encoding to use in the database.

-
locale
-string -		 -

Maps to the LOCALE parameter of CREATE DATABASE. This setting -cannot be changed. Sets the default collation order and character -classification in the new database.

-
localeProvider
-string -		 -

Maps to the LOCALE_PROVIDER parameter of CREATE DATABASE. This -setting cannot be changed. This option sets the locale provider for -databases created in the new cluster. Available from PostgreSQL 16.

-
localeCollate
-string -		 -

Maps to the LC_COLLATE parameter of CREATE DATABASE. This -setting cannot be changed.

-
localeCType
-string -		 -

Maps to the LC_CTYPE parameter of CREATE DATABASE. This setting -cannot be changed.

-
icuLocale
-string -		 -

Maps to the ICU_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the ICU locale when the ICU -provider is used. This option requires localeProvider to be set to -icu. Available from PostgreSQL 15.

-
icuRules
-string -		 -

Maps to the ICU_RULES parameter of CREATE DATABASE. This setting -cannot be changed. Specifies additional collation rules to customize -the behavior of the default collation. This option requires -localeProvider to be set to icu. Available from PostgreSQL 16.

-
builtinLocale
-string -		 -

Maps to the BUILTIN_LOCALE parameter of CREATE DATABASE. This -setting cannot be changed. Specifies the locale name when the -builtin provider is used. This option requires localeProvider to -be set to builtin. Available from PostgreSQL 17.

-
collationVersion
-string -		 -

Maps to the COLLATION_VERSION parameter of CREATE DATABASE. This -setting cannot be changed.

-
isTemplate
-bool -		 -

Maps to the IS_TEMPLATE parameter of CREATE DATABASE and ALTER DATABASE. If true, this database is considered a template and can -be cloned by any user with CREATEDB privileges.

-
allowConnections
-bool -		 -

Maps to the ALLOW_CONNECTIONS parameter of CREATE DATABASE and -ALTER DATABASE. If false then no one can connect to this database.

-
connectionLimit
-int -		 -

Maps to the CONNECTION LIMIT clause of CREATE DATABASE and -ALTER DATABASE. How many concurrent connections can be made to -this database. -1 (the default) means no limit.

-
tablespace
-string -		 -

Maps to the TABLESPACE parameter of CREATE DATABASE. -Maps to the SET TABLESPACE command of ALTER DATABASE. -The name of the tablespace (in PostgreSQL) that will be associated -with the new database. This tablespace will be the default -tablespace used for objects created in this database.

-
databaseReclaimPolicy
-DatabaseReclaimPolicy -		 -

The policy for end-of-life maintenance of this database.

-
schemas
-[]SchemaSpec -		 -

The list of schemas to be managed in the database

-
extensions
-[]ExtensionSpec -		 -

The list of extensions to be managed in the database

-
- -
- -## DatabaseStatus - -**Appears in:** - -- [Database](#postgresql-k8s-enterprisedb-io-v1-Database) - -

DatabaseStatus defines the observed state of Database

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the database was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
schemas
-[]DatabaseObjectStatus -		 -

Schemas is the status of the managed schemas

-
extensions
-[]DatabaseObjectStatus -		 -

Extensions is the status of the managed extensions

-
- -
- -## EPASConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

EPASConfiguration contains EDB Postgres Advanced Server specific configurations

- - - - - - - - - - - -
FieldDescription
audit
-bool -		 -

If true enables edb_audit logging

-
tde
-TDEConfiguration -		 -

TDE configuration

-
- -
- -## EmbeddedObjectMetadata - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster

- - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 - No description provided.
annotations
-map[string]string -		 - No description provided.
- -
- -## EnsureOption - -(Alias of `string`) - -**Appears in:** - -- [DatabaseObjectSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseObjectSpec) - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -- [RoleConfiguration](#postgresql-k8s-enterprisedb-io-v1-RoleConfiguration) - -

EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance

- -
- -## EphemeralVolumesSizeLimitConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage

- - - - - - - - - - - -
FieldDescription
shm
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Shm is the size limit of the shared memory volume

-
temporaryData
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

TemporaryData is the size limit of the temporary data volume

-
- -
- -## ExtensionConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

ExtensionConfiguration is the configuration used to add -PostgreSQL extensions to the Cluster.

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the extension, required

-
image [Required]
-core/v1.ImageVolumeSource -		 -

The image containing the extension, required

-
extension_control_path
-[]string -		 -

The list of directories inside the image which should be added to extension_control_path. -If not defined, defaults to "/share".

-
dynamic_library_path
-[]string -		 -

The list of directories inside the image which should be added to dynamic_library_path. -If not defined, defaults to "/lib".

-
ld_library_path
-[]string -		 -

The list of directories inside the image which should be added to ld_library_path.

-
- -
- -## ExtensionSpec - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

ExtensionSpec configures an extension in a database

- - - - - - - - - - - - - - -
FieldDescription
DatabaseObjectSpec
-DatabaseObjectSpec -		(Members of DatabaseObjectSpec are embedded into this type.) -

Common fields

-
version [Required]
-string -		 -

The version of the extension to install. If empty, the operator will -install the default version (whatever is specified in the -extension's control file)

-
schema [Required]
-string -		 -

The name of the schema in which to install the extension's objects, -in case the extension allows its contents to be relocated. If not -specified (default), and the extension's control file does not -specify a schema either, the current default object creation schema -is used.

-
- -
- -## ExternalCluster - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The server name, required

-
connectionParameters
-map[string]string -		 -

The list of connection parameters, such as dbname, host, username, etc

-
sslCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL certificate to be used to connect to this -instance

-
sslKey
-core/v1.SecretKeySelector -		 -

The reference to an SSL private key to be used to connect to this -instance

-
sslRootCert
-core/v1.SecretKeySelector -		 -

The reference to an SSL CA public key to be used to connect to this -instance

-
password
-core/v1.SecretKeySelector -		 -

The reference to the password to be used to connect to the server. -If a password is provided, {{name.ln}} 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.

-
barmanObjectStore
-github.com/cloudnative-pg/barman-cloud/pkg/api.BarmanObjectStoreConfiguration -		 -

The configuration for the barman-cloud tool suite

-
plugin [Required]
-PluginConfiguration -		 -

The configuration of the plugin that is taking care -of WAL archiving and backups for this external cluster

-
- -
- -## FailoverQuorumStatus - -**Appears in:** - -- [FailoverQuorum](#postgresql-k8s-enterprisedb-io-v1-FailoverQuorum) - -

FailoverQuorumStatus is the latest observed status of the failover -quorum of the PG cluster.

- - - - - - - - - - - - - - - - - -
FieldDescription
method
-string -		 -

Contains the latest reported Method value.

-
standbyNames
-[]string -		 -

StandbyNames is the list of potentially synchronous -instance names.

-
standbyNumber
-int -		 -

StandbyNumber is the number of synchronous standbys that transactions -need to wait for replies from.

-
primary
-string -		 -

Primary is the name of the primary instance that updated -this object the latest time.

-
- -
- -## ImageCatalogRef - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ImageCatalogRef defines the reference to a major version in an ImageCatalog

- - - - - - - - - - - -
FieldDescription
TypedLocalObjectReference
-core/v1.TypedLocalObjectReference -		(Members of TypedLocalObjectReference are embedded into this type.) - No description provided.
major [Required]
-int -		 -

The major version of PostgreSQL we want to use from the ImageCatalog

-
- -
- -## ImageCatalogSpec - -**Appears in:** - -- [ClusterImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ClusterImageCatalog) - -- [ImageCatalog](#postgresql-k8s-enterprisedb-io-v1-ImageCatalog) - -

ImageCatalogSpec defines the desired ImageCatalog

- - - - - - - - -
FieldDescription
images [Required]
-[]CatalogImage -		 -

List of CatalogImages available in the catalog

-
- -
- -## ImageInfo - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ImageInfo contains the information about a PostgreSQL image

- - - - - - - - - - - -
FieldDescription
image [Required]
-string -		 -

Image is the image name

-
majorVersion [Required]
-int -		 -

MajorVersion is the major version of the image

-
- -
- -## Import - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

Import contains the configuration to init a database from a logic snapshot of an externalCluster

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
source [Required]
-ImportSource -		 -

The source of the import

-
type [Required]
-SnapshotType -		 -

The import type. Can be microservice or monolith.

-
databases [Required]
-[]string -		 -

The databases to import

-
roles
-[]string -		 -

The roles to import

-
postImportApplicationSQL
-[]string -		 -

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.

-
schemaOnly
-bool -		 -

When set to true, only the pre-data and post-data sections of -pg_restore are invoked, avoiding data import. Default: false.

-
pgDumpExtraOptions
-[]string -		 -

List of custom options to pass to the pg_dump command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
pgRestoreExtraOptions
-[]string -		 -

List of custom options to pass to the pg_restore command. IMPORTANT: -Use these options with caution and at your own risk, as the operator -does not validate their content. Be aware that certain options may -conflict with the operator's intended functionality or design.

-
- -
- -## ImportSource - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

ImportSource describes the source for the logical snapshot

- - - - - - - - -
FieldDescription
externalCluster [Required]
-string -		 -

The name of the externalCluster used for import

-
- -
- -## InstanceID - -**Appears in:** - -- [BackupStatus](#postgresql-k8s-enterprisedb-io-v1-BackupStatus) - -

InstanceID contains the information to identify an instance

- - - - - - - - - - - -
FieldDescription
podName
-string -		 -

The pod name

-
ContainerID
-string -		 -

The container ID

-
- -
- -## InstanceReportedState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

InstanceReportedState describes the last reported state of an instance during a reconciliation loop

- - - - - - - - - - - - - - -
FieldDescription
isPrimary [Required]
-bool -		 -

indicates if an instance is the primary one

-
timeLineID
-int -		 -

indicates on which TimelineId the instance is

-
ip [Required]
-string -		 -

IP address of the instance

-
- -
- -## IsolationCheckConfiguration - -**Appears in:** - -- [LivenessProbe](#postgresql-k8s-enterprisedb-io-v1-LivenessProbe) - -

IsolationCheckConfiguration contains the configuration for the isolation check -functionality in the liveness probe

- - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

Whether primary isolation checking is enabled for the liveness probe

-
requestTimeout
-int -		 -

Timeout in milliseconds for requests during the primary isolation check

-
connectionTimeout
-int -		 -

Timeout in milliseconds for connections during the primary isolation check

-
- -
- -## LDAPBindAsAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP

- - - - - - - - - - - -
FieldDescription
prefix
-string -		 -

Prefix for the bind authentication option

-
suffix
-string -		 -

Suffix for the bind authentication option

-
- -
- -## LDAPBindSearchAuth - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
baseDN
-string -		 -

Root DN to begin the user search

-
bindDN
-string -		 -

DN of the user to bind to the directory

-
bindPassword
-core/v1.SecretKeySelector -		 -

Secret with the password for the user to bind to the directory

-
searchAttribute
-string -		 -

Attribute to match against the username

-
searchFilter
-string -		 -

Search filter to use when doing the search+bind authentication

-
- -
- -## LDAPConfig - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

LDAPConfig contains the parameters needed for LDAP authentication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
server
-string -		 -

LDAP hostname or IP address

-
port
-int -		 -

LDAP server port

-
scheme
-LDAPScheme -		 -

LDAP schema to be used, possible options are ldap and ldaps

-
bindAsAuth
-LDAPBindAsAuth -		 -

Bind as authentication configuration

-
bindSearchAuth
-LDAPBindSearchAuth -		 -

Bind+Search authentication configuration

-
tls
-bool -		 -

Set to 'true' to enable LDAP over TLS. 'false' is default

-
- -
- -## LDAPScheme - -(Alias of `string`) - -**Appears in:** - -- [LDAPConfig](#postgresql-k8s-enterprisedb-io-v1-LDAPConfig) - -

LDAPScheme defines the possible schemes for LDAP

- -
- -## LivenessProbe - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

LivenessProbe is the configuration of the liveness probe

- - - - - - - - - - - -
FieldDescription
Probe
-Probe -		(Members of Probe are embedded into this type.) -

Probe is the standard probe configuration

-
isolationCheck
-IsolationCheckConfiguration -		 -

Configure the feature that extends the liveness probe for a primary -instance. In addition to the basic checks, this verifies whether the -primary is isolated from the Kubernetes API server and from its -replicas, ensuring that it can be safely shut down if network -partition or API unavailability is detected. Enabled by default.

-
- -
- -## ManagedConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager

- - - - - - - - - - - -
FieldDescription
roles
-[]RoleConfiguration -		 -

Database roles managed by the Cluster

-
services
-ManagedServices -		 -

Services roles managed by the Cluster

-
- -
- -## ManagedRoles - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

ManagedRoles tracks the status of a cluster's managed roles

- - - - - - - - - - - - - - -
FieldDescription
byStatus
-map[RoleStatus][]string -		 -

ByStatus gives the list of roles in each state

-
cannotReconcile
-map[string][]string -		 -

CannotReconcile lists roles that cannot be reconciled in PostgreSQL, -with an explanation of the cause

-
passwordStatus
-map[string]PasswordState -		 -

PasswordStatus gives the last transaction id and password secret version for each managed role

-
- -
- -## ManagedService - -**Appears in:** - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification.

- - - - - - - - - - - - - - -
FieldDescription
selectorType [Required]
-ServiceSelectorType -		 -

SelectorType specifies the type of selectors that the service will have. -Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.

-
updateStrategy
-ServiceUpdateStrategy -		 -

UpdateStrategy describes how the service differences should be reconciled

-
serviceTemplate [Required]
-ServiceTemplateSpec -		 -

ServiceTemplate is the template specification for the service.

-
- -
- -## ManagedServices - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

ManagedServices represents the services managed by the cluster.

- - - - - - - - - - - -
FieldDescription
disabledDefaultServices
-[]ServiceSelectorType -		 -

DisabledDefaultServices is a list of service types that are disabled by default. -Valid values are "r", and "ro", representing read, and read-only services.

-
additional
-[]ManagedService -		 -

Additional is a list of additional managed services specified by the user.

-
- -
- -## Metadata - -**Appears in:** - -- [PodTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-PodTemplateSpec) - -- [ServiceAccountTemplate](#postgresql-k8s-enterprisedb-io-v1-ServiceAccountTemplate) - -- [ServiceTemplateSpec](#postgresql-k8s-enterprisedb-io-v1-ServiceTemplateSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the resource. Only supported for certain types

-
labels
-map[string]string -		 -

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
-map[string]string -		 -

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

-
- -
- -## MonitoringConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
disableDefaultQueries
-bool -		 -

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.

-
customQueriesConfigMap
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

The list of config maps containing the custom queries

-
customQueriesSecret
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

The list of secrets containing the custom queries

-
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-

Deprecated: This feature will be removed in an upcoming release. If -you need this functionality, you can create a PodMonitor manually.

-
tls
-ClusterMonitoringTLSConfiguration -		 -

Configure TLS communication for the metrics endpoint. -Changing tls.enabled option will force a rollout of all instances.

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-

Deprecated: This feature will be removed in an upcoming release. If -you need this functionality, you can create a PodMonitor manually.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-

Deprecated: This feature will be removed in an upcoming release. If -you need this functionality, you can create a PodMonitor manually.

-
- -
- -## NodeMaintenanceWindow - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

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.

- - - - - - - - - - - -
FieldDescription
reusePVC
-bool -		 -

Reuse the existing PVC (wait for the node to come -up again) or not (recreate it elsewhere - when instances >1)

-
inProgress
-bool -		 -

Is there a node maintenance activity in progress?

-
- -
- -## OnlineConfiguration - -**Appears in:** - -- [BackupSpec](#postgresql-k8s-enterprisedb-io-v1-BackupSpec) - -- [ScheduledBackupSpec](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackupSpec) - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

OnlineConfiguration contains the configuration parameters for the online volume snapshot

- - - - - - - - - - - -
FieldDescription
waitForArchive
-bool -		 -

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.

-
immediateCheckpoint
-bool -		 -

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.

-
- -
- -## PasswordState - -**Appears in:** - -- [ManagedRoles](#postgresql-k8s-enterprisedb-io-v1-ManagedRoles) - -

PasswordState represents the state of the password of a managed RoleConfiguration

- - - - - - - - - - - -
FieldDescription
transactionID
-int64 -		 -

the last transaction ID to affect the role definition in PostgreSQL

-
resourceVersion
-string -		 -

the resource version of the password secret

-
- -
- -## PgBouncerIntegrationStatus - -**Appears in:** - -- [PoolerIntegrations](#postgresql-k8s-enterprisedb-io-v1-PoolerIntegrations) - -

PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster

- - - - - - - - -
FieldDescription
secrets
-[]string -		 - No description provided.
- -
- -## PgBouncerPoolMode - -(Alias of `string`) - -**Appears in:** - -- [PgBouncerSpec](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSpec) - -

PgBouncerPoolMode is the mode of PgBouncer

- -
- -## PgBouncerSecrets - -**Appears in:** - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

PgBouncerSecrets contains the versions of the secrets used -by pgbouncer

- - - - - - - - -
FieldDescription
authQuery
-SecretVersion -		 -

The auth query secret version

-
- -
- -## PgBouncerSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PgBouncerSpec defines how to configure PgBouncer

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
poolMode
-PgBouncerPoolMode -		 -

The pool mode. Default: session.

-
authQuerySecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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.

-
authQuery
-string -		 -

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.

-
parameters
-map[string]string -		 -

Additional parameters to be passed to PgBouncer - please check -the CNP documentation for a list of options you can configure

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
paused
-bool -		 -

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.

-
- -
- -## PluginConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [ExternalCluster](#postgresql-k8s-enterprisedb-io-v1-ExternalCluster) - -

PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the plugin name

-
enabled
-bool -		 -

Enabled is true if this plugin will be used

-
isWALArchiver
-bool -		 -

Marks the plugin as the WAL archiver. At most one plugin can be -designated as a WAL archiver. This cannot be enabled if the -.spec.backup.barmanObjectStore configuration is present.

-
parameters
-map[string]string -		 -

Parameters is the configuration of the plugin

-
- -
- -## PluginStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PluginStatus is the status of a loaded plugin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the plugin

-
version [Required]
-string -		 -

Version is the version of the plugin loaded by the -latest reconciliation loop

-
capabilities
-[]string -		 -

Capabilities are the list of capabilities of the -plugin

-
operatorCapabilities
-[]string -		 -

OperatorCapabilities are the list of capabilities of the -plugin regarding the reconciler

-
walCapabilities
-[]string -		 -

WALCapabilities are the list of capabilities of the -plugin regarding the WAL management

-
backupCapabilities
-[]string -		 -

BackupCapabilities are the list of capabilities of the -plugin regarding the Backup management

-
restoreJobHookCapabilities
-[]string -		 -

RestoreJobHookCapabilities are the list of capabilities of the -plugin regarding the RestoreJobHook management

-
status
-string -		 -

Status contain the status reported by the plugin through the SetStatusInCluster interface

-
- -
- -## PodTemplateSpec - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.PodSpec -		 -

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

-
- -
- -## PodTopologyLabels - -(Alias of `map[string]string`) - -**Appears in:** - -- [Topology](#postgresql-k8s-enterprisedb-io-v1-Topology) - -

PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue

- -
- -## PoolerIntegrations - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster

- - - - - - - - -
FieldDescription
pgBouncerIntegration
-PgBouncerIntegrationStatus -		 - No description provided.
- -
- -## PoolerMonitoringConfiguration - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enablePodMonitor
-bool -		 -

Enable or disable the PodMonitor

-
podMonitorMetricRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.

-
podMonitorRelabelings
-[]github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1.RelabelConfig -		 -

The list of relabelings for the PodMonitor. Applied to samples before scraping.

-
- -
- -## PoolerSecrets - -**Appears in:** - -- [PoolerStatus](#postgresql-k8s-enterprisedb-io-v1-PoolerStatus) - -

PoolerSecrets contains the versions of all the secrets used

- - - - - - - - - - - - - - - - - -
FieldDescription
serverTLS
-SecretVersion -		 -

The server TLS secret version

-
serverCA
-SecretVersion -		 -

The server CA secret version

-
clientCA
-SecretVersion -		 -

The client CA secret version

-
pgBouncerSecrets
-PgBouncerSecrets -		 -

The version of the secrets used by PgBouncer

-
- -
- -## PoolerSpec - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerSpec defines the desired state of Pooler

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

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
-PoolerType -		 -

Type of service to forward traffic to. Default: rw.

-
instances
-int32 -		 -

The number of replicas we want. Default: 1.

-
template
-PodTemplateSpec -		 -

The template of the Pod to be created

-
pgbouncer [Required]
-PgBouncerSpec -		 -

The PgBouncer configuration

-
deploymentStrategy
-apps/v1.DeploymentStrategy -		 -

The deployment strategy to use for pgbouncer to replace existing pods with new ones

-
monitoring
-PoolerMonitoringConfiguration -		 -

The configuration of the monitoring infrastructure of this pooler.

-

Deprecated: This feature will be removed in an upcoming release. If -you need this functionality, you can create a PodMonitor manually.

-
serviceTemplate
-ServiceTemplateSpec -		 -

Template for the Service to be created

-
- -
- -## PoolerStatus - -**Appears in:** - -- [Pooler](#postgresql-k8s-enterprisedb-io-v1-Pooler) - -

PoolerStatus defines the observed state of Pooler

- - - - - - - - - - - -
FieldDescription
secrets
-PoolerSecrets -		 -

The resource version of the config object

-
instances
-int32 -		 -

The number of pods trying to be scheduled

-
- -
- -## PoolerType - -(Alias of `string`) - -**Appears in:** - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are rw and ro.

- -
- -## PostgresConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PostgresConfiguration defines the PostgreSQL configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
parameters
-map[string]string -		 -

PostgreSQL configuration options (postgresql.conf)

-
synchronous
-SynchronousReplicaConfiguration -		 -

Configuration of the PostgreSQL synchronous replication feature

-
pg_hba
-[]string -		 -

PostgreSQL Host Based Authentication rules (lines to be appended -to the pg_hba.conf file)

-
pg_ident
-[]string -		 -

PostgreSQL User Name Maps rules (lines to be appended -to the pg_ident.conf file)

-
epas
-EPASConfiguration -		 -

EDB Postgres Advanced Server specific configurations

-
syncReplicaElectionConstraint
-SyncReplicaElectionConstraints -		 -

Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be -set up.

-
shared_preload_libraries
-[]string -		 -

Lists of shared preload libraries to add to the default ones

-
ldap
-LDAPConfig -		 -

Options to specify LDAP configuration

-
promotionTimeout
-int32 -		 -

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

-
enableAlterSystem
-bool -		 -

If this parameter is true, the user will be able to invoke ALTER SYSTEM -on this {{name.ln}} Cluster. -This should only be used for debugging and troubleshooting. -Defaults to false.

-
extensions
-[]ExtensionConfiguration -		 -

The configuration of the extensions to be added

-
- -
- -## PrimaryUpdateMethod - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## PrimaryUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates

- -
- -## Probe - -**Appears in:** - -- [LivenessProbe](#postgresql-k8s-enterprisedb-io-v1-LivenessProbe) - -- [ProbeWithStrategy](#postgresql-k8s-enterprisedb-io-v1-ProbeWithStrategy) - -

Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
initialDelaySeconds
-int32 -		 -

Number of seconds after the container has started before liveness probes are initiated. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
timeoutSeconds
-int32 -		 -

Number of seconds after which the probe times out. -Defaults to 1 second. Minimum value is 1. -More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes

-
periodSeconds
-int32 -		 -

How often (in seconds) to perform the probe. -Default to 10 seconds. Minimum value is 1.

-
successThreshold
-int32 -		 -

Minimum consecutive successes for the probe to be considered successful after having failed. -Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.

-
failureThreshold
-int32 -		 -

Minimum consecutive failures for the probe to be considered failed after having succeeded. -Defaults to 3. Minimum value is 1.

-
terminationGracePeriodSeconds
-int64 -		 -

Optional duration in seconds the pod needs to terminate gracefully upon probe failure. -The grace period is the duration in seconds after the processes running in the pod are sent -a termination signal and the time when the processes are forcibly halted with a kill signal. -Set this value longer than the expected cleanup time for your process. -If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this -value overrides the value provided by the pod spec. -Value must be non-negative integer. The value zero indicates stop immediately via -the kill signal (no opportunity to shut down). -This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. -Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.

-
- -
- -## ProbeStrategyType - -(Alias of `string`) - -**Appears in:** - -- [ProbeWithStrategy](#postgresql-k8s-enterprisedb-io-v1-ProbeWithStrategy) - -

ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready

- -
- -## ProbeWithStrategy - -**Appears in:** - -- [ProbesConfiguration](#postgresql-k8s-enterprisedb-io-v1-ProbesConfiguration) - -

ProbeWithStrategy is the configuration of the startup probe

- - - - - - - - - - - - - - -
FieldDescription
Probe
-Probe -		(Members of Probe are embedded into this type.) -

Probe is the standard probe configuration

-
type
-ProbeStrategyType -		 -

The probe strategy

-
maximumLag
-k8s.io/apimachinery/pkg/api/resource.Quantity -		 -

Lag limit. Used only for streaming strategy

-
- -
- -## ProbesConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods

- - - - - - - - - - - - - - -
FieldDescription
startup [Required]
-ProbeWithStrategy -		 -

The startup probe configuration

-
liveness [Required]
-LivenessProbe -		 -

The liveness probe configuration

-
readiness [Required]
-ProbeWithStrategy -		 -

The readiness probe configuration

-
- -
- -## PublicationReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications.

- -
- -## PublicationSpec - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationSpec defines the desired state of Publication

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "publisher"

-
name [Required]
-string -		 -

The name of the publication inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "publisher" cluster

-
parameters
-map[string]string -		 -

Publication parameters part of the WITH clause as expected by -PostgreSQL CREATE PUBLICATION command

-
target [Required]
-PublicationTarget -		 -

Target of the publication as expected by PostgreSQL CREATE PUBLICATION command

-
publicationReclaimPolicy
-PublicationReclaimPolicy -		 -

The policy for end-of-life maintenance of this publication

-
- -
- -## PublicationStatus - -**Appears in:** - -- [Publication](#postgresql-k8s-enterprisedb-io-v1-Publication) - -

PublicationStatus defines the observed state of Publication

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the publication was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## PublicationTarget - -**Appears in:** - -- [PublicationSpec](#postgresql-k8s-enterprisedb-io-v1-PublicationSpec) - -

PublicationTarget is what this publication should publish

- - - - - - - - - - - -
FieldDescription
allTables
-bool -		 -

Marks the publication as one that replicates changes for all tables -in the database, including tables created in the future. -Corresponding to FOR ALL TABLES in PostgreSQL.

-
objects
-[]PublicationTargetObject -		 -

Just the following schema objects

-
- -
- -## PublicationTargetObject - -**Appears in:** - -- [PublicationTarget](#postgresql-k8s-enterprisedb-io-v1-PublicationTarget) - -

PublicationTargetObject is an object to publish

- - - - - - - - - - - -
FieldDescription
tablesInSchema
-string -		 -

Marks the publication as one that replicates changes for all tables -in the specified list of schemas, including tables created in the -future. Corresponding to FOR TABLES IN SCHEMA in PostgreSQL.

-
table
-PublicationTargetTable -		 -

Specifies a list of tables to add to the publication. Corresponding -to FOR TABLE in PostgreSQL.

-
- -
- -## PublicationTargetTable - -**Appears in:** - -- [PublicationTargetObject](#postgresql-k8s-enterprisedb-io-v1-PublicationTargetObject) - -

PublicationTargetTable is a table to publish

- - - - - - - - - - - - - - - - - -
FieldDescription
only
-bool -		 -

Whether to limit to the table only or include all its descendants

-
name [Required]
-string -		 -

The table name

-
schema
-string -		 -

The schema name

-
columns
-[]string -		 -

The columns to publish

-
- -
- -## RecoveryTarget - -**Appears in:** - -- [BootstrapRecovery](#postgresql-k8s-enterprisedb-io-v1-BootstrapRecovery) - -

RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
backupID
-string -		 -

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.

-
targetTLI
-string -		 -

The target timeline ("latest" or a positive integer)

-
targetXID
-string -		 -

The target transaction ID

-
targetName
-string -		 -

The target name (to be previously created -with pg_create_restore_point)

-
targetLSN
-string -		 -

The target LSN (Log Sequence Number)

-
targetTime
-string -		 -

The target time as a timestamp in the RFC3339 standard

-
targetImmediate
-bool -		 -

End recovery as soon as a consistent state is reached

-
exclusive
-bool -		 -

Set the target to be exclusive. If omitted, defaults to false, so that -in Postgres, recovery_target_inclusive will be true

-
- -
- -## ReplicaClusterConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
self
-string -		 -

Self defines the name of this cluster. It is used to determine if this is a primary -or a replica cluster, comparing it with primary

-
primary
-string -		 -

Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the -topology specified in externalClusters

-
source [Required]
-string -		 -

The name of the external cluster which is the replication origin

-
enabled
-bool -		 -

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.

-
promotionToken
-string -		 -

A demotion token generated by an external cluster used to -check if the promotion requirements are met.

-
minApplyDelay
-meta/v1.Duration -		 -

When replica mode is enabled, this parameter allows you to replay -transactions only when the system time is at least the configured -time past the commit time. This provides an opportunity to correct -data loss errors. Note that when this parameter is set, a promotion -token cannot be used.

-
- -
- -## ReplicationSlotsConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ReplicationSlotsConfiguration encapsulates the configuration -of replication slots

- - - - - - - - - - - - - - -
FieldDescription
highAvailability
-ReplicationSlotsHAConfiguration -		 -

Replication slots for high availability configuration

-
updateInterval
-int -		 -

Standby will update the status of the local replication slots -every updateInterval seconds (default 30).

-
synchronizeReplicas
-SynchronizeReplicasConfiguration -		 -

Configures the synchronization of the user defined physical replication slots

-
- -
- -## ReplicationSlotsHAConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

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.

- - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

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.

-
slotPrefix
-string -		 -

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_.

-
synchronizeLogicalDecoding
-bool -		 -

When enabled, the operator automatically manages synchronization of logical -decoding (replication) slots across high-availability clusters.

-

Requires one of the following conditions:

-
    -
  • PostgreSQL version 17 or later
    • -
  • PostgreSQL version < 17 with pg_failover_slots extension enabled
    • -
-
- -
- -## RoleConfiguration - -**Appears in:** - -- [ManagedConfiguration](#postgresql-k8s-enterprisedb-io-v1-ManagedConfiguration) - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name of the role

-
comment
-string -		 -

Description of the role

-
ensure
-EnsureOption -		 -

Ensure the role is present or absent - defaults to "present"

-
passwordSecret
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

Secret containing the password of the role (if present) -If null, the password will be ignored unless DisablePassword is set

-
connectionLimit
-int64 -		 -

If the role can log in, this specifies how many concurrent -connections the role can make. -1 (the default) means no limit.

-
validUntil
-meta/v1.Time -		 -

Date and time after which the role's password is no longer valid. -When omitted, the password will never expire (default).

-
inRoles
-[]string -		 -

List of one or more existing roles to which this role will be -immediately added as a new member. Default empty.

-
inherit
-bool -		 -

Whether a role "inherits" the privileges of roles it is a member of. -Defaults is true.

-
disablePassword
-bool -		 -

DisablePassword indicates that a role's password should be set to NULL in Postgres

-
superuser
-bool -		 -

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.

-
createdb
-bool -		 -

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.

-
createrole
-bool -		 -

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.

-
login
-bool -		 -

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.

-
replication
-bool -		 -

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.

-
bypassrls
-bool -		 -

Whether a role bypasses every row-level security (RLS) policy. -Default is false.

-
- -
- -## SQLRefs - -**Appears in:** - -- [BootstrapInitDB](#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB) - -

SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays.

- - - - - - - - - - - -
FieldDescription
secretRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.SecretKeySelector -		 -

SecretRefs holds a list of references to Secrets

-
configMapRefs
-[]github.com/cloudnative-pg/machinery/pkg/api.ConfigMapKeySelector -		 -

ConfigMapRefs holds a list of references to ConfigMaps

-
- -
- -## ScheduledBackupSpec - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupSpec defines the desired state of ScheduledBackup

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
suspend
-bool -		 -

If this backup is suspended or not

-
immediate
-bool -		 -

If the first backup has to be immediately start after creation or not

-
schedule [Required]
-string -		 -

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

-
cluster [Required]
-github.com/cloudnative-pg/machinery/pkg/api.LocalObjectReference -		 -

The cluster to backup

-
backupOwnerReference
-string -		 -

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
    • -
-
target
-BackupTarget -		 -

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.

-
method
-BackupMethod -		 -

The backup method to be used, possible options are barmanObjectStore, -volumeSnapshot or plugin. Defaults to: barmanObjectStore.

-
pluginConfiguration
-BackupPluginConfiguration -		 -

Configuration parameters passed to the plugin managing this backup

-
online
-bool -		 -

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'

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots -Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza

-
- -
- -## ScheduledBackupStatus - -**Appears in:** - -- [ScheduledBackup](#postgresql-k8s-enterprisedb-io-v1-ScheduledBackup) - -

ScheduledBackupStatus defines the observed state of ScheduledBackup

- - - - - - - - - - - - - - -
FieldDescription
lastCheckTime
-meta/v1.Time -		 -

The latest time the schedule

-
lastScheduleTime
-meta/v1.Time -		 -

Information when was the last time that backup was successfully scheduled.

-
nextScheduleTime
-meta/v1.Time -		 -

Next time we will run a backup

-
- -
- -## SchemaSpec - -**Appears in:** - -- [DatabaseSpec](#postgresql-k8s-enterprisedb-io-v1-DatabaseSpec) - -

SchemaSpec configures a schema in a database

- - - - - - - - - - - -
FieldDescription
DatabaseObjectSpec
-DatabaseObjectSpec -		(Members of DatabaseObjectSpec are embedded into this type.) -

Common fields

-
owner [Required]
-string -		 -

The role name of the user who owns the schema inside PostgreSQL. -It maps to the AUTHORIZATION parameter of CREATE SCHEMA and the -OWNER TO command of ALTER SCHEMA.

-
- -
- -## SecretVersion - -**Appears in:** - -- [PgBouncerSecrets](#postgresql-k8s-enterprisedb-io-v1-PgBouncerSecrets) - -- [PoolerSecrets](#postgresql-k8s-enterprisedb-io-v1-PoolerSecrets) - -

SecretVersion contains a secret name and its ResourceVersion

- - - - - - - - - - - -
FieldDescription
name
-string -		 -

The name of the secret

-
version
-string -		 -

The ResourceVersion of the secret

-
- -
- -## SecretsResourceVersion - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SecretsResourceVersion is the resource versions of the secrets -managed by the operator

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
superuserSecretVersion
-string -		 -

The resource version of the "postgres" user secret

-
replicationSecretVersion
-string -		 -

The resource version of the "streaming_replica" user secret

-
applicationSecretVersion
-string -		 -

The resource version of the "app" user secret

-
managedRoleSecretVersion
-map[string]string -		 -

The resource versions of the managed roles secrets

-
caSecretVersion
-string -		 -

Unused. Retained for compatibility with old versions.

-
clientCaSecretVersion
-string -		 -

The resource version of the PostgreSQL client-side CA secret version

-
serverCaSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side CA secret version

-
serverSecretVersion
-string -		 -

The resource version of the PostgreSQL server-side secret version

-
barmanEndpointCA
-string -		 -

The resource version of the Barman Endpoint CA if provided

-
externalClusterSecretVersion
-map[string]string -		 -

The resource versions of the external cluster secrets

-
metrics
-map[string]string -		 -

A map with the versions of all the secrets used to pass metrics. -Map keys are the secret names, map values are the versions

-
- -
- -## ServiceAccountTemplate - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

ServiceAccountTemplate contains the template needed to generate the service accounts

- - - - - - - - -
FieldDescription
metadata [Required]
-Metadata -		 -

Metadata are the metadata to be used for the generated -service account

-
- -
- -## ServiceSelectorType - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [ManagedServices](#postgresql-k8s-enterprisedb-io-v1-ManagedServices) - -

ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only

- -
- -## ServiceTemplateSpec - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -- [PoolerSpec](#postgresql-k8s-enterprisedb-io-v1-PoolerSpec) - -

ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation.

- - - - - - - - - - - -
FieldDescription
metadata
-Metadata -		 -

Standard object's metadata. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

-
spec
-core/v1.ServiceSpec -		 -

Specification of the desired behavior of the service. -More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

-
- -
- -## ServiceUpdateStrategy - -(Alias of `string`) - -**Appears in:** - -- [ManagedService](#postgresql-k8s-enterprisedb-io-v1-ManagedService) - -

ServiceUpdateStrategy describes how the changes to the managed service should be handled

- -
- -## SnapshotOwnerReference - -(Alias of `string`) - -**Appears in:** - -- [VolumeSnapshotConfiguration](#postgresql-k8s-enterprisedb-io-v1-VolumeSnapshotConfiguration) - -

SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to.

- -
- -## SnapshotType - -(Alias of `string`) - -**Appears in:** - -- [Import](#postgresql-k8s-enterprisedb-io-v1-Import) - -

SnapshotType is a type of allowed import

- -
- -## StorageConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -- [TablespaceConfiguration](#postgresql-k8s-enterprisedb-io-v1-TablespaceConfiguration) - -

StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces

- - - - - - - - - - - - - - - - - -
FieldDescription
storageClass
-string -		 -

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
-string -		 -

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.

-
resizeInUseVolumes
-bool -		 -

Resize existent PVCs, defaults to true

-
pvcTemplate
-core/v1.PersistentVolumeClaimSpec -		 -

Template to be used to generate the Persistent Volume Claim

-
- -
- -## SubscriptionReclaimPolicy - -(Alias of `string`) - -**Appears in:** - -- [SubscriptionSpec](#postgresql-k8s-enterprisedb-io-v1-SubscriptionSpec) - -

SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions.

- -
- -## SubscriptionSpec - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionSpec defines the desired state of Subscription

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
cluster [Required]
-core/v1.LocalObjectReference -		 -

The name of the PostgreSQL cluster that identifies the "subscriber"

-
name [Required]
-string -		 -

The name of the subscription inside PostgreSQL

-
dbname [Required]
-string -		 -

The name of the database where the publication will be installed in -the "subscriber" cluster

-
parameters
-map[string]string -		 -

Subscription parameters included in the WITH clause of the PostgreSQL -CREATE SUBSCRIPTION command. Most parameters cannot be changed -after the subscription is created and will be ignored if modified -later, except for a limited set documented at: -https://www.postgresql.org/docs/current/sql-altersubscription.html#SQL-ALTERSUBSCRIPTION-PARAMS-SET

-
publicationName [Required]
-string -		 -

The name of the publication inside the PostgreSQL database in the -"publisher"

-
publicationDBName
-string -		 -

The name of the database containing the publication on the external -cluster. Defaults to the one in the external cluster definition.

-
externalClusterName [Required]
-string -		 -

The name of the external cluster with the publication ("publisher")

-
subscriptionReclaimPolicy
-SubscriptionReclaimPolicy -		 -

The policy for end-of-life maintenance of this subscription

-
- -
- -## SubscriptionStatus - -**Appears in:** - -- [Subscription](#postgresql-k8s-enterprisedb-io-v1-Subscription) - -

SubscriptionStatus defines the observed state of Subscription

- - - - - - - - - - - - - - -
FieldDescription
observedGeneration
-int64 -		 -

A sequence number representing the latest -desired state that was synchronized

-
applied
-bool -		 -

Applied is true if the subscription was reconciled correctly

-
message
-string -		 -

Message is the reconciliation output message

-
- -
- -## SwitchReplicaClusterStatus - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster

- - - - - - - - -
FieldDescription
inProgress
-bool -		 -

InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster.

-
- -
- -## SyncReplicaElectionConstraints - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

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.

- - - - - - - - - - - -
FieldDescription
nodeLabelsAntiAffinity
-[]string -		 -

A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not

-
enabled [Required]
-bool -		 -

This flag enables the constraints for sync replicas

-
- -
- -## SynchronizeReplicasConfiguration - -**Appears in:** - -- [ReplicationSlotsConfiguration](#postgresql-k8s-enterprisedb-io-v1-ReplicationSlotsConfiguration) - -

SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots

- - - - - - - - - - - -
FieldDescription
enabled [Required]
-bool -		 -

When set to true, every replication slot that is on the primary is synchronized on each standby

-
excludePatterns
-[]string -		 -

List of regular expression patterns to match the names of replication slots to be excluded (by default empty)

-
- -
- -## SynchronousReplicaConfiguration - -**Appears in:** - -- [PostgresConfiguration](#postgresql-k8s-enterprisedb-io-v1-PostgresConfiguration) - -

SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also .spec.minSyncReplicas and .spec.maxSyncReplicas -need to be considered.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
method [Required]
-SynchronousReplicaConfigurationMethod -		 -

Method to select synchronous replication standbys from the listed -servers, accepting 'any' (quorum-based synchronous replication) or -'first' (priority-based synchronous replication) as values.

-
number [Required]
-int -		 -

Specifies the number of synchronous standby servers that -transactions must wait for responses from.

-
maxStandbyNamesFromCluster
-int -		 -

Specifies the maximum number of local cluster pods that can be -automatically included in the synchronous_standby_names option in -PostgreSQL.

-
standbyNamesPre
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names before local cluster pods (the order is -only useful for priority-based synchronous replication).

-
standbyNamesPost
-[]string -		 -

A user-defined list of application names to be added to -synchronous_standby_names after local cluster pods (the order is -only useful for priority-based synchronous replication).

-
dataDurability
-DataDurabilityLevel -		 -

If set to "required", data durability is strictly enforced. Write operations -with synchronous commit settings (on, remote_write, or remote_apply) will -block if there are insufficient healthy replicas, ensuring data persistence. -If set to "preferred", data durability is maintained when healthy replicas -are available, but the required number of instances will adjust dynamically -if replicas become unavailable. This setting relaxes strict durability enforcement -to allow for operational continuity. This setting is only applicable if both -standbyNamesPre and standbyNamesPost are unset (empty).

-
- -
- -## SynchronousReplicaConfigurationMethod - -(Alias of `string`) - -**Appears in:** - -- [SynchronousReplicaConfiguration](#postgresql-k8s-enterprisedb-io-v1-SynchronousReplicaConfiguration) - -

SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list

- -
- -## TDEConfiguration - -**Appears in:** - -- [EPASConfiguration](#postgresql-k8s-enterprisedb-io-v1-EPASConfiguration) - -

TDEConfiguration contains the Transparent Data Encryption configuration

- - - - - - - - - - - - - - - - - - - - -
FieldDescription
enabled
-bool -		 -

True if we want to have TDE enabled

-
secretKeyRef
-core/v1.SecretKeySelector -		 -

Reference to the secret that contains the encryption key

-
wrapCommand
-core/v1.SecretKeySelector -		 -

WrapCommand is the encrypt command provided by the user

-
unwrapCommand
-core/v1.SecretKeySelector -		 -

UnwrapCommand is the decryption command provided by the user

-
passphraseCommand
-core/v1.SecretKeySelector -		 -

PassphraseCommand is the command executed to get the passphrase that will be -passed to the OpenSSL command to encrypt and decrypt

-
- -
- -## TablespaceConfiguration - -**Appears in:** - -- [ClusterSpec](#postgresql-k8s-enterprisedb-io-v1-ClusterSpec) - -

TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

The name of the tablespace

-
storage [Required]
-StorageConfiguration -		 -

The storage configuration for the tablespace

-
owner
-DatabaseRoleRef -		 -

Owner is the PostgreSQL user owning the tablespace

-
temporary
-bool -		 -

When set to true, the tablespace will be added as a temp_tablespaces -entry 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.

-
- -
- -## TablespaceState - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

TablespaceState represents the state of a tablespace in a cluster

- - - - - - - - - - - - - - - - - -
FieldDescription
name [Required]
-string -		 -

Name is the name of the tablespace

-
owner
-string -		 -

Owner is the PostgreSQL user owning the tablespace

-
state [Required]
-TablespaceStatus -		 -

State is the latest reconciliation state

-
error
-string -		 -

Error is the reconciliation error, if any

-
- -
- -## TablespaceStatus - -(Alias of `string`) - -**Appears in:** - -- [TablespaceState](#postgresql-k8s-enterprisedb-io-v1-TablespaceState) - -

TablespaceStatus represents the status of a tablespace in the cluster

- -
- -## Topology - -**Appears in:** - -- [ClusterStatus](#postgresql-k8s-enterprisedb-io-v1-ClusterStatus) - -

Topology contains the cluster topology

- - - - - - - - - - - - - - -
FieldDescription
instances
-map[PodName]PodTopologyLabels -		 -

Instances contains the pod topology of the instances

-
nodesUsed
-int32 -		 -

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
-bool -		 -

SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors -in synchronous replica election in case of failures

-
- -
- -## VolumeSnapshotConfiguration - -**Appears in:** - -- [BackupConfiguration](#postgresql-k8s-enterprisedb-io-v1-BackupConfiguration) - -

VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription
labels
-map[string]string -		 -

Labels are key-value pairs that will be added to .metadata.labels snapshot resources.

-
annotations
-map[string]string -		 -

Annotations key-value pairs that will be added to .metadata.annotations snapshot resources.

-
className
-string -		 -

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
-string -		 -

WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim.

-
tablespaceClassName
-map[string]string -		 -

TablespaceClassName specifies the Snapshot Class to be used for the tablespaces. -defaults to the PGDATA Snapshot Class, if set

-
snapshotOwnerReference
-SnapshotOwnerReference -		 -

SnapshotOwnerReference indicates the type of owner reference the snapshot should have

-
online
-bool -		 -

Whether the default type of backup with volume snapshots is -online/hot (true, default) or offline/cold (false)

-
onlineConfiguration
-OnlineConfiguration -		 -

Configuration parameters to control the online/hot backup with volume snapshots

-
diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.28.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.28.0.mdx deleted file mode 100644 index 88247ccccd4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.28.0.mdx +++ /dev/null @@ -1,2349 +0,0 @@ ---- -title: API Reference - v1.28.0 -navTitle: v1.28.0 -pdfExclude: 'true' - ---- - -## Packages - -- [postgresql.k8s.enterprisedb.io/v1](#postgresqlk8senterprisedbiov1) - -## postgresql.k8s.enterprisedb.io/v1 - -Package v1 contains API Schema definitions for the postgresql v1 API group - -### Resource Types - -- [Backup](#backup) -- [Cluster](#cluster) -- [ClusterImageCatalog](#clusterimagecatalog) -- [Database](#database) -- [FailoverQuorum](#failoverquorum) -- [ImageCatalog](#imagecatalog) -- [Pooler](#pooler) -- [Publication](#publication) -- [ScheduledBackup](#scheduledbackup) -- [Subscription](#subscription) - -#### AffinityConfiguration - -AffinityConfiguration contains the info we need to create the -affinity rules for Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `enablePodAntiAffinity` *boolean* | Activates anti-affinity for the pods. The operator will define pods
anti-affinity unless this field is explicitly set to false | | | | -| `topologyKey` *string* | TopologyKey to use for anti-affinity configuration. See k8s documentation
for more info on that | | | | -| `nodeSelector` *object (keys:string, values:string)* | NodeSelector is map of key-value pairs used to define the nodes on which
the pods can run.
More info: | | | | -| `nodeAffinity` *[NodeAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#nodeaffinity-v1-core)* | NodeAffinity describes node affinity scheduling rules for the pod.
More info: | | | | -| `tolerations` *[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#toleration-v1-core) array* | 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: | | | | -| `podAntiAffinityType` *string* | 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:
| | | | -| `additionalPodAntiAffinity` *[PodAntiAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podantiaffinity-v1-core)* | 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` *[PodAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podaffinity-v1-core)* | AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods. | | | | - -#### AvailableArchitecture - -AvailableArchitecture represents the state of a cluster's architecture - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------- | ------------------------------------------------- | -------- | ------- | ---------- | -| `goArch` *string* | GoArch is the name of the executable architecture | True | | | -| `hash` *string* | Hash is the hash of the executable | True | | | - -#### Backup - -A Backup resource is a request for a PostgreSQL backup by the user. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Backup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[BackupSpec](#backupspec)* | Specification of the desired behavior of the backup.
More info: | True | | | -| `status` *[BackupStatus](#backupstatus)* | Most recently observed status of the backup. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### BackupConfiguration - -BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `volumeSnapshot` *[VolumeSnapshotConfiguration](#volumesnapshotconfiguration)* | VolumeSnapshot provides the configuration for the execution of volume snapshot backups. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `retentionPolicy` *string* | 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. | | | Pattern: `^[1-9][0-9]*[dwm]$`
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| - -#### BackupMethod - -*Underlying type:* *string* - -BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance - -*Appears in:* - -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [ClusterStatus](#clusterstatus) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | -| ------------------- | -------------------------------------------------------------------------------------------- | -| `volumeSnapshot` | BackupMethodVolumeSnapshot means using the volume snapshot
Kubernetes feature
| -| `barmanObjectStore` | BackupMethodBarmanObjectStore means using barman to backup the
PostgreSQL cluster
| -| `plugin` | BackupMethodPlugin means that this backup should be handled by
a plugin
| - -#### BackupPhase - -*Underlying type:* *string* - -BackupPhase is the phase of the backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -#### BackupPluginConfiguration - -BackupPluginConfiguration contains the backup configuration used by -the backup plugin - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin managing this backup | True | | | -| `parameters` *object (keys:string, values:string)* | Parameters are the configuration parameters passed to the backup
plugin for this backup | | | | - -#### BackupSnapshotElementStatus - -BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup - -*Appears in:* - -- [BackupSnapshotStatus](#backupsnapshotstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the snapshot resource name | True | | | -| `type` *string* | Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE | True | | | -| `tablespaceName` *string* | TablespaceName is the name of the snapshotted tablespace. Only set
when type is PG_TABLESPACE | | | | - -#### BackupSnapshotStatus - -BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `elements` *[BackupSnapshotElementStatus](#backupsnapshotelementstatus) array* | The elements list, populated with the gathered volume snapshots | | | | - -#### BackupSource - -BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name of the referent. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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 - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### BackupStatus - -BackupStatus defines the observed state of Backup - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `googleCredentials` *[GoogleCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#GoogleCredentials)* | The credentials to use to upload data to Google Cloud Storage | | | | -| `s3Credentials` *[S3Credentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#S3Credentials)* | The credentials to use to upload data to S3 | | | | -| `azureCredentials` *[AzureCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#AzureCredentials)* | The credentials to use to upload data to Azure Blob Storage | | | | -| `majorVersion` *integer* | The PostgreSQL major version that was running when the
backup was taken. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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` *string* | Endpoint to be used to upload data to the cloud,
overriding the automatic endpoint discovery | | | | -| `destinationPath` *string* | 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. | | | | -| `serverName` *string* | The server name on S3, the cluster name is used if this
parameter is omitted | | | | -| `encryption` *string* | Encryption method required to S3 API | | | | -| `backupId` *string* | The ID of the Barman backup | | | | -| `backupName` *string* | The Name of the Barman backup | | | | -| `phase` *[BackupPhase](#backupphase)* | The last backup status | | | | -| `startedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup was started | | | | -| `stoppedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup was terminated | | | | -| `beginWal` *string* | The starting WAL | | | | -| `endWal` *string* | The ending WAL | | | | -| `beginLSN` *string* | The starting xlog | | | | -| `endLSN` *string* | The ending xlog | | | | -| `error` *string* | The detected error | | | | -| `commandOutput` *string* | Unused. Retained for compatibility with old versions. | | | | -| `commandError` *string* | The backup command output in case of error | | | | -| `backupLabelFile` *integer array* | Backup label file content as returned by Postgres in case of online (hot) backups | | | | -| `tablespaceMapFile` *integer array* | Tablespace map file content as returned by Postgres in case of online (hot) backups | | | | -| `instanceID` *[InstanceID](#instanceid)* | Information to identify the instance where the backup has been taken from | | | | -| `snapshotBackupStatus` *[BackupSnapshotStatus](#backupsnapshotstatus)* | Status of the volumeSnapshot backup | | | | -| `method` *[BackupMethod](#backupmethod)* | The backup method being used | | | | -| `online` *boolean* | Whether the backup was online/hot (`true`) or offline/cold (`false`) | | | | -| `pluginMetadata` *object (keys:string, values:string)* | A map containing the plugin metadata | | | | - -#### BackupTarget - -*Underlying type:* *string* - -BackupTarget describes the preferred targets for a backup - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initdb` *[BootstrapInitDB](#bootstrapinitdb)* | Bootstrap the cluster via initdb | | | | -| `recovery` *[BootstrapRecovery](#bootstraprecovery)* | Bootstrap the cluster from a backup | | | | -| `pg_basebackup` *[BootstrapPgBaseBackup](#bootstrappgbasebackup)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | -| `redwood` *boolean* | If we need to enable/disable Redwood compatibility. Requires
EPAS and for EPAS defaults to true | | | | -| `options` *string array* | 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. | | | | -| `dataChecksums` *boolean* | Whether the `-k` option should be passed to initdb,
enabling checksums on data pages (default: `false`) | | | | -| `encoding` *string* | The value to be passed as option `--encoding` for initdb (default:`UTF8`) | | | | -| `localeCollate` *string* | The value to be passed as option `--lc-collate` for initdb (default:`C`) | | | | -| `localeCType` *string* | The value to be passed as option `--lc-ctype` for initdb (default:`C`) | | | | -| `locale` *string* | Sets the default collation order and character classification in the new database. | | | | -| `localeProvider` *string* | This option sets the locale provider for databases created in the new cluster.
Available from PostgreSQL 16. | | | | -| `icuLocale` *string* | Specifies the ICU locale when the ICU provider is used.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Specifies additional collation rules to customize the behavior of the default collation.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Specifies the locale name when the builtin provider is used.
This option requires `localeProvider` to be set to `builtin`.
Available from PostgreSQL 17. | | | | -| `walSegmentSize` *integer* | The value in megabytes (1 to 1024) to be passed to the `--wal-segsize`
option for initdb (default: empty, resulting in PostgreSQL default: 16MB) | | | Maximum: 1024
Minimum: 1
| -| `postInitSQL` *string array* | List of SQL queries to be executed as a superuser in the `postgres`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitApplicationSQL` *string array* | List of SQL queries to be executed as a superuser in the application
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitTemplateSQL` *string array* | List of SQL queries to be executed as a superuser in the `template1`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `import` *[Import](#import)* | Bootstraps the new cluster by importing data from an existing PostgreSQL
instance using logical backup (`pg_dump` and `pg_restore`) | | | | -| `postInitApplicationSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the application database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitTemplateSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `template1` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `postgres` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | - -#### BootstrapPgBaseBackup - -BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ------------------- | -| `source` *string* | The name of the server of which we need to take a physical backup | True | | MinLength: 1
| -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backup` *[BackupSource](#backupsource)* | The backup object containing the physical base backup from which to
initiate the recovery procedure.
Mutually exclusive with `source` and `volumeSnapshots`. | | | | -| `source` *string* | 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`. | | | | -| `volumeSnapshots` *[DataSource](#datasource)* | 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 {{name.ln}}, 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`. | | | | -| `recoveryTarget` *[RecoveryTarget](#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: | | | | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | - -#### CatalogImage - -CatalogImage defines the image and major version - -*Appears in:* - -- [ImageCatalogSpec](#imagecatalogspec) - -| Field | Description | Required | Default | Validation | -| ----------------- | ----------------------------------------------------------------------------- | -------- | ------- | ------------------ | -| `image` *string* | The image reference | True | | | -| `major` *integer* | The PostgreSQL major version of the image. Must be unique within the catalog. | True | | Minimum: 10
| - -#### CertificatesConfiguration - -CertificatesConfiguration contains the needed configurations to handle server certificates. - -*Appears in:* - -- [CertificatesStatus](#certificatesstatus) -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | - -#### CertificatesStatus - -CertificatesStatus contains configuration certificates and related expiration dates. - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | -| `expirations` *object (keys:string, values:string)* | Expiration dates for all certificates. | | | | - -#### Cluster - -Cluster defines the API schema for a highly available PostgreSQL database cluster -managed by {{name.ln}}. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Cluster` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ClusterSpec](#clusterspec)* | Specification of the desired behavior of the cluster.
More info: | True | | | -| `status` *[ClusterStatus](#clusterstatus)* | Most recently observed status of the cluster. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ClusterImageCatalog - -ClusterImageCatalog is the Schema for the clusterimagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ClusterImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ClusterImageCatalog.
More info: | True | | | - -#### ClusterMonitoringTLSConfiguration - -ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring - -*Appears in:* - -- [MonitoringConfiguration](#monitoringconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------- | -------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Enable TLS for the monitoring endpoint.
Changing this option will force a rollout of all instances. | | false | | - -#### ClusterSpec - -ClusterSpec defines the desired state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ | --------------------------------------------- | -| `description` *string* | Description of this PostgreSQL cluster | | | | -| `inheritedMetadata` *[EmbeddedObjectMetadata](#embeddedobjectmetadata)* | Metadata that will be inherited by all objects related to the Cluster | | | | -| `imageName` *string* | Name of the container image, supporting both tags (`:`)
and digests for deterministic and repeatable deployments
(`:@sha256:`) | | | | -| `imageCatalogRef` *[ImageCatalogRef](#imagecatalogref)* | Defines the major PostgreSQL version we want to use within an ImageCatalog | | | | -| `imagePullPolicy` *[PullPolicy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#pullpolicy-v1-core)* | Image pull policy.
One of `Always`, `Never` or `IfNotPresent`.
If not defined, it defaults to `IfNotPresent`.
Cannot be updated.
More info: | | | | -| `schedulerName` *string* | 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:
| | | | -| `postgresUID` *integer* | The UID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `postgresGID` *integer* | The GID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `instances` *integer* | Number of instances required in the cluster | True | 1 | Minimum: 1
| -| `minSyncReplicas` *integer* | Minimum number of instances required in synchronous replication with the
primary. Undefined or 0 allow writes to complete when no standby is
available. | | 0 | Minimum: 0
| -| `maxSyncReplicas` *integer* | 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. | | 0 | Minimum: 0
| -| `postgresql` *[PostgresConfiguration](#postgresconfiguration)* | Configuration of the PostgreSQL server | | | | -| `replicationSlots` *[ReplicationSlotsConfiguration](#replicationslotsconfiguration)* | Replication slots management configuration | | | | -| `bootstrap` *[BootstrapConfiguration](#bootstrapconfiguration)* | Instructions to bootstrap this cluster | | | | -| `replica` *[ReplicaClusterConfiguration](#replicaclusterconfiguration)* | Replica cluster configuration | | | | -| `superuserSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The secret containing the superuser password. If not defined a new
secret will be created with a randomly generated password | | | | -| `enableSuperuserAccess` *boolean* | 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`. Disabled by default. | | | | -| `certificates` *[CertificatesConfiguration](#certificatesconfiguration)* | The configuration for the CA and related certificates | | | | -| `imagePullSecrets` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference) array* | 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. | | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage of the instances | | | | -| `serviceAccountTemplate` *[ServiceAccountTemplate](#serviceaccounttemplate)* | Configure the generation of the service account | | | | -| `walStorage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `ephemeralVolumeSource` *[EphemeralVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#ephemeralvolumesource-v1-core)* | EphemeralVolumeSource allows the user to configure the source of ephemeral volumes. | | | | -| `startDelay` *integer* | 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). | | 3600 | | -| `stopDelay` *integer* | The time in seconds that is allowed for a PostgreSQL instance to
gracefully shutdown (default 1800) | | 1800 | | -| `smartStopDelay` *integer* | Deprecated: please use SmartShutdownTimeout instead | | | | -| `smartShutdownTimeout` *integer* | 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`). Default is 180 seconds. | | 180 | | -| `switchoverDelay` *integer* | 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). | | 3600 | | -| `failoverDelay` *integer* | 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 | | 0 | | -| `livenessProbeTimeout` *integer* | 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` *[AffinityConfiguration](#affinityconfiguration)* | Affinity/Anti-affinity rules for Pods | | | | -| `topologySpreadConstraints` *[TopologySpreadConstraint](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#topologyspreadconstraint-v1-core) array* | TopologySpreadConstraints specifies how to spread matching pods among the given topology.
More info:
| | | | -| `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#resourcerequirements-v1-core)* | Resources requirements of every generated Pod. Please refer to

for more information. | | | | -| `ephemeralVolumesSizeLimit` *[EphemeralVolumesSizeLimitConfiguration](#ephemeralvolumessizelimitconfiguration)* | EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral
volumes | | | | -| `priorityClassName` *string* | 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

for more information | | | | -| `primaryUpdateStrategy` *[PrimaryUpdateStrategy](#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`) | | unsupervised | Enum: [unsupervised supervised]
| -| `primaryUpdateMethod` *[PrimaryUpdateMethod](#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).
Note: when using `switchover`, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process. | | | Enum: [switchover restart]
| -| `backup` *[BackupConfiguration](#backupconfiguration)* | The configuration to be used for backups | | | | -| `nodeMaintenanceWindow` *[NodeMaintenanceWindow](#nodemaintenancewindow)* | Define a maintenance window for the Kubernetes nodes | | | | -| `licenseKey` *string* | 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. | | | | -| `licenseKeySecret` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the license key. When this is set it take precedence over LicenseKey. | | | | -| `monitoring` *[MonitoringConfiguration](#monitoringconfiguration)* | The configuration of the monitoring infrastructure of this cluster | | | | -| `externalClusters` *[ExternalCluster](#externalcluster) array* | The list of external clusters which are used in the configuration | | | | -| `logLevel` *string* | The instances' log level, one of the following values: error, warning, info (default), debug, trace | | info | Enum: [error warning info debug trace]
| -| `projectedVolumeTemplate` *[ProjectedVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#projectedvolumesource-v1-core)* | Template to be used to define projected volumes, projected volumes will be mounted
under `/projected` base folder | | | | -| `env` *[EnvVar](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envvar-v1-core) array* | Env follows the Env format to pass environment variables
to the pods created in the cluster | | | | -| `envFrom` *[EnvFromSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envfromsource-v1-core) array* | EnvFrom follows the EnvFrom format to pass environment variables
sources to the pods to be used by Env | | | | -| `managed` *[ManagedConfiguration](#managedconfiguration)* | The configuration that is used by the portions of PostgreSQL that are managed by the instance manager | | | | -| `seccompProfile` *[SeccompProfile](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#seccompprofile-v1-core)* | The SeccompProfile applied to every Pod and Container.
Defaults to: `RuntimeDefault` | | | | -| `podSecurityContext` *[PodSecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podsecuritycontext-v1-core)* | Override the PodSecurityContext applied to every Pod of the cluster.
When set, this overrides the operator's default PodSecurityContext for the cluster.
If omitted, the operator defaults are used.
This field doesn't have any effect if SecurityContextConstraints are present. | | | | -| `securityContext` *[SecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#securitycontext-v1-core)* | Override the SecurityContext applied to every Container in the Pod of the cluster.
When set, this overrides the operator's default Container SecurityContext.
If omitted, the operator defaults are used. | | | | -| `tablespaces` *[TablespaceConfiguration](#tablespaceconfiguration) array* | The tablespaces configuration | | | | -| `enablePDB` *boolean* | 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 any
`PodDisruptionBudget` 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. | | true | | -| `plugins` *[PluginConfiguration](#pluginconfiguration) array* | The plugins configuration, containing
any plugin to be loaded with the corresponding configuration | | | | -| `probes` *[ProbesConfiguration](#probesconfiguration)* | The configuration of the probes to be injected
in the PostgreSQL Pods. | | | | - -#### ClusterStatus - -ClusterStatus defines the observed state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *integer* | The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods. | | | | -| `readyInstances` *integer* | The total number of ready instances in the cluster. It is equal to the number of ready instance pods. | | | | -| `instancesStatus` *object (keys:[PodStatus](#podstatus), values:string array)* | InstancesStatus indicates in which status the instances are | | | | -| `instancesReportedState` *object (keys:[PodName](#podname), values:[InstanceReportedState](#instancereportedstate))* | The reported state of the instances during the last reconciliation loop | | | | -| `managedRolesStatus` *[ManagedRoles](#managedroles)* | ManagedRolesStatus reports the state of the managed roles in the cluster | | | | -| `tablespacesStatus` *[TablespaceState](#tablespacestate) array* | TablespacesStatus reports the state of the declarative tablespaces in the cluster | | | | -| `timelineID` *integer* | The timeline of the Postgres cluster | | | | -| `topology` *[Topology](#topology)* | Instances topology. | | | | -| `latestGeneratedNode` *integer* | ID of the latest generated node (used to avoid node name clashing) | | | | -| `currentPrimary` *string* | Current primary instance | | | | -| `targetPrimary` *string* | Target primary instance, this is different from the previous one
during a switchover or a failover | | | | -| `lastPromotionToken` *string* | LastPromotionToken is the last verified promotion token that
was used to promote a replica cluster | | | | -| `pvcCount` *integer* | How many PVCs have been created by this cluster | | | | -| `jobCount` *integer* | How many Jobs have been created by this cluster | | | | -| `danglingPVC` *string array* | List of all the PVCs created by this cluster and still available
which are not attached to a Pod | | | | -| `resizingPVC` *string array* | List of all the PVCs that have ResizingPVC condition. | | | | -| `initializingPVC` *string array* | List of all the PVCs that are being initialized by this cluster | | | | -| `healthyPVC` *string array* | List of all the PVCs not dangling nor initializing | | | | -| `unusablePVC` *string array* | List of all the PVCs that are unusable because another PVC is missing | | | | -| `licenseStatus` *Status* | Status of the license | | | | -| `writeService` *string* | Current write pod | | | | -| `readService` *string* | Current list of read pods | | | | -| `phase` *string* | Current phase of the cluster | | | | -| `phaseReason` *string* | Reason for the current phase | | | | -| `secretsResourceVersion` *[SecretsResourceVersion](#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` *[ConfigMapResourceVersion](#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` *[CertificatesStatus](#certificatesstatus)* | The configuration for the CA and related certificates, initialized with defaults. | | | | -| `firstRecoverabilityPoint` *string* | The first recoverability point, stored as a date in RFC3339 format.
This field is calculated from the content of FirstRecoverabilityPointByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `firstRecoverabilityPointByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | The first recoverability point, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackup` *string* | Last successful backup, stored as a date in RFC3339 format.
This field is calculated from the content of LastSuccessfulBackupByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackupByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | Last successful backup, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastFailedBackup` *string* | Last failed backup, stored as a date in RFC3339 format.
Deprecated: the field is not set for backup plugins. | | | | -| `cloudNativePostgresqlCommitHash` *string* | The commit hash number of which this operator running | | | | -| `currentPrimaryTimestamp` *string* | The timestamp when the last actual promotion to primary has occurred | | | | -| `currentPrimaryFailingSinceTimestamp` *string* | The timestamp when the primary was detected to be unhealthy
This field is reported when `.spec.failoverDelay` is populated or during online upgrades | | | | -| `targetPrimaryTimestamp` *string* | The timestamp when the last request for a new primary has occurred | | | | -| `poolerIntegrations` *[PoolerIntegrations](#poolerintegrations)* | The integration needed by poolers referencing the cluster | | | | -| `cloudNativePostgresqlOperatorHash` *string* | The hash of the binary of the operator | | | | -| `availableArchitectures` *[AvailableArchitecture](#availablearchitecture) array* | AvailableArchitectures reports the available architectures of a cluster | | | | -| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for cluster object | | | | -| `instanceNames` *string array* | List of instance names in the cluster | | | | -| `onlineUpdateEnabled` *boolean* | OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster | | | | -| `image` *string* | Image contains the image name used by the pods | | | | -| `pgDataImageInfo` *[ImageInfo](#imageinfo)* | PGDataImageInfo contains the details of the latest image that has run on the current data directory. | | | | -| `pluginStatus` *[PluginStatus](#pluginstatus) array* | PluginStatus is the status of the loaded plugins | | | | -| `switchReplicaClusterStatus` *[SwitchReplicaClusterStatus](#switchreplicaclusterstatus)* | SwitchReplicaClusterStatus is the status of the switch to replica cluster | | | | -| `demotionToken` *string* | DemotionToken is a JSON token containing the information
from pg_controldata such as Database system identifier, Latest checkpoint's
TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO
WAL file, and Time of latest checkpoint | | | | -| `systemID` *string* | SystemID is the latest detected PostgreSQL SystemID | | | | - -#### ConfigMapResourceVersion - -ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metrics` *object (keys:string, values:string)* | 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 | | | | - -#### DataDurabilityLevel - -*Underlying type:* *string* - -DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are `required` or `preferred`. - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -| Field | Description | -| ----------- | ----------------------------------------------------------------------------------------------------------------------- | -| `required` | DataDurabilityLevelRequired means that data durability is strictly enforced
| -| `preferred` | DataDurabilityLevelPreferred means that data durability is enforced
only when healthy replicas are available
| - -#### DataSource - -DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `storage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage of the instances | True | | | -| `walStorage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `tablespaceStorage` *object (keys:string, values:[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core))* | Configuration of the storage for PostgreSQL tablespaces | | | | - -#### Database - -Database is the Schema for the databases API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Database` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[DatabaseSpec](#databasespec)* | Specification of the desired Database.
More info: | True | | | -| `status` *[DatabaseStatus](#databasestatus)* | Most recently observed status of the Database. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### DatabaseObjectSpec - -DatabaseObjectSpec contains the fields which are common to every -database object - -*Appears in:* - -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| - -#### DatabaseObjectStatus - -DatabaseObjectStatus is the status of the managed database objects - -*Appears in:* - -- [DatabaseStatus](#databasestatus) - -| Field | Description | Required | Default | Validation | -| ------------------- | ----------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the object | True | | | -| `applied` *boolean* | True of the object has been installed successfully in
the database | True | | | -| `message` *string* | Message is the object reconciliation message | | | | - -#### DatabaseReclaimPolicy - -*Underlying type:* *string* - -DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases. - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | DatabaseReclaimDelete means the database will be deleted from its PostgreSQL Cluster on release
from its claim.
| -| `retain` | DatabaseReclaimRetain means the database will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### DatabaseRoleRef - -DatabaseRoleRef is a reference an a role available inside PostgreSQL - -*Appears in:* - -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------- | ----------- | -------- | ------- | ---------- | -| `name` *string* | | | | | - -#### DatabaseSpec - -DatabaseSpec is the specification of a Postgresql Database, built around the -`CREATE DATABASE`, `ALTER DATABASE`, and `DROP DATABASE` SQL commands of -PostgreSQL. - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster hosting the database. | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the PostgreSQL database is `present` or `absent` - defaults to "present". | | present | Enum: [present absent]
| -| `name` *string* | The name of the database to create inside PostgreSQL. This setting cannot be changed. | True | | | -| `owner` *string* | Maps to the `OWNER` parameter of `CREATE DATABASE`.
Maps to the `OWNER TO` command of `ALTER DATABASE`.
The role name of the user who owns the database inside PostgreSQL. | True | | | -| `template` *string* | Maps to the `TEMPLATE` parameter of `CREATE DATABASE`. This setting
cannot be changed. The name of the template from which to create
this database. | | | | -| `encoding` *string* | Maps to the `ENCODING` parameter of `CREATE DATABASE`. This setting
cannot be changed. Character set encoding to use in the database. | | | | -| `locale` *string* | Maps to the `LOCALE` parameter of `CREATE DATABASE`. This setting
cannot be changed. Sets the default collation order and character
classification in the new database. | | | | -| `localeProvider` *string* | Maps to the `LOCALE_PROVIDER` parameter of `CREATE DATABASE`. This
setting cannot be changed. This option sets the locale provider for
databases created in the new cluster. Available from PostgreSQL 16. | | | | -| `localeCollate` *string* | Maps to the `LC_COLLATE` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `localeCType` *string* | Maps to the `LC_CTYPE` parameter of `CREATE DATABASE`. This setting
cannot be changed. | | | | -| `icuLocale` *string* | Maps to the `ICU_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the ICU locale when the ICU
provider is used. This option requires `localeProvider` to be set to
`icu`. Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Maps to the `ICU_RULES` parameter of `CREATE DATABASE`. This setting
cannot be changed. Specifies additional collation rules to customize
the behavior of the default collation. This option requires
`localeProvider` to be set to `icu`. Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Maps to the `BUILTIN_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the locale name when the
builtin provider is used. This option requires `localeProvider` to
be set to `builtin`. Available from PostgreSQL 17. | | | | -| `collationVersion` *string* | Maps to the `COLLATION_VERSION` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `isTemplate` *boolean* | Maps to the `IS_TEMPLATE` parameter of `CREATE DATABASE` and `ALTER
DATABASE`. If true, this database is considered a template and can
be cloned by any user with `CREATEDB` privileges. | | | | -| `allowConnections` *boolean* | Maps to the `ALLOW_CONNECTIONS` parameter of `CREATE DATABASE` and
`ALTER DATABASE`. If false then no one can connect to this database. | | | | -| `connectionLimit` *integer* | Maps to the `CONNECTION LIMIT` clause of `CREATE DATABASE` and
`ALTER DATABASE`. How many concurrent connections can be made to
this database. -1 (the default) means no limit. | | | | -| `tablespace` *string* | Maps to the `TABLESPACE` parameter of `CREATE DATABASE`.
Maps to the `SET TABLESPACE` command of `ALTER DATABASE`.
The name of the tablespace (in PostgreSQL) that will be associated
with the new database. This tablespace will be the default
tablespace used for objects created in this database. | | | | -| `databaseReclaimPolicy` *[DatabaseReclaimPolicy](#databasereclaimpolicy)* | The policy for end-of-life maintenance of this database. | | retain | Enum: [delete retain]
| -| `schemas` *[SchemaSpec](#schemaspec) array* | The list of schemas to be managed in the database | | | | -| `extensions` *[ExtensionSpec](#extensionspec) array* | The list of extensions to be managed in the database | | | | -| `fdws` *[FDWSpec](#fdwspec) array* | The list of foreign data wrappers to be managed in the database | | | | -| `servers` *[ServerSpec](#serverspec) array* | The list of foreign servers to be managed in the database | | | | - -#### DatabaseStatus - -DatabaseStatus defines the observed state of Database - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the database was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | -| `schemas` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Schemas is the status of the managed schemas | | | | -| `extensions` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Extensions is the status of the managed extensions | | | | -| `fdws` *[DatabaseObjectStatus](#databaseobjectstatus) array* | FDWs is the status of the managed FDWs | | | | -| `servers` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Servers is the status of the managed servers | | | | - -#### EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `audit` *boolean* | If true enables edb_audit logging | | | | -| `tde` *[TDEConfiguration](#tdeconfiguration)* | TDE configuration | | | | - -#### EmbeddedObjectMetadata - -EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `labels` *object (keys:string, values:string)* | | | | | -| `annotations` *object (keys:string, values:string)* | | | | | - -#### EnsureOption - -*Underlying type:* *string* - -EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance - -*Appears in:* - -- [DatabaseObjectSpec](#databaseobjectspec) -- [DatabaseSpec](#databasespec) -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [OptionSpec](#optionspec) -- [RoleConfiguration](#roleconfiguration) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | -| --------- | ----------- | -| `present` | | -| `absent` | | - -#### EphemeralVolumesSizeLimitConfiguration - -EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------ | -------- | ------- | ---------- | -| `shm` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Shm is the size limit of the shared memory volume | | | | -| `temporaryData` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | TemporaryData is the size limit of the temporary data volume | | | | - -#### ExtensionConfiguration - -ExtensionConfiguration is the configuration used to add -PostgreSQL extensions to the Cluster. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | -------------------------------------------------------------------- | -| `name` *string* | The name of the extension, required | True | | MinLength: 1
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| -| `image` *[ImageVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#imagevolumesource-v1-core)* | The image containing the extension, required | True | | | -| `extension_control_path` *string array* | The list of directories inside the image which should be added to extension_control_path.
If not defined, defaults to "/share". | | | | -| `dynamic_library_path` *string array* | The list of directories inside the image which should be added to dynamic_library_path.
If not defined, defaults to "/lib". | | | | -| `ld_library_path` *string array* | The list of directories inside the image which should be added to ld_library_path. | | | | - -#### ExtensionSpec - -ExtensionSpec configures an extension in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `version` *string* | The version of the extension to install. If empty, the operator will
install the default version (whatever is specified in the
extension's control file) | True | | | -| `schema` *string* | The name of the schema in which to install the extension's objects,
in case the extension allows its contents to be relocated. If not
specified (default), and the extension's control file does not
specify a schema either, the current default object creation schema
is used. | True | | | - -#### ExternalCluster - -ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The server name, required | True | | | -| `connectionParameters` *object (keys:string, values:string)* | The list of connection parameters, such as dbname, host, username, etc | | | | -| `sslCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL certificate to be used to connect to this
instance | | | | -| `sslKey` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL private key to be used to connect to this
instance | | | | -| `sslRootCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL CA public key to be used to connect to this
instance | | | | -| `password` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the password to be used to connect to the server.
If a password is provided, {{name.ln}} 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. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `plugin` *[PluginConfiguration](#pluginconfiguration)* | The configuration of the plugin that is taking care
of WAL archiving and backups for this external cluster | True | | | - -#### FDWSpec - -FDWSpec configures an Foreign Data Wrapper in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `handler` *string* | Name of the handler function (e.g., "postgres_fdw_handler").
This will be empty if no handler is specified. In that case,
the default handler is registered when the FDW extension is created. | | | | -| `validator` *string* | Name of the validator function (e.g., "postgres_fdw_validator").
This will be empty if no validator is specified. In that case,
the default validator is registered when the FDW extension is created. | | | | -| `owner` *string* | Owner specifies the database role that will own the Foreign Data Wrapper.
The role must have superuser privileges in the target database. | | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the FDW. | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the FDW are granted or revoked. | | | | - -#### FailoverQuorum - -FailoverQuorum contains the information about the current failover -quorum status of a PG cluster. It is updated by the instance manager -of the primary node and reset to zero by the operator to trigger -an update. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `FailoverQuorum` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `status` *[FailoverQuorumStatus](#failoverquorumstatus)* | Most recently observed status of the failover quorum. | | | | - -#### FailoverQuorumStatus - -FailoverQuorumStatus is the latest observed status of the failover -quorum of the PG cluster. - -*Appears in:* - -- [FailoverQuorum](#failoverquorum) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | --------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `method` *string* | Contains the latest reported Method value. | | | | -| `standbyNames` *string array* | StandbyNames is the list of potentially synchronous
instance names. | | | | -| `standbyNumber` *integer* | StandbyNumber is the number of synchronous standbys that transactions
need to wait for replies from. | | | | -| `primary` *string* | Primary is the name of the primary instance that updated
this object the latest time. | | | | - -#### ImageCatalog - -ImageCatalog is the Schema for the imagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ImageCatalog.
More info: | True | | | - -#### ImageCatalogRef - -ImageCatalogRef defines the reference to a major version in an ImageCatalog - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiGroup` *string* | APIGroup is the group for the resource being referenced.
If APIGroup is not specified, the specified Kind must be in the core API group.
For any other third-party types, APIGroup is required. | | | | -| `kind` *string* | Kind is the type of resource being referenced | True | | | -| `name` *string* | Name is the name of resource being referenced | True | | | -| `major` *integer* | The major version of PostgreSQL we want to use from the ImageCatalog | True | | | - -#### ImageCatalogSpec - -ImageCatalogSpec defines the desired ImageCatalog - -*Appears in:* - -- [ClusterImageCatalog](#clusterimagecatalog) -- [ImageCatalog](#imagecatalog) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------- | ---------------------------------------------- | -------- | ------- | ------------------------------------ | -| `images` *[CatalogImage](#catalogimage) array* | List of CatalogImages available in the catalog | True | | MaxItems: 8
MinItems: 1
| - -#### ImageInfo - -ImageInfo contains the information about a PostgreSQL image - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ---------------------------------------------- | -------- | ------- | ---------- | -| `image` *string* | Image is the image name | True | | | -| `majorVersion` *integer* | MajorVersion is the major version of the image | True | | | - -#### Import - -Import contains the configuration to init a database from a logic snapshot of an externalCluster - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------ | -| `source` *[ImportSource](#importsource)* | The source of the import | True | | | -| `type` *[SnapshotType](#snapshottype)* | The import type. Can be `microservice` or `monolith`. | True | | Enum: [microservice monolith]
| -| `databases` *string array* | The databases to import | True | | | -| `roles` *string array* | The roles to import | | | | -| `postImportApplicationSQL` *string array* | 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. | | | | -| `schemaOnly` *boolean* | When set to true, only the `pre-data` and `post-data` sections of
`pg_restore` are invoked, avoiding data import. Default: `false`. | | | | -| `pgDumpExtraOptions` *string array* | List of custom options to pass to the `pg_dump` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreExtraOptions` *string array* | List of custom options to pass to the `pg_restore` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePredataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `pre-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreDataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePostdataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `post-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | - -#### ImportSource - -ImportSource describes the source for the logical snapshot - -*Appears in:* - -- [Import](#import) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ----------------------------------------------- | -------- | ------- | ---------- | -| `externalCluster` *string* | The name of the externalCluster used for import | True | | | - -#### InstanceID - -InstanceID contains the information to identify an instance - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | ---------------- | -------- | ------- | ---------- | -| `podName` *string* | The pod name | | | | -| `ContainerID` *string* | The container ID | | | | - -#### InstanceReportedState - -InstanceReportedState describes the last reported state of an instance during a reconciliation loop - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------- | -------- | ------- | ---------- | -| `isPrimary` *boolean* | indicates if an instance is the primary one | True | | | -| `timeLineID` *integer* | indicates on which TimelineId the instance is | | | | -| `ip` *string* | IP address of the instance | True | | | - -#### IsolationCheckConfiguration - -IsolationCheckConfiguration contains the configuration for the isolation check -functionality in the liveness probe - -*Appears in:* - -- [LivenessProbe](#livenessprobe) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Whether primary isolation checking is enabled for the liveness probe | | true | | -| `requestTimeout` *integer* | Timeout in milliseconds for requests during the primary isolation check | | 1000 | | -| `connectionTimeout` *integer* | Timeout in milliseconds for connections during the primary isolation check | | 1000 | | - -#### LDAPBindAsAuth - -LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ----------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `prefix` *string* | Prefix for the bind authentication option | | | | -| `suffix` *string* | Suffix for the bind authentication option | | | | - -#### LDAPBindSearchAuth - -LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | -------- | ------- | ---------- | -| `baseDN` *string* | Root DN to begin the user search | | | | -| `bindDN` *string* | DN of the user to bind to the directory | | | | -| `bindPassword` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Secret with the password for the user to bind to the directory | | | | -| `searchAttribute` *string* | Attribute to match against the username | | | | -| `searchFilter` *string* | Search filter to use when doing the search+bind authentication | | | | - -#### LDAPConfig - -LDAPConfig contains the parameters needed for LDAP authentication - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ------------------------- | -| `server` *string* | LDAP hostname or IP address | | | | -| `port` *integer* | LDAP server port | | | | -| `scheme` *[LDAPScheme](#ldapscheme)* | LDAP schema to be used, possible options are `ldap` and `ldaps` | | | Enum: [ldap ldaps]
| -| `bindAsAuth` *[LDAPBindAsAuth](#ldapbindasauth)* | Bind as authentication configuration | | | | -| `bindSearchAuth` *[LDAPBindSearchAuth](#ldapbindsearchauth)* | Bind+Search authentication configuration | | | | -| `tls` *boolean* | Set to 'true' to enable LDAP over TLS. 'false' is default | | | | - -#### LDAPScheme - -*Underlying type:* *string* - -LDAPScheme defines the possible schemes for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | -| ------- | ----------- | -| `ldap` | | -| `ldaps` | | - -#### LivenessProbe - -LivenessProbe is the configuration of the liveness probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `isolationCheck` *[IsolationCheckConfiguration](#isolationcheckconfiguration)* | Configure the feature that extends the liveness probe for a primary
instance. In addition to the basic checks, this verifies whether the
primary is isolated from the Kubernetes API server and from its
replicas, ensuring that it can be safely shut down if network
partition or API unavailability is detected. Enabled by default. | | | | - -#### ManagedConfiguration - -ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------- | --------------------------------------- | -------- | ------- | ---------- | -| `roles` *[RoleConfiguration](#roleconfiguration) array* | Database roles managed by the `Cluster` | | | | -| `services` *[ManagedServices](#managedservices)* | Services roles managed by the `Cluster` | | | | - -#### ManagedRoles - -ManagedRoles tracks the status of a cluster's managed roles - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `byStatus` *object (keys:[RoleStatus](#rolestatus), values:string array)* | ByStatus gives the list of roles in each state | | | | -| `cannotReconcile` *object (keys:string, values:string array)* | CannotReconcile lists roles that cannot be reconciled in PostgreSQL,
with an explanation of the cause | | | | -| `passwordStatus` *object (keys:string, values:[PasswordState](#passwordstate))* | PasswordStatus gives the last transaction id and password secret version for each managed role | | | | - -#### ManagedService - -ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification. - -*Appears in:* - -- [ManagedServices](#managedservices) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `selectorType` *[ServiceSelectorType](#serviceselectortype)* | SelectorType specifies the type of selectors that the service will have.
Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services. | True | | Enum: [rw r ro]
| -| `updateStrategy` *[ServiceUpdateStrategy](#serviceupdatestrategy)* | UpdateStrategy describes how the service differences should be reconciled | | patch | Enum: [patch replace]
| -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | ServiceTemplate is the template specification for the service. | True | | | - -#### ManagedServices - -ManagedServices represents the services managed by the cluster. - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------- | -| `disabledDefaultServices` *[ServiceSelectorType](#serviceselectortype) array* | DisabledDefaultServices is a list of service types that are disabled by default.
Valid values are "r", and "ro", representing read, and read-only services. | | | Enum: [rw r ro]
| -| `additional` *[ManagedService](#managedservice) array* | Additional is a list of additional managed services specified by the user. | | | | - -#### 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. - -*Appears in:* - -- [PodTemplateSpec](#podtemplatespec) -- [ServiceAccountTemplate](#serviceaccounttemplate) -- [ServiceTemplateSpec](#servicetemplatespec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the resource. Only supported for certain types | | | | -| `labels` *object (keys:string, values:string)* | 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: | | | | -| `annotations` *object (keys:string, values:string)* | 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: | | | | - -#### MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `disableDefaultQueries` *boolean* | 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. | | false | | -| `customQueriesConfigMap` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | The list of config maps containing the custom queries | | | | -| `customQueriesSecret` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | The list of secrets containing the custom queries | | | | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor`
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | false | | -| `tls` *[ClusterMonitoringTLSConfiguration](#clustermonitoringtlsconfiguration)* | Configure TLS communication for the metrics endpoint.
Changing tls.enabled option will force a rollout of all instances. | | | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `metricsQueriesTTL` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | The interval during which metrics computed from queries are considered current.
Once it is exceeded, a new scrape will trigger a rerun
of the queries.
If not set, defaults to 30 seconds, in line with Prometheus scraping defaults.
Setting this to zero disables the caching mechanism and can cause heavy load on the PostgreSQL server. | | | | - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `reusePVC` *boolean* | Reuse the existing PVC (wait for the node to come
up again) or not (recreate it elsewhere - when `instances` >1) | | true | | -| `inProgress` *boolean* | Is there a node maintenance activity in progress? | | false | | - -#### OnlineConfiguration - -OnlineConfiguration contains the configuration parameters for the online volume snapshot - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `waitForArchive` *boolean* | 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. | | true | | -| `immediateCheckpoint` *boolean* | 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. | | | | - -#### OptionSpec - -OptionSpec holds the name, value and the ensure field for an option - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the option | True | | | -| `value` *string* | Value of the option | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an option should be present or absent in
the database. If set to `present`, the option will be
created if it does not exist. If set to `absent`, the
option will be removed if it exists. | | present | Enum: [present absent]
| - -#### PasswordState - -PasswordState represents the state of the password of a managed RoleConfiguration - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ------------------------------------------------------------------- | -------- | ------- | ---------- | -| `transactionID` *integer* | the last transaction ID to affect the role definition in PostgreSQL | | | | -| `resourceVersion` *string* | the resource version of the password secret | | | | - -#### PgBouncerIntegrationStatus - -PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster - -*Appears in:* - -- [PoolerIntegrations](#poolerintegrations) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------- | -------- | ------- | ---------- | -| `secrets` *string array* | | | | | - -#### PgBouncerPoolMode - -*Underlying type:* *string* - -PgBouncerPoolMode is the mode of PgBouncer - -*Validation:* - -- Enum: [session transaction] - -*Appears in:* - -- [PgBouncerSpec](#pgbouncerspec) - -#### PgBouncerSecrets - -PgBouncerSecrets contains the versions of the secrets used -by pgbouncer - -*Appears in:* - -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | ----------------------------- | -------- | ------- | ---------- | -| `authQuery` *[SecretVersion](#secretversion)* | The auth query secret version | | | | - -#### PgBouncerSpec - -PgBouncerSpec defines how to configure PgBouncer - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------------- | -| `poolMode` *[PgBouncerPoolMode](#pgbouncerpoolmode)* | The pool mode. Default: `session`. | | session | Enum: [session transaction]
| -| `serverTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerTLSSecret, when pointing to a TLS secret, provides pgbouncer's
`server_tls_key_file` and `server_tls_cert_file`, used when
authenticating against PostgreSQL. | | | | -| `serverCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerCASecret provides PgBouncer’s server_tls_ca_file, the root
CA for validating PostgreSQL certificates | | | | -| `clientCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientCASecret provides PgBouncer’s client_tls_ca_file, the root
CA for validating client certificates | | | | -| `clientTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientTLSSecret provides PgBouncer’s client_tls_key_file (private key)
and client_tls_cert_file (certificate) used to accept client connections | | | | -| `authQuerySecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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.
Deprecated. | | | | -| `authQuery` *string* | 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. | | | | -| `parameters` *object (keys:string, values:string)* | Additional parameters to be passed to PgBouncer - please check
the CNP documentation for a list of options you can configure | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file) | | | | -| `paused` *boolean* | 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. | | false | | - -#### PluginConfiguration - -PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [ExternalCluster](#externalcluster) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the plugin name | True | | | -| `enabled` *boolean* | Enabled is true if this plugin will be used | | true | | -| `isWALArchiver` *boolean* | Marks the plugin as the WAL archiver. At most one plugin can be
designated as a WAL archiver. This cannot be enabled if the
`.spec.backup.barmanObjectStore` configuration is present. | | false | | -| `parameters` *object (keys:string, values:string)* | Parameters is the configuration of the plugin | | | | - -#### PluginStatus - -PluginStatus is the status of a loaded plugin - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin | True | | | -| `version` *string* | Version is the version of the plugin loaded by the
latest reconciliation loop | True | | | -| `capabilities` *string array* | Capabilities are the list of capabilities of the
plugin | | | | -| `operatorCapabilities` *string array* | OperatorCapabilities are the list of capabilities of the
plugin regarding the reconciler | | | | -| `walCapabilities` *string array* | WALCapabilities are the list of capabilities of the
plugin regarding the WAL management | | | | -| `backupCapabilities` *string array* | BackupCapabilities are the list of capabilities of the
plugin regarding the Backup management | | | | -| `restoreJobHookCapabilities` *string array* | RestoreJobHookCapabilities are the list of capabilities of the
plugin regarding the RestoreJobHook management | | | | -| `status` *string* | Status contain the status reported by the plugin through the SetStatusInCluster interface | | | | - -#### PodName - -*Underlying type:* *string* - -PodName is the name of a Pod - -*Appears in:* - -- [ClusterStatus](#clusterstatus) -- [Topology](#topology) - -#### PodStatus - -*Underlying type:* *string* - -PodStatus represent the possible status of pods - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -#### 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: - - - - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[PodSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podspec-v1-core)* | Specification of the desired behavior of the pod.
More info: | | | | - -#### PodTopologyLabels - -*Underlying type:* *object* - -PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue - -*Appears in:* - -- [Topology](#topology) - -#### Pooler - -Pooler is the Schema for the poolers API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Pooler` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PoolerSpec](#poolerspec)* | Specification of the desired behavior of the Pooler.
More info: | True | | | -| `status` *[PoolerStatus](#poolerstatus)* | Most recently observed status of the Pooler. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `pgBouncerIntegration` *[PgBouncerIntegrationStatus](#pgbouncerintegrationstatus)* | | | | | - -#### 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. - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor` | | false | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping. | | | | - -#### PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -*Appears in:* - -- [PoolerStatus](#poolerstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------- | -------------------------------------------- | -------- | ------- | ---------- | -| `clientTLS` *[SecretVersion](#secretversion)* | The client TLS secret version | | | | -| `serverTLS` *[SecretVersion](#secretversion)* | The server TLS secret version | | | | -| `serverCA` *[SecretVersion](#secretversion)* | The server CA secret version | | | | -| `clientCA` *[SecretVersion](#secretversion)* | The client CA secret version | | | | -| `pgBouncerSecrets` *[PgBouncerSecrets](#pgbouncersecrets)* | The version of the secrets used by PgBouncer | | | | - -#### PoolerSpec - -PoolerSpec defines the desired state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------- | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | This is the cluster reference on which the Pooler will work.
Pooler name should never match with any cluster name within the same namespace. | True | | | -| `type` *[PoolerType](#poolertype)* | Type of service to forward traffic to. Default: `rw`. | | rw | Enum: [rw ro r]
| -| `instances` *integer* | The number of replicas we want. Default: 1. | | 1 | | -| `template` *[PodTemplateSpec](#podtemplatespec)* | The template of the Pod to be created | | | | -| `pgbouncer` *[PgBouncerSpec](#pgbouncerspec)* | The PgBouncer configuration | True | | | -| `deploymentStrategy` *[DeploymentStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#deploymentstrategy-v1-apps)* | The deployment strategy to use for pgbouncer to replace existing pods with new ones | | | | -| `monitoring` *[PoolerMonitoringConfiguration](#poolermonitoringconfiguration)* | The configuration of the monitoring infrastructure of this pooler.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | Template for the Service to be created | | | | - -#### PoolerStatus - -PoolerStatus defines the observed state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `secrets` *[PoolerSecrets](#poolersecrets)* | The resource version of the config object | | | | -| `instances` *integer* | The number of pods trying to be scheduled | | | | - -#### PoolerType - -*Underlying type:* *string* - -PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are `rw` and `ro`. - -*Validation:* - -- Enum: [rw ro r] - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -#### PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `parameters` *object (keys:string, values:string)* | PostgreSQL configuration options (postgresql.conf) | | | | -| `synchronous` *[SynchronousReplicaConfiguration](#synchronousreplicaconfiguration)* | Configuration of the PostgreSQL synchronous replication feature | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file) | | | | -| `pg_ident` *string array* | PostgreSQL User Name Maps rules (lines to be appended
to the pg_ident.conf file) | | | | -| `epas` *[EPASConfiguration](#epasconfiguration)* | EDB Postgres Advanced Server specific configurations | | | | -| `syncReplicaElectionConstraint` *[SyncReplicaElectionConstraints](#syncreplicaelectionconstraints)* | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be
set up. | | | | -| `shared_preload_libraries` *string array* | Lists of shared preload libraries to add to the default ones | | | | -| `ldap` *[LDAPConfig](#ldapconfig)* | Options to specify LDAP configuration | | | | -| `promotionTimeout` *integer* | 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 | | | | -| `enableAlterSystem` *boolean* | If this parameter is true, the user will be able to invoke `ALTER SYSTEM`
on this {{name.ln}} Cluster.
This should only be used for debugging and troubleshooting.
Defaults to false. | | | | -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | - -#### PrimaryUpdateMethod - -*Underlying type:* *string* - -PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `switchover` | PrimaryUpdateMethodSwitchover means that the operator will switchover to another updated
replica when it needs to upgrade the primary instance.
Note: when using this method, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process.
| -| `restart` | PrimaryUpdateMethodRestart means that the operator will restart the primary instance in-place
when it needs to upgrade it
| - -#### PrimaryUpdateStrategy - -*Underlying type:* *string* - -PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `supervised` | PrimaryUpdateStrategySupervised means that the operator need to wait for the
user to manually issue a switchover request before updating the primary
server (`supervised`)
| -| `unsupervised` | PrimaryUpdateStrategyUnsupervised means that the operator will proceed with the
selected PrimaryUpdateMethod to another updated replica and then automatically update
the primary server (`unsupervised`, default)
| - -#### Probe - -Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic. - -*Appears in:* - -- [LivenessProbe](#livenessprobe) -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | - -#### ProbeStrategyType - -*Underlying type:* *string* - -ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready - -*Appears in:* - -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `pg_isready` | ProbeStrategyPgIsReady means that the pg_isready tool is used to determine
whether PostgreSQL is started up
| -| `streaming` | ProbeStrategyStreaming means that pg_isready is positive and the replica is
connected via streaming replication to the current primary and the lag is, if specified,
within the limit.
| -| `query` | ProbeStrategyQuery means that the server is able to connect to the superuser database
and able to execute a simple query like "-- ping"
| - -#### ProbeWithStrategy - -ProbeWithStrategy is the configuration of the startup probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------------------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `type` *[ProbeStrategyType](#probestrategytype)* | The probe strategy | | | Enum: [pg_isready streaming query]
| -| `maximumLag` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Lag limit. Used only for `streaming` strategy | | | | - -#### ProbesConfiguration - -ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `startup` *[ProbeWithStrategy](#probewithstrategy)* | The startup probe configuration | True | | | -| `liveness` *[LivenessProbe](#livenessprobe)* | The liveness probe configuration | True | | | -| `readiness` *[ProbeWithStrategy](#probewithstrategy)* | The readiness probe configuration | True | | | - -#### Publication - -Publication is the Schema for the publications API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Publication` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PublicationSpec](#publicationspec)* | | True | | | -| `status` *[PublicationStatus](#publicationstatus)* | | True | | | - -#### PublicationReclaimPolicy - -*Underlying type:* *string* - -PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications. - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | PublicationReclaimDelete means the publication will be deleted from Kubernetes on release
from its claim.
| -| `retain` | PublicationReclaimRetain means the publication will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### PublicationSpec - -PublicationSpec defines the desired state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "publisher" | True | | | -| `name` *string* | The name of the publication inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "publisher" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Publication parameters part of the `WITH` clause as expected by
PostgreSQL `CREATE PUBLICATION` command | | | | -| `target` *[PublicationTarget](#publicationtarget)* | Target of the publication as expected by PostgreSQL `CREATE PUBLICATION` command | True | | | -| `publicationReclaimPolicy` *[PublicationReclaimPolicy](#publicationreclaimpolicy)* | The policy for end-of-life maintenance of this publication | | retain | Enum: [delete retain]
| - -#### PublicationStatus - -PublicationStatus defines the observed state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the publication was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### PublicationTarget - -PublicationTarget is what this publication should publish - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------- | -| `allTables` *boolean* | Marks the publication as one that replicates changes for all tables
in the database, including tables created in the future.
Corresponding to `FOR ALL TABLES` in PostgreSQL. | | | | -| `objects` *[PublicationTargetObject](#publicationtargetobject) array* | Just the following schema objects | | | MaxItems: 100000
| - -#### PublicationTargetObject - -PublicationTargetObject is an object to publish - -*Appears in:* - -- [PublicationTarget](#publicationtarget) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `tablesInSchema` *string* | Marks the publication as one that replicates changes for all tables
in the specified list of schemas, including tables created in the
future. Corresponding to `FOR TABLES IN SCHEMA` in PostgreSQL. | | | | -| `table` *[PublicationTargetTable](#publicationtargettable)* | Specifies a list of tables to add to the publication. Corresponding
to `FOR TABLE` in PostgreSQL. | | | | - -#### PublicationTargetTable - -PublicationTargetTable is a table to publish - -*Appears in:* - -- [PublicationTargetObject](#publicationtargetobject) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `only` *boolean* | Whether to limit to the table only or include all its descendants | | | | -| `name` *string* | The table name | True | | | -| `schema` *string* | The schema name | | | | -| `columns` *string array* | The columns to publish | | | | - -#### RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backupID` *string* | 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. | | | | -| `targetTLI` *string* | The target timeline ("latest" or a positive integer) | | | | -| `targetXID` *string* | The target transaction ID | | | | -| `targetName` *string* | The target name (to be previously created
with `pg_create_restore_point`) | | | | -| `targetLSN` *string* | The target LSN (Log Sequence Number) | | | | -| `targetTime` *string* | The target time as a timestamp in the RFC3339 standard | | | | -| `targetImmediate` *boolean* | End recovery as soon as a consistent state is reached | | | | -| `exclusive` *boolean* | Set the target to be exclusive. If omitted, defaults to false, so that
in Postgres, `recovery_target_inclusive` will be true | | | | - -#### ReplicaClusterConfiguration - -ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------- | -| `self` *string* | Self defines the name of this cluster. It is used to determine if this is a primary
or a replica cluster, comparing it with `primary` | | | | -| `primary` *string* | Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the
topology specified in externalClusters | | | | -| `source` *string* | The name of the external cluster which is the replication origin | True | | MinLength: 1
| -| `enabled` *boolean* | 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. | | | | -| `promotionToken` *string* | A demotion token generated by an external cluster used to
check if the promotion requirements are met. | | | | -| `minApplyDelay` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | When replica mode is enabled, this parameter allows you to replay
transactions only when the system time is at least the configured
time past the commit time. This provides an opportunity to correct
data loss errors. Note that when this parameter is set, a promotion
token cannot be used. | | | | - -#### ReplicationSlotsConfiguration - -ReplicationSlotsConfiguration encapsulates the configuration -of replication slots - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------- | -| `highAvailability` *[ReplicationSlotsHAConfiguration](#replicationslotshaconfiguration)* | Replication slots for high availability configuration | | | | -| `updateInterval` *integer* | Standby will update the status of the local replication slots
every `updateInterval` seconds (default 30). | | | Minimum: 1
| -| `synchronizeReplicas` *[SynchronizeReplicasConfiguration](#synchronizereplicasconfiguration)* | Configures the synchronization of the user defined physical replication slots | | | | - -#### 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. - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------ | -| `enabled` *boolean* | 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. | | | | -| `slotPrefix` *string* | 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_`. | | | Pattern: `^[0-9a-z_]*$`
| -| `synchronizeLogicalDecoding` *boolean* | When enabled, the operator automatically manages synchronization of logical
decoding (replication) slots across high-availability clusters.
Requires one of the following conditions:
- PostgreSQL version 17 or later
- PostgreSQL version < 17 with pg_failover_slots extension enabled | | | | - -#### 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: - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the role | True | | | -| `comment` *string* | Description of the role | | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the role is `present` or `absent` - defaults to "present" | | present | Enum: [present absent]
| -| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present)
If null, the password will be ignored unless DisablePassword is set | | | | -| `connectionLimit` *integer* | If the role can log in, this specifies how many concurrent
connections the role can make. `-1` (the default) means no limit. | | -1 | | -| `validUntil` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Date and time after which the role's password is no longer valid.
When omitted, the password will never expire (default). | | | | -| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty. | | | | -| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Defaults is `true`. | | true | | -| `disablePassword` *boolean* | DisablePassword indicates that a role's password should be set to NULL in Postgres | | | | -| `superuser` *boolean* | 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`. | | | | -| `createdb` *boolean* | 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. | | | | -| `createrole` *boolean* | 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`. | | | | -| `login` *boolean* | 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`. | | | | -| `replication` *boolean* | 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`. | | | | -| `bypassrls` *boolean* | Whether a role bypasses every row-level security (RLS) policy.
Default is `false`. | | | | - -#### RoleStatus - -*Underlying type:* *string* - -RoleStatus represents the status of a managed role in the cluster - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | -| ------------------------ | ----------------------------------------------------------------------------------------------------- | -| `reconciled` | RoleStatusReconciled indicates the role in DB matches the Spec
| -| `not-managed` | RoleStatusNotManaged indicates the role is not in the Spec, therefore not managed
| -| `pending-reconciliation` | RoleStatusPendingReconciliation indicates the role in Spec requires updated/creation in DB
| -| `reserved` | RoleStatusReserved indicates this is one of the roles reserved by the operator. E.g. `postgres`
| - -#### SQLRefs - -SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------- | ------- | ---------- | -| `secretRefs` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | SecretRefs holds a list of references to Secrets | | | | -| `configMapRefs` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | ConfigMapRefs holds a list of references to ConfigMaps | | | | - -#### ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ScheduledBackup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ScheduledBackupSpec](#scheduledbackupspec)* | Specification of the desired behavior of the ScheduledBackup.
More info: | True | | | -| `status` *[ScheduledBackupStatus](#scheduledbackupstatus)* | Most recently observed status of the ScheduledBackup. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `suspend` *boolean* | If this backup is suspended or not | | | | -| `immediate` *boolean* | If the first backup has to be immediately start after creation or not | | | | -| `schedule` *string* | The schedule does not follow the same format used in Kubernetes CronJobs
as it includes an additional seconds specifier,
see | True | | | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `backupOwnerReference` *string* | 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
| | none | Enum: [none self cluster]
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `lastCheckTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | The latest time the schedule | | | | -| `lastScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Information when was the last time that backup was successfully scheduled. | | | | -| `nextScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Next time we will run a backup | | | | - -#### SchemaSpec - -SchemaSpec configures a schema in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `owner` *string* | The role name of the user who owns the schema inside PostgreSQL.
It maps to the `AUTHORIZATION` parameter of `CREATE SCHEMA` and the
`OWNER TO` command of `ALTER SCHEMA`. | True | | | - -#### SecretVersion - -SecretVersion contains a secret name and its ResourceVersion - -*Appears in:* - -- [PgBouncerSecrets](#pgbouncersecrets) -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| ------------------ | --------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the secret | | | | -| `version` *string* | The ResourceVersion of the secret | | | | - -#### SecretsResourceVersion - -SecretsResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `superuserSecretVersion` *string* | The resource version of the "postgres" user secret | | | | -| `replicationSecretVersion` *string* | The resource version of the "streaming_replica" user secret | | | | -| `applicationSecretVersion` *string* | The resource version of the "app" user secret | | | | -| `managedRoleSecretVersion` *object (keys:string, values:string)* | The resource versions of the managed roles secrets | | | | -| `caSecretVersion` *string* | Unused. Retained for compatibility with old versions. | | | | -| `clientCaSecretVersion` *string* | The resource version of the PostgreSQL client-side CA secret version | | | | -| `serverCaSecretVersion` *string* | The resource version of the PostgreSQL server-side CA secret version | | | | -| `serverSecretVersion` *string* | The resource version of the PostgreSQL server-side secret version | | | | -| `barmanEndpointCA` *string* | The resource version of the Barman Endpoint CA if provided | | | | -| `externalClusterSecretVersion` *object (keys:string, values:string)* | The resource versions of the external cluster secrets | | | | -| `metrics` *object (keys:string, values:string)* | A map with the versions of all the secrets used to pass metrics.
Map keys are the secret names, map values are the versions | | | | - -#### ServerSpec - -ServerSpec configures a server of a foreign data wrapper - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `fdw` *string* | The name of the Foreign Data Wrapper (FDW) | True | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the server
(key is the option name, value is the option value). | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the server are granted or revoked. | | | | - -#### ServiceAccountTemplate - -ServiceAccountTemplate contains the template needed to generate the service accounts - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | - -#### ServiceSelectorType - -*Underlying type:* *string* - -ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only - -*Validation:* - -- Enum: [rw r ro] - -*Appears in:* - -- [ManagedService](#managedservice) -- [ManagedServices](#managedservices) - -| Field | Description | -| ----- | ----------------------------------------------------------- | -| `rw` | ServiceSelectorTypeRW selects the read-write service.
| -| `r` | ServiceSelectorTypeR selects the read service.
| -| `ro` | ServiceSelectorTypeRO selects the read-only service.
| - -#### ServiceTemplateSpec - -ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation. - -*Appears in:* - -- [ManagedService](#managedservice) -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[ServiceSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#servicespec-v1-core)* | Specification of the desired behavior of the service.
More info: | | | | - -#### ServiceUpdateStrategy - -*Underlying type:* *string* - -ServiceUpdateStrategy describes how the changes to the managed service should be handled - -*Validation:* - -- Enum: [patch replace] - -*Appears in:* - -- [ManagedService](#managedservice) - -#### SnapshotOwnerReference - -*Underlying type:* *string* - -SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to. - -*Appears in:* - -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | -| --------- | ------------------------------------------------------------------------------------------------- | -| `none` | SnapshotOwnerReferenceNone indicates that the snapshot does not have any owner reference.
| -| `backup` | SnapshotOwnerReferenceBackup indicates that the snapshot is owned by the backup resource.
| -| `cluster` | SnapshotOwnerReferenceCluster indicates that the snapshot is owned by the cluster resource.
| - -#### SnapshotType - -*Underlying type:* *string* - -SnapshotType is a type of allowed import - -*Appears in:* - -- [Import](#import) - -| Field | Description | -| -------------- | ----------------------------------------------------------------------------------- | -| `monolith` | MonolithSnapshotType indicates to execute the monolith clone typology
| -| `microservice` | MicroserviceSnapshotType indicates to execute the microservice clone typology
| - -#### StorageConfiguration - -StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `storageClass` *string* | 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` *string* | 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. | | | | -| `resizeInUseVolumes` *boolean* | Resize existent PVCs, defaults to true | | true | | -| `pvcTemplate` *[PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#persistentvolumeclaimspec-v1-core)* | Template to be used to generate the Persistent Volume Claim | | | | - -#### Subscription - -Subscription is the Schema for the subscriptions API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Subscription` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[SubscriptionSpec](#subscriptionspec)* | | True | | | -| `status` *[SubscriptionStatus](#subscriptionstatus)* | | True | | | - -#### SubscriptionReclaimPolicy - -*Underlying type:* *string* - -SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions. - -*Appears in:* - -- [SubscriptionSpec](#subscriptionspec) - -| Field | Description | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `delete` | SubscriptionReclaimDelete means the subscription will be deleted from Kubernetes on release
from its claim.
| -| `retain` | SubscriptionReclaimRetain means the subscription will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### SubscriptionSpec - -SubscriptionSpec defines the desired state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "subscriber" | True | | | -| `name` *string* | The name of the subscription inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "subscriber" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Subscription parameters included in the `WITH` clause of the PostgreSQL
`CREATE SUBSCRIPTION` command. Most parameters cannot be changed
after the subscription is created and will be ignored if modified
later, except for a limited set documented at:
| | | | -| `publicationName` *string* | The name of the publication inside the PostgreSQL database in the
"publisher" | True | | | -| `publicationDBName` *string* | The name of the database containing the publication on the external
cluster. Defaults to the one in the external cluster definition. | | | | -| `externalClusterName` *string* | The name of the external cluster with the publication ("publisher") | True | | | -| `subscriptionReclaimPolicy` *[SubscriptionReclaimPolicy](#subscriptionreclaimpolicy)* | The policy for end-of-life maintenance of this subscription | | retain | Enum: [delete retain]
| - -#### SubscriptionStatus - -SubscriptionStatus defines the observed state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the subscription was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### SwitchReplicaClusterStatus - -SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `inProgress` *boolean* | InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster. | | | | - -#### 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. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `nodeLabelsAntiAffinity` *string array* | A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not | | | | -| `enabled` *boolean* | This flag enables the constraints for sync replicas | True | | | - -#### SynchronizeReplicasConfiguration - -SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | When set to true, every replication slot that is on the primary is synchronized on each standby | True | | | -| `excludePatterns` *string array* | List of regular expression patterns to match the names of replication slots to be excluded (by default empty) | | | | - -#### SynchronousReplicaConfiguration - -SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also `.spec.minSyncReplicas` and `.spec.maxSyncReplicas` -need to be considered. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------- | -| `method` *[SynchronousReplicaConfigurationMethod](#synchronousreplicaconfigurationmethod)* | Method to select synchronous replication standbys from the listed
servers, accepting 'any' (quorum-based synchronous replication) or
'first' (priority-based synchronous replication) as values. | True | | Enum: [any first]
| -| `number` *integer* | Specifies the number of synchronous standby servers that
transactions must wait for responses from. | True | | | -| `maxStandbyNamesFromCluster` *integer* | Specifies the maximum number of local cluster pods that can be
automatically included in the `synchronous_standby_names` option in
PostgreSQL. | | | | -| `standbyNamesPre` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` before local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `standbyNamesPost` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` after local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `dataDurability` *[DataDurabilityLevel](#datadurabilitylevel)* | If set to "required", data durability is strictly enforced. Write operations
with synchronous commit settings (`on`, `remote_write`, or `remote_apply`) will
block if there are insufficient healthy replicas, ensuring data persistence.
If set to "preferred", data durability is maintained when healthy replicas
are available, but the required number of instances will adjust dynamically
if replicas become unavailable. This setting relaxes strict durability enforcement
to allow for operational continuity. This setting is only applicable if both
`standbyNamesPre` and `standbyNamesPost` are unset (empty). | | | Enum: [required preferred]
| -| `failoverQuorum` *boolean* | FailoverQuorum enables a quorum-based check before failover, improving
data durability and safety during failover events in {{name.ln}}-managed
PostgreSQL clusters. | | | | - -#### SynchronousReplicaConfigurationMethod - -*Underlying type:* *string* - -SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -#### TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -*Appears in:* - -- [EPASConfiguration](#epasconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | True if we want to have TDE enabled | | | | -| `secretKeyRef` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Reference to the secret that contains the encryption key | | | | -| `wrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | WrapCommand is the encrypt command provided by the user | | | | -| `unwrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | UnwrapCommand is the decryption command provided by the user | | | | -| `passphraseCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | PassphraseCommand is the command executed to get the passphrase that will be
passed to the OpenSSL command to encrypt and decrypt | | | | - -#### TablespaceConfiguration - -TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the tablespace | True | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | The storage configuration for the tablespace | True | | | -| `owner` *[DatabaseRoleRef](#databaseroleref)* | Owner is the PostgreSQL user owning the tablespace | | | | -| `temporary` *boolean* | When set to true, the tablespace will be added as a `temp_tablespaces`
entry 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. | | false | | - -#### TablespaceState - -TablespaceState represents the state of a tablespace in a cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | -------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the tablespace | True | | | -| `owner` *string* | Owner is the PostgreSQL user owning the tablespace | | | | -| `state` *[TablespaceStatus](#tablespacestatus)* | State is the latest reconciliation state | True | | | -| `error` *string* | Error is the reconciliation error, if any | | | | - -#### TablespaceStatus - -*Underlying type:* *string* - -TablespaceStatus represents the status of a tablespace in the cluster - -*Appears in:* - -- [TablespaceState](#tablespacestate) - -| Field | Description | -| ------------ | -------------------------------------------------------------------------------------------------------- | -| `reconciled` | TablespaceStatusReconciled indicates the tablespace in DB matches the Spec
| -| `pending` | TablespaceStatusPendingReconciliation indicates the tablespace in Spec requires creation in the DB
| - -#### Topology - -Topology contains the cluster topology - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *object (keys:[PodName](#podname), values:[PodTopologyLabels](#podtopologylabels))* | Instances contains the pod topology of the instances | | | | -| `nodesUsed` *integer* | 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` *boolean* | SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors
in synchronous replica election in case of failures | | | | - -#### UsageSpec - -UsageSpec configures a usage for a foreign data wrapper - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------- | -------- | ------- | --------------------------- | -| `name` *string* | Name of the usage | True | | | -| `type` *[UsageSpecType](#usagespectype)* | The type of usage | | grant | Enum: [grant revoke]
| - -#### UsageSpecType - -*Underlying type:* *string* - -UsageSpecType describes the type of usage specified in the `usage` field of the -`Database` object. - -*Appears in:* - -- [UsageSpec](#usagespec) - -| Field | Description | -| -------- | -------------------------------------------------------------------------------------------------------- | -| `grant` | GrantUsageSpecType indicates a grant usage permission.
The default usage permission is grant.
| -| `revoke` | RevokeUsageSpecType indicates a revoke usage permission.
| - -#### VolumeSnapshotConfiguration - -VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups. - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------- | ---------------------------------- | -| `labels` *object (keys:string, values:string)* | Labels are key-value pairs that will be added to .metadata.labels snapshot resources. | | | | -| `annotations` *object (keys:string, values:string)* | Annotations key-value pairs that will be added to .metadata.annotations snapshot resources. | | | | -| `className` *string* | 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` *string* | WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim. | | | | -| `tablespaceClassName` *object (keys:string, values:string)* | TablespaceClassName specifies the Snapshot Class to be used for the tablespaces.
defaults to the PGDATA Snapshot Class, if set | | | | -| `snapshotOwnerReference` *[SnapshotOwnerReference](#snapshotownerreference)* | SnapshotOwnerReference indicates the type of owner reference the snapshot should have | | none | Enum: [none cluster backup]
| -| `online` *boolean* | Whether the default type of backup with volume snapshots is
online/hot (`true`, default) or offline/cold (`false`) | | true | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots | | { immediateCheckpoint:false waitForArchive:true } | | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.28.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.28.1.mdx deleted file mode 100644 index edf180deed7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.28.1.mdx +++ /dev/null @@ -1,2350 +0,0 @@ ---- -title: API Reference - v1.28.1 -navTitle: v1.28.1 -pdfExclude: 'true' - ---- - -## Packages - -- [postgresql.k8s.enterprisedb.io/v1](#postgresqlk8senterprisedbiov1) - -## postgresql.k8s.enterprisedb.io/v1 - -Package v1 contains API Schema definitions for the postgresql v1 API group - -### Resource Types - -- [Backup](#backup) -- [Cluster](#cluster) -- [ClusterImageCatalog](#clusterimagecatalog) -- [Database](#database) -- [FailoverQuorum](#failoverquorum) -- [ImageCatalog](#imagecatalog) -- [Pooler](#pooler) -- [Publication](#publication) -- [ScheduledBackup](#scheduledbackup) -- [Subscription](#subscription) - -#### AffinityConfiguration - -AffinityConfiguration contains the info we need to create the -affinity rules for Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `enablePodAntiAffinity` *boolean* | Activates anti-affinity for the pods. The operator will define pods
anti-affinity unless this field is explicitly set to false | | | | -| `topologyKey` *string* | TopologyKey to use for anti-affinity configuration. See k8s documentation
for more info on that | | | | -| `nodeSelector` *object (keys:string, values:string)* | NodeSelector is map of key-value pairs used to define the nodes on which
the pods can run.
More info: | | | | -| `nodeAffinity` *[NodeAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#nodeaffinity-v1-core)* | NodeAffinity describes node affinity scheduling rules for the pod.
More info: | | | | -| `tolerations` *[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#toleration-v1-core) array* | 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: | | | | -| `podAntiAffinityType` *string* | 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:
| | | | -| `additionalPodAntiAffinity` *[PodAntiAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podantiaffinity-v1-core)* | 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` *[PodAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podaffinity-v1-core)* | AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods. | | | | - -#### AvailableArchitecture - -AvailableArchitecture represents the state of a cluster's architecture - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------- | ------------------------------------------------- | -------- | ------- | ---------- | -| `goArch` *string* | GoArch is the name of the executable architecture | True | | | -| `hash` *string* | Hash is the hash of the executable | True | | | - -#### Backup - -A Backup resource is a request for a PostgreSQL backup by the user. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Backup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[BackupSpec](#backupspec)* | Specification of the desired behavior of the backup.
More info: | True | | | -| `status` *[BackupStatus](#backupstatus)* | Most recently observed status of the backup. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### BackupConfiguration - -BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `volumeSnapshot` *[VolumeSnapshotConfiguration](#volumesnapshotconfiguration)* | VolumeSnapshot provides the configuration for the execution of volume snapshot backups. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `retentionPolicy` *string* | 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. | | | Pattern: `^[1-9][0-9]*[dwm]$`
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| - -#### BackupMethod - -*Underlying type:* *string* - -BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance - -*Appears in:* - -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [ClusterStatus](#clusterstatus) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | -| ------------------- | -------------------------------------------------------------------------------------------- | -| `volumeSnapshot` | BackupMethodVolumeSnapshot means using the volume snapshot
Kubernetes feature
| -| `barmanObjectStore` | BackupMethodBarmanObjectStore means using barman to backup the
PostgreSQL cluster
| -| `plugin` | BackupMethodPlugin means that this backup should be handled by
a plugin
| - -#### BackupPhase - -*Underlying type:* *string* - -BackupPhase is the phase of the backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -#### BackupPluginConfiguration - -BackupPluginConfiguration contains the backup configuration used by -the backup plugin - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin managing this backup | True | | | -| `parameters` *object (keys:string, values:string)* | Parameters are the configuration parameters passed to the backup
plugin for this backup | | | | - -#### BackupSnapshotElementStatus - -BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup - -*Appears in:* - -- [BackupSnapshotStatus](#backupsnapshotstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the snapshot resource name | True | | | -| `type` *string* | Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE | True | | | -| `tablespaceName` *string* | TablespaceName is the name of the snapshotted tablespace. Only set
when type is PG_TABLESPACE | | | | - -#### BackupSnapshotStatus - -BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `elements` *[BackupSnapshotElementStatus](#backupsnapshotelementstatus) array* | The elements list, populated with the gathered volume snapshots | | | | - -#### BackupSource - -BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name of the referent. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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 - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### BackupStatus - -BackupStatus defines the observed state of Backup - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `googleCredentials` *[GoogleCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#GoogleCredentials)* | The credentials to use to upload data to Google Cloud Storage | | | | -| `s3Credentials` *[S3Credentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#S3Credentials)* | The credentials to use to upload data to S3 | | | | -| `azureCredentials` *[AzureCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#AzureCredentials)* | The credentials to use to upload data to Azure Blob Storage | | | | -| `majorVersion` *integer* | The PostgreSQL major version that was running when the
backup was taken. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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` *string* | Endpoint to be used to upload data to the cloud,
overriding the automatic endpoint discovery | | | | -| `destinationPath` *string* | 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. | | | | -| `serverName` *string* | The server name on S3, the cluster name is used if this
parameter is omitted | | | | -| `encryption` *string* | Encryption method required to S3 API | | | | -| `backupId` *string* | The ID of the Barman backup | | | | -| `backupName` *string* | The Name of the Barman backup | | | | -| `phase` *[BackupPhase](#backupphase)* | The last backup status | | | | -| `startedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup was started | | | | -| `stoppedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup was terminated | | | | -| `beginWal` *string* | The starting WAL | | | | -| `endWal` *string* | The ending WAL | | | | -| `beginLSN` *string* | The starting xlog | | | | -| `endLSN` *string* | The ending xlog | | | | -| `error` *string* | The detected error | | | | -| `commandOutput` *string* | Unused. Retained for compatibility with old versions. | | | | -| `commandError` *string* | The backup command output in case of error | | | | -| `backupLabelFile` *integer array* | Backup label file content as returned by Postgres in case of online (hot) backups | | | | -| `tablespaceMapFile` *integer array* | Tablespace map file content as returned by Postgres in case of online (hot) backups | | | | -| `instanceID` *[InstanceID](#instanceid)* | Information to identify the instance where the backup has been taken from | | | | -| `snapshotBackupStatus` *[BackupSnapshotStatus](#backupsnapshotstatus)* | Status of the volumeSnapshot backup | | | | -| `method` *[BackupMethod](#backupmethod)* | The backup method being used | | | | -| `online` *boolean* | Whether the backup was online/hot (`true`) or offline/cold (`false`) | | | | -| `pluginMetadata` *object (keys:string, values:string)* | A map containing the plugin metadata | | | | - -#### BackupTarget - -*Underlying type:* *string* - -BackupTarget describes the preferred targets for a backup - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initdb` *[BootstrapInitDB](#bootstrapinitdb)* | Bootstrap the cluster via initdb | | | | -| `recovery` *[BootstrapRecovery](#bootstraprecovery)* | Bootstrap the cluster from a backup | | | | -| `pg_basebackup` *[BootstrapPgBaseBackup](#bootstrappgbasebackup)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | -| `redwood` *boolean* | If we need to enable/disable Redwood compatibility. Requires
EPAS and for EPAS defaults to true | | | | -| `options` *string array* | 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. | | | | -| `dataChecksums` *boolean* | Whether the `-k` option should be passed to initdb,
enabling checksums on data pages (default: `false`) | | | | -| `encoding` *string* | The value to be passed as option `--encoding` for initdb (default:`UTF8`) | | | | -| `localeCollate` *string* | The value to be passed as option `--lc-collate` for initdb (default:`C`) | | | | -| `localeCType` *string* | The value to be passed as option `--lc-ctype` for initdb (default:`C`) | | | | -| `locale` *string* | Sets the default collation order and character classification in the new database. | | | | -| `localeProvider` *string* | This option sets the locale provider for databases created in the new cluster.
Available from PostgreSQL 16. | | | | -| `icuLocale` *string* | Specifies the ICU locale when the ICU provider is used.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Specifies additional collation rules to customize the behavior of the default collation.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Specifies the locale name when the builtin provider is used.
This option requires `localeProvider` to be set to `builtin`.
Available from PostgreSQL 17. | | | | -| `walSegmentSize` *integer* | The value in megabytes (1 to 1024) to be passed to the `--wal-segsize`
option for initdb (default: empty, resulting in PostgreSQL default: 16MB) | | | Maximum: 1024
Minimum: 1
| -| `postInitSQL` *string array* | List of SQL queries to be executed as a superuser in the `postgres`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitApplicationSQL` *string array* | List of SQL queries to be executed as a superuser in the application
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitTemplateSQL` *string array* | List of SQL queries to be executed as a superuser in the `template1`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `import` *[Import](#import)* | Bootstraps the new cluster by importing data from an existing PostgreSQL
instance using logical backup (`pg_dump` and `pg_restore`) | | | | -| `postInitApplicationSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the application database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitTemplateSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `template1` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `postgres` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | - -#### BootstrapPgBaseBackup - -BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ------------------- | -| `source` *string* | The name of the server of which we need to take a physical backup | True | | MinLength: 1
| -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backup` *[BackupSource](#backupsource)* | The backup object containing the physical base backup from which to
initiate the recovery procedure.
Mutually exclusive with `source` and `volumeSnapshots`. | | | | -| `source` *string* | 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`. | | | | -| `volumeSnapshots` *[DataSource](#datasource)* | 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 {{name.ln}}, 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`. | | | | -| `recoveryTarget` *[RecoveryTarget](#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: | | | | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | - -#### CatalogImage - -CatalogImage defines the image and major version - -*Appears in:* - -- [ImageCatalogSpec](#imagecatalogspec) - -| Field | Description | Required | Default | Validation | -| ----------------- | ----------------------------------------------------------------------------- | -------- | ------- | ------------------ | -| `image` *string* | The image reference | True | | | -| `major` *integer* | The PostgreSQL major version of the image. Must be unique within the catalog. | True | | Minimum: 10
| - -#### CertificatesConfiguration - -CertificatesConfiguration contains the needed configurations to handle server certificates. - -*Appears in:* - -- [CertificatesStatus](#certificatesstatus) -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | - -#### CertificatesStatus - -CertificatesStatus contains configuration certificates and related expiration dates. - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | -| `expirations` *object (keys:string, values:string)* | Expiration dates for all certificates. | | | | - -#### Cluster - -Cluster defines the API schema for a highly available PostgreSQL database cluster -managed by {{name.ln}}. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Cluster` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ClusterSpec](#clusterspec)* | Specification of the desired behavior of the cluster.
More info: | True | | | -| `status` *[ClusterStatus](#clusterstatus)* | Most recently observed status of the cluster. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ClusterImageCatalog - -ClusterImageCatalog is the Schema for the clusterimagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ClusterImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ClusterImageCatalog.
More info: | True | | | - -#### ClusterMonitoringTLSConfiguration - -ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring - -*Appears in:* - -- [MonitoringConfiguration](#monitoringconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------- | -------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Enable TLS for the monitoring endpoint.
Changing this option will force a rollout of all instances. | | false | | - -#### ClusterSpec - -ClusterSpec defines the desired state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ | --------------------------------------------- | -| `description` *string* | Description of this PostgreSQL cluster | | | | -| `inheritedMetadata` *[EmbeddedObjectMetadata](#embeddedobjectmetadata)* | Metadata that will be inherited by all objects related to the Cluster | | | | -| `imageName` *string* | Name of the container image, supporting both tags (`:`)
and digests for deterministic and repeatable deployments
(`:@sha256:`) | | | | -| `imageCatalogRef` *[ImageCatalogRef](#imagecatalogref)* | Defines the major PostgreSQL version we want to use within an ImageCatalog | | | | -| `imagePullPolicy` *[PullPolicy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#pullpolicy-v1-core)* | Image pull policy.
One of `Always`, `Never` or `IfNotPresent`.
If not defined, it defaults to `IfNotPresent`.
Cannot be updated.
More info: | | | | -| `schedulerName` *string* | 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:
| | | | -| `postgresUID` *integer* | The UID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `postgresGID` *integer* | The GID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `instances` *integer* | Number of instances required in the cluster | True | 1 | Minimum: 1
| -| `minSyncReplicas` *integer* | Minimum number of instances required in synchronous replication with the
primary. Undefined or 0 allow writes to complete when no standby is
available. | | 0 | Minimum: 0
| -| `maxSyncReplicas` *integer* | 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. | | 0 | Minimum: 0
| -| `postgresql` *[PostgresConfiguration](#postgresconfiguration)* | Configuration of the PostgreSQL server | | | | -| `replicationSlots` *[ReplicationSlotsConfiguration](#replicationslotsconfiguration)* | Replication slots management configuration | | | | -| `bootstrap` *[BootstrapConfiguration](#bootstrapconfiguration)* | Instructions to bootstrap this cluster | | | | -| `replica` *[ReplicaClusterConfiguration](#replicaclusterconfiguration)* | Replica cluster configuration | | | | -| `superuserSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The secret containing the superuser password. If not defined a new
secret will be created with a randomly generated password | | | | -| `enableSuperuserAccess` *boolean* | 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`. Disabled by default. | | | | -| `certificates` *[CertificatesConfiguration](#certificatesconfiguration)* | The configuration for the CA and related certificates | | | | -| `imagePullSecrets` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference) array* | 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. | | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage of the instances | | | | -| `serviceAccountTemplate` *[ServiceAccountTemplate](#serviceaccounttemplate)* | Configure the generation of the service account | | | | -| `walStorage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `ephemeralVolumeSource` *[EphemeralVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#ephemeralvolumesource-v1-core)* | EphemeralVolumeSource allows the user to configure the source of ephemeral volumes. | | | | -| `startDelay` *integer* | 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). | | 3600 | | -| `stopDelay` *integer* | The time in seconds that is allowed for a PostgreSQL instance to
gracefully shutdown (default 1800) | | 1800 | | -| `smartStopDelay` *integer* | Deprecated: please use SmartShutdownTimeout instead | | | | -| `smartShutdownTimeout` *integer* | 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`). Default is 180 seconds. | | 180 | | -| `switchoverDelay` *integer* | 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). | | 3600 | | -| `failoverDelay` *integer* | 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 | | 0 | | -| `livenessProbeTimeout` *integer* | 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` *[AffinityConfiguration](#affinityconfiguration)* | Affinity/Anti-affinity rules for Pods | | | | -| `topologySpreadConstraints` *[TopologySpreadConstraint](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#topologyspreadconstraint-v1-core) array* | TopologySpreadConstraints specifies how to spread matching pods among the given topology.
More info:
| | | | -| `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#resourcerequirements-v1-core)* | Resources requirements of every generated Pod. Please refer to

for more information. | | | | -| `ephemeralVolumesSizeLimit` *[EphemeralVolumesSizeLimitConfiguration](#ephemeralvolumessizelimitconfiguration)* | EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral
volumes | | | | -| `priorityClassName` *string* | 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

for more information | | | | -| `primaryUpdateStrategy` *[PrimaryUpdateStrategy](#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`) | | unsupervised | Enum: [unsupervised supervised]
| -| `primaryUpdateMethod` *[PrimaryUpdateMethod](#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).
Note: when using `switchover`, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process. | | | Enum: [switchover restart]
| -| `backup` *[BackupConfiguration](#backupconfiguration)* | The configuration to be used for backups | | | | -| `nodeMaintenanceWindow` *[NodeMaintenanceWindow](#nodemaintenancewindow)* | Define a maintenance window for the Kubernetes nodes | | | | -| `licenseKey` *string* | 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. | | | | -| `licenseKeySecret` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the license key. When this is set it take precedence over LicenseKey. | | | | -| `monitoring` *[MonitoringConfiguration](#monitoringconfiguration)* | The configuration of the monitoring infrastructure of this cluster | | | | -| `externalClusters` *[ExternalCluster](#externalcluster) array* | The list of external clusters which are used in the configuration | | | | -| `logLevel` *string* | The instances' log level, one of the following values: error, warning, info (default), debug, trace | | info | Enum: [error warning info debug trace]
| -| `projectedVolumeTemplate` *[ProjectedVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#projectedvolumesource-v1-core)* | Template to be used to define projected volumes, projected volumes will be mounted
under `/projected` base folder | | | | -| `env` *[EnvVar](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envvar-v1-core) array* | Env follows the Env format to pass environment variables
to the pods created in the cluster | | | | -| `envFrom` *[EnvFromSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envfromsource-v1-core) array* | EnvFrom follows the EnvFrom format to pass environment variables
sources to the pods to be used by Env | | | | -| `managed` *[ManagedConfiguration](#managedconfiguration)* | The configuration that is used by the portions of PostgreSQL that are managed by the instance manager | | | | -| `seccompProfile` *[SeccompProfile](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#seccompprofile-v1-core)* | The SeccompProfile applied to every Pod and Container.
Defaults to: `RuntimeDefault` | | | | -| `podSecurityContext` *[PodSecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podsecuritycontext-v1-core)* | Override the PodSecurityContext applied to every Pod of the cluster.
When set, this overrides the operator's default PodSecurityContext for the cluster.
If omitted, the operator defaults are used.
This field doesn't have any effect if SecurityContextConstraints are present. | | | | -| `securityContext` *[SecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#securitycontext-v1-core)* | Override the SecurityContext applied to every Container in the Pod of the cluster.
When set, this overrides the operator's default Container SecurityContext.
If omitted, the operator defaults are used. | | | | -| `tablespaces` *[TablespaceConfiguration](#tablespaceconfiguration) array* | The tablespaces configuration | | | | -| `enablePDB` *boolean* | 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 any
`PodDisruptionBudget` 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. | | true | | -| `plugins` *[PluginConfiguration](#pluginconfiguration) array* | The plugins configuration, containing
any plugin to be loaded with the corresponding configuration | | | | -| `probes` *[ProbesConfiguration](#probesconfiguration)* | The configuration of the probes to be injected
in the PostgreSQL Pods. | | | | - -#### ClusterStatus - -ClusterStatus defines the observed state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *integer* | The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods. | | | | -| `readyInstances` *integer* | The total number of ready instances in the cluster. It is equal to the number of ready instance pods. | | | | -| `instancesStatus` *object (keys:[PodStatus](#podstatus), values:string array)* | InstancesStatus indicates in which status the instances are | | | | -| `instancesReportedState` *object (keys:[PodName](#podname), values:[InstanceReportedState](#instancereportedstate))* | The reported state of the instances during the last reconciliation loop | | | | -| `managedRolesStatus` *[ManagedRoles](#managedroles)* | ManagedRolesStatus reports the state of the managed roles in the cluster | | | | -| `tablespacesStatus` *[TablespaceState](#tablespacestate) array* | TablespacesStatus reports the state of the declarative tablespaces in the cluster | | | | -| `timelineID` *integer* | The timeline of the Postgres cluster | | | | -| `topology` *[Topology](#topology)* | Instances topology. | | | | -| `latestGeneratedNode` *integer* | ID of the latest generated node (used to avoid node name clashing) | | | | -| `currentPrimary` *string* | Current primary instance | | | | -| `targetPrimary` *string* | Target primary instance, this is different from the previous one
during a switchover or a failover | | | | -| `lastPromotionToken` *string* | LastPromotionToken is the last verified promotion token that
was used to promote a replica cluster | | | | -| `pvcCount` *integer* | How many PVCs have been created by this cluster | | | | -| `jobCount` *integer* | How many Jobs have been created by this cluster | | | | -| `danglingPVC` *string array* | List of all the PVCs created by this cluster and still available
which are not attached to a Pod | | | | -| `resizingPVC` *string array* | List of all the PVCs that have ResizingPVC condition. | | | | -| `initializingPVC` *string array* | List of all the PVCs that are being initialized by this cluster | | | | -| `healthyPVC` *string array* | List of all the PVCs not dangling nor initializing | | | | -| `unusablePVC` *string array* | List of all the PVCs that are unusable because another PVC is missing | | | | -| `licenseStatus` *Status* | Status of the license | | | | -| `writeService` *string* | Current write pod | | | | -| `readService` *string* | Current list of read pods | | | | -| `phase` *string* | Current phase of the cluster | | | | -| `phaseReason` *string* | Reason for the current phase | | | | -| `secretsResourceVersion` *[SecretsResourceVersion](#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` *[ConfigMapResourceVersion](#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` *[CertificatesStatus](#certificatesstatus)* | The configuration for the CA and related certificates, initialized with defaults. | | | | -| `firstRecoverabilityPoint` *string* | The first recoverability point, stored as a date in RFC3339 format.
This field is calculated from the content of FirstRecoverabilityPointByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `firstRecoverabilityPointByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | The first recoverability point, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackup` *string* | Last successful backup, stored as a date in RFC3339 format.
This field is calculated from the content of LastSuccessfulBackupByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackupByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | Last successful backup, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastFailedBackup` *string* | Last failed backup, stored as a date in RFC3339 format.
Deprecated: the field is not set for backup plugins. | | | | -| `cloudNativePostgresqlCommitHash` *string* | The commit hash number of which this operator running | | | | -| `currentPrimaryTimestamp` *string* | The timestamp when the last actual promotion to primary has occurred | | | | -| `currentPrimaryFailingSinceTimestamp` *string* | The timestamp when the primary was detected to be unhealthy
This field is reported when `.spec.failoverDelay` is populated or during online upgrades | | | | -| `targetPrimaryTimestamp` *string* | The timestamp when the last request for a new primary has occurred | | | | -| `poolerIntegrations` *[PoolerIntegrations](#poolerintegrations)* | The integration needed by poolers referencing the cluster | | | | -| `cloudNativePostgresqlOperatorHash` *string* | The hash of the binary of the operator | | | | -| `availableArchitectures` *[AvailableArchitecture](#availablearchitecture) array* | AvailableArchitectures reports the available architectures of a cluster | | | | -| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for cluster object | | | | -| `instanceNames` *string array* | List of instance names in the cluster | | | | -| `onlineUpdateEnabled` *boolean* | OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster | | | | -| `image` *string* | Image contains the image name used by the pods | | | | -| `pgDataImageInfo` *[ImageInfo](#imageinfo)* | PGDataImageInfo contains the details of the latest image that has run on the current data directory. | | | | -| `pluginStatus` *[PluginStatus](#pluginstatus) array* | PluginStatus is the status of the loaded plugins | | | | -| `switchReplicaClusterStatus` *[SwitchReplicaClusterStatus](#switchreplicaclusterstatus)* | SwitchReplicaClusterStatus is the status of the switch to replica cluster | | | | -| `demotionToken` *string* | DemotionToken is a JSON token containing the information
from pg_controldata such as Database system identifier, Latest checkpoint's
TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO
WAL file, and Time of latest checkpoint | | | | -| `systemID` *string* | SystemID is the latest detected PostgreSQL SystemID | | | | - -#### ConfigMapResourceVersion - -ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metrics` *object (keys:string, values:string)* | 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 | | | | - -#### DataDurabilityLevel - -*Underlying type:* *string* - -DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are `required` or `preferred`. - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -| Field | Description | -| ----------- | ----------------------------------------------------------------------------------------------------------------------- | -| `required` | DataDurabilityLevelRequired means that data durability is strictly enforced
| -| `preferred` | DataDurabilityLevelPreferred means that data durability is enforced
only when healthy replicas are available
| - -#### DataSource - -DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `storage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage of the instances | True | | | -| `walStorage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `tablespaceStorage` *object (keys:string, values:[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core))* | Configuration of the storage for PostgreSQL tablespaces | | | | - -#### Database - -Database is the Schema for the databases API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Database` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[DatabaseSpec](#databasespec)* | Specification of the desired Database.
More info: | True | | | -| `status` *[DatabaseStatus](#databasestatus)* | Most recently observed status of the Database. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### DatabaseObjectSpec - -DatabaseObjectSpec contains the fields which are common to every -database object - -*Appears in:* - -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| - -#### DatabaseObjectStatus - -DatabaseObjectStatus is the status of the managed database objects - -*Appears in:* - -- [DatabaseStatus](#databasestatus) - -| Field | Description | Required | Default | Validation | -| ------------------- | ----------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the object | True | | | -| `applied` *boolean* | True of the object has been installed successfully in
the database | True | | | -| `message` *string* | Message is the object reconciliation message | | | | - -#### DatabaseReclaimPolicy - -*Underlying type:* *string* - -DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases. - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | DatabaseReclaimDelete means the database will be deleted from its PostgreSQL Cluster on release
from its claim.
| -| `retain` | DatabaseReclaimRetain means the database will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### DatabaseRoleRef - -DatabaseRoleRef is a reference an a role available inside PostgreSQL - -*Appears in:* - -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------- | ----------- | -------- | ------- | ---------- | -| `name` *string* | | | | | - -#### DatabaseSpec - -DatabaseSpec is the specification of a Postgresql Database, built around the -`CREATE DATABASE`, `ALTER DATABASE`, and `DROP DATABASE` SQL commands of -PostgreSQL. - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster hosting the database. | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the PostgreSQL database is `present` or `absent` - defaults to "present". | | present | Enum: [present absent]
| -| `name` *string* | The name of the database to create inside PostgreSQL. This setting cannot be changed. | True | | | -| `owner` *string* | Maps to the `OWNER` parameter of `CREATE DATABASE`.
Maps to the `OWNER TO` command of `ALTER DATABASE`.
The role name of the user who owns the database inside PostgreSQL. | True | | | -| `template` *string* | Maps to the `TEMPLATE` parameter of `CREATE DATABASE`. This setting
cannot be changed. The name of the template from which to create
this database. | | | | -| `encoding` *string* | Maps to the `ENCODING` parameter of `CREATE DATABASE`. This setting
cannot be changed. Character set encoding to use in the database. | | | | -| `locale` *string* | Maps to the `LOCALE` parameter of `CREATE DATABASE`. This setting
cannot be changed. Sets the default collation order and character
classification in the new database. | | | | -| `localeProvider` *string* | Maps to the `LOCALE_PROVIDER` parameter of `CREATE DATABASE`. This
setting cannot be changed. This option sets the locale provider for
databases created in the new cluster. Available from PostgreSQL 16. | | | | -| `localeCollate` *string* | Maps to the `LC_COLLATE` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `localeCType` *string* | Maps to the `LC_CTYPE` parameter of `CREATE DATABASE`. This setting
cannot be changed. | | | | -| `icuLocale` *string* | Maps to the `ICU_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the ICU locale when the ICU
provider is used. This option requires `localeProvider` to be set to
`icu`. Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Maps to the `ICU_RULES` parameter of `CREATE DATABASE`. This setting
cannot be changed. Specifies additional collation rules to customize
the behavior of the default collation. This option requires
`localeProvider` to be set to `icu`. Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Maps to the `BUILTIN_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the locale name when the
builtin provider is used. This option requires `localeProvider` to
be set to `builtin`. Available from PostgreSQL 17. | | | | -| `collationVersion` *string* | Maps to the `COLLATION_VERSION` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `isTemplate` *boolean* | Maps to the `IS_TEMPLATE` parameter of `CREATE DATABASE` and `ALTER
DATABASE`. If true, this database is considered a template and can
be cloned by any user with `CREATEDB` privileges. | | | | -| `allowConnections` *boolean* | Maps to the `ALLOW_CONNECTIONS` parameter of `CREATE DATABASE` and
`ALTER DATABASE`. If false then no one can connect to this database. | | | | -| `connectionLimit` *integer* | Maps to the `CONNECTION LIMIT` clause of `CREATE DATABASE` and
`ALTER DATABASE`. How many concurrent connections can be made to
this database. -1 (the default) means no limit. | | | | -| `tablespace` *string* | Maps to the `TABLESPACE` parameter of `CREATE DATABASE`.
Maps to the `SET TABLESPACE` command of `ALTER DATABASE`.
The name of the tablespace (in PostgreSQL) that will be associated
with the new database. This tablespace will be the default
tablespace used for objects created in this database. | | | | -| `databaseReclaimPolicy` *[DatabaseReclaimPolicy](#databasereclaimpolicy)* | The policy for end-of-life maintenance of this database. | | retain | Enum: [delete retain]
| -| `schemas` *[SchemaSpec](#schemaspec) array* | The list of schemas to be managed in the database | | | | -| `extensions` *[ExtensionSpec](#extensionspec) array* | The list of extensions to be managed in the database | | | | -| `fdws` *[FDWSpec](#fdwspec) array* | The list of foreign data wrappers to be managed in the database | | | | -| `servers` *[ServerSpec](#serverspec) array* | The list of foreign servers to be managed in the database | | | | - -#### DatabaseStatus - -DatabaseStatus defines the observed state of Database - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the database was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | -| `schemas` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Schemas is the status of the managed schemas | | | | -| `extensions` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Extensions is the status of the managed extensions | | | | -| `fdws` *[DatabaseObjectStatus](#databaseobjectstatus) array* | FDWs is the status of the managed FDWs | | | | -| `servers` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Servers is the status of the managed servers | | | | - -#### EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `audit` *boolean* | If true enables edb_audit logging | | | | -| `tde` *[TDEConfiguration](#tdeconfiguration)* | TDE configuration | | | | - -#### EmbeddedObjectMetadata - -EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `labels` *object (keys:string, values:string)* | | | | | -| `annotations` *object (keys:string, values:string)* | | | | | - -#### EnsureOption - -*Underlying type:* *string* - -EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance - -*Appears in:* - -- [DatabaseObjectSpec](#databaseobjectspec) -- [DatabaseSpec](#databasespec) -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [OptionSpec](#optionspec) -- [RoleConfiguration](#roleconfiguration) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | -| --------- | ----------- | -| `present` | | -| `absent` | | - -#### EphemeralVolumesSizeLimitConfiguration - -EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------ | -------- | ------- | ---------- | -| `shm` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Shm is the size limit of the shared memory volume | | | | -| `temporaryData` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | TemporaryData is the size limit of the temporary data volume | | | | - -#### ExtensionConfiguration - -ExtensionConfiguration is the configuration used to add -PostgreSQL extensions to the Cluster. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | --------------------------------------------------------------------- | -| `name` *string* | The name of the extension, required | True | | MinLength: 1
Pattern: `^[a-z0-9]([-a-z0-9_]*[a-z0-9])?$`
| -| `image` *[ImageVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#imagevolumesource-v1-core)* | The image containing the extension, required | True | | | -| `extension_control_path` *string array* | The list of directories inside the image which should be added to extension_control_path.
If not defined, defaults to "/share". | | | | -| `dynamic_library_path` *string array* | The list of directories inside the image which should be added to dynamic_library_path.
If not defined, defaults to "/lib". | | | | -| `ld_library_path` *string array* | The list of directories inside the image which should be added to ld_library_path. | | | | - -#### ExtensionSpec - -ExtensionSpec configures an extension in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `version` *string* | The version of the extension to install. If empty, the operator will
install the default version (whatever is specified in the
extension's control file) | True | | | -| `schema` *string* | The name of the schema in which to install the extension's objects,
in case the extension allows its contents to be relocated. If not
specified (default), and the extension's control file does not
specify a schema either, the current default object creation schema
is used. | True | | | - -#### ExternalCluster - -ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The server name, required | True | | | -| `connectionParameters` *object (keys:string, values:string)* | The list of connection parameters, such as dbname, host, username, etc | | | | -| `sslCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL certificate to be used to connect to this
instance | | | | -| `sslKey` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL private key to be used to connect to this
instance | | | | -| `sslRootCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL CA public key to be used to connect to this
instance | | | | -| `password` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the password to be used to connect to the server.
If a password is provided, {{name.ln}} 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. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `plugin` *[PluginConfiguration](#pluginconfiguration)* | The configuration of the plugin that is taking care
of WAL archiving and backups for this external cluster | True | | | - -#### FDWSpec - -FDWSpec configures an Foreign Data Wrapper in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `handler` *string* | Name of the handler function (e.g., "postgres_fdw_handler").
This will be empty if no handler is specified. In that case,
the default handler is registered when the FDW extension is created. | | | | -| `validator` *string* | Name of the validator function (e.g., "postgres_fdw_validator").
This will be empty if no validator is specified. In that case,
the default validator is registered when the FDW extension is created. | | | | -| `owner` *string* | Owner specifies the database role that will own the Foreign Data Wrapper.
The role must have superuser privileges in the target database. | | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the FDW. | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the FDW are granted or revoked. | | | | - -#### FailoverQuorum - -FailoverQuorum contains the information about the current failover -quorum status of a PG cluster. It is updated by the instance manager -of the primary node and reset to zero by the operator to trigger -an update. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `FailoverQuorum` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `status` *[FailoverQuorumStatus](#failoverquorumstatus)* | Most recently observed status of the failover quorum. | | | | - -#### FailoverQuorumStatus - -FailoverQuorumStatus is the latest observed status of the failover -quorum of the PG cluster. - -*Appears in:* - -- [FailoverQuorum](#failoverquorum) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | --------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `method` *string* | Contains the latest reported Method value. | | | | -| `standbyNames` *string array* | StandbyNames is the list of potentially synchronous
instance names. | | | | -| `standbyNumber` *integer* | StandbyNumber is the number of synchronous standbys that transactions
need to wait for replies from. | | | | -| `primary` *string* | Primary is the name of the primary instance that updated
this object the latest time. | | | | - -#### ImageCatalog - -ImageCatalog is the Schema for the imagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ImageCatalog.
More info: | True | | | - -#### ImageCatalogRef - -ImageCatalogRef defines the reference to a major version in an ImageCatalog - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiGroup` *string* | APIGroup is the group for the resource being referenced.
If APIGroup is not specified, the specified Kind must be in the core API group.
For any other third-party types, APIGroup is required. | | | | -| `kind` *string* | Kind is the type of resource being referenced | True | | | -| `name` *string* | Name is the name of resource being referenced | True | | | -| `major` *integer* | The major version of PostgreSQL we want to use from the ImageCatalog | True | | | - -#### ImageCatalogSpec - -ImageCatalogSpec defines the desired ImageCatalog - -*Appears in:* - -- [ClusterImageCatalog](#clusterimagecatalog) -- [ImageCatalog](#imagecatalog) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------- | ---------------------------------------------- | -------- | ------- | ------------------------------------ | -| `images` *[CatalogImage](#catalogimage) array* | List of CatalogImages available in the catalog | True | | MaxItems: 8
MinItems: 1
| - -#### ImageInfo - -ImageInfo contains the information about a PostgreSQL image - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ---------------------------------------------- | -------- | ------- | ---------- | -| `image` *string* | Image is the image name | True | | | -| `majorVersion` *integer* | MajorVersion is the major version of the image | True | | | - -#### Import - -Import contains the configuration to init a database from a logic snapshot of an externalCluster - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------ | -| `source` *[ImportSource](#importsource)* | The source of the import | True | | | -| `type` *[SnapshotType](#snapshottype)* | The import type. Can be `microservice` or `monolith`. | True | | Enum: [microservice monolith]
| -| `databases` *string array* | The databases to import | True | | | -| `roles` *string array* | The roles to import | | | | -| `postImportApplicationSQL` *string array* | 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. | | | | -| `schemaOnly` *boolean* | When set to true, only the `pre-data` and `post-data` sections of
`pg_restore` are invoked, avoiding data import. Default: `false`. | | | | -| `pgDumpExtraOptions` *string array* | List of custom options to pass to the `pg_dump` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreExtraOptions` *string array* | List of custom options to pass to the `pg_restore` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePredataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `pre-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreDataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePostdataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `post-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | - -#### ImportSource - -ImportSource describes the source for the logical snapshot - -*Appears in:* - -- [Import](#import) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ----------------------------------------------- | -------- | ------- | ---------- | -| `externalCluster` *string* | The name of the externalCluster used for import | True | | | - -#### InstanceID - -InstanceID contains the information to identify an instance - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `podName` *string* | The pod name | | | | -| `ContainerID` *string* | The container ID | | | | -| `sessionID` *string* | The instance manager session ID. This is a unique identifier generated at instance manager
startup and changes on every restart (including container reboots). Used to detect if
the instance manager was restarted during long-running operations like backups, which
would terminate any running backup process. | | | | - -#### InstanceReportedState - -InstanceReportedState describes the last reported state of an instance during a reconciliation loop - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------- | -------- | ------- | ---------- | -| `isPrimary` *boolean* | indicates if an instance is the primary one | True | | | -| `timeLineID` *integer* | indicates on which TimelineId the instance is | | | | -| `ip` *string* | IP address of the instance | True | | | - -#### IsolationCheckConfiguration - -IsolationCheckConfiguration contains the configuration for the isolation check -functionality in the liveness probe - -*Appears in:* - -- [LivenessProbe](#livenessprobe) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Whether primary isolation checking is enabled for the liveness probe | | true | | -| `requestTimeout` *integer* | Timeout in milliseconds for requests during the primary isolation check | | 1000 | | -| `connectionTimeout` *integer* | Timeout in milliseconds for connections during the primary isolation check | | 1000 | | - -#### LDAPBindAsAuth - -LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ----------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `prefix` *string* | Prefix for the bind authentication option | | | | -| `suffix` *string* | Suffix for the bind authentication option | | | | - -#### LDAPBindSearchAuth - -LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | -------- | ------- | ---------- | -| `baseDN` *string* | Root DN to begin the user search | | | | -| `bindDN` *string* | DN of the user to bind to the directory | | | | -| `bindPassword` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Secret with the password for the user to bind to the directory | | | | -| `searchAttribute` *string* | Attribute to match against the username | | | | -| `searchFilter` *string* | Search filter to use when doing the search+bind authentication | | | | - -#### LDAPConfig - -LDAPConfig contains the parameters needed for LDAP authentication - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ------------------------- | -| `server` *string* | LDAP hostname or IP address | | | | -| `port` *integer* | LDAP server port | | | | -| `scheme` *[LDAPScheme](#ldapscheme)* | LDAP schema to be used, possible options are `ldap` and `ldaps` | | | Enum: [ldap ldaps]
| -| `bindAsAuth` *[LDAPBindAsAuth](#ldapbindasauth)* | Bind as authentication configuration | | | | -| `bindSearchAuth` *[LDAPBindSearchAuth](#ldapbindsearchauth)* | Bind+Search authentication configuration | | | | -| `tls` *boolean* | Set to 'true' to enable LDAP over TLS. 'false' is default | | | | - -#### LDAPScheme - -*Underlying type:* *string* - -LDAPScheme defines the possible schemes for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | -| ------- | ----------- | -| `ldap` | | -| `ldaps` | | - -#### LivenessProbe - -LivenessProbe is the configuration of the liveness probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `isolationCheck` *[IsolationCheckConfiguration](#isolationcheckconfiguration)* | Configure the feature that extends the liveness probe for a primary
instance. In addition to the basic checks, this verifies whether the
primary is isolated from the Kubernetes API server and from its
replicas, ensuring that it can be safely shut down if network
partition or API unavailability is detected. Enabled by default. | | | | - -#### ManagedConfiguration - -ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------- | --------------------------------------- | -------- | ------- | ---------- | -| `roles` *[RoleConfiguration](#roleconfiguration) array* | Database roles managed by the `Cluster` | | | | -| `services` *[ManagedServices](#managedservices)* | Services roles managed by the `Cluster` | | | | - -#### ManagedRoles - -ManagedRoles tracks the status of a cluster's managed roles - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `byStatus` *object (keys:[RoleStatus](#rolestatus), values:string array)* | ByStatus gives the list of roles in each state | | | | -| `cannotReconcile` *object (keys:string, values:string array)* | CannotReconcile lists roles that cannot be reconciled in PostgreSQL,
with an explanation of the cause | | | | -| `passwordStatus` *object (keys:string, values:[PasswordState](#passwordstate))* | PasswordStatus gives the last transaction id and password secret version for each managed role | | | | - -#### ManagedService - -ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification. - -*Appears in:* - -- [ManagedServices](#managedservices) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `selectorType` *[ServiceSelectorType](#serviceselectortype)* | SelectorType specifies the type of selectors that the service will have.
Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services. | True | | Enum: [rw r ro]
| -| `updateStrategy` *[ServiceUpdateStrategy](#serviceupdatestrategy)* | UpdateStrategy describes how the service differences should be reconciled | | patch | Enum: [patch replace]
| -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | ServiceTemplate is the template specification for the service. | True | | | - -#### ManagedServices - -ManagedServices represents the services managed by the cluster. - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------- | -| `disabledDefaultServices` *[ServiceSelectorType](#serviceselectortype) array* | DisabledDefaultServices is a list of service types that are disabled by default.
Valid values are "r", and "ro", representing read, and read-only services. | | | Enum: [rw r ro]
| -| `additional` *[ManagedService](#managedservice) array* | Additional is a list of additional managed services specified by the user. | | | | - -#### 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. - -*Appears in:* - -- [PodTemplateSpec](#podtemplatespec) -- [ServiceAccountTemplate](#serviceaccounttemplate) -- [ServiceTemplateSpec](#servicetemplatespec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the resource. Only supported for certain types | | | | -| `labels` *object (keys:string, values:string)* | 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: | | | | -| `annotations` *object (keys:string, values:string)* | 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: | | | | - -#### MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `disableDefaultQueries` *boolean* | 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. | | false | | -| `customQueriesConfigMap` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | The list of config maps containing the custom queries | | | | -| `customQueriesSecret` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | The list of secrets containing the custom queries | | | | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor`
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | false | | -| `tls` *[ClusterMonitoringTLSConfiguration](#clustermonitoringtlsconfiguration)* | Configure TLS communication for the metrics endpoint.
Changing tls.enabled option will force a rollout of all instances. | | | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `metricsQueriesTTL` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | The interval during which metrics computed from queries are considered current.
Once it is exceeded, a new scrape will trigger a rerun
of the queries.
If not set, defaults to 30 seconds, in line with Prometheus scraping defaults.
Setting this to zero disables the caching mechanism and can cause heavy load on the PostgreSQL server. | | | | - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `reusePVC` *boolean* | Reuse the existing PVC (wait for the node to come
up again) or not (recreate it elsewhere - when `instances` >1) | | true | | -| `inProgress` *boolean* | Is there a node maintenance activity in progress? | | false | | - -#### OnlineConfiguration - -OnlineConfiguration contains the configuration parameters for the online volume snapshot - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `waitForArchive` *boolean* | 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. | | true | | -| `immediateCheckpoint` *boolean* | 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. | | | | - -#### OptionSpec - -OptionSpec holds the name, value and the ensure field for an option - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the option | True | | | -| `value` *string* | Value of the option | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an option should be present or absent in
the database. If set to `present`, the option will be
created if it does not exist. If set to `absent`, the
option will be removed if it exists. | | present | Enum: [present absent]
| - -#### PasswordState - -PasswordState represents the state of the password of a managed RoleConfiguration - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ------------------------------------------------------------------- | -------- | ------- | ---------- | -| `transactionID` *integer* | the last transaction ID to affect the role definition in PostgreSQL | | | | -| `resourceVersion` *string* | the resource version of the password secret | | | | - -#### PgBouncerIntegrationStatus - -PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster - -*Appears in:* - -- [PoolerIntegrations](#poolerintegrations) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------- | -------- | ------- | ---------- | -| `secrets` *string array* | | | | | - -#### PgBouncerPoolMode - -*Underlying type:* *string* - -PgBouncerPoolMode is the mode of PgBouncer - -*Validation:* - -- Enum: [session transaction] - -*Appears in:* - -- [PgBouncerSpec](#pgbouncerspec) - -#### PgBouncerSecrets - -PgBouncerSecrets contains the versions of the secrets used -by pgbouncer - -*Appears in:* - -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | ----------------------------- | -------- | ------- | ---------- | -| `authQuery` *[SecretVersion](#secretversion)* | The auth query secret version | | | | - -#### PgBouncerSpec - -PgBouncerSpec defines how to configure PgBouncer - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------------- | -| `poolMode` *[PgBouncerPoolMode](#pgbouncerpoolmode)* | The pool mode. Default: `session`. | | session | Enum: [session transaction]
| -| `serverTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerTLSSecret, when pointing to a TLS secret, provides pgbouncer's
`server_tls_key_file` and `server_tls_cert_file`, used when
authenticating against PostgreSQL. | | | | -| `serverCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerCASecret provides PgBouncer’s server_tls_ca_file, the root
CA for validating PostgreSQL certificates | | | | -| `clientCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientCASecret provides PgBouncer’s client_tls_ca_file, the root
CA for validating client certificates | | | | -| `clientTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientTLSSecret provides PgBouncer’s client_tls_key_file (private key)
and client_tls_cert_file (certificate) used to accept client connections | | | | -| `authQuerySecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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.
Deprecated. | | | | -| `authQuery` *string* | 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. | | | | -| `parameters` *object (keys:string, values:string)* | Additional parameters to be passed to PgBouncer - please check
the CNP documentation for a list of options you can configure | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file) | | | | -| `paused` *boolean* | 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. | | false | | - -#### PluginConfiguration - -PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [ExternalCluster](#externalcluster) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the plugin name | True | | | -| `enabled` *boolean* | Enabled is true if this plugin will be used | | true | | -| `isWALArchiver` *boolean* | Marks the plugin as the WAL archiver. At most one plugin can be
designated as a WAL archiver. This cannot be enabled if the
`.spec.backup.barmanObjectStore` configuration is present. | | false | | -| `parameters` *object (keys:string, values:string)* | Parameters is the configuration of the plugin | | | | - -#### PluginStatus - -PluginStatus is the status of a loaded plugin - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin | True | | | -| `version` *string* | Version is the version of the plugin loaded by the
latest reconciliation loop | True | | | -| `capabilities` *string array* | Capabilities are the list of capabilities of the
plugin | | | | -| `operatorCapabilities` *string array* | OperatorCapabilities are the list of capabilities of the
plugin regarding the reconciler | | | | -| `walCapabilities` *string array* | WALCapabilities are the list of capabilities of the
plugin regarding the WAL management | | | | -| `backupCapabilities` *string array* | BackupCapabilities are the list of capabilities of the
plugin regarding the Backup management | | | | -| `restoreJobHookCapabilities` *string array* | RestoreJobHookCapabilities are the list of capabilities of the
plugin regarding the RestoreJobHook management | | | | -| `status` *string* | Status contain the status reported by the plugin through the SetStatusInCluster interface | | | | - -#### PodName - -*Underlying type:* *string* - -PodName is the name of a Pod - -*Appears in:* - -- [ClusterStatus](#clusterstatus) -- [Topology](#topology) - -#### PodStatus - -*Underlying type:* *string* - -PodStatus represent the possible status of pods - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -#### 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: - - - - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[PodSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podspec-v1-core)* | Specification of the desired behavior of the pod.
More info: | | | | - -#### PodTopologyLabels - -*Underlying type:* *object* - -PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue - -*Appears in:* - -- [Topology](#topology) - -#### Pooler - -Pooler is the Schema for the poolers API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Pooler` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PoolerSpec](#poolerspec)* | Specification of the desired behavior of the Pooler.
More info: | True | | | -| `status` *[PoolerStatus](#poolerstatus)* | Most recently observed status of the Pooler. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `pgBouncerIntegration` *[PgBouncerIntegrationStatus](#pgbouncerintegrationstatus)* | | | | | - -#### 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. - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor` | | false | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping. | | | | - -#### PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -*Appears in:* - -- [PoolerStatus](#poolerstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------- | -------------------------------------------- | -------- | ------- | ---------- | -| `clientTLS` *[SecretVersion](#secretversion)* | The client TLS secret version | | | | -| `serverTLS` *[SecretVersion](#secretversion)* | The server TLS secret version | | | | -| `serverCA` *[SecretVersion](#secretversion)* | The server CA secret version | | | | -| `clientCA` *[SecretVersion](#secretversion)* | The client CA secret version | | | | -| `pgBouncerSecrets` *[PgBouncerSecrets](#pgbouncersecrets)* | The version of the secrets used by PgBouncer | | | | - -#### PoolerSpec - -PoolerSpec defines the desired state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------- | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | This is the cluster reference on which the Pooler will work.
Pooler name should never match with any cluster name within the same namespace. | True | | | -| `type` *[PoolerType](#poolertype)* | Type of service to forward traffic to. Default: `rw`. | | rw | Enum: [rw ro r]
| -| `instances` *integer* | The number of replicas we want. Default: 1. | | 1 | | -| `template` *[PodTemplateSpec](#podtemplatespec)* | The template of the Pod to be created | | | | -| `pgbouncer` *[PgBouncerSpec](#pgbouncerspec)* | The PgBouncer configuration | True | | | -| `deploymentStrategy` *[DeploymentStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#deploymentstrategy-v1-apps)* | The deployment strategy to use for pgbouncer to replace existing pods with new ones | | | | -| `monitoring` *[PoolerMonitoringConfiguration](#poolermonitoringconfiguration)* | The configuration of the monitoring infrastructure of this pooler.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | Template for the Service to be created | | | | - -#### PoolerStatus - -PoolerStatus defines the observed state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `secrets` *[PoolerSecrets](#poolersecrets)* | The resource version of the config object | | | | -| `instances` *integer* | The number of pods trying to be scheduled | | | | - -#### PoolerType - -*Underlying type:* *string* - -PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are `rw` and `ro`. - -*Validation:* - -- Enum: [rw ro r] - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -#### PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `parameters` *object (keys:string, values:string)* | PostgreSQL configuration options (postgresql.conf) | | | | -| `synchronous` *[SynchronousReplicaConfiguration](#synchronousreplicaconfiguration)* | Configuration of the PostgreSQL synchronous replication feature | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file) | | | | -| `pg_ident` *string array* | PostgreSQL User Name Maps rules (lines to be appended
to the pg_ident.conf file) | | | | -| `epas` *[EPASConfiguration](#epasconfiguration)* | EDB Postgres Advanced Server specific configurations | | | | -| `syncReplicaElectionConstraint` *[SyncReplicaElectionConstraints](#syncreplicaelectionconstraints)* | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be
set up. | | | | -| `shared_preload_libraries` *string array* | Lists of shared preload libraries to add to the default ones | | | | -| `ldap` *[LDAPConfig](#ldapconfig)* | Options to specify LDAP configuration | | | | -| `promotionTimeout` *integer* | 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 | | | | -| `enableAlterSystem` *boolean* | If this parameter is true, the user will be able to invoke `ALTER SYSTEM`
on this {{name.ln}} Cluster.
This should only be used for debugging and troubleshooting.
Defaults to false. | | | | -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | - -#### PrimaryUpdateMethod - -*Underlying type:* *string* - -PrimaryUpdateMethod contains the method to use when upgrading -the primary server of the cluster as part of rolling updates - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `switchover` | PrimaryUpdateMethodSwitchover means that the operator will switchover to another updated
replica when it needs to upgrade the primary instance.
Note: when using this method, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process.
| -| `restart` | PrimaryUpdateMethodRestart means that the operator will restart the primary instance in-place
when it needs to upgrade it
| - -#### PrimaryUpdateStrategy - -*Underlying type:* *string* - -PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `supervised` | PrimaryUpdateStrategySupervised means that the operator need to wait for the
user to manually issue a switchover request before updating the primary
server (`supervised`)
| -| `unsupervised` | PrimaryUpdateStrategyUnsupervised means that the operator will proceed with the
selected PrimaryUpdateMethod to another updated replica and then automatically update
the primary server (`unsupervised`, default)
| - -#### Probe - -Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic. - -*Appears in:* - -- [LivenessProbe](#livenessprobe) -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | - -#### ProbeStrategyType - -*Underlying type:* *string* - -ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready - -*Appears in:* - -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `pg_isready` | ProbeStrategyPgIsReady means that the pg_isready tool is used to determine
whether PostgreSQL is started up
| -| `streaming` | ProbeStrategyStreaming means that pg_isready is positive and the replica is
connected via streaming replication to the current primary and the lag is, if specified,
within the limit.
| -| `query` | ProbeStrategyQuery means that the server is able to connect to the superuser database
and able to execute a simple query like "-- ping"
| - -#### ProbeWithStrategy - -ProbeWithStrategy is the configuration of the startup probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------------------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `type` *[ProbeStrategyType](#probestrategytype)* | The probe strategy | | | Enum: [pg_isready streaming query]
| -| `maximumLag` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Lag limit. Used only for `streaming` strategy | | | | - -#### ProbesConfiguration - -ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `startup` *[ProbeWithStrategy](#probewithstrategy)* | The startup probe configuration | True | | | -| `liveness` *[LivenessProbe](#livenessprobe)* | The liveness probe configuration | True | | | -| `readiness` *[ProbeWithStrategy](#probewithstrategy)* | The readiness probe configuration | True | | | - -#### Publication - -Publication is the Schema for the publications API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Publication` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PublicationSpec](#publicationspec)* | | True | | | -| `status` *[PublicationStatus](#publicationstatus)* | | True | | | - -#### PublicationReclaimPolicy - -*Underlying type:* *string* - -PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications. - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | PublicationReclaimDelete means the publication will be deleted from Kubernetes on release
from its claim.
| -| `retain` | PublicationReclaimRetain means the publication will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### PublicationSpec - -PublicationSpec defines the desired state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "publisher" | True | | | -| `name` *string* | The name of the publication inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "publisher" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Publication parameters part of the `WITH` clause as expected by
PostgreSQL `CREATE PUBLICATION` command | | | | -| `target` *[PublicationTarget](#publicationtarget)* | Target of the publication as expected by PostgreSQL `CREATE PUBLICATION` command | True | | | -| `publicationReclaimPolicy` *[PublicationReclaimPolicy](#publicationreclaimpolicy)* | The policy for end-of-life maintenance of this publication | | retain | Enum: [delete retain]
| - -#### PublicationStatus - -PublicationStatus defines the observed state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the publication was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### PublicationTarget - -PublicationTarget is what this publication should publish - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------- | -| `allTables` *boolean* | Marks the publication as one that replicates changes for all tables
in the database, including tables created in the future.
Corresponding to `FOR ALL TABLES` in PostgreSQL. | | | | -| `objects` *[PublicationTargetObject](#publicationtargetobject) array* | Just the following schema objects | | | MaxItems: 100000
| - -#### PublicationTargetObject - -PublicationTargetObject is an object to publish - -*Appears in:* - -- [PublicationTarget](#publicationtarget) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `tablesInSchema` *string* | Marks the publication as one that replicates changes for all tables
in the specified list of schemas, including tables created in the
future. Corresponding to `FOR TABLES IN SCHEMA` in PostgreSQL. | | | | -| `table` *[PublicationTargetTable](#publicationtargettable)* | Specifies a list of tables to add to the publication. Corresponding
to `FOR TABLE` in PostgreSQL. | | | | - -#### PublicationTargetTable - -PublicationTargetTable is a table to publish - -*Appears in:* - -- [PublicationTargetObject](#publicationtargetobject) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `only` *boolean* | Whether to limit to the table only or include all its descendants | | | | -| `name` *string* | The table name | True | | | -| `schema` *string* | The schema name | | | | -| `columns` *string array* | The columns to publish | | | | - -#### RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backupID` *string* | 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. | | | | -| `targetTLI` *string* | The target timeline ("latest" or a positive integer) | | | | -| `targetXID` *string* | The target transaction ID | | | | -| `targetName` *string* | The target name (to be previously created
with `pg_create_restore_point`) | | | | -| `targetLSN` *string* | The target LSN (Log Sequence Number) | | | | -| `targetTime` *string* | The target time as a timestamp in RFC3339 format or PostgreSQL timestamp format.
Timestamps without an explicit timezone are interpreted as UTC. | | | | -| `targetImmediate` *boolean* | End recovery as soon as a consistent state is reached | | | | -| `exclusive` *boolean* | Set the target to be exclusive. If omitted, defaults to false, so that
in Postgres, `recovery_target_inclusive` will be true | | | | - -#### ReplicaClusterConfiguration - -ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------- | -| `self` *string* | Self defines the name of this cluster. It is used to determine if this is a primary
or a replica cluster, comparing it with `primary` | | | | -| `primary` *string* | Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the
topology specified in externalClusters | | | | -| `source` *string* | The name of the external cluster which is the replication origin | True | | MinLength: 1
| -| `enabled` *boolean* | 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. | | | | -| `promotionToken` *string* | A demotion token generated by an external cluster used to
check if the promotion requirements are met. | | | | -| `minApplyDelay` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | When replica mode is enabled, this parameter allows you to replay
transactions only when the system time is at least the configured
time past the commit time. This provides an opportunity to correct
data loss errors. Note that when this parameter is set, a promotion
token cannot be used. | | | | - -#### ReplicationSlotsConfiguration - -ReplicationSlotsConfiguration encapsulates the configuration -of replication slots - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------- | -| `highAvailability` *[ReplicationSlotsHAConfiguration](#replicationslotshaconfiguration)* | Replication slots for high availability configuration | | | | -| `updateInterval` *integer* | Standby will update the status of the local replication slots
every `updateInterval` seconds (default 30). | | | Minimum: 1
| -| `synchronizeReplicas` *[SynchronizeReplicasConfiguration](#synchronizereplicasconfiguration)* | Configures the synchronization of the user defined physical replication slots | | | | - -#### 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. - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------ | -| `enabled` *boolean* | 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. | | | | -| `slotPrefix` *string* | 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_`. | | | Pattern: `^[0-9a-z_]*$`
| -| `synchronizeLogicalDecoding` *boolean* | When enabled, the operator automatically manages synchronization of logical
decoding (replication) slots across high-availability clusters.
Requires one of the following conditions:
- PostgreSQL version 17 or later
- PostgreSQL version < 17 with pg_failover_slots extension enabled | | | | - -#### 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: - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the role | True | | | -| `comment` *string* | Description of the role | | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the role is `present` or `absent` - defaults to "present" | | present | Enum: [present absent]
| -| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present)
If null, the password will be ignored unless DisablePassword is set | | | | -| `connectionLimit` *integer* | If the role can log in, this specifies how many concurrent
connections the role can make. `-1` (the default) means no limit. | | -1 | | -| `validUntil` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Date and time after which the role's password is no longer valid.
When omitted, the password will never expire (default). | | | | -| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty. | | | | -| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Defaults is `true`. | | true | | -| `disablePassword` *boolean* | DisablePassword indicates that a role's password should be set to NULL in Postgres | | | | -| `superuser` *boolean* | 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`. | | | | -| `createdb` *boolean* | 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. | | | | -| `createrole` *boolean* | 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`. | | | | -| `login` *boolean* | 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`. | | | | -| `replication` *boolean* | 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`. | | | | -| `bypassrls` *boolean* | Whether a role bypasses every row-level security (RLS) policy.
Default is `false`. | | | | - -#### RoleStatus - -*Underlying type:* *string* - -RoleStatus represents the status of a managed role in the cluster - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | -| ------------------------ | ----------------------------------------------------------------------------------------------------- | -| `reconciled` | RoleStatusReconciled indicates the role in DB matches the Spec
| -| `not-managed` | RoleStatusNotManaged indicates the role is not in the Spec, therefore not managed
| -| `pending-reconciliation` | RoleStatusPendingReconciliation indicates the role in Spec requires updated/creation in DB
| -| `reserved` | RoleStatusReserved indicates this is one of the roles reserved by the operator. E.g. `postgres`
| - -#### SQLRefs - -SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------- | ------- | ---------- | -| `secretRefs` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | SecretRefs holds a list of references to Secrets | | | | -| `configMapRefs` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | ConfigMapRefs holds a list of references to ConfigMaps | | | | - -#### ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ScheduledBackup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ScheduledBackupSpec](#scheduledbackupspec)* | Specification of the desired behavior of the ScheduledBackup.
More info: | True | | | -| `status` *[ScheduledBackupStatus](#scheduledbackupstatus)* | Most recently observed status of the ScheduledBackup. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `suspend` *boolean* | If this backup is suspended or not | | | | -| `immediate` *boolean* | If the first backup has to be immediately start after creation or not | | | | -| `schedule` *string* | The schedule does not follow the same format used in Kubernetes CronJobs
as it includes an additional seconds specifier,
see | True | | | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `backupOwnerReference` *string* | 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
| | none | Enum: [none self cluster]
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `lastCheckTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | The latest time the schedule | | | | -| `lastScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Information when was the last time that backup was successfully scheduled. | | | | -| `nextScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Next time we will run a backup | | | | - -#### SchemaSpec - -SchemaSpec configures a schema in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `owner` *string* | The role name of the user who owns the schema inside PostgreSQL.
It maps to the `AUTHORIZATION` parameter of `CREATE SCHEMA` and the
`OWNER TO` command of `ALTER SCHEMA`. | True | | | - -#### SecretVersion - -SecretVersion contains a secret name and its ResourceVersion - -*Appears in:* - -- [PgBouncerSecrets](#pgbouncersecrets) -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| ------------------ | --------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the secret | | | | -| `version` *string* | The ResourceVersion of the secret | | | | - -#### SecretsResourceVersion - -SecretsResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `superuserSecretVersion` *string* | The resource version of the "postgres" user secret | | | | -| `replicationSecretVersion` *string* | The resource version of the "streaming_replica" user secret | | | | -| `applicationSecretVersion` *string* | The resource version of the "app" user secret | | | | -| `managedRoleSecretVersion` *object (keys:string, values:string)* | The resource versions of the managed roles secrets | | | | -| `caSecretVersion` *string* | Unused. Retained for compatibility with old versions. | | | | -| `clientCaSecretVersion` *string* | The resource version of the PostgreSQL client-side CA secret version | | | | -| `serverCaSecretVersion` *string* | The resource version of the PostgreSQL server-side CA secret version | | | | -| `serverSecretVersion` *string* | The resource version of the PostgreSQL server-side secret version | | | | -| `barmanEndpointCA` *string* | The resource version of the Barman Endpoint CA if provided | | | | -| `externalClusterSecretVersion` *object (keys:string, values:string)* | The resource versions of the external cluster secrets | | | | -| `metrics` *object (keys:string, values:string)* | A map with the versions of all the secrets used to pass metrics.
Map keys are the secret names, map values are the versions | | | | - -#### ServerSpec - -ServerSpec configures a server of a foreign data wrapper - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `fdw` *string* | The name of the Foreign Data Wrapper (FDW) | True | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the server
(key is the option name, value is the option value). | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the server are granted or revoked. | | | | - -#### ServiceAccountTemplate - -ServiceAccountTemplate contains the template needed to generate the service accounts - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | - -#### ServiceSelectorType - -*Underlying type:* *string* - -ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only - -*Validation:* - -- Enum: [rw r ro] - -*Appears in:* - -- [ManagedService](#managedservice) -- [ManagedServices](#managedservices) - -| Field | Description | -| ----- | ----------------------------------------------------------- | -| `rw` | ServiceSelectorTypeRW selects the read-write service.
| -| `r` | ServiceSelectorTypeR selects the read service.
| -| `ro` | ServiceSelectorTypeRO selects the read-only service.
| - -#### ServiceTemplateSpec - -ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation. - -*Appears in:* - -- [ManagedService](#managedservice) -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[ServiceSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#servicespec-v1-core)* | Specification of the desired behavior of the service.
More info: | | | | - -#### ServiceUpdateStrategy - -*Underlying type:* *string* - -ServiceUpdateStrategy describes how the changes to the managed service should be handled - -*Validation:* - -- Enum: [patch replace] - -*Appears in:* - -- [ManagedService](#managedservice) - -#### SnapshotOwnerReference - -*Underlying type:* *string* - -SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to. - -*Appears in:* - -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | -| --------- | ------------------------------------------------------------------------------------------------- | -| `none` | SnapshotOwnerReferenceNone indicates that the snapshot does not have any owner reference.
| -| `backup` | SnapshotOwnerReferenceBackup indicates that the snapshot is owned by the backup resource.
| -| `cluster` | SnapshotOwnerReferenceCluster indicates that the snapshot is owned by the cluster resource.
| - -#### SnapshotType - -*Underlying type:* *string* - -SnapshotType is a type of allowed import - -*Appears in:* - -- [Import](#import) - -| Field | Description | -| -------------- | ----------------------------------------------------------------------------------- | -| `monolith` | MonolithSnapshotType indicates to execute the monolith clone typology
| -| `microservice` | MicroserviceSnapshotType indicates to execute the microservice clone typology
| - -#### StorageConfiguration - -StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `storageClass` *string* | 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` *string* | 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. | | | | -| `resizeInUseVolumes` *boolean* | Resize existent PVCs, defaults to true | | true | | -| `pvcTemplate` *[PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#persistentvolumeclaimspec-v1-core)* | Template to be used to generate the Persistent Volume Claim | | | | - -#### Subscription - -Subscription is the Schema for the subscriptions API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Subscription` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[SubscriptionSpec](#subscriptionspec)* | | True | | | -| `status` *[SubscriptionStatus](#subscriptionstatus)* | | True | | | - -#### SubscriptionReclaimPolicy - -*Underlying type:* *string* - -SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions. - -*Appears in:* - -- [SubscriptionSpec](#subscriptionspec) - -| Field | Description | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `delete` | SubscriptionReclaimDelete means the subscription will be deleted from Kubernetes on release
from its claim.
| -| `retain` | SubscriptionReclaimRetain means the subscription will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### SubscriptionSpec - -SubscriptionSpec defines the desired state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "subscriber" | True | | | -| `name` *string* | The name of the subscription inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "subscriber" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Subscription parameters included in the `WITH` clause of the PostgreSQL
`CREATE SUBSCRIPTION` command. Most parameters cannot be changed
after the subscription is created and will be ignored if modified
later, except for a limited set documented at:
| | | | -| `publicationName` *string* | The name of the publication inside the PostgreSQL database in the
"publisher" | True | | | -| `publicationDBName` *string* | The name of the database containing the publication on the external
cluster. Defaults to the one in the external cluster definition. | | | | -| `externalClusterName` *string* | The name of the external cluster with the publication ("publisher") | True | | | -| `subscriptionReclaimPolicy` *[SubscriptionReclaimPolicy](#subscriptionreclaimpolicy)* | The policy for end-of-life maintenance of this subscription | | retain | Enum: [delete retain]
| - -#### SubscriptionStatus - -SubscriptionStatus defines the observed state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the subscription was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### SwitchReplicaClusterStatus - -SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `inProgress` *boolean* | InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster. | | | | - -#### 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. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `nodeLabelsAntiAffinity` *string array* | A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not | | | | -| `enabled` *boolean* | This flag enables the constraints for sync replicas | True | | | - -#### SynchronizeReplicasConfiguration - -SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | When set to true, every replication slot that is on the primary is synchronized on each standby | True | | | -| `excludePatterns` *string array* | List of regular expression patterns to match the names of replication slots to be excluded (by default empty) | | | | - -#### SynchronousReplicaConfiguration - -SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also `.spec.minSyncReplicas` and `.spec.maxSyncReplicas` -need to be considered. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------- | -| `method` *[SynchronousReplicaConfigurationMethod](#synchronousreplicaconfigurationmethod)* | Method to select synchronous replication standbys from the listed
servers, accepting 'any' (quorum-based synchronous replication) or
'first' (priority-based synchronous replication) as values. | True | | Enum: [any first]
| -| `number` *integer* | Specifies the number of synchronous standby servers that
transactions must wait for responses from. | True | | | -| `maxStandbyNamesFromCluster` *integer* | Specifies the maximum number of local cluster pods that can be
automatically included in the `synchronous_standby_names` option in
PostgreSQL. | | | | -| `standbyNamesPre` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` before local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `standbyNamesPost` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` after local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `dataDurability` *[DataDurabilityLevel](#datadurabilitylevel)* | If set to "required", data durability is strictly enforced. Write operations
with synchronous commit settings (`on`, `remote_write`, or `remote_apply`) will
block if there are insufficient healthy replicas, ensuring data persistence.
If set to "preferred", data durability is maintained when healthy replicas
are available, but the required number of instances will adjust dynamically
if replicas become unavailable. This setting relaxes strict durability enforcement
to allow for operational continuity. This setting is only applicable if both
`standbyNamesPre` and `standbyNamesPost` are unset (empty). | | | Enum: [required preferred]
| -| `failoverQuorum` *boolean* | FailoverQuorum enables a quorum-based check before failover, improving
data durability and safety during failover events in {{name.ln}}-managed
PostgreSQL clusters. | | | | - -#### SynchronousReplicaConfigurationMethod - -*Underlying type:* *string* - -SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -#### TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -*Appears in:* - -- [EPASConfiguration](#epasconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | True if we want to have TDE enabled | | | | -| `secretKeyRef` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Reference to the secret that contains the encryption key | | | | -| `wrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | WrapCommand is the encrypt command provided by the user | | | | -| `unwrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | UnwrapCommand is the decryption command provided by the user | | | | -| `passphraseCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | PassphraseCommand is the command executed to get the passphrase that will be
passed to the OpenSSL command to encrypt and decrypt | | | | - -#### TablespaceConfiguration - -TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the tablespace | True | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | The storage configuration for the tablespace | True | | | -| `owner` *[DatabaseRoleRef](#databaseroleref)* | Owner is the PostgreSQL user owning the tablespace | | | | -| `temporary` *boolean* | When set to true, the tablespace will be added as a `temp_tablespaces`
entry 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. | | false | | - -#### TablespaceState - -TablespaceState represents the state of a tablespace in a cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | -------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the tablespace | True | | | -| `owner` *string* | Owner is the PostgreSQL user owning the tablespace | | | | -| `state` *[TablespaceStatus](#tablespacestatus)* | State is the latest reconciliation state | True | | | -| `error` *string* | Error is the reconciliation error, if any | | | | - -#### TablespaceStatus - -*Underlying type:* *string* - -TablespaceStatus represents the status of a tablespace in the cluster - -*Appears in:* - -- [TablespaceState](#tablespacestate) - -| Field | Description | -| ------------ | -------------------------------------------------------------------------------------------------------- | -| `reconciled` | TablespaceStatusReconciled indicates the tablespace in DB matches the Spec
| -| `pending` | TablespaceStatusPendingReconciliation indicates the tablespace in Spec requires creation in the DB
| - -#### Topology - -Topology contains the cluster topology - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *object (keys:[PodName](#podname), values:[PodTopologyLabels](#podtopologylabels))* | Instances contains the pod topology of the instances | | | | -| `nodesUsed` *integer* | 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` *boolean* | SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors
in synchronous replica election in case of failures | | | | - -#### UsageSpec - -UsageSpec configures a usage for a foreign data wrapper - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------- | -------- | ------- | --------------------------- | -| `name` *string* | Name of the usage | True | | | -| `type` *[UsageSpecType](#usagespectype)* | The type of usage | | grant | Enum: [grant revoke]
| - -#### UsageSpecType - -*Underlying type:* *string* - -UsageSpecType describes the type of usage specified in the `usage` field of the -`Database` object. - -*Appears in:* - -- [UsageSpec](#usagespec) - -| Field | Description | -| -------- | -------------------------------------------------------------------------------------------------------- | -| `grant` | GrantUsageSpecType indicates a grant usage permission.
The default usage permission is grant.
| -| `revoke` | RevokeUsageSpecType indicates a revoke usage permission.
| - -#### VolumeSnapshotConfiguration - -VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups. - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------- | ---------------------------------- | -| `labels` *object (keys:string, values:string)* | Labels are key-value pairs that will be added to .metadata.labels snapshot resources. | | | | -| `annotations` *object (keys:string, values:string)* | Annotations key-value pairs that will be added to .metadata.annotations snapshot resources. | | | | -| `className` *string* | 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` *string* | WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim. | | | | -| `tablespaceClassName` *object (keys:string, values:string)* | TablespaceClassName specifies the Snapshot Class to be used for the tablespaces.
defaults to the PGDATA Snapshot Class, if set | | | | -| `snapshotOwnerReference` *[SnapshotOwnerReference](#snapshotownerreference)* | SnapshotOwnerReference indicates the type of owner reference the snapshot should have | | none | Enum: [none cluster backup]
| -| `online` *boolean* | Whether the default type of backup with volume snapshots is
online/hot (`true`, default) or offline/cold (`false`) | | true | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots | | { immediateCheckpoint:false waitForArchive:true } | | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.29.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.29.0.mdx deleted file mode 100644 index 62060859191..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.29.0.mdx +++ /dev/null @@ -1,2406 +0,0 @@ ---- -title: API Reference - v1.29.0 -navTitle: v1.29.0 -pdfExclude: 'true' - ---- - -## Packages - -- [postgresql.k8s.enterprisedb.io/v1](#postgresqlk8senterprisedbiov1) - -## postgresql.k8s.enterprisedb.io/v1 - -Package v1 contains API Schema definitions for the postgresql v1 API group - -### Resource Types - -- [Backup](#backup) -- [Cluster](#cluster) -- [ClusterImageCatalog](#clusterimagecatalog) -- [Database](#database) -- [FailoverQuorum](#failoverquorum) -- [ImageCatalog](#imagecatalog) -- [Pooler](#pooler) -- [Publication](#publication) -- [ScheduledBackup](#scheduledbackup) -- [Subscription](#subscription) - -#### AffinityConfiguration - -AffinityConfiguration contains the info we need to create the -affinity rules for Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `enablePodAntiAffinity` *boolean* | Activates anti-affinity for the pods. The operator will define pods
anti-affinity unless this field is explicitly set to false | | | | -| `topologyKey` *string* | TopologyKey to use for anti-affinity configuration. See k8s documentation
for more info on that | | | | -| `nodeSelector` *object (keys:string, values:string)* | NodeSelector is map of key-value pairs used to define the nodes on which
the pods can run.
More info: | | | | -| `nodeAffinity` *[NodeAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#nodeaffinity-v1-core)* | NodeAffinity describes node affinity scheduling rules for the pod.
More info: | | | | -| `tolerations` *[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#toleration-v1-core) array* | 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: | | | | -| `podAntiAffinityType` *string* | 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:
| | | | -| `additionalPodAntiAffinity` *[PodAntiAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podantiaffinity-v1-core)* | 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` *[PodAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podaffinity-v1-core)* | AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods. | | | | - -#### AvailableArchitecture - -AvailableArchitecture represents the state of a cluster's architecture - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------- | ------------------------------------------------- | -------- | ------- | ---------- | -| `goArch` *string* | GoArch is the name of the executable architecture | True | | | -| `hash` *string* | Hash is the hash of the executable | True | | | - -#### Backup - -A Backup resource is a request for a PostgreSQL backup by the user. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Backup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[BackupSpec](#backupspec)* | Specification of the desired behavior of the backup.
More info: | True | | | -| `status` *[BackupStatus](#backupstatus)* | Most recently observed status of the backup. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### BackupConfiguration - -BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `volumeSnapshot` *[VolumeSnapshotConfiguration](#volumesnapshotconfiguration)* | VolumeSnapshot provides the configuration for the execution of volume snapshot backups. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `retentionPolicy` *string* | 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. | | | Pattern: `^[1-9][0-9]*[dwm]$`
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| - -#### BackupMethod - -*Underlying type:* *string* - -BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance - -*Appears in:* - -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [ClusterStatus](#clusterstatus) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | -| ------------------- | -------------------------------------------------------------------------------------------- | -| `volumeSnapshot` | BackupMethodVolumeSnapshot means using the volume snapshot
Kubernetes feature
| -| `barmanObjectStore` | BackupMethodBarmanObjectStore means using barman to backup the
PostgreSQL cluster
| -| `plugin` | BackupMethodPlugin means that this backup should be handled by
a plugin
| - -#### BackupPhase - -*Underlying type:* *string* - -BackupPhase is the phase of the backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -#### BackupPluginConfiguration - -BackupPluginConfiguration contains the backup configuration used by -the backup plugin - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin managing this backup | True | | | -| `parameters` *object (keys:string, values:string)* | Parameters are the configuration parameters passed to the backup
plugin for this backup | | | | - -#### BackupSnapshotElementStatus - -BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup - -*Appears in:* - -- [BackupSnapshotStatus](#backupsnapshotstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the snapshot resource name | True | | | -| `type` *string* | Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE | True | | | -| `tablespaceName` *string* | TablespaceName is the name of the snapshotted tablespace. Only set
when type is PG_TABLESPACE | | | | - -#### BackupSnapshotStatus - -BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `elements` *[BackupSnapshotElementStatus](#backupsnapshotelementstatus) array* | The elements list, populated with the gathered volume snapshots | | | | - -#### BackupSource - -BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name of the referent. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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 - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### BackupStatus - -BackupStatus defines the observed state of Backup - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `googleCredentials` *[GoogleCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#GoogleCredentials)* | The credentials to use to upload data to Google Cloud Storage | | | | -| `s3Credentials` *[S3Credentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#S3Credentials)* | The credentials to use to upload data to S3 | | | | -| `azureCredentials` *[AzureCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#AzureCredentials)* | The credentials to use to upload data to Azure Blob Storage | | | | -| `majorVersion` *integer* | The PostgreSQL major version that was running when the
backup was taken. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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` *string* | Endpoint to be used to upload data to the cloud,
overriding the automatic endpoint discovery | | | | -| `destinationPath` *string* | 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. | | | | -| `serverName` *string* | The server name on S3, the cluster name is used if this
parameter is omitted | | | | -| `encryption` *string* | Encryption method required to S3 API | | | | -| `backupId` *string* | The ID of the Barman backup | | | | -| `backupName` *string* | The Name of the Barman backup | | | | -| `phase` *[BackupPhase](#backupphase)* | The last backup status | | | | -| `startedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup execution was started by the backup tool | | | | -| `stoppedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup execution was terminated by the backup tool | | | | -| `reconciliationStartedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup process was started by the operator | | | | -| `reconciliationTerminatedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the reconciliation was terminated by the operator (either successfully or not) | | | | -| `beginWal` *string* | The starting WAL | | | | -| `endWal` *string* | The ending WAL | | | | -| `beginLSN` *string* | The starting xlog | | | | -| `endLSN` *string* | The ending xlog | | | | -| `error` *string* | The detected error | | | | -| `commandOutput` *string* | Unused. Retained for compatibility with old versions. | | | | -| `commandError` *string* | The backup command output in case of error | | | | -| `backupLabelFile` *integer array* | Backup label file content as returned by Postgres in case of online (hot) backups | | | | -| `tablespaceMapFile` *integer array* | Tablespace map file content as returned by Postgres in case of online (hot) backups | | | | -| `instanceID` *[InstanceID](#instanceid)* | Information to identify the instance where the backup has been taken from | | | | -| `snapshotBackupStatus` *[BackupSnapshotStatus](#backupsnapshotstatus)* | Status of the volumeSnapshot backup | | | | -| `method` *[BackupMethod](#backupmethod)* | The backup method being used | | | | -| `online` *boolean* | Whether the backup was online/hot (`true`) or offline/cold (`false`) | | | | -| `pluginMetadata` *object (keys:string, values:string)* | A map containing the plugin metadata | | | | - -#### BackupTarget - -*Underlying type:* *string* - -BackupTarget describes the preferred targets for a backup - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initdb` *[BootstrapInitDB](#bootstrapinitdb)* | Bootstrap the cluster via initdb | | | | -| `recovery` *[BootstrapRecovery](#bootstraprecovery)* | Bootstrap the cluster from a backup | | | | -| `pg_basebackup` *[BootstrapPgBaseBackup](#bootstrappgbasebackup)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | -| `redwood` *boolean* | If we need to enable/disable Redwood compatibility. Requires
EPAS and for EPAS defaults to true | | | | -| `options` *string array* | 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. | | | | -| `dataChecksums` *boolean* | Whether the `-k` option should be passed to initdb,
enabling checksums on data pages (default: `false`) | | | | -| `encoding` *string* | The value to be passed as option `--encoding` for initdb (default:`UTF8`) | | | | -| `localeCollate` *string* | The value to be passed as option `--lc-collate` for initdb (default:`C`) | | | | -| `localeCType` *string* | The value to be passed as option `--lc-ctype` for initdb (default:`C`) | | | | -| `locale` *string* | Sets the default collation order and character classification in the new database. | | | | -| `localeProvider` *string* | This option sets the locale provider for databases created in the new cluster.
Available from PostgreSQL 16. | | | | -| `icuLocale` *string* | Specifies the ICU locale when the ICU provider is used.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Specifies additional collation rules to customize the behavior of the default collation.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Specifies the locale name when the builtin provider is used.
This option requires `localeProvider` to be set to `builtin`.
Available from PostgreSQL 17. | | | | -| `walSegmentSize` *integer* | The value in megabytes (1 to 1024) to be passed to the `--wal-segsize`
option for initdb (default: empty, resulting in PostgreSQL default: 16MB) | | | Maximum: 1024
Minimum: 1
| -| `postInitSQL` *string array* | List of SQL queries to be executed as a superuser in the `postgres`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitApplicationSQL` *string array* | List of SQL queries to be executed as a superuser in the application
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitTemplateSQL` *string array* | List of SQL queries to be executed as a superuser in the `template1`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `import` *[Import](#import)* | Bootstraps the new cluster by importing data from an existing PostgreSQL
instance using logical backup (`pg_dump` and `pg_restore`) | | | | -| `postInitApplicationSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the application database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitTemplateSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `template1` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `postgres` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | - -#### BootstrapPgBaseBackup - -BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ------------------- | -| `source` *string* | The name of the server of which we need to take a physical backup | True | | MinLength: 1
| -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backup` *[BackupSource](#backupsource)* | The backup object containing the physical base backup from which to
initiate the recovery procedure.
Mutually exclusive with `source` and `volumeSnapshots`. | | | | -| `source` *string* | 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`. | | | | -| `volumeSnapshots` *[DataSource](#datasource)* | 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 {{name.ln}}, 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`. | | | | -| `recoveryTarget` *[RecoveryTarget](#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: | | | | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | - -#### CatalogImage - -CatalogImage defines the image and major version - -*Appears in:* - -- [ImageCatalogSpec](#imagecatalogspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------- | -------- | ------- | ------------------ | -| `image` *string* | The image reference | True | | | -| `major` *integer* | The PostgreSQL major version of the image. Must be unique within the catalog. | True | | Minimum: 10
| -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | - -#### CertificatesConfiguration - -CertificatesConfiguration contains the needed configurations to handle server certificates. - -*Appears in:* - -- [CertificatesStatus](#certificatesstatus) -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | - -#### CertificatesStatus - -CertificatesStatus contains configuration certificates and related expiration dates. - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | -| `expirations` *object (keys:string, values:string)* | Expiration dates for all certificates. | | | | - -#### Cluster - -Cluster defines the API schema for a highly available PostgreSQL database cluster -managed by {{name.ln}}. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Cluster` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ClusterSpec](#clusterspec)* | Specification of the desired behavior of the cluster.
More info: | True | | | -| `status` *[ClusterStatus](#clusterstatus)* | Most recently observed status of the cluster. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ClusterImageCatalog - -ClusterImageCatalog is the Schema for the clusterimagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ClusterImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ClusterImageCatalog.
More info: | True | | | - -#### ClusterMonitoringTLSConfiguration - -ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring - -*Appears in:* - -- [MonitoringConfiguration](#monitoringconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------- | -------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Enable TLS for the monitoring endpoint.
Changing this option will force a rollout of all instances. | | false | | - -#### ClusterSpec - -ClusterSpec defines the desired state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ | ---------------------------------------------------------------------- | -| `description` *string* | Description of this PostgreSQL cluster | | | | -| `inheritedMetadata` *[EmbeddedObjectMetadata](#embeddedobjectmetadata)* | Metadata that will be inherited by all objects related to the Cluster | | | | -| `imageName` *string* | Name of the container image, supporting both tags (`:`)
and digests for deterministic and repeatable deployments
(`:@sha256:`) | | | | -| `imageCatalogRef` *[ImageCatalogRef](#imagecatalogref)* | Defines the major PostgreSQL version we want to use within an ImageCatalog | | | | -| `imagePullPolicy` *[PullPolicy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#pullpolicy-v1-core)* | Image pull policy.
One of `Always`, `Never` or `IfNotPresent`.
If not defined, it defaults to `IfNotPresent`.
Cannot be updated.
More info: | | | | -| `schedulerName` *string* | 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:
| | | | -| `postgresUID` *integer* | The UID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `postgresGID` *integer* | The GID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `instances` *integer* | Number of instances required in the cluster | True | 1 | Minimum: 1
| -| `minSyncReplicas` *integer* | Minimum number of instances required in synchronous replication with the
primary. Undefined or 0 allow writes to complete when no standby is
available. | | 0 | Minimum: 0
| -| `maxSyncReplicas` *integer* | 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. | | 0 | Minimum: 0
| -| `postgresql` *[PostgresConfiguration](#postgresconfiguration)* | Configuration of the PostgreSQL server | | | | -| `podSelectorRefs` *[PodSelectorRef](#podselectorref) array* | PodSelectorRefs defines named pod label selectors that can be referenced
in pg_hba rules using the ${podselector:NAME} syntax in the address field.
The operator resolves matching pod IPs and the instance manager expands
pg_hba lines accordingly. Only pods in the Cluster's own namespace are considered. | | | | -| `replicationSlots` *[ReplicationSlotsConfiguration](#replicationslotsconfiguration)* | Replication slots management configuration | | | | -| `bootstrap` *[BootstrapConfiguration](#bootstrapconfiguration)* | Instructions to bootstrap this cluster | | | | -| `replica` *[ReplicaClusterConfiguration](#replicaclusterconfiguration)* | Replica cluster configuration | | | | -| `superuserSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The secret containing the superuser password. If not defined a new
secret will be created with a randomly generated password | | | | -| `enableSuperuserAccess` *boolean* | 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`. Disabled by default. | | | | -| `certificates` *[CertificatesConfiguration](#certificatesconfiguration)* | The configuration for the CA and related certificates | | | | -| `imagePullSecrets` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference) array* | 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. | | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage of the instances | | | | -| `serviceAccountTemplate` *[ServiceAccountTemplate](#serviceaccounttemplate)* | Configure the generation of the service account | | | | -| `serviceAccountName` *string* | Name of an existing ServiceAccount in the same namespace to use for the cluster.
When specified, the operator will not create a new ServiceAccount
but will use the provided one. This is useful for sharing a single
ServiceAccount across multiple clusters (e.g., for cloud IAM configurations).
If not specified, a ServiceAccount will be created with the cluster name.
Mutually exclusive with ServiceAccountTemplate. | | | MaxLength: 253
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| -| `walStorage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `ephemeralVolumeSource` *[EphemeralVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#ephemeralvolumesource-v1-core)* | EphemeralVolumeSource allows the user to configure the source of ephemeral volumes. | | | | -| `startDelay` *integer* | 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). | | 3600 | | -| `stopDelay` *integer* | The time in seconds that is allowed for a PostgreSQL instance to
gracefully shutdown (default 1800) | | 1800 | | -| `smartStopDelay` *integer* | Deprecated: please use SmartShutdownTimeout instead | | | | -| `smartShutdownTimeout` *integer* | 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`). Default is 180 seconds. | | 180 | | -| `switchoverDelay` *integer* | 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). | | 3600 | | -| `failoverDelay` *integer* | 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 | | 0 | | -| `livenessProbeTimeout` *integer* | 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` *[AffinityConfiguration](#affinityconfiguration)* | Affinity/Anti-affinity rules for Pods | | | | -| `topologySpreadConstraints` *[TopologySpreadConstraint](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#topologyspreadconstraint-v1-core) array* | TopologySpreadConstraints specifies how to spread matching pods among the given topology.
More info:
| | | | -| `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#resourcerequirements-v1-core)* | Resources requirements of every generated Pod. Please refer to

for more information. | | | | -| `ephemeralVolumesSizeLimit` *[EphemeralVolumesSizeLimitConfiguration](#ephemeralvolumessizelimitconfiguration)* | EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral
volumes | | | | -| `priorityClassName` *string* | 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

for more information | | | | -| `primaryUpdateStrategy` *[PrimaryUpdateStrategy](#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`) | | unsupervised | Enum: [unsupervised supervised]
| -| `primaryUpdateMethod` *[PrimaryUpdateMethod](#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).
Note: when using `switchover`, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process. | | | Enum: [switchover restart]
| -| `backup` *[BackupConfiguration](#backupconfiguration)* | The configuration to be used for backups | | | | -| `nodeMaintenanceWindow` *[NodeMaintenanceWindow](#nodemaintenancewindow)* | Define a maintenance window for the Kubernetes nodes | | | | -| `licenseKey` *string* | 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. | | | | -| `licenseKeySecret` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the license key. When this is set it take precedence over LicenseKey. | | | | -| `monitoring` *[MonitoringConfiguration](#monitoringconfiguration)* | The configuration of the monitoring infrastructure of this cluster | | | | -| `externalClusters` *[ExternalCluster](#externalcluster) array* | The list of external clusters which are used in the configuration | | | | -| `logLevel` *string* | The instances' log level, one of the following values: error, warning, info (default), debug, trace | | info | Enum: [error warning info debug trace]
| -| `projectedVolumeTemplate` *[ProjectedVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#projectedvolumesource-v1-core)* | Template to be used to define projected volumes, projected volumes will be mounted
under `/projected` base folder | | | | -| `env` *[EnvVar](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envvar-v1-core) array* | Env follows the Env format to pass environment variables
to the pods created in the cluster | | | | -| `envFrom` *[EnvFromSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envfromsource-v1-core) array* | EnvFrom follows the EnvFrom format to pass environment variables
sources to the pods to be used by Env | | | | -| `managed` *[ManagedConfiguration](#managedconfiguration)* | The configuration that is used by the portions of PostgreSQL that are managed by the instance manager | | | | -| `seccompProfile` *[SeccompProfile](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#seccompprofile-v1-core)* | The SeccompProfile applied to every Pod and Container.
Defaults to: `RuntimeDefault` | | | | -| `podSecurityContext` *[PodSecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podsecuritycontext-v1-core)* | Override the PodSecurityContext applied to every Pod of the cluster.
When set, this overrides the operator's default PodSecurityContext for the cluster.
If omitted, the operator defaults are used.
This field doesn't have any effect if SecurityContextConstraints are present. | | | | -| `securityContext` *[SecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#securitycontext-v1-core)* | Override the SecurityContext applied to every Container in the Pod of the cluster.
When set, this overrides the operator's default Container SecurityContext.
If omitted, the operator defaults are used. | | | | -| `tablespaces` *[TablespaceConfiguration](#tablespaceconfiguration) array* | The tablespaces configuration | | | | -| `enablePDB` *boolean* | 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 any
`PodDisruptionBudget` 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. | | true | | -| `plugins` *[PluginConfiguration](#pluginconfiguration) array* | The plugins configuration, containing
any plugin to be loaded with the corresponding configuration | | | | -| `probes` *[ProbesConfiguration](#probesconfiguration)* | The configuration of the probes to be injected
in the PostgreSQL Pods. | | | | - -#### ClusterStatus - -ClusterStatus defines the observed state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *integer* | The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods. | | | | -| `readyInstances` *integer* | The total number of ready instances in the cluster. It is equal to the number of ready instance pods. | | | | -| `instancesStatus` *object (keys:[PodStatus](#podstatus), values:string array)* | InstancesStatus indicates in which status the instances are | | | | -| `instancesReportedState` *object (keys:[PodName](#podname), values:[InstanceReportedState](#instancereportedstate))* | The reported state of the instances during the last reconciliation loop | | | | -| `managedRolesStatus` *[ManagedRoles](#managedroles)* | ManagedRolesStatus reports the state of the managed roles in the cluster | | | | -| `tablespacesStatus` *[TablespaceState](#tablespacestate) array* | TablespacesStatus reports the state of the declarative tablespaces in the cluster | | | | -| `podSelectorRefs` *[PodSelectorRefStatus](#podselectorrefstatus) array* | PodSelectorRefs contains the resolved pod IPs for each named selector
defined in spec.podSelectorRefs. | | | | -| `timelineID` *integer* | The timeline of the Postgres cluster | | | | -| `topology` *[Topology](#topology)* | Instances topology. | | | | -| `latestGeneratedNode` *integer* | ID of the latest generated node (used to avoid node name clashing) | | | | -| `currentPrimary` *string* | Current primary instance | | | | -| `targetPrimary` *string* | Target primary instance, this is different from the previous one
during a switchover or a failover | | | | -| `lastPromotionToken` *string* | LastPromotionToken is the last verified promotion token that
was used to promote a replica cluster | | | | -| `pvcCount` *integer* | How many PVCs have been created by this cluster | | | | -| `jobCount` *integer* | How many Jobs have been created by this cluster | | | | -| `danglingPVC` *string array* | List of all the PVCs created by this cluster and still available
which are not attached to a Pod | | | | -| `resizingPVC` *string array* | List of all the PVCs that have ResizingPVC condition. | | | | -| `initializingPVC` *string array* | List of all the PVCs that are being initialized by this cluster | | | | -| `healthyPVC` *string array* | List of all the PVCs not dangling nor initializing | | | | -| `unusablePVC` *string array* | List of all the PVCs that are unusable because another PVC is missing | | | | -| `licenseStatus` *Status* | Status of the license | | | | -| `writeService` *string* | Current write pod | | | | -| `readService` *string* | Current list of read pods | | | | -| `phase` *string* | Current phase of the cluster | | | | -| `phaseReason` *string* | Reason for the current phase | | | | -| `secretsResourceVersion` *[SecretsResourceVersion](#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` *[ConfigMapResourceVersion](#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` *[CertificatesStatus](#certificatesstatus)* | The configuration for the CA and related certificates, initialized with defaults. | | | | -| `firstRecoverabilityPoint` *string* | The first recoverability point, stored as a date in RFC3339 format.
This field is calculated from the content of FirstRecoverabilityPointByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `firstRecoverabilityPointByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | The first recoverability point, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackup` *string* | Last successful backup, stored as a date in RFC3339 format.
This field is calculated from the content of LastSuccessfulBackupByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackupByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | Last successful backup, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastFailedBackup` *string* | Last failed backup, stored as a date in RFC3339 format.
Deprecated: the field is not set for backup plugins. | | | | -| `cloudNativePostgresqlCommitHash` *string* | The commit hash number of which this operator running | | | | -| `currentPrimaryTimestamp` *string* | The timestamp when the last actual promotion to primary has occurred | | | | -| `currentPrimaryFailingSinceTimestamp` *string* | The timestamp when the primary was detected to be unhealthy
This field is reported when `.spec.failoverDelay` is populated or during online upgrades | | | | -| `targetPrimaryTimestamp` *string* | The timestamp when the last request for a new primary has occurred | | | | -| `poolerIntegrations` *[PoolerIntegrations](#poolerintegrations)* | The integration needed by poolers referencing the cluster | | | | -| `cloudNativePostgresqlOperatorHash` *string* | The hash of the binary of the operator | | | | -| `availableArchitectures` *[AvailableArchitecture](#availablearchitecture) array* | AvailableArchitectures reports the available architectures of a cluster | | | | -| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for cluster object | | | | -| `instanceNames` *string array* | List of instance names in the cluster | | | | -| `onlineUpdateEnabled` *boolean* | OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster | | | | -| `image` *string* | Image contains the image name used by the pods | | | | -| `pgDataImageInfo` *[ImageInfo](#imageinfo)* | PGDataImageInfo contains the details of the latest image that has run on the current data directory. | | | | -| `pluginStatus` *[PluginStatus](#pluginstatus) array* | PluginStatus is the status of the loaded plugins | | | | -| `switchReplicaClusterStatus` *[SwitchReplicaClusterStatus](#switchreplicaclusterstatus)* | SwitchReplicaClusterStatus is the status of the switch to replica cluster | | | | -| `demotionToken` *string* | DemotionToken is a JSON token containing the information
from pg_controldata such as Database system identifier, Latest checkpoint's
TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO
WAL file, and Time of latest checkpoint | | | | -| `systemID` *string* | SystemID is the latest detected PostgreSQL SystemID | | | | - -#### ConfigMapResourceVersion - -ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metrics` *object (keys:string, values:string)* | 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 | | | | - -#### DataDurabilityLevel - -*Underlying type:* *string* - -DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are `required` or `preferred`. - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -| Field | Description | -| ----------- | ----------------------------------------------------------------------------------------------------------------------- | -| `required` | DataDurabilityLevelRequired means that data durability is strictly enforced
| -| `preferred` | DataDurabilityLevelPreferred means that data durability is enforced
only when healthy replicas are available
| - -#### DataSource - -DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `storage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage of the instances | True | | | -| `walStorage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `tablespaceStorage` *object (keys:string, values:[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core))* | Configuration of the storage for PostgreSQL tablespaces | | | | - -#### Database - -Database is the Schema for the databases API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Database` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[DatabaseSpec](#databasespec)* | Specification of the desired Database.
More info: | True | | | -| `status` *[DatabaseStatus](#databasestatus)* | Most recently observed status of the Database. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### DatabaseObjectSpec - -DatabaseObjectSpec contains the fields which are common to every -database object - -*Appears in:* - -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| - -#### DatabaseObjectStatus - -DatabaseObjectStatus is the status of the managed database objects - -*Appears in:* - -- [DatabaseStatus](#databasestatus) - -| Field | Description | Required | Default | Validation | -| ------------------- | ----------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the object | True | | | -| `applied` *boolean* | True of the object has been installed successfully in
the database | True | | | -| `message` *string* | Message is the object reconciliation message | | | | - -#### DatabaseReclaimPolicy - -*Underlying type:* *string* - -DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases. - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | DatabaseReclaimDelete means the database will be deleted from its PostgreSQL Cluster on release
from its claim.
| -| `retain` | DatabaseReclaimRetain means the database will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### DatabaseRoleRef - -DatabaseRoleRef is a reference an a role available inside PostgreSQL - -*Appears in:* - -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------- | ----------- | -------- | ------- | ---------- | -| `name` *string* | | | | | - -#### DatabaseSpec - -DatabaseSpec is the specification of a Postgresql Database, built around the -`CREATE DATABASE`, `ALTER DATABASE`, and `DROP DATABASE` SQL commands of -PostgreSQL. - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster hosting the database. | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the PostgreSQL database is `present` or `absent` - defaults to "present". | | present | Enum: [present absent]
| -| `name` *string* | The name of the database to create inside PostgreSQL. This setting cannot be changed. | True | | | -| `owner` *string* | Maps to the `OWNER` parameter of `CREATE DATABASE`.
Maps to the `OWNER TO` command of `ALTER DATABASE`.
The role name of the user who owns the database inside PostgreSQL. | True | | | -| `template` *string* | Maps to the `TEMPLATE` parameter of `CREATE DATABASE`. This setting
cannot be changed. The name of the template from which to create
this database. | | | | -| `encoding` *string* | Maps to the `ENCODING` parameter of `CREATE DATABASE`. This setting
cannot be changed. Character set encoding to use in the database. | | | | -| `locale` *string* | Maps to the `LOCALE` parameter of `CREATE DATABASE`. This setting
cannot be changed. Sets the default collation order and character
classification in the new database. | | | | -| `localeProvider` *string* | Maps to the `LOCALE_PROVIDER` parameter of `CREATE DATABASE`. This
setting cannot be changed. This option sets the locale provider for
databases created in the new cluster. Available from PostgreSQL 16. | | | | -| `localeCollate` *string* | Maps to the `LC_COLLATE` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `localeCType` *string* | Maps to the `LC_CTYPE` parameter of `CREATE DATABASE`. This setting
cannot be changed. | | | | -| `icuLocale` *string* | Maps to the `ICU_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the ICU locale when the ICU
provider is used. This option requires `localeProvider` to be set to
`icu`. Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Maps to the `ICU_RULES` parameter of `CREATE DATABASE`. This setting
cannot be changed. Specifies additional collation rules to customize
the behavior of the default collation. This option requires
`localeProvider` to be set to `icu`. Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Maps to the `BUILTIN_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the locale name when the
builtin provider is used. This option requires `localeProvider` to
be set to `builtin`. Available from PostgreSQL 17. | | | | -| `collationVersion` *string* | Maps to the `COLLATION_VERSION` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `isTemplate` *boolean* | Maps to the `IS_TEMPLATE` parameter of `CREATE DATABASE` and `ALTER
DATABASE`. If true, this database is considered a template and can
be cloned by any user with `CREATEDB` privileges. | | | | -| `allowConnections` *boolean* | Maps to the `ALLOW_CONNECTIONS` parameter of `CREATE DATABASE` and
`ALTER DATABASE`. If false then no one can connect to this database. | | | | -| `connectionLimit` *integer* | Maps to the `CONNECTION LIMIT` clause of `CREATE DATABASE` and
`ALTER DATABASE`. How many concurrent connections can be made to
this database. -1 (the default) means no limit. | | | | -| `tablespace` *string* | Maps to the `TABLESPACE` parameter of `CREATE DATABASE`.
Maps to the `SET TABLESPACE` command of `ALTER DATABASE`.
The name of the tablespace (in PostgreSQL) that will be associated
with the new database. This tablespace will be the default
tablespace used for objects created in this database. | | | | -| `databaseReclaimPolicy` *[DatabaseReclaimPolicy](#databasereclaimpolicy)* | The policy for end-of-life maintenance of this database. | | retain | Enum: [delete retain]
| -| `schemas` *[SchemaSpec](#schemaspec) array* | The list of schemas to be managed in the database | | | | -| `extensions` *[ExtensionSpec](#extensionspec) array* | The list of extensions to be managed in the database | | | | -| `fdws` *[FDWSpec](#fdwspec) array* | The list of foreign data wrappers to be managed in the database | | | | -| `servers` *[ServerSpec](#serverspec) array* | The list of foreign servers to be managed in the database | | | | - -#### DatabaseStatus - -DatabaseStatus defines the observed state of Database - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the database was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | -| `schemas` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Schemas is the status of the managed schemas | | | | -| `extensions` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Extensions is the status of the managed extensions | | | | -| `fdws` *[DatabaseObjectStatus](#databaseobjectstatus) array* | FDWs is the status of the managed FDWs | | | | -| `servers` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Servers is the status of the managed servers | | | | - -#### EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `audit` *boolean* | If true enables edb_audit logging | | | | -| `tde` *[TDEConfiguration](#tdeconfiguration)* | TDE configuration | | | | - -#### EmbeddedObjectMetadata - -EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `labels` *object (keys:string, values:string)* | | | | | -| `annotations` *object (keys:string, values:string)* | | | | | - -#### EnsureOption - -*Underlying type:* *string* - -EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance - -*Appears in:* - -- [DatabaseObjectSpec](#databaseobjectspec) -- [DatabaseSpec](#databasespec) -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [OptionSpec](#optionspec) -- [RoleConfiguration](#roleconfiguration) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | -| --------- | ----------- | -| `present` | | -| `absent` | | - -#### EphemeralVolumesSizeLimitConfiguration - -EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------ | -------- | ------- | ---------- | -| `shm` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Shm is the size limit of the shared memory volume | | | | -| `temporaryData` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | TemporaryData is the size limit of the temporary data volume | | | | - -#### ExtensionConfiguration - -ExtensionConfiguration is the configuration used to add -PostgreSQL extensions to the Cluster. - -*Appears in:* - -- [CatalogImage](#catalogimage) -- [ImageInfo](#imageinfo) -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------------------------------------------- | -| `name` *string* | The name of the extension, required | True | | MinLength: 1
Pattern: `^[a-z0-9]([-a-z0-9_]*[a-z0-9])?$`
| -| `image` *[ImageVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#imagevolumesource-v1-core)* | The image containing the extension. | | | | -| `extension_control_path` *string array* | The list of directories inside the image which should be added to extension_control_path.
If not defined, defaults to "/share". | | | | -| `dynamic_library_path` *string array* | The list of directories inside the image which should be added to dynamic_library_path.
If not defined, defaults to "/lib". | | | | -| `ld_library_path` *string array* | The list of directories inside the image which should be added to ld_library_path. | | | | -| `bin_path` *string array* | A list of directories within the image to be appended to the
PostgreSQL process's `PATH` environment variable. | | | | -| `env` *[ExtensionEnvVar](#extensionenvvar) array* | Env is a list of custom environment variables to be set in the
PostgreSQL process for this extension. It is the responsibility of the
cluster administrator to ensure the variables are correct for the
specific extension. Note that changes to these variables require
a manual cluster restart to take effect. | | | | - -#### ExtensionEnvVar - -ExtensionEnvVar defines an environment variable for a specific extension -image volume. - -*Appears in:* - -- [ExtensionConfiguration](#extensionconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------------------------------- | -| `name` *string* | Name of the environment variable to be injected into the
PostgreSQL process. | True | | MinLength: 1
Pattern: `^[a-zA-Z_][a-zA-Z0-9_]*$`
| -| `value` *string* | Value of the environment variable. {{name.ln}} performs a direct
replacement of this value, with support for placeholder expansion.
The ${`image_root`} placeholder resolves to the absolute mount path
of the extension's volume (e.g., `/extensions/my-extension`). This
is particularly useful for allowing applications or libraries to
locate specific directories within the mounted image.
Unrecognized placeholders are rejected. To include a literal ${...}
in the value, escape it as $${...}. | True | | MinLength: 1
| - -#### ExtensionSpec - -ExtensionSpec configures an extension in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `version` *string* | The version of the extension to install. If empty, the operator will
install the default version (whatever is specified in the
extension's control file) | True | | | -| `schema` *string* | The name of the schema in which to install the extension's objects,
in case the extension allows its contents to be relocated. If not
specified (default), and the extension's control file does not
specify a schema either, the current default object creation schema
is used. | True | | | - -#### ExternalCluster - -ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The server name, required | True | | | -| `connectionParameters` *object (keys:string, values:string)* | The list of connection parameters, such as dbname, host, username, etc | | | | -| `sslCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL certificate to be used to connect to this
instance | | | | -| `sslKey` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL private key to be used to connect to this
instance | | | | -| `sslRootCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL CA public key to be used to connect to this
instance | | | | -| `password` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the password to be used to connect to the server.
If a password is provided, {{name.ln}} 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. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `plugin` *[PluginConfiguration](#pluginconfiguration)* | The configuration of the plugin that is taking care
of WAL archiving and backups for this external cluster | True | | | - -#### FDWSpec - -FDWSpec configures an Foreign Data Wrapper in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `handler` *string* | Name of the handler function (e.g., "postgres_fdw_handler").
This will be empty if no handler is specified. In that case,
the default handler is registered when the FDW extension is created. | | | | -| `validator` *string* | Name of the validator function (e.g., "postgres_fdw_validator").
This will be empty if no validator is specified. In that case,
the default validator is registered when the FDW extension is created. | | | | -| `owner` *string* | Owner specifies the database role that will own the Foreign Data Wrapper.
The role must have superuser privileges in the target database. | | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the FDW. | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the FDW are granted or revoked. | | | | - -#### FailoverQuorum - -FailoverQuorum contains the information about the current failover -quorum status of a PG cluster. It is updated by the instance manager -of the primary node and reset to zero by the operator to trigger -an update. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `FailoverQuorum` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `status` *[FailoverQuorumStatus](#failoverquorumstatus)* | Most recently observed status of the failover quorum. | | | | - -#### FailoverQuorumStatus - -FailoverQuorumStatus is the latest observed status of the failover -quorum of the PG cluster. - -*Appears in:* - -- [FailoverQuorum](#failoverquorum) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | --------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `method` *string* | Contains the latest reported Method value. | | | | -| `standbyNames` *string array* | StandbyNames is the list of potentially synchronous
instance names. | | | | -| `standbyNumber` *integer* | StandbyNumber is the number of synchronous standbys that transactions
need to wait for replies from. | | | | -| `primary` *string* | Primary is the name of the primary instance that updated
this object the latest time. | | | | - -#### ImageCatalog - -ImageCatalog is the Schema for the imagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ImageCatalog.
More info: | True | | | - -#### ImageCatalogRef - -ImageCatalogRef defines the reference to a major version in an ImageCatalog - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiGroup` *string* | APIGroup is the group for the resource being referenced.
If APIGroup is not specified, the specified Kind must be in the core API group.
For any other third-party types, APIGroup is required. | | | | -| `kind` *string* | Kind is the type of resource being referenced | True | | | -| `name` *string* | Name is the name of resource being referenced | True | | | -| `major` *integer* | The major version of PostgreSQL we want to use from the ImageCatalog | True | | | - -#### ImageCatalogSpec - -ImageCatalogSpec defines the desired ImageCatalog - -*Appears in:* - -- [ClusterImageCatalog](#clusterimagecatalog) -- [ImageCatalog](#imagecatalog) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------- | ---------------------------------------------- | -------- | ------- | ------------------------------------ | -| `images` *[CatalogImage](#catalogimage) array* | List of CatalogImages available in the catalog | True | | MaxItems: 8
MinItems: 1
| - -#### ImageInfo - -ImageInfo contains the information about a PostgreSQL image - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `image` *string* | Image is the image name | True | | | -| `majorVersion` *integer* | MajorVersion is the major version of the image | True | | | -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | Extensions contains the container image extensions available for the current Image | | | | - -#### Import - -Import contains the configuration to init a database from a logic snapshot of an externalCluster - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------ | -| `source` *[ImportSource](#importsource)* | The source of the import | True | | | -| `type` *[SnapshotType](#snapshottype)* | The import type. Can be `microservice` or `monolith`. | True | | Enum: [microservice monolith]
| -| `databases` *string array* | The databases to import | True | | | -| `roles` *string array* | The roles to import | | | | -| `postImportApplicationSQL` *string array* | 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. | | | | -| `schemaOnly` *boolean* | When set to true, only the `pre-data` and `post-data` sections of
`pg_restore` are invoked, avoiding data import. Default: `false`. | | | | -| `pgDumpExtraOptions` *string array* | List of custom options to pass to the `pg_dump` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreExtraOptions` *string array* | List of custom options to pass to the `pg_restore` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePredataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `pre-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreDataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePostdataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `post-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | - -#### ImportSource - -ImportSource describes the source for the logical snapshot - -*Appears in:* - -- [Import](#import) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ----------------------------------------------- | -------- | ------- | ---------- | -| `externalCluster` *string* | The name of the externalCluster used for import | True | | | - -#### InstanceID - -InstanceID contains the information to identify an instance - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `podName` *string* | The pod name | | | | -| `ContainerID` *string* | The container ID | | | | -| `sessionID` *string* | The instance manager session ID. This is a unique identifier generated at instance manager
startup and changes on every restart (including container reboots). Used to detect if
the instance manager was restarted during long-running operations like backups, which
would terminate any running backup process. | | | | - -#### InstanceReportedState - -InstanceReportedState describes the last reported state of an instance during a reconciliation loop - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------- | -------- | ------- | ---------- | -| `isPrimary` *boolean* | indicates if an instance is the primary one | True | | | -| `timeLineID` *integer* | indicates on which TimelineId the instance is | | | | -| `ip` *string* | IP address of the instance | True | | | - -#### IsolationCheckConfiguration - -IsolationCheckConfiguration contains the configuration for the isolation check -functionality in the liveness probe - -*Appears in:* - -- [LivenessProbe](#livenessprobe) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Whether primary isolation checking is enabled for the liveness probe | | true | | -| `requestTimeout` *integer* | Timeout in milliseconds for requests during the primary isolation check | | 1000 | | -| `connectionTimeout` *integer* | Timeout in milliseconds for connections during the primary isolation check | | 1000 | | - -#### LDAPBindAsAuth - -LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ----------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `prefix` *string* | Prefix for the bind authentication option | | | | -| `suffix` *string* | Suffix for the bind authentication option | | | | - -#### LDAPBindSearchAuth - -LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | -------- | ------- | ---------- | -| `baseDN` *string* | Root DN to begin the user search | | | | -| `bindDN` *string* | DN of the user to bind to the directory | | | | -| `bindPassword` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Secret with the password for the user to bind to the directory | | | | -| `searchAttribute` *string* | Attribute to match against the username | | | | -| `searchFilter` *string* | Search filter to use when doing the search+bind authentication | | | | - -#### LDAPConfig - -LDAPConfig contains the parameters needed for LDAP authentication - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ------------------------- | -| `server` *string* | LDAP hostname or IP address | | | | -| `port` *integer* | LDAP server port | | | | -| `scheme` *[LDAPScheme](#ldapscheme)* | LDAP schema to be used, possible options are `ldap` and `ldaps` | | | Enum: [ldap ldaps]
| -| `bindAsAuth` *[LDAPBindAsAuth](#ldapbindasauth)* | Bind as authentication configuration | | | | -| `bindSearchAuth` *[LDAPBindSearchAuth](#ldapbindsearchauth)* | Bind+Search authentication configuration | | | | -| `tls` *boolean* | Set to 'true' to enable LDAP over TLS. 'false' is default | | | | - -#### LDAPScheme - -*Underlying type:* *string* - -LDAPScheme defines the possible schemes for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | -| ------- | ----------- | -| `ldap` | | -| `ldaps` | | - -#### LivenessProbe - -LivenessProbe is the configuration of the liveness probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `isolationCheck` *[IsolationCheckConfiguration](#isolationcheckconfiguration)* | Configure the feature that extends the liveness probe for a primary
instance. In addition to the basic checks, this verifies whether the
primary is isolated from the Kubernetes API server and from its
replicas, ensuring that it can be safely shut down if network
partition or API unavailability is detected. Enabled by default. | | | | - -#### ManagedConfiguration - -ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------- | --------------------------------------- | -------- | ------- | ---------- | -| `roles` *[RoleConfiguration](#roleconfiguration) array* | Database roles managed by the `Cluster` | | | | -| `services` *[ManagedServices](#managedservices)* | Services roles managed by the `Cluster` | | | | - -#### ManagedRoles - -ManagedRoles tracks the status of a cluster's managed roles - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `byStatus` *object (keys:[RoleStatus](#rolestatus), values:string array)* | ByStatus gives the list of roles in each state | | | | -| `cannotReconcile` *object (keys:string, values:string array)* | CannotReconcile lists roles that cannot be reconciled in PostgreSQL,
with an explanation of the cause | | | | -| `passwordStatus` *object (keys:string, values:[PasswordState](#passwordstate))* | PasswordStatus gives the last transaction id and password secret version for each managed role | | | | - -#### ManagedService - -ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification. - -*Appears in:* - -- [ManagedServices](#managedservices) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `selectorType` *[ServiceSelectorType](#serviceselectortype)* | SelectorType specifies the type of selectors that the service will have.
Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services. | True | | Enum: [rw r ro]
| -| `updateStrategy` *[ServiceUpdateStrategy](#serviceupdatestrategy)* | UpdateStrategy describes how the service differences should be reconciled | | patch | Enum: [patch replace]
| -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | ServiceTemplate is the template specification for the service. | True | | | - -#### ManagedServices - -ManagedServices represents the services managed by the cluster. - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------- | -| `disabledDefaultServices` *[ServiceSelectorType](#serviceselectortype) array* | DisabledDefaultServices is a list of service types that are disabled by default.
Valid values are "r", and "ro", representing read, and read-only services. | | | Enum: [rw r ro]
| -| `additional` *[ManagedService](#managedservice) array* | Additional is a list of additional managed services specified by the user. | | | | - -#### 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. - -*Appears in:* - -- [PodTemplateSpec](#podtemplatespec) -- [ServiceAccountTemplate](#serviceaccounttemplate) -- [ServiceTemplateSpec](#servicetemplatespec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the resource. Only supported for certain types | | | | -| `labels` *object (keys:string, values:string)* | 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: | | | | -| `annotations` *object (keys:string, values:string)* | 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: | | | | - -#### MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `disableDefaultQueries` *boolean* | 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. | | false | | -| `customQueriesConfigMap` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | The list of config maps containing the custom queries | | | | -| `customQueriesSecret` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | The list of secrets containing the custom queries | | | | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor`
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | false | | -| `tls` *[ClusterMonitoringTLSConfiguration](#clustermonitoringtlsconfiguration)* | Configure TLS communication for the metrics endpoint.
Changing tls.enabled option will force a rollout of all instances. | | | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `metricsQueriesTTL` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | The interval during which metrics computed from queries are considered current.
Once it is exceeded, a new scrape will trigger a rerun
of the queries.
If not set, defaults to 30 seconds, in line with Prometheus scraping defaults.
Setting this to zero disables the caching mechanism and can cause heavy load on the PostgreSQL server. | | | | - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `reusePVC` *boolean* | Reuse the existing PVC (wait for the node to come
up again) or not (recreate it elsewhere - when `instances` >1) | | true | | -| `inProgress` *boolean* | Is there a node maintenance activity in progress? | | false | | - -#### OnlineConfiguration - -OnlineConfiguration contains the configuration parameters for the online volume snapshot - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `waitForArchive` *boolean* | 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. | | true | | -| `immediateCheckpoint` *boolean* | 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. | | | | - -#### OptionSpec - -OptionSpec holds the name, value and the ensure field for an option - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the option | True | | | -| `value` *string* | Value of the option | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an option should be present or absent in
the database. If set to `present`, the option will be
created if it does not exist. If set to `absent`, the
option will be removed if it exists. | | present | Enum: [present absent]
| - -#### PasswordState - -PasswordState represents the state of the password of a managed RoleConfiguration - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ------------------------------------------------------------------- | -------- | ------- | ---------- | -| `transactionID` *integer* | the last transaction ID to affect the role definition in PostgreSQL | | | | -| `resourceVersion` *string* | the resource version of the password secret | | | | - -#### PgBouncerIntegrationStatus - -PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster - -*Appears in:* - -- [PoolerIntegrations](#poolerintegrations) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------- | -------- | ------- | ---------- | -| `secrets` *string array* | | | | | - -#### PgBouncerPoolMode - -*Underlying type:* *string* - -PgBouncerPoolMode is the mode of PgBouncer - -*Validation:* - -- Enum: [session transaction] - -*Appears in:* - -- [PgBouncerSpec](#pgbouncerspec) - -#### PgBouncerSecrets - -PgBouncerSecrets contains the versions of the secrets used -by pgbouncer - -*Appears in:* - -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | ----------------------------- | -------- | ------- | ---------- | -| `authQuery` *[SecretVersion](#secretversion)* | The auth query secret version | | | | - -#### PgBouncerSpec - -PgBouncerSpec defines how to configure PgBouncer - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------------- | -| `poolMode` *[PgBouncerPoolMode](#pgbouncerpoolmode)* | The pool mode. Default: `session`. | | session | Enum: [session transaction]
| -| `serverTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerTLSSecret, when pointing to a TLS secret, provides pgbouncer's
`server_tls_key_file` and `server_tls_cert_file`, used when
authenticating against PostgreSQL. | | | | -| `serverCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerCASecret provides PgBouncer’s server_tls_ca_file, the root
CA for validating PostgreSQL certificates | | | | -| `clientCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientCASecret provides PgBouncer’s client_tls_ca_file, the root
CA for validating client certificates | | | | -| `clientTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientTLSSecret provides PgBouncer’s client_tls_key_file (private key)
and client_tls_cert_file (certificate) used to accept client connections | | | | -| `authQuerySecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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.
Deprecated. | | | | -| `authQuery` *string* | 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. | | | | -| `parameters` *object (keys:string, values:string)* | Additional parameters to be passed to PgBouncer - please check
the CNP documentation for a list of options you can configure | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file) | | | | -| `paused` *boolean* | 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. | | false | | - -#### PluginConfiguration - -PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [ExternalCluster](#externalcluster) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the plugin name | True | | | -| `enabled` *boolean* | Enabled is true if this plugin will be used | | true | | -| `isWALArchiver` *boolean* | Marks the plugin as the WAL archiver. At most one plugin can be
designated as a WAL archiver. This cannot be enabled if the
`.spec.backup.barmanObjectStore` configuration is present. | | false | | -| `parameters` *object (keys:string, values:string)* | Parameters is the configuration of the plugin | | | | - -#### PluginStatus - -PluginStatus is the status of a loaded plugin - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin | True | | | -| `version` *string* | Version is the version of the plugin loaded by the
latest reconciliation loop | True | | | -| `capabilities` *string array* | Capabilities are the list of capabilities of the
plugin | | | | -| `operatorCapabilities` *string array* | OperatorCapabilities are the list of capabilities of the
plugin regarding the reconciler | | | | -| `walCapabilities` *string array* | WALCapabilities are the list of capabilities of the
plugin regarding the WAL management | | | | -| `backupCapabilities` *string array* | BackupCapabilities are the list of capabilities of the
plugin regarding the Backup management | | | | -| `restoreJobHookCapabilities` *string array* | RestoreJobHookCapabilities are the list of capabilities of the
plugin regarding the RestoreJobHook management | | | | -| `status` *string* | Status contain the status reported by the plugin through the SetStatusInCluster interface | | | | - -#### PodName - -*Underlying type:* *string* - -PodName is the name of a Pod - -*Appears in:* - -- [ClusterStatus](#clusterstatus) -- [Topology](#topology) - -#### PodSelectorRef - -PodSelectorRef defines a named pod label selector for use in pg_hba rules. -Pods matching the selector in the Cluster's namespace will have their IPs -resolved and made available for pg_hba address expansion via the -`${podselector:NAME}` syntax. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------------------------------------ | -| `name` *string* | Name is the identifier used to reference this selector in pg_hba rules
via the ${podselector:NAME} syntax in the address field. | True | | MinLength: 1
Pattern: `^[a-z]([a-z0-9_-]*[a-z0-9])?$`
| -| `selector` *[LabelSelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#labelselector-v1-meta)* | Selector is a label selector that identifies the pods whose IPs
should be resolved. Only pods in the Cluster's namespace are considered. | True | | | - -#### PodSelectorRefStatus - -PodSelectorRefStatus contains the resolved pod IPs for a named selector. - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| -------------------- | ------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name corresponds to the name in the spec's PodSelectorRef. | True | | | -| `ips` *string array* | IPs is the list of pod IPs matching the selector.
Each IP is a single address (no CIDR notation). | | | | - -#### PodStatus - -*Underlying type:* *string* - -PodStatus represent the possible status of pods - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -#### 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: - - - - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[PodSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podspec-v1-core)* | Specification of the desired behavior of the pod.
More info: | | | | - -#### PodTopologyLabels - -*Underlying type:* *object* - -PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue - -*Appears in:* - -- [Topology](#topology) - -#### Pooler - -Pooler is the Schema for the poolers API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Pooler` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PoolerSpec](#poolerspec)* | Specification of the desired behavior of the Pooler.
More info: | True | | | -| `status` *[PoolerStatus](#poolerstatus)* | Most recently observed status of the Pooler. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `pgBouncerIntegration` *[PgBouncerIntegrationStatus](#pgbouncerintegrationstatus)* | | | | | - -#### 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. - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor` | | false | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping. | | | | - -#### PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -*Appears in:* - -- [PoolerStatus](#poolerstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------- | -------------------------------------------- | -------- | ------- | ---------- | -| `clientTLS` *[SecretVersion](#secretversion)* | The client TLS secret version | | | | -| `serverTLS` *[SecretVersion](#secretversion)* | The server TLS secret version | | | | -| `serverCA` *[SecretVersion](#secretversion)* | The server CA secret version | | | | -| `clientCA` *[SecretVersion](#secretversion)* | The client CA secret version | | | | -| `pgBouncerSecrets` *[PgBouncerSecrets](#pgbouncersecrets)* | The version of the secrets used by PgBouncer | | | | - -#### PoolerSpec - -PoolerSpec defines the desired state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------------------------------------------------- | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | This is the cluster reference on which the Pooler will work.
Pooler name should never match with any cluster name within the same namespace. | True | | | -| `type` *[PoolerType](#poolertype)* | Type of service to forward traffic to. Default: `rw`. | | rw | Enum: [rw ro r]
| -| `instances` *integer* | The number of replicas we want. Default: 1. | | 1 | | -| `template` *[PodTemplateSpec](#podtemplatespec)* | The template of the Pod to be created | | | | -| `pgbouncer` *[PgBouncerSpec](#pgbouncerspec)* | The PgBouncer configuration | True | | | -| `deploymentStrategy` *[DeploymentStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#deploymentstrategy-v1-apps)* | The deployment strategy to use for pgbouncer to replace existing pods with new ones | | | | -| `monitoring` *[PoolerMonitoringConfiguration](#poolermonitoringconfiguration)* | The configuration of the monitoring infrastructure of this pooler.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | Template for the Service to be created | | | | -| `serviceAccountName` *string* | Name of an existing ServiceAccount in the same namespace to use for the pooler.
When specified, the operator will not create a new ServiceAccount
but will use the provided one. This is useful for sharing a single
ServiceAccount across multiple poolers (e.g., for cloud IAM configurations).
If not specified, a ServiceAccount will be created with the pooler name. | | | MaxLength: 253
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| - -#### PoolerStatus - -PoolerStatus defines the observed state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `secrets` *[PoolerSecrets](#poolersecrets)* | The resource version of the config object | | | | -| `instances` *integer* | The number of pods trying to be scheduled | | | | - -#### PoolerType - -*Underlying type:* *string* - -PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are `rw` and `ro`. - -*Validation:* - -- Enum: [rw ro r] - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -#### PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `parameters` *object (keys:string, values:string)* | PostgreSQL configuration options (postgresql.conf) | | | | -| `synchronous` *[SynchronousReplicaConfiguration](#synchronousreplicaconfiguration)* | Configuration of the PostgreSQL synchronous replication feature | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file).
Use the ${podselector:NAME} syntax to reference a pod selector;
the rule will be expanded for each Pod IP matching that selector. | | | | -| `pg_ident` *string array* | PostgreSQL User Name Maps rules (lines to be appended
to the pg_ident.conf file) | | | | -| `epas` *[EPASConfiguration](#epasconfiguration)* | EDB Postgres Advanced Server specific configurations | | | | -| `syncReplicaElectionConstraint` *[SyncReplicaElectionConstraints](#syncreplicaelectionconstraints)* | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be
set up. | | | | -| `shared_preload_libraries` *string array* | Lists of shared preload libraries to add to the default ones | | | | -| `ldap` *[LDAPConfig](#ldapconfig)* | Options to specify LDAP configuration | | | | -| `promotionTimeout` *integer* | 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 | | | | -| `enableAlterSystem` *boolean* | If this parameter is true, the user will be able to invoke `ALTER SYSTEM`
on this {{name.ln}} Cluster.
This should only be used for debugging and troubleshooting.
Defaults to false. | | | | -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | - -#### PrimaryUpdateMethod - -*Underlying type:* *string* - -PrimaryUpdateMethod defines the method to use when upgrading -the primary instance of the cluster as part of rolling updates. -The default method is "restart" - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `switchover` | PrimaryUpdateMethodSwitchover means that the operator will switchover to another updated
replica when it needs to upgrade the primary instance.
Note: when using this method, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process.
| -| `restart` | PrimaryUpdateMethodRestart means that the operator will restart the primary instance in-place
when it needs to upgrade it
| - -#### PrimaryUpdateStrategy - -*Underlying type:* *string* - -PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `supervised` | PrimaryUpdateStrategySupervised means that the operator need to wait for the
user to manually issue a switchover request before updating the primary
server (`supervised`)
| -| `unsupervised` | PrimaryUpdateStrategyUnsupervised means that the operator will proceed with the
selected PrimaryUpdateMethod to another updated replica and then automatically update
the primary server (`unsupervised`, default)
| - -#### Probe - -Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic. - -*Appears in:* - -- [LivenessProbe](#livenessprobe) -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | - -#### ProbeStrategyType - -*Underlying type:* *string* - -ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready - -*Appears in:* - -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `pg_isready` | ProbeStrategyPgIsReady means that the pg_isready tool is used to determine
whether PostgreSQL is started up
| -| `streaming` | ProbeStrategyStreaming means that pg_isready is positive and the replica is
connected via streaming replication to the current primary and the lag is, if specified,
within the limit.
| -| `query` | ProbeStrategyQuery means that the server is able to connect to the superuser database
and able to execute a simple query like "-- ping"
| - -#### ProbeWithStrategy - -ProbeWithStrategy is the configuration of the startup probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------------------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `type` *[ProbeStrategyType](#probestrategytype)* | The probe strategy | | | Enum: [pg_isready streaming query]
| -| `maximumLag` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Lag limit. Used only for `streaming` strategy | | | | - -#### ProbesConfiguration - -ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `startup` *[ProbeWithStrategy](#probewithstrategy)* | The startup probe configuration | True | | | -| `liveness` *[LivenessProbe](#livenessprobe)* | The liveness probe configuration | True | | | -| `readiness` *[ProbeWithStrategy](#probewithstrategy)* | The readiness probe configuration | True | | | - -#### Publication - -Publication is the Schema for the publications API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Publication` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PublicationSpec](#publicationspec)* | | True | | | -| `status` *[PublicationStatus](#publicationstatus)* | | True | | | - -#### PublicationReclaimPolicy - -*Underlying type:* *string* - -PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications. - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | PublicationReclaimDelete means the publication will be deleted from Kubernetes on release
from its claim.
| -| `retain` | PublicationReclaimRetain means the publication will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### PublicationSpec - -PublicationSpec defines the desired state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "publisher" | True | | | -| `name` *string* | The name of the publication inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "publisher" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Publication parameters part of the `WITH` clause as expected by
PostgreSQL `CREATE PUBLICATION` command | | | | -| `target` *[PublicationTarget](#publicationtarget)* | Target of the publication as expected by PostgreSQL `CREATE PUBLICATION` command | True | | | -| `publicationReclaimPolicy` *[PublicationReclaimPolicy](#publicationreclaimpolicy)* | The policy for end-of-life maintenance of this publication | | retain | Enum: [delete retain]
| - -#### PublicationStatus - -PublicationStatus defines the observed state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the publication was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### PublicationTarget - -PublicationTarget is what this publication should publish - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------- | -| `allTables` *boolean* | Marks the publication as one that replicates changes for all tables
in the database, including tables created in the future.
Corresponding to `FOR ALL TABLES` in PostgreSQL. | | | | -| `objects` *[PublicationTargetObject](#publicationtargetobject) array* | Just the following schema objects | | | MaxItems: 100000
| - -#### PublicationTargetObject - -PublicationTargetObject is an object to publish - -*Appears in:* - -- [PublicationTarget](#publicationtarget) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `tablesInSchema` *string* | Marks the publication as one that replicates changes for all tables
in the specified list of schemas, including tables created in the
future. Corresponding to `FOR TABLES IN SCHEMA` in PostgreSQL. | | | | -| `table` *[PublicationTargetTable](#publicationtargettable)* | Specifies a list of tables to add to the publication. Corresponding
to `FOR TABLE` in PostgreSQL. | | | | - -#### PublicationTargetTable - -PublicationTargetTable is a table to publish - -*Appears in:* - -- [PublicationTargetObject](#publicationtargetobject) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `only` *boolean* | Whether to limit to the table only or include all its descendants | | | | -| `name` *string* | The table name | True | | | -| `schema` *string* | The schema name | | | | -| `columns` *string array* | The columns to publish | | | | - -#### RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backupID` *string* | 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. | | | | -| `targetTLI` *string* | The target timeline ("latest" or a positive integer) | | | | -| `targetXID` *string* | The target transaction ID | | | | -| `targetName` *string* | The target name (to be previously created
with `pg_create_restore_point`) | | | | -| `targetLSN` *string* | The target LSN (Log Sequence Number) | | | | -| `targetTime` *string* | The target time as a timestamp in RFC3339 format or PostgreSQL timestamp format.
Timestamps without an explicit timezone are interpreted as UTC. | | | | -| `targetImmediate` *boolean* | End recovery as soon as a consistent state is reached | | | | -| `exclusive` *boolean* | Set the target to be exclusive. If omitted, defaults to false, so that
in Postgres, `recovery_target_inclusive` will be true | | | | - -#### ReplicaClusterConfiguration - -ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------- | -| `self` *string* | Self defines the name of this cluster. It is used to determine if this is a primary
or a replica cluster, comparing it with `primary` | | | | -| `primary` *string* | Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the
topology specified in externalClusters | | | | -| `source` *string* | The name of the external cluster which is the replication origin | True | | MinLength: 1
| -| `enabled` *boolean* | 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. | | | | -| `promotionToken` *string* | A demotion token generated by an external cluster used to
check if the promotion requirements are met. | | | | -| `minApplyDelay` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | When replica mode is enabled, this parameter allows you to replay
transactions only when the system time is at least the configured
time past the commit time. This provides an opportunity to correct
data loss errors. Note that when this parameter is set, a promotion
token cannot be used. | | | | - -#### ReplicationSlotsConfiguration - -ReplicationSlotsConfiguration encapsulates the configuration -of replication slots - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------- | -| `highAvailability` *[ReplicationSlotsHAConfiguration](#replicationslotshaconfiguration)* | Replication slots for high availability configuration | | | | -| `updateInterval` *integer* | Standby will update the status of the local replication slots
every `updateInterval` seconds (default 30). | | | Minimum: 1
| -| `synchronizeReplicas` *[SynchronizeReplicasConfiguration](#synchronizereplicasconfiguration)* | Configures the synchronization of the user defined physical replication slots | | | | - -#### 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. - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------ | -| `enabled` *boolean* | 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. | | | | -| `slotPrefix` *string* | 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_`. | | | Pattern: `^[0-9a-z_]*$`
| -| `synchronizeLogicalDecoding` *boolean* | When enabled, the operator automatically manages synchronization of logical
decoding (replication) slots across high-availability clusters.
Requires one of the following conditions:
- PostgreSQL version 17 or later
- PostgreSQL version < 17 with pg_failover_slots extension enabled | | | | - -#### 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: - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the role | True | | | -| `comment` *string* | Description of the role | | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the role is `present` or `absent` - defaults to "present" | | present | Enum: [present absent]
| -| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present)
If null, the password will be ignored unless DisablePassword is set | | | | -| `connectionLimit` *integer* | If the role can log in, this specifies how many concurrent
connections the role can make. `-1` (the default) means no limit. | | -1 | | -| `validUntil` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Date and time after which the role's password is no longer valid.
When omitted, the password will never expire (default). | | | | -| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty. | | | | -| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Defaults is `true`. | | true | | -| `disablePassword` *boolean* | DisablePassword indicates that a role's password should be set to NULL in Postgres | | | | -| `superuser` *boolean* | 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`. | | | | -| `createdb` *boolean* | 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. | | | | -| `createrole` *boolean* | 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`. | | | | -| `login` *boolean* | 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`. | | | | -| `replication` *boolean* | 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`. | | | | -| `bypassrls` *boolean* | Whether a role bypasses every row-level security (RLS) policy.
Default is `false`. | | | | - -#### RoleStatus - -*Underlying type:* *string* - -RoleStatus represents the status of a managed role in the cluster - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | -| ------------------------ | ----------------------------------------------------------------------------------------------------- | -| `reconciled` | RoleStatusReconciled indicates the role in DB matches the Spec
| -| `not-managed` | RoleStatusNotManaged indicates the role is not in the Spec, therefore not managed
| -| `pending-reconciliation` | RoleStatusPendingReconciliation indicates the role in Spec requires updated/creation in DB
| -| `reserved` | RoleStatusReserved indicates this is one of the roles reserved by the operator. E.g. `postgres`
| - -#### SQLRefs - -SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------- | ------- | ---------- | -| `secretRefs` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | SecretRefs holds a list of references to Secrets | | | | -| `configMapRefs` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | ConfigMapRefs holds a list of references to ConfigMaps | | | | - -#### ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ScheduledBackup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ScheduledBackupSpec](#scheduledbackupspec)* | Specification of the desired behavior of the ScheduledBackup.
More info: | True | | | -| `status` *[ScheduledBackupStatus](#scheduledbackupstatus)* | Most recently observed status of the ScheduledBackup. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `suspend` *boolean* | If this backup is suspended or not | | | | -| `immediate` *boolean* | If the first backup has to be immediately start after creation or not | | | | -| `schedule` *string* | The schedule does not follow the same format used in Kubernetes CronJobs
as it includes an additional seconds specifier,
see | True | | | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `backupOwnerReference` *string* | 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
| | none | Enum: [none self cluster]
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `lastCheckTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | The latest time the schedule | | | | -| `lastScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Information when was the last time that backup was successfully scheduled. | | | | -| `nextScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Next time we will run a backup | | | | - -#### SchemaSpec - -SchemaSpec configures a schema in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `owner` *string* | The role name of the user who owns the schema inside PostgreSQL.
It maps to the `AUTHORIZATION` parameter of `CREATE SCHEMA` and the
`OWNER TO` command of `ALTER SCHEMA`. | True | | | - -#### SecretVersion - -SecretVersion contains a secret name and its ResourceVersion - -*Appears in:* - -- [PgBouncerSecrets](#pgbouncersecrets) -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| ------------------ | --------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the secret | | | | -| `version` *string* | The ResourceVersion of the secret | | | | - -#### SecretsResourceVersion - -SecretsResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `superuserSecretVersion` *string* | The resource version of the "postgres" user secret | | | | -| `replicationSecretVersion` *string* | The resource version of the "streaming_replica" user secret | | | | -| `applicationSecretVersion` *string* | The resource version of the "app" user secret | | | | -| `managedRoleSecretVersion` *object (keys:string, values:string)* | The resource versions of the managed roles secrets | | | | -| `caSecretVersion` *string* | Unused. Retained for compatibility with old versions. | | | | -| `clientCaSecretVersion` *string* | The resource version of the PostgreSQL client-side CA secret version | | | | -| `serverCaSecretVersion` *string* | The resource version of the PostgreSQL server-side CA secret version | | | | -| `serverSecretVersion` *string* | The resource version of the PostgreSQL server-side secret version | | | | -| `barmanEndpointCA` *string* | The resource version of the Barman Endpoint CA if provided | | | | -| `externalClusterSecretVersion` *object (keys:string, values:string)* | The resource versions of the external cluster secrets | | | | -| `metrics` *object (keys:string, values:string)* | A map with the versions of all the secrets used to pass metrics.
Map keys are the secret names, map values are the versions | | | | - -#### ServerSpec - -ServerSpec configures a server of a foreign data wrapper - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `fdw` *string* | The name of the Foreign Data Wrapper (FDW) | True | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the server
(key is the option name, value is the option value). | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the server are granted or revoked. | | | | - -#### ServiceAccountTemplate - -ServiceAccountTemplate contains the template needed to generate the service accounts - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | - -#### ServiceSelectorType - -*Underlying type:* *string* - -ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only - -*Validation:* - -- Enum: [rw r ro] - -*Appears in:* - -- [ManagedService](#managedservice) -- [ManagedServices](#managedservices) - -| Field | Description | -| ----- | ----------------------------------------------------------- | -| `rw` | ServiceSelectorTypeRW selects the read-write service.
| -| `r` | ServiceSelectorTypeR selects the read service.
| -| `ro` | ServiceSelectorTypeRO selects the read-only service.
| - -#### ServiceTemplateSpec - -ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation. - -*Appears in:* - -- [ManagedService](#managedservice) -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[ServiceSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#servicespec-v1-core)* | Specification of the desired behavior of the service.
More info: | | | | - -#### ServiceUpdateStrategy - -*Underlying type:* *string* - -ServiceUpdateStrategy describes how the changes to the managed service should be handled - -*Validation:* - -- Enum: [patch replace] - -*Appears in:* - -- [ManagedService](#managedservice) - -#### SnapshotOwnerReference - -*Underlying type:* *string* - -SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to. - -*Appears in:* - -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | -| --------- | ------------------------------------------------------------------------------------------------- | -| `none` | SnapshotOwnerReferenceNone indicates that the snapshot does not have any owner reference.
| -| `backup` | SnapshotOwnerReferenceBackup indicates that the snapshot is owned by the backup resource.
| -| `cluster` | SnapshotOwnerReferenceCluster indicates that the snapshot is owned by the cluster resource.
| - -#### SnapshotType - -*Underlying type:* *string* - -SnapshotType is a type of allowed import - -*Appears in:* - -- [Import](#import) - -| Field | Description | -| -------------- | ----------------------------------------------------------------------------------- | -| `monolith` | MonolithSnapshotType indicates to execute the monolith clone typology
| -| `microservice` | MicroserviceSnapshotType indicates to execute the microservice clone typology
| - -#### StorageConfiguration - -StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `storageClass` *string* | 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` *string* | 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. | | | | -| `resizeInUseVolumes` *boolean* | Resize existent PVCs, defaults to true | | true | | -| `pvcTemplate` *[PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#persistentvolumeclaimspec-v1-core)* | Template to be used to generate the Persistent Volume Claim | | | | - -#### Subscription - -Subscription is the Schema for the subscriptions API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Subscription` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[SubscriptionSpec](#subscriptionspec)* | | True | | | -| `status` *[SubscriptionStatus](#subscriptionstatus)* | | True | | | - -#### SubscriptionReclaimPolicy - -*Underlying type:* *string* - -SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions. - -*Appears in:* - -- [SubscriptionSpec](#subscriptionspec) - -| Field | Description | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `delete` | SubscriptionReclaimDelete means the subscription will be deleted from Kubernetes on release
from its claim.
| -| `retain` | SubscriptionReclaimRetain means the subscription will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### SubscriptionSpec - -SubscriptionSpec defines the desired state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "subscriber" | True | | | -| `name` *string* | The name of the subscription inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "subscriber" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Subscription parameters included in the `WITH` clause of the PostgreSQL
`CREATE SUBSCRIPTION` command. Most parameters cannot be changed
after the subscription is created and will be ignored if modified
later, except for a limited set documented at:
| | | | -| `publicationName` *string* | The name of the publication inside the PostgreSQL database in the
"publisher" | True | | | -| `publicationDBName` *string* | The name of the database containing the publication on the external
cluster. Defaults to the one in the external cluster definition. | | | | -| `externalClusterName` *string* | The name of the external cluster with the publication ("publisher") | True | | | -| `subscriptionReclaimPolicy` *[SubscriptionReclaimPolicy](#subscriptionreclaimpolicy)* | The policy for end-of-life maintenance of this subscription | | retain | Enum: [delete retain]
| - -#### SubscriptionStatus - -SubscriptionStatus defines the observed state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the subscription was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### SwitchReplicaClusterStatus - -SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `inProgress` *boolean* | InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster. | | | | - -#### 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. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `nodeLabelsAntiAffinity` *string array* | A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not | | | | -| `enabled` *boolean* | This flag enables the constraints for sync replicas | True | | | - -#### SynchronizeReplicasConfiguration - -SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | When set to true, every replication slot that is on the primary is synchronized on each standby | True | | | -| `excludePatterns` *string array* | List of regular expression patterns to match the names of replication slots to be excluded (by default empty) | | | | - -#### SynchronousReplicaConfiguration - -SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also `.spec.minSyncReplicas` and `.spec.maxSyncReplicas` -need to be considered. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------- | -| `method` *[SynchronousReplicaConfigurationMethod](#synchronousreplicaconfigurationmethod)* | Method to select synchronous replication standbys from the listed
servers, accepting 'any' (quorum-based synchronous replication) or
'first' (priority-based synchronous replication) as values. | True | | Enum: [any first]
| -| `number` *integer* | Specifies the number of synchronous standby servers that
transactions must wait for responses from. | True | | | -| `maxStandbyNamesFromCluster` *integer* | Specifies the maximum number of local cluster pods that can be
automatically included in the `synchronous_standby_names` option in
PostgreSQL. | | | | -| `standbyNamesPre` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` before local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `standbyNamesPost` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` after local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `dataDurability` *[DataDurabilityLevel](#datadurabilitylevel)* | If set to "required", data durability is strictly enforced. Write operations
with synchronous commit settings (`on`, `remote_write`, or `remote_apply`) will
block if there are insufficient healthy replicas, ensuring data persistence.
If set to "preferred", data durability is maintained when healthy replicas
are available, but the required number of instances will adjust dynamically
if replicas become unavailable. This setting relaxes strict durability enforcement
to allow for operational continuity. This setting is only applicable if both
`standbyNamesPre` and `standbyNamesPost` are unset (empty). | | | Enum: [required preferred]
| -| `failoverQuorum` *boolean* | FailoverQuorum enables a quorum-based check before failover, improving
data durability and safety during failover events in {{name.ln}}-managed
PostgreSQL clusters. | | | | - -#### SynchronousReplicaConfigurationMethod - -*Underlying type:* *string* - -SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -#### TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -*Appears in:* - -- [EPASConfiguration](#epasconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | True if we want to have TDE enabled | | | | -| `secretKeyRef` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Reference to the secret that contains the encryption key | | | | -| `wrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | WrapCommand is the encrypt command provided by the user | | | | -| `unwrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | UnwrapCommand is the decryption command provided by the user | | | | -| `passphraseCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | PassphraseCommand is the command executed to get the passphrase that will be
passed to the OpenSSL command to encrypt and decrypt | | | | - -#### TablespaceConfiguration - -TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the tablespace | True | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | The storage configuration for the tablespace | True | | | -| `owner` *[DatabaseRoleRef](#databaseroleref)* | Owner is the PostgreSQL user owning the tablespace | | | | -| `temporary` *boolean* | When set to true, the tablespace will be added as a `temp_tablespaces`
entry 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. | | false | | - -#### TablespaceState - -TablespaceState represents the state of a tablespace in a cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | -------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the tablespace | True | | | -| `owner` *string* | Owner is the PostgreSQL user owning the tablespace | | | | -| `state` *[TablespaceStatus](#tablespacestatus)* | State is the latest reconciliation state | True | | | -| `error` *string* | Error is the reconciliation error, if any | | | | - -#### TablespaceStatus - -*Underlying type:* *string* - -TablespaceStatus represents the status of a tablespace in the cluster - -*Appears in:* - -- [TablespaceState](#tablespacestate) - -| Field | Description | -| ------------ | -------------------------------------------------------------------------------------------------------- | -| `reconciled` | TablespaceStatusReconciled indicates the tablespace in DB matches the Spec
| -| `pending` | TablespaceStatusPendingReconciliation indicates the tablespace in Spec requires creation in the DB
| - -#### Topology - -Topology contains the cluster topology - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *object (keys:[PodName](#podname), values:[PodTopologyLabels](#podtopologylabels))* | Instances contains the pod topology of the instances | | | | -| `nodesUsed` *integer* | 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` *boolean* | SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors
in synchronous replica election in case of failures | | | | - -#### UsageSpec - -UsageSpec configures a usage for a foreign data wrapper - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------- | -------- | ------- | --------------------------- | -| `name` *string* | Name of the usage | True | | | -| `type` *[UsageSpecType](#usagespectype)* | The type of usage | | grant | Enum: [grant revoke]
| - -#### UsageSpecType - -*Underlying type:* *string* - -UsageSpecType describes the type of usage specified in the `usage` field of the -`Database` object. - -*Appears in:* - -- [UsageSpec](#usagespec) - -| Field | Description | -| -------- | -------------------------------------------------------------------------------------------------------- | -| `grant` | GrantUsageSpecType indicates a grant usage permission.
The default usage permission is grant.
| -| `revoke` | RevokeUsageSpecType indicates a revoke usage permission.
| - -#### VolumeSnapshotConfiguration - -VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups. - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------- | ---------------------------------- | -| `labels` *object (keys:string, values:string)* | Labels are key-value pairs that will be added to .metadata.labels snapshot resources. | | | | -| `annotations` *object (keys:string, values:string)* | Annotations key-value pairs that will be added to .metadata.annotations snapshot resources. | | | | -| `className` *string* | 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` *string* | WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim. | | | | -| `tablespaceClassName` *object (keys:string, values:string)* | TablespaceClassName specifies the Snapshot Class to be used for the tablespaces.
defaults to the PGDATA Snapshot Class, if set | | | | -| `snapshotOwnerReference` *[SnapshotOwnerReference](#snapshotownerreference)* | SnapshotOwnerReference indicates the type of owner reference the snapshot should have | | none | Enum: [none cluster backup]
| -| `online` *boolean* | Whether the default type of backup with volume snapshots is
online/hot (`true`, default) or offline/cold (`false`) | | true | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots | | { immediateCheckpoint:false waitForArchive:true } | | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.29.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.29.1.mdx deleted file mode 100644 index 01107e5d96e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.29.1.mdx +++ /dev/null @@ -1,2406 +0,0 @@ ---- -title: API Reference - v1.29.1 -navTitle: v1.29.1 -pdfExclude: 'true' - ---- - -## Packages - -- [postgresql.k8s.enterprisedb.io/v1](#postgresqlk8senterprisedbiov1) - -## postgresql.k8s.enterprisedb.io/v1 - -Package v1 contains API Schema definitions for the postgresql v1 API group - -### Resource Types - -- [Backup](#backup) -- [Cluster](#cluster) -- [ClusterImageCatalog](#clusterimagecatalog) -- [Database](#database) -- [FailoverQuorum](#failoverquorum) -- [ImageCatalog](#imagecatalog) -- [Pooler](#pooler) -- [Publication](#publication) -- [ScheduledBackup](#scheduledbackup) -- [Subscription](#subscription) - -#### AffinityConfiguration - -AffinityConfiguration contains the info we need to create the -affinity rules for Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `enablePodAntiAffinity` *boolean* | Activates anti-affinity for the pods. The operator will define pods
anti-affinity unless this field is explicitly set to false | | | | -| `topologyKey` *string* | TopologyKey to use for anti-affinity configuration. See k8s documentation
for more info on that | | | | -| `nodeSelector` *object (keys:string, values:string)* | NodeSelector is map of key-value pairs used to define the nodes on which
the pods can run.
More info: | | | | -| `nodeAffinity` *[NodeAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#nodeaffinity-v1-core)* | NodeAffinity describes node affinity scheduling rules for the pod.
More info: | | | | -| `tolerations` *[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#toleration-v1-core) array* | 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: | | | | -| `podAntiAffinityType` *string* | 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:
| | | | -| `additionalPodAntiAffinity` *[PodAntiAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podantiaffinity-v1-core)* | 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` *[PodAffinity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podaffinity-v1-core)* | AdditionalPodAffinity allows to specify pod affinity terms to be passed to all the cluster's pods. | | | | - -#### AvailableArchitecture - -AvailableArchitecture represents the state of a cluster's architecture - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------- | ------------------------------------------------- | -------- | ------- | ---------- | -| `goArch` *string* | GoArch is the name of the executable architecture | True | | | -| `hash` *string* | Hash is the hash of the executable | True | | | - -#### Backup - -A Backup resource is a request for a PostgreSQL backup by the user. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Backup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[BackupSpec](#backupspec)* | Specification of the desired behavior of the backup.
More info: | True | | | -| `status` *[BackupStatus](#backupstatus)* | Most recently observed status of the backup. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### BackupConfiguration - -BackupConfiguration defines how the backup of the cluster are taken. -The supported backup methods are BarmanObjectStore and VolumeSnapshot. -For details and examples refer to the Backup and Recovery section of the -documentation - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `volumeSnapshot` *[VolumeSnapshotConfiguration](#volumesnapshotconfiguration)* | VolumeSnapshot provides the configuration for the execution of volume snapshot backups. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `retentionPolicy` *string* | 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. | | | Pattern: `^[1-9][0-9]*[dwm]$`
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| - -#### BackupMethod - -*Underlying type:* *string* - -BackupMethod defines the way of executing the physical base backups of -the selected PostgreSQL instance - -*Appears in:* - -- [BackupSpec](#backupspec) -- [BackupStatus](#backupstatus) -- [ClusterStatus](#clusterstatus) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | -| ------------------- | -------------------------------------------------------------------------------------------- | -| `volumeSnapshot` | BackupMethodVolumeSnapshot means using the volume snapshot
Kubernetes feature
| -| `barmanObjectStore` | BackupMethodBarmanObjectStore means using barman to backup the
PostgreSQL cluster
| -| `plugin` | BackupMethodPlugin means that this backup should be handled by
a plugin
| - -#### BackupPhase - -*Underlying type:* *string* - -BackupPhase is the phase of the backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -#### BackupPluginConfiguration - -BackupPluginConfiguration contains the backup configuration used by -the backup plugin - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin managing this backup | True | | | -| `parameters` *object (keys:string, values:string)* | Parameters are the configuration parameters passed to the backup
plugin for this backup | | | | - -#### BackupSnapshotElementStatus - -BackupSnapshotElementStatus is a volume snapshot that is part of a volume snapshot method backup - -*Appears in:* - -- [BackupSnapshotStatus](#backupsnapshotstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the snapshot resource name | True | | | -| `type` *string* | Type is tho role of the snapshot in the cluster, such as PG_DATA, PG_WAL and PG_TABLESPACE | True | | | -| `tablespaceName` *string* | TablespaceName is the name of the snapshotted tablespace. Only set
when type is PG_TABLESPACE | | | | - -#### BackupSnapshotStatus - -BackupSnapshotStatus the fields exclusive to the volumeSnapshot method backup - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `elements` *[BackupSnapshotElementStatus](#backupsnapshotelementstatus) array* | The elements list, populated with the gathered volume snapshots | | | | - -#### BackupSource - -BackupSource contains the backup we need to restore from, plus some -information that could be needed to correctly restore it. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name of the referent. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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 - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### BackupStatus - -BackupStatus defines the observed state of Backup - -*Appears in:* - -- [Backup](#backup) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `googleCredentials` *[GoogleCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#GoogleCredentials)* | The credentials to use to upload data to Google Cloud Storage | | | | -| `s3Credentials` *[S3Credentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#S3Credentials)* | The credentials to use to upload data to S3 | | | | -| `azureCredentials` *[AzureCredentials](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#AzureCredentials)* | The credentials to use to upload data to Azure Blob Storage | | | | -| `majorVersion` *integer* | The PostgreSQL major version that was running when the
backup was taken. | True | | | -| `endpointCA` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector)* | 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` *string* | Endpoint to be used to upload data to the cloud,
overriding the automatic endpoint discovery | | | | -| `destinationPath` *string* | 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. | | | | -| `serverName` *string* | The server name on S3, the cluster name is used if this
parameter is omitted | | | | -| `encryption` *string* | Encryption method required to S3 API | | | | -| `backupId` *string* | The ID of the Barman backup | | | | -| `backupName` *string* | The Name of the Barman backup | | | | -| `phase` *[BackupPhase](#backupphase)* | The last backup status | | | | -| `startedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup execution was started by the backup tool | | | | -| `stoppedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup execution was terminated by the backup tool | | | | -| `reconciliationStartedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the backup process was started by the operator | | | | -| `reconciliationTerminatedAt` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | When the reconciliation was terminated by the operator (either successfully or not) | | | | -| `beginWal` *string* | The starting WAL | | | | -| `endWal` *string* | The ending WAL | | | | -| `beginLSN` *string* | The starting xlog | | | | -| `endLSN` *string* | The ending xlog | | | | -| `error` *string* | The detected error | | | | -| `commandOutput` *string* | Unused. Retained for compatibility with old versions. | | | | -| `commandError` *string* | The backup command output in case of error | | | | -| `backupLabelFile` *integer array* | Backup label file content as returned by Postgres in case of online (hot) backups | | | | -| `tablespaceMapFile` *integer array* | Tablespace map file content as returned by Postgres in case of online (hot) backups | | | | -| `instanceID` *[InstanceID](#instanceid)* | Information to identify the instance where the backup has been taken from | | | | -| `snapshotBackupStatus` *[BackupSnapshotStatus](#backupsnapshotstatus)* | Status of the volumeSnapshot backup | | | | -| `method` *[BackupMethod](#backupmethod)* | The backup method being used | | | | -| `online` *boolean* | Whether the backup was online/hot (`true`) or offline/cold (`false`) | | | | -| `pluginMetadata` *object (keys:string, values:string)* | A map containing the plugin metadata | | | | - -#### BackupTarget - -*Underlying type:* *string* - -BackupTarget describes the preferred targets for a backup - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initdb` *[BootstrapInitDB](#bootstrapinitdb)* | Bootstrap the cluster via initdb | | | | -| `recovery` *[BootstrapRecovery](#bootstraprecovery)* | Bootstrap the cluster from a backup | | | | -| `pg_basebackup` *[BootstrapPgBaseBackup](#bootstrappgbasebackup)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------- | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | -| `redwood` *boolean* | If we need to enable/disable Redwood compatibility. Requires
EPAS and for EPAS defaults to true | | | | -| `options` *string array* | 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. | | | | -| `dataChecksums` *boolean* | Whether the `-k` option should be passed to initdb,
enabling checksums on data pages (default: `false`) | | | | -| `encoding` *string* | The value to be passed as option `--encoding` for initdb (default:`UTF8`) | | | | -| `localeCollate` *string* | The value to be passed as option `--lc-collate` for initdb (default:`C`) | | | | -| `localeCType` *string* | The value to be passed as option `--lc-ctype` for initdb (default:`C`) | | | | -| `locale` *string* | Sets the default collation order and character classification in the new database. | | | | -| `localeProvider` *string* | This option sets the locale provider for databases created in the new cluster.
Available from PostgreSQL 16. | | | | -| `icuLocale` *string* | Specifies the ICU locale when the ICU provider is used.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Specifies additional collation rules to customize the behavior of the default collation.
This option requires `localeProvider` to be set to `icu`.
Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Specifies the locale name when the builtin provider is used.
This option requires `localeProvider` to be set to `builtin`.
Available from PostgreSQL 17. | | | | -| `walSegmentSize` *integer* | The value in megabytes (1 to 1024) to be passed to the `--wal-segsize`
option for initdb (default: empty, resulting in PostgreSQL default: 16MB) | | | Maximum: 1024
Minimum: 1
| -| `postInitSQL` *string array* | List of SQL queries to be executed as a superuser in the `postgres`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitApplicationSQL` *string array* | List of SQL queries to be executed as a superuser in the application
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `postInitTemplateSQL` *string array* | List of SQL queries to be executed as a superuser in the `template1`
database right after the cluster has been created - to be used with extreme care
(by default empty) | | | | -| `import` *[Import](#import)* | Bootstraps the new cluster by importing data from an existing PostgreSQL
instance using logical backup (`pg_dump` and `pg_restore`) | | | | -| `postInitApplicationSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the application database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitTemplateSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `template1` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | -| `postInitSQLRefs` *[SQLRefs](#sqlrefs)* | List of references to ConfigMaps or Secrets containing SQL files
to be executed as a superuser in the `postgres` database right after
the cluster has been created. The references are processed in a specific order:
first, all Secrets are processed, followed by all ConfigMaps.
Within each group, the processing order follows the sequence specified
in their respective arrays.
(by default empty) | | | | - -#### BootstrapPgBaseBackup - -BootstrapPgBaseBackup contains the configuration required to take -a physical backup of an existing PostgreSQL cluster - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ------------------- | -| `source` *string* | The name of the server of which we need to take a physical backup | True | | MinLength: 1
| -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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. - -*Appears in:* - -- [BootstrapConfiguration](#bootstrapconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backup` *[BackupSource](#backupsource)* | The backup object containing the physical base backup from which to
initiate the recovery procedure.
Mutually exclusive with `source` and `volumeSnapshots`. | | | | -| `source` *string* | 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`. | | | | -| `volumeSnapshots` *[DataSource](#datasource)* | 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 {{name.ln}}, 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`. | | | | -| `recoveryTarget` *[RecoveryTarget](#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: | | | | -| `database` *string* | Name of the database used by the application. Default: `app`. | | | | -| `owner` *string* | Name of the owner of the database in the instance to be used
by applications. Defaults to the value of the `database` key. | | | | -| `secret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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 | | | | - -#### CatalogImage - -CatalogImage defines the image and major version - -*Appears in:* - -- [ImageCatalogSpec](#imagecatalogspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------- | -------- | ------- | ------------------ | -| `image` *string* | The image reference | True | | | -| `major` *integer* | The PostgreSQL major version of the image. Must be unique within the catalog. | True | | Minimum: 10
| -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | - -#### CertificatesConfiguration - -CertificatesConfiguration contains the needed configurations to handle server certificates. - -*Appears in:* - -- [CertificatesStatus](#certificatesstatus) -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | - -#### CertificatesStatus - -CertificatesStatus contains configuration certificates and related expiration dates. - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `serverCASecret` *string* | 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.
| | | | -| `serverTLSSecret` *string* | 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. | | | | -| `replicationTLSSecret` *string* | 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. | | | | -| `clientCASecret` *string* | 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.
| | | | -| `serverAltDNSNames` *string array* | The list of the server alternative DNS names to be added to the generated server TLS certificates, when required. | | | | -| `expirations` *object (keys:string, values:string)* | Expiration dates for all certificates. | | | | - -#### Cluster - -Cluster defines the API schema for a highly available PostgreSQL database cluster -managed by {{name.ln}}. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Cluster` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ClusterSpec](#clusterspec)* | Specification of the desired behavior of the cluster.
More info: | True | | | -| `status` *[ClusterStatus](#clusterstatus)* | Most recently observed status of the cluster. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ClusterImageCatalog - -ClusterImageCatalog is the Schema for the clusterimagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ClusterImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ClusterImageCatalog.
More info: | True | | | - -#### ClusterMonitoringTLSConfiguration - -ClusterMonitoringTLSConfiguration is the type containing the TLS configuration -for the cluster's monitoring - -*Appears in:* - -- [MonitoringConfiguration](#monitoringconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------- | -------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Enable TLS for the monitoring endpoint.
Changing this option will force a rollout of all instances. | | false | | - -#### ClusterSpec - -ClusterSpec defines the desired state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ | ---------------------------------------------------------------------- | -| `description` *string* | Description of this PostgreSQL cluster | | | | -| `inheritedMetadata` *[EmbeddedObjectMetadata](#embeddedobjectmetadata)* | Metadata that will be inherited by all objects related to the Cluster | | | | -| `imageName` *string* | Name of the container image, supporting both tags (`:`)
and digests for deterministic and repeatable deployments
(`:@sha256:`) | | | | -| `imageCatalogRef` *[ImageCatalogRef](#imagecatalogref)* | Defines the major PostgreSQL version we want to use within an ImageCatalog | | | | -| `imagePullPolicy` *[PullPolicy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#pullpolicy-v1-core)* | Image pull policy.
One of `Always`, `Never` or `IfNotPresent`.
If not defined, it defaults to `IfNotPresent`.
Cannot be updated.
More info: | | | | -| `schedulerName` *string* | 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:
| | | | -| `postgresUID` *integer* | The UID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `postgresGID` *integer* | The GID of the `postgres` user inside the image, defaults to `26` | | 26 | | -| `instances` *integer* | Number of instances required in the cluster | True | 1 | Minimum: 1
| -| `minSyncReplicas` *integer* | Minimum number of instances required in synchronous replication with the
primary. Undefined or 0 allow writes to complete when no standby is
available. | | 0 | Minimum: 0
| -| `maxSyncReplicas` *integer* | 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. | | 0 | Minimum: 0
| -| `postgresql` *[PostgresConfiguration](#postgresconfiguration)* | Configuration of the PostgreSQL server | | | | -| `podSelectorRefs` *[PodSelectorRef](#podselectorref) array* | PodSelectorRefs defines named pod label selectors that can be referenced
in pg_hba rules using the ${podselector:NAME} syntax in the address field.
The operator resolves matching pod IPs and the instance manager expands
pg_hba lines accordingly. Only pods in the Cluster's own namespace are considered. | | | | -| `replicationSlots` *[ReplicationSlotsConfiguration](#replicationslotsconfiguration)* | Replication slots management configuration | | | | -| `bootstrap` *[BootstrapConfiguration](#bootstrapconfiguration)* | Instructions to bootstrap this cluster | | | | -| `replica` *[ReplicaClusterConfiguration](#replicaclusterconfiguration)* | Replica cluster configuration | | | | -| `superuserSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The secret containing the superuser password. If not defined a new
secret will be created with a randomly generated password | | | | -| `enableSuperuserAccess` *boolean* | 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`. Disabled by default. | | | | -| `certificates` *[CertificatesConfiguration](#certificatesconfiguration)* | The configuration for the CA and related certificates | | | | -| `imagePullSecrets` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference) array* | 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. | | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage of the instances | | | | -| `serviceAccountTemplate` *[ServiceAccountTemplate](#serviceaccounttemplate)* | Configure the generation of the service account | | | | -| `serviceAccountName` *string* | Name of an existing ServiceAccount in the same namespace to use for the cluster.
When specified, the operator will not create a new ServiceAccount
but will use the provided one. This is useful for sharing a single
ServiceAccount across multiple clusters (e.g., for cloud IAM configurations).
If not specified, a ServiceAccount will be created with the cluster name.
Mutually exclusive with ServiceAccountTemplate. | | | MaxLength: 253
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| -| `walStorage` *[StorageConfiguration](#storageconfiguration)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `ephemeralVolumeSource` *[EphemeralVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#ephemeralvolumesource-v1-core)* | EphemeralVolumeSource allows the user to configure the source of ephemeral volumes. | | | | -| `startDelay` *integer* | 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). | | 3600 | | -| `stopDelay` *integer* | The time in seconds that is allowed for a PostgreSQL instance to
gracefully shutdown (default 1800) | | 1800 | | -| `smartStopDelay` *integer* | Deprecated: please use SmartShutdownTimeout instead | | | | -| `smartShutdownTimeout` *integer* | 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`). Default is 180 seconds. | | 180 | | -| `switchoverDelay` *integer* | 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). | | 3600 | | -| `failoverDelay` *integer* | 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 | | 0 | | -| `livenessProbeTimeout` *integer* | 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` *[AffinityConfiguration](#affinityconfiguration)* | Affinity/Anti-affinity rules for Pods | | | | -| `topologySpreadConstraints` *[TopologySpreadConstraint](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#topologyspreadconstraint-v1-core) array* | TopologySpreadConstraints specifies how to spread matching pods among the given topology.
More info:
| | | | -| `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#resourcerequirements-v1-core)* | Resources requirements of every generated Pod. Please refer to

for more information. | | | | -| `ephemeralVolumesSizeLimit` *[EphemeralVolumesSizeLimitConfiguration](#ephemeralvolumessizelimitconfiguration)* | EphemeralVolumesSizeLimit allows the user to set the limits for the ephemeral
volumes | | | | -| `priorityClassName` *string* | 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

for more information | | | | -| `primaryUpdateStrategy` *[PrimaryUpdateStrategy](#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`) | | unsupervised | Enum: [unsupervised supervised]
| -| `primaryUpdateMethod` *[PrimaryUpdateMethod](#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).
Note: when using `switchover`, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process. | | | Enum: [switchover restart]
| -| `backup` *[BackupConfiguration](#backupconfiguration)* | The configuration to be used for backups | | | | -| `nodeMaintenanceWindow` *[NodeMaintenanceWindow](#nodemaintenancewindow)* | Define a maintenance window for the Kubernetes nodes | | | | -| `licenseKey` *string* | 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. | | | | -| `licenseKeySecret` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the license key. When this is set it take precedence over LicenseKey. | | | | -| `monitoring` *[MonitoringConfiguration](#monitoringconfiguration)* | The configuration of the monitoring infrastructure of this cluster | | | | -| `externalClusters` *[ExternalCluster](#externalcluster) array* | The list of external clusters which are used in the configuration | | | | -| `logLevel` *string* | The instances' log level, one of the following values: error, warning, info (default), debug, trace | | info | Enum: [error warning info debug trace]
| -| `projectedVolumeTemplate` *[ProjectedVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#projectedvolumesource-v1-core)* | Template to be used to define projected volumes, projected volumes will be mounted
under `/projected` base folder | | | | -| `env` *[EnvVar](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envvar-v1-core) array* | Env follows the Env format to pass environment variables
to the pods created in the cluster | | | | -| `envFrom` *[EnvFromSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#envfromsource-v1-core) array* | EnvFrom follows the EnvFrom format to pass environment variables
sources to the pods to be used by Env | | | | -| `managed` *[ManagedConfiguration](#managedconfiguration)* | The configuration that is used by the portions of PostgreSQL that are managed by the instance manager | | | | -| `seccompProfile` *[SeccompProfile](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#seccompprofile-v1-core)* | The SeccompProfile applied to every Pod and Container.
Defaults to: `RuntimeDefault` | | | | -| `podSecurityContext` *[PodSecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podsecuritycontext-v1-core)* | Override the PodSecurityContext applied to every Pod of the cluster.
When set, this overrides the operator's default PodSecurityContext for the cluster.
If omitted, the operator defaults are used.
This field doesn't have any effect if SecurityContextConstraints are present. | | | | -| `securityContext` *[SecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#securitycontext-v1-core)* | Override the SecurityContext applied to every Container in the Pod of the cluster.
When set, this overrides the operator's default Container SecurityContext.
If omitted, the operator defaults are used. | | | | -| `tablespaces` *[TablespaceConfiguration](#tablespaceconfiguration) array* | The tablespaces configuration | | | | -| `enablePDB` *boolean* | 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 any
`PodDisruptionBudget` 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. | | true | | -| `plugins` *[PluginConfiguration](#pluginconfiguration) array* | The plugins configuration, containing
any plugin to be loaded with the corresponding configuration | | | | -| `probes` *[ProbesConfiguration](#probesconfiguration)* | The configuration of the probes to be injected
in the PostgreSQL Pods. | | | | - -#### ClusterStatus - -ClusterStatus defines the observed state of a PostgreSQL cluster managed by -{{name.ln}}. - -*Appears in:* - -- [Cluster](#cluster) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *integer* | The total number of PVC Groups detected in the cluster. It may differ from the number of existing instance pods. | | | | -| `readyInstances` *integer* | The total number of ready instances in the cluster. It is equal to the number of ready instance pods. | | | | -| `instancesStatus` *object (keys:[PodStatus](#podstatus), values:string array)* | InstancesStatus indicates in which status the instances are | | | | -| `instancesReportedState` *object (keys:[PodName](#podname), values:[InstanceReportedState](#instancereportedstate))* | The reported state of the instances during the last reconciliation loop | | | | -| `managedRolesStatus` *[ManagedRoles](#managedroles)* | ManagedRolesStatus reports the state of the managed roles in the cluster | | | | -| `tablespacesStatus` *[TablespaceState](#tablespacestate) array* | TablespacesStatus reports the state of the declarative tablespaces in the cluster | | | | -| `podSelectorRefs` *[PodSelectorRefStatus](#podselectorrefstatus) array* | PodSelectorRefs contains the resolved pod IPs for each named selector
defined in spec.podSelectorRefs. | | | | -| `timelineID` *integer* | The timeline of the Postgres cluster | | | | -| `topology` *[Topology](#topology)* | Instances topology. | | | | -| `latestGeneratedNode` *integer* | ID of the latest generated node (used to avoid node name clashing) | | | | -| `currentPrimary` *string* | Current primary instance | | | | -| `targetPrimary` *string* | Target primary instance, this is different from the previous one
during a switchover or a failover | | | | -| `lastPromotionToken` *string* | LastPromotionToken is the last verified promotion token that
was used to promote a replica cluster | | | | -| `pvcCount` *integer* | How many PVCs have been created by this cluster | | | | -| `jobCount` *integer* | How many Jobs have been created by this cluster | | | | -| `danglingPVC` *string array* | List of all the PVCs created by this cluster and still available
which are not attached to a Pod | | | | -| `resizingPVC` *string array* | List of all the PVCs that have ResizingPVC condition. | | | | -| `initializingPVC` *string array* | List of all the PVCs that are being initialized by this cluster | | | | -| `healthyPVC` *string array* | List of all the PVCs not dangling nor initializing | | | | -| `unusablePVC` *string array* | List of all the PVCs that are unusable because another PVC is missing | | | | -| `licenseStatus` *Status* | Status of the license | | | | -| `writeService` *string* | Current write pod | | | | -| `readService` *string* | Current list of read pods | | | | -| `phase` *string* | Current phase of the cluster | | | | -| `phaseReason` *string* | Reason for the current phase | | | | -| `secretsResourceVersion` *[SecretsResourceVersion](#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` *[ConfigMapResourceVersion](#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` *[CertificatesStatus](#certificatesstatus)* | The configuration for the CA and related certificates, initialized with defaults. | | | | -| `firstRecoverabilityPoint` *string* | The first recoverability point, stored as a date in RFC3339 format.
This field is calculated from the content of FirstRecoverabilityPointByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `firstRecoverabilityPointByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | The first recoverability point, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackup` *string* | Last successful backup, stored as a date in RFC3339 format.
This field is calculated from the content of LastSuccessfulBackupByMethod.
Deprecated: the field is not set for backup plugins. | | | | -| `lastSuccessfulBackupByMethod` *object (keys:[BackupMethod](#backupmethod), values:[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta))* | Last successful backup, stored as a date in RFC3339 format, per backup method type.
Deprecated: the field is not set for backup plugins. | | | | -| `lastFailedBackup` *string* | Last failed backup, stored as a date in RFC3339 format.
Deprecated: the field is not set for backup plugins. | | | | -| `cloudNativePostgresqlCommitHash` *string* | The commit hash number of which this operator running | | | | -| `currentPrimaryTimestamp` *string* | The timestamp when the last actual promotion to primary has occurred | | | | -| `currentPrimaryFailingSinceTimestamp` *string* | The timestamp when the primary was detected to be unhealthy
This field is reported when `.spec.failoverDelay` is populated or during online upgrades | | | | -| `targetPrimaryTimestamp` *string* | The timestamp when the last request for a new primary has occurred | | | | -| `poolerIntegrations` *[PoolerIntegrations](#poolerintegrations)* | The integration needed by poolers referencing the cluster | | | | -| `cloudNativePostgresqlOperatorHash` *string* | The hash of the binary of the operator | | | | -| `availableArchitectures` *[AvailableArchitecture](#availablearchitecture) array* | AvailableArchitectures reports the available architectures of a cluster | | | | -| `conditions` *[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#condition-v1-meta) array* | Conditions for cluster object | | | | -| `instanceNames` *string array* | List of instance names in the cluster | | | | -| `onlineUpdateEnabled` *boolean* | OnlineUpdateEnabled shows if the online upgrade is enabled inside the cluster | | | | -| `image` *string* | Image contains the image name used by the pods | | | | -| `pgDataImageInfo` *[ImageInfo](#imageinfo)* | PGDataImageInfo contains the details of the latest image that has run on the current data directory. | | | | -| `pluginStatus` *[PluginStatus](#pluginstatus) array* | PluginStatus is the status of the loaded plugins | | | | -| `switchReplicaClusterStatus` *[SwitchReplicaClusterStatus](#switchreplicaclusterstatus)* | SwitchReplicaClusterStatus is the status of the switch to replica cluster | | | | -| `demotionToken` *string* | DemotionToken is a JSON token containing the information
from pg_controldata such as Database system identifier, Latest checkpoint's
TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO
WAL file, and Time of latest checkpoint | | | | -| `systemID` *string* | SystemID is the latest detected PostgreSQL SystemID | | | | - -#### ConfigMapResourceVersion - -ConfigMapResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metrics` *object (keys:string, values:string)* | 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 | | | | - -#### DataDurabilityLevel - -*Underlying type:* *string* - -DataDurabilityLevel specifies how strictly to enforce synchronous replication -when cluster instances are unavailable. Options are `required` or `preferred`. - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -| Field | Description | -| ----------- | ----------------------------------------------------------------------------------------------------------------------- | -| `required` | DataDurabilityLevelRequired means that data durability is strictly enforced
| -| `preferred` | DataDurabilityLevelPreferred means that data durability is enforced
only when healthy replicas are available
| - -#### DataSource - -DataSource contains the configuration required to bootstrap a -PostgreSQL cluster from an existing storage - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `storage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage of the instances | True | | | -| `walStorage` *[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core)* | Configuration of the storage for PostgreSQL WAL (Write-Ahead Log) | | | | -| `tablespaceStorage` *object (keys:string, values:[TypedLocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#typedlocalobjectreference-v1-core))* | Configuration of the storage for PostgreSQL tablespaces | | | | - -#### Database - -Database is the Schema for the databases API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Database` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[DatabaseSpec](#databasespec)* | Specification of the desired Database.
More info: | True | | | -| `status` *[DatabaseStatus](#databasestatus)* | Most recently observed status of the Database. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### DatabaseObjectSpec - -DatabaseObjectSpec contains the fields which are common to every -database object - -*Appears in:* - -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| - -#### DatabaseObjectStatus - -DatabaseObjectStatus is the status of the managed database objects - -*Appears in:* - -- [DatabaseStatus](#databasestatus) - -| Field | Description | Required | Default | Validation | -| ------------------- | ----------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the object | True | | | -| `applied` *boolean* | True of the object has been installed successfully in
the database | True | | | -| `message` *string* | Message is the object reconciliation message | | | | - -#### DatabaseReclaimPolicy - -*Underlying type:* *string* - -DatabaseReclaimPolicy describes a policy for end-of-life maintenance of databases. - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | DatabaseReclaimDelete means the database will be deleted from its PostgreSQL Cluster on release
from its claim.
| -| `retain` | DatabaseReclaimRetain means the database will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### DatabaseRoleRef - -DatabaseRoleRef is a reference an a role available inside PostgreSQL - -*Appears in:* - -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------- | ----------- | -------- | ------- | ---------- | -| `name` *string* | | | | | - -#### DatabaseSpec - -DatabaseSpec is the specification of a Postgresql Database, built around the -`CREATE DATABASE`, `ALTER DATABASE`, and `DROP DATABASE` SQL commands of -PostgreSQL. - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster hosting the database. | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the PostgreSQL database is `present` or `absent` - defaults to "present". | | present | Enum: [present absent]
| -| `name` *string* | The name of the database to create inside PostgreSQL. This setting cannot be changed. | True | | | -| `owner` *string* | Maps to the `OWNER` parameter of `CREATE DATABASE`.
Maps to the `OWNER TO` command of `ALTER DATABASE`.
The role name of the user who owns the database inside PostgreSQL. | True | | | -| `template` *string* | Maps to the `TEMPLATE` parameter of `CREATE DATABASE`. This setting
cannot be changed. The name of the template from which to create
this database. | | | | -| `encoding` *string* | Maps to the `ENCODING` parameter of `CREATE DATABASE`. This setting
cannot be changed. Character set encoding to use in the database. | | | | -| `locale` *string* | Maps to the `LOCALE` parameter of `CREATE DATABASE`. This setting
cannot be changed. Sets the default collation order and character
classification in the new database. | | | | -| `localeProvider` *string* | Maps to the `LOCALE_PROVIDER` parameter of `CREATE DATABASE`. This
setting cannot be changed. This option sets the locale provider for
databases created in the new cluster. Available from PostgreSQL 16. | | | | -| `localeCollate` *string* | Maps to the `LC_COLLATE` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `localeCType` *string* | Maps to the `LC_CTYPE` parameter of `CREATE DATABASE`. This setting
cannot be changed. | | | | -| `icuLocale` *string* | Maps to the `ICU_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the ICU locale when the ICU
provider is used. This option requires `localeProvider` to be set to
`icu`. Available from PostgreSQL 15. | | | | -| `icuRules` *string* | Maps to the `ICU_RULES` parameter of `CREATE DATABASE`. This setting
cannot be changed. Specifies additional collation rules to customize
the behavior of the default collation. This option requires
`localeProvider` to be set to `icu`. Available from PostgreSQL 16. | | | | -| `builtinLocale` *string* | Maps to the `BUILTIN_LOCALE` parameter of `CREATE DATABASE`. This
setting cannot be changed. Specifies the locale name when the
builtin provider is used. This option requires `localeProvider` to
be set to `builtin`. Available from PostgreSQL 17. | | | | -| `collationVersion` *string* | Maps to the `COLLATION_VERSION` parameter of `CREATE DATABASE`. This
setting cannot be changed. | | | | -| `isTemplate` *boolean* | Maps to the `IS_TEMPLATE` parameter of `CREATE DATABASE` and `ALTER
DATABASE`. If true, this database is considered a template and can
be cloned by any user with `CREATEDB` privileges. | | | | -| `allowConnections` *boolean* | Maps to the `ALLOW_CONNECTIONS` parameter of `CREATE DATABASE` and
`ALTER DATABASE`. If false then no one can connect to this database. | | | | -| `connectionLimit` *integer* | Maps to the `CONNECTION LIMIT` clause of `CREATE DATABASE` and
`ALTER DATABASE`. How many concurrent connections can be made to
this database. -1 (the default) means no limit. | | | | -| `tablespace` *string* | Maps to the `TABLESPACE` parameter of `CREATE DATABASE`.
Maps to the `SET TABLESPACE` command of `ALTER DATABASE`.
The name of the tablespace (in PostgreSQL) that will be associated
with the new database. This tablespace will be the default
tablespace used for objects created in this database. | | | | -| `databaseReclaimPolicy` *[DatabaseReclaimPolicy](#databasereclaimpolicy)* | The policy for end-of-life maintenance of this database. | | retain | Enum: [delete retain]
| -| `schemas` *[SchemaSpec](#schemaspec) array* | The list of schemas to be managed in the database | | | | -| `extensions` *[ExtensionSpec](#extensionspec) array* | The list of extensions to be managed in the database | | | | -| `fdws` *[FDWSpec](#fdwspec) array* | The list of foreign data wrappers to be managed in the database | | | | -| `servers` *[ServerSpec](#serverspec) array* | The list of foreign servers to be managed in the database | | | | - -#### DatabaseStatus - -DatabaseStatus defines the observed state of Database - -*Appears in:* - -- [Database](#database) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the database was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | -| `schemas` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Schemas is the status of the managed schemas | | | | -| `extensions` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Extensions is the status of the managed extensions | | | | -| `fdws` *[DatabaseObjectStatus](#databaseobjectstatus) array* | FDWs is the status of the managed FDWs | | | | -| `servers` *[DatabaseObjectStatus](#databaseobjectstatus) array* | Servers is the status of the managed servers | | | | - -#### EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `audit` *boolean* | If true enables edb_audit logging | | | | -| `tde` *[TDEConfiguration](#tdeconfiguration)* | TDE configuration | | | | - -#### EmbeddedObjectMetadata - -EmbeddedObjectMetadata contains metadata to be inherited by all resources related to a Cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `labels` *object (keys:string, values:string)* | | | | | -| `annotations` *object (keys:string, values:string)* | | | | | - -#### EnsureOption - -*Underlying type:* *string* - -EnsureOption represents whether we should enforce the presence or absence of -a Role in a PostgreSQL instance - -*Appears in:* - -- [DatabaseObjectSpec](#databaseobjectspec) -- [DatabaseSpec](#databasespec) -- [ExtensionSpec](#extensionspec) -- [FDWSpec](#fdwspec) -- [OptionSpec](#optionspec) -- [RoleConfiguration](#roleconfiguration) -- [SchemaSpec](#schemaspec) -- [ServerSpec](#serverspec) - -| Field | Description | -| --------- | ----------- | -| `present` | | -| `absent` | | - -#### EphemeralVolumesSizeLimitConfiguration - -EphemeralVolumesSizeLimitConfiguration contains the configuration of the ephemeral -storage - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------ | -------- | ------- | ---------- | -| `shm` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Shm is the size limit of the shared memory volume | | | | -| `temporaryData` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | TemporaryData is the size limit of the temporary data volume | | | | - -#### ExtensionConfiguration - -ExtensionConfiguration is the configuration used to add -PostgreSQL extensions to the Cluster. - -*Appears in:* - -- [CatalogImage](#catalogimage) -- [ImageInfo](#imageinfo) -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------------------------------------------- | -| `name` *string* | The name of the extension, required | True | | MinLength: 1
Pattern: `^[a-z0-9]([-a-z0-9_]*[a-z0-9])?$`
| -| `image` *[ImageVolumeSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#imagevolumesource-v1-core)* | The image containing the extension. | | | | -| `extension_control_path` *string array* | The list of directories inside the image which should be added to extension_control_path.
If not defined, defaults to "/share". | | | | -| `dynamic_library_path` *string array* | The list of directories inside the image which should be added to dynamic_library_path.
If not defined, defaults to "/lib". | | | | -| `ld_library_path` *string array* | The list of directories inside the image which should be added to ld_library_path. | | | | -| `bin_path` *string array* | A list of directories within the image to be appended to the
PostgreSQL process's `PATH` environment variable. | | | | -| `env` *[ExtensionEnvVar](#extensionenvvar) array* | Env is a list of custom environment variables to be set in the
PostgreSQL process for this extension. It is the responsibility of the
cluster administrator to ensure the variables are correct for the
specific extension. Note that changes to these variables require
a manual cluster restart to take effect. | | | | - -#### ExtensionEnvVar - -ExtensionEnvVar defines an environment variable for a specific extension -image volume. - -*Appears in:* - -- [ExtensionConfiguration](#extensionconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------------------------------- | -| `name` *string* | Name of the environment variable to be injected into the
PostgreSQL process. | True | | MinLength: 1
Pattern: `^[a-zA-Z_][a-zA-Z0-9_]*$`
| -| `value` *string* | Value of the environment variable. {{name.ln}} performs a direct
replacement of this value, with support for placeholder expansion.
The ${`image_root`} placeholder resolves to the absolute mount path
of the extension's volume (e.g., `/extensions/my-extension`). This
is particularly useful for allowing applications or libraries to
locate specific directories within the mounted image.
Unrecognized placeholders are rejected. To include a literal ${...}
in the value, escape it as $${...}. | True | | MinLength: 1
| - -#### ExtensionSpec - -ExtensionSpec configures an extension in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `version` *string* | The version of the extension to install. If empty, the operator will
install the default version (whatever is specified in the
extension's control file) | True | | | -| `schema` *string* | The name of the schema in which to install the extension's objects,
in case the extension allows its contents to be relocated. If not
specified (default), and the extension's control file does not
specify a schema either, the current default object creation schema
is used. | True | | | - -#### ExternalCluster - -ExternalCluster represents the connection parameters to an -external cluster which is used in the other sections of the configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The server name, required | True | | | -| `connectionParameters` *object (keys:string, values:string)* | The list of connection parameters, such as dbname, host, username, etc | | | | -| `sslCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL certificate to be used to connect to this
instance | | | | -| `sslKey` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL private key to be used to connect to this
instance | | | | -| `sslRootCert` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to an SSL CA public key to be used to connect to this
instance | | | | -| `password` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | The reference to the password to be used to connect to the server.
If a password is provided, {{name.ln}} 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. | | | | -| `barmanObjectStore` *[BarmanObjectStoreConfiguration](https://pkg.go.dev/github.com/cloudnative-pg/barman-cloud/pkg/api#BarmanObjectStoreConfiguration)* | The configuration for the barman-cloud tool suite | | | | -| `plugin` *[PluginConfiguration](#pluginconfiguration)* | The configuration of the plugin that is taking care
of WAL archiving and backups for this external cluster | True | | | - -#### FDWSpec - -FDWSpec configures an Foreign Data Wrapper in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `handler` *string* | Name of the handler function (e.g., "postgres_fdw_handler").
This will be empty if no handler is specified. In that case,
the default handler is registered when the FDW extension is created. | | | | -| `validator` *string* | Name of the validator function (e.g., "postgres_fdw_validator").
This will be empty if no validator is specified. In that case,
the default validator is registered when the FDW extension is created. | | | | -| `owner` *string* | Owner specifies the database role that will own the Foreign Data Wrapper.
The role must have superuser privileges in the target database. | | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the FDW. | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the FDW are granted or revoked. | | | | - -#### FailoverQuorum - -FailoverQuorum contains the information about the current failover -quorum status of a PG cluster. It is updated by the instance manager -of the primary node and reset to zero by the operator to trigger -an update. - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `FailoverQuorum` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `status` *[FailoverQuorumStatus](#failoverquorumstatus)* | Most recently observed status of the failover quorum. | | | | - -#### FailoverQuorumStatus - -FailoverQuorumStatus is the latest observed status of the failover -quorum of the PG cluster. - -*Appears in:* - -- [FailoverQuorum](#failoverquorum) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | --------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `method` *string* | Contains the latest reported Method value. | | | | -| `standbyNames` *string array* | StandbyNames is the list of potentially synchronous
instance names. | | | | -| `standbyNumber` *integer* | StandbyNumber is the number of synchronous standbys that transactions
need to wait for replies from. | | | | -| `primary` *string* | Primary is the name of the primary instance that updated
this object the latest time. | | | | - -#### ImageCatalog - -ImageCatalog is the Schema for the imagecatalogs API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ImageCatalog` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ImageCatalogSpec](#imagecatalogspec)* | Specification of the desired behavior of the ImageCatalog.
More info: | True | | | - -#### ImageCatalogRef - -ImageCatalogRef defines the reference to a major version in an ImageCatalog - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiGroup` *string* | APIGroup is the group for the resource being referenced.
If APIGroup is not specified, the specified Kind must be in the core API group.
For any other third-party types, APIGroup is required. | | | | -| `kind` *string* | Kind is the type of resource being referenced | True | | | -| `name` *string* | Name is the name of resource being referenced | True | | | -| `major` *integer* | The major version of PostgreSQL we want to use from the ImageCatalog | True | | | - -#### ImageCatalogSpec - -ImageCatalogSpec defines the desired ImageCatalog - -*Appears in:* - -- [ClusterImageCatalog](#clusterimagecatalog) -- [ImageCatalog](#imagecatalog) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------- | ---------------------------------------------- | -------- | ------- | ------------------------------------ | -| `images` *[CatalogImage](#catalogimage) array* | List of CatalogImages available in the catalog | True | | MaxItems: 8
MinItems: 1
| - -#### ImageInfo - -ImageInfo contains the information about a PostgreSQL image - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `image` *string* | Image is the image name | True | | | -| `majorVersion` *integer* | MajorVersion is the major version of the image | True | | | -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | Extensions contains the container image extensions available for the current Image | | | | - -#### Import - -Import contains the configuration to init a database from a logic snapshot of an externalCluster - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------ | -| `source` *[ImportSource](#importsource)* | The source of the import | True | | | -| `type` *[SnapshotType](#snapshottype)* | The import type. Can be `microservice` or `monolith`. | True | | Enum: [microservice monolith]
| -| `databases` *string array* | The databases to import | True | | | -| `roles` *string array* | The roles to import | | | | -| `postImportApplicationSQL` *string array* | 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. | | | | -| `schemaOnly` *boolean* | When set to true, only the `pre-data` and `post-data` sections of
`pg_restore` are invoked, avoiding data import. Default: `false`. | | | | -| `pgDumpExtraOptions` *string array* | List of custom options to pass to the `pg_dump` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreExtraOptions` *string array* | List of custom options to pass to the `pg_restore` command.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePredataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `pre-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestoreDataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | -| `pgRestorePostdataOptions` *string array* | Custom options to pass to the `pg_restore` command during the `post-data`
section. This setting overrides the generic `pgRestoreExtraOptions` value.
IMPORTANT: Use with caution. The operator does not validate these options,
and certain flags may interfere with its intended functionality or design.
You are responsible for ensuring that the provided options are compatible
with your environment and desired behavior. | | | | - -#### ImportSource - -ImportSource describes the source for the logical snapshot - -*Appears in:* - -- [Import](#import) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ----------------------------------------------- | -------- | ------- | ---------- | -| `externalCluster` *string* | The name of the externalCluster used for import | True | | | - -#### InstanceID - -InstanceID contains the information to identify an instance - -*Appears in:* - -- [BackupStatus](#backupstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `podName` *string* | The pod name | | | | -| `ContainerID` *string* | The container ID | | | | -| `sessionID` *string* | The instance manager session ID. This is a unique identifier generated at instance manager
startup and changes on every restart (including container reboots). Used to detect if
the instance manager was restarted during long-running operations like backups, which
would terminate any running backup process. | | | | - -#### InstanceReportedState - -InstanceReportedState describes the last reported state of an instance during a reconciliation loop - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------- | -------- | ------- | ---------- | -| `isPrimary` *boolean* | indicates if an instance is the primary one | True | | | -| `timeLineID` *integer* | indicates on which TimelineId the instance is | | | | -| `ip` *string* | IP address of the instance | True | | | - -#### IsolationCheckConfiguration - -IsolationCheckConfiguration contains the configuration for the isolation check -functionality in the liveness probe - -*Appears in:* - -- [LivenessProbe](#livenessprobe) - -| Field | Description | Required | Default | Validation | -| ----------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | Whether primary isolation checking is enabled for the liveness probe | | true | | -| `requestTimeout` *integer* | Timeout in milliseconds for requests during the primary isolation check | | 1000 | | -| `connectionTimeout` *integer* | Timeout in milliseconds for connections during the primary isolation check | | 1000 | | - -#### LDAPBindAsAuth - -LDAPBindAsAuth provides the required fields to use the -bind authentication for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ----------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `prefix` *string* | Prefix for the bind authentication option | | | | -| `suffix` *string* | Suffix for the bind authentication option | | | | - -#### LDAPBindSearchAuth - -LDAPBindSearchAuth provides the required fields to use -the bind+search LDAP authentication process - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | -------- | ------- | ---------- | -| `baseDN` *string* | Root DN to begin the user search | | | | -| `bindDN` *string* | DN of the user to bind to the directory | | | | -| `bindPassword` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Secret with the password for the user to bind to the directory | | | | -| `searchAttribute` *string* | Attribute to match against the username | | | | -| `searchFilter` *string* | Search filter to use when doing the search+bind authentication | | | | - -#### LDAPConfig - -LDAPConfig contains the parameters needed for LDAP authentication - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ------------------------- | -| `server` *string* | LDAP hostname or IP address | | | | -| `port` *integer* | LDAP server port | | | | -| `scheme` *[LDAPScheme](#ldapscheme)* | LDAP schema to be used, possible options are `ldap` and `ldaps` | | | Enum: [ldap ldaps]
| -| `bindAsAuth` *[LDAPBindAsAuth](#ldapbindasauth)* | Bind as authentication configuration | | | | -| `bindSearchAuth` *[LDAPBindSearchAuth](#ldapbindsearchauth)* | Bind+Search authentication configuration | | | | -| `tls` *boolean* | Set to 'true' to enable LDAP over TLS. 'false' is default | | | | - -#### LDAPScheme - -*Underlying type:* *string* - -LDAPScheme defines the possible schemes for LDAP - -*Appears in:* - -- [LDAPConfig](#ldapconfig) - -| Field | Description | -| ------- | ----------- | -| `ldap` | | -| `ldaps` | | - -#### LivenessProbe - -LivenessProbe is the configuration of the liveness probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `isolationCheck` *[IsolationCheckConfiguration](#isolationcheckconfiguration)* | Configure the feature that extends the liveness probe for a primary
instance. In addition to the basic checks, this verifies whether the
primary is isolated from the Kubernetes API server and from its
replicas, ensuring that it can be safely shut down if network
partition or API unavailability is detected. Enabled by default. | | | | - -#### ManagedConfiguration - -ManagedConfiguration represents the portions of PostgreSQL that are managed -by the instance manager - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------- | --------------------------------------- | -------- | ------- | ---------- | -| `roles` *[RoleConfiguration](#roleconfiguration) array* | Database roles managed by the `Cluster` | | | | -| `services` *[ManagedServices](#managedservices)* | Services roles managed by the `Cluster` | | | | - -#### ManagedRoles - -ManagedRoles tracks the status of a cluster's managed roles - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `byStatus` *object (keys:[RoleStatus](#rolestatus), values:string array)* | ByStatus gives the list of roles in each state | | | | -| `cannotReconcile` *object (keys:string, values:string array)* | CannotReconcile lists roles that cannot be reconciled in PostgreSQL,
with an explanation of the cause | | | | -| `passwordStatus` *object (keys:string, values:[PasswordState](#passwordstate))* | PasswordStatus gives the last transaction id and password secret version for each managed role | | | | - -#### ManagedService - -ManagedService represents a specific service managed by the cluster. -It includes the type of service and its associated template specification. - -*Appears in:* - -- [ManagedServices](#managedservices) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `selectorType` *[ServiceSelectorType](#serviceselectortype)* | SelectorType specifies the type of selectors that the service will have.
Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services. | True | | Enum: [rw r ro]
| -| `updateStrategy` *[ServiceUpdateStrategy](#serviceupdatestrategy)* | UpdateStrategy describes how the service differences should be reconciled | | patch | Enum: [patch replace]
| -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | ServiceTemplate is the template specification for the service. | True | | | - -#### ManagedServices - -ManagedServices represents the services managed by the cluster. - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------- | -| `disabledDefaultServices` *[ServiceSelectorType](#serviceselectortype) array* | DisabledDefaultServices is a list of service types that are disabled by default.
Valid values are "r", and "ro", representing read, and read-only services. | | | Enum: [rw r ro]
| -| `additional` *[ManagedService](#managedservice) array* | Additional is a list of additional managed services specified by the user. | | | | - -#### 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. - -*Appears in:* - -- [PodTemplateSpec](#podtemplatespec) -- [ServiceAccountTemplate](#serviceaccounttemplate) -- [ServiceTemplateSpec](#servicetemplatespec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the resource. Only supported for certain types | | | | -| `labels` *object (keys:string, values:string)* | 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: | | | | -| `annotations` *object (keys:string, values:string)* | 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: | | | | - -#### MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring -configuration for a certain cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `disableDefaultQueries` *boolean* | 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. | | false | | -| `customQueriesConfigMap` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | The list of config maps containing the custom queries | | | | -| `customQueriesSecret` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | The list of secrets containing the custom queries | | | | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor`
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | false | | -| `tls` *[ClusterMonitoringTLSConfiguration](#clustermonitoringtlsconfiguration)* | Configure TLS communication for the metrics endpoint.
Changing tls.enabled option will force a rollout of all instances. | | | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `metricsQueriesTTL` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | The interval during which metrics computed from queries are considered current.
Once it is exceeded, a new scrape will trigger a rerun
of the queries.
If not set, defaults to 30 seconds, in line with Prometheus scraping defaults.
Setting this to zero disables the caching mechanism and can cause heavy load on the PostgreSQL server. | | | | - -#### 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. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `reusePVC` *boolean* | Reuse the existing PVC (wait for the node to come
up again) or not (recreate it elsewhere - when `instances` >1) | | true | | -| `inProgress` *boolean* | Is there a node maintenance activity in progress? | | false | | - -#### OnlineConfiguration - -OnlineConfiguration contains the configuration parameters for the online volume snapshot - -*Appears in:* - -- [BackupSpec](#backupspec) -- [ScheduledBackupSpec](#scheduledbackupspec) -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `waitForArchive` *boolean* | 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. | | true | | -| `immediateCheckpoint` *boolean* | 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. | | | | - -#### OptionSpec - -OptionSpec holds the name, value and the ensure field for an option - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the option | True | | | -| `value` *string* | Value of the option | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an option should be present or absent in
the database. If set to `present`, the option will be
created if it does not exist. If set to `absent`, the
option will be removed if it exists. | | present | Enum: [present absent]
| - -#### PasswordState - -PasswordState represents the state of the password of a managed RoleConfiguration - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | Required | Default | Validation | -| -------------------------- | ------------------------------------------------------------------- | -------- | ------- | ---------- | -| `transactionID` *integer* | the last transaction ID to affect the role definition in PostgreSQL | | | | -| `resourceVersion` *string* | the resource version of the password secret | | | | - -#### PgBouncerIntegrationStatus - -PgBouncerIntegrationStatus encapsulates the needed integration for the pgbouncer poolers referencing the cluster - -*Appears in:* - -- [PoolerIntegrations](#poolerintegrations) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------- | -------- | ------- | ---------- | -| `secrets` *string array* | | | | | - -#### PgBouncerPoolMode - -*Underlying type:* *string* - -PgBouncerPoolMode is the mode of PgBouncer - -*Validation:* - -- Enum: [session transaction] - -*Appears in:* - -- [PgBouncerSpec](#pgbouncerspec) - -#### PgBouncerSecrets - -PgBouncerSecrets contains the versions of the secrets used -by pgbouncer - -*Appears in:* - -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------- | ----------------------------- | -------- | ------- | ---------- | -| `authQuery` *[SecretVersion](#secretversion)* | The auth query secret version | | | | - -#### PgBouncerSpec - -PgBouncerSpec defines how to configure PgBouncer - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------------- | -| `poolMode` *[PgBouncerPoolMode](#pgbouncerpoolmode)* | The pool mode. Default: `session`. | | session | Enum: [session transaction]
| -| `serverTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerTLSSecret, when pointing to a TLS secret, provides pgbouncer's
`server_tls_key_file` and `server_tls_cert_file`, used when
authenticating against PostgreSQL. | | | | -| `serverCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ServerCASecret provides PgBouncer’s server_tls_ca_file, the root
CA for validating PostgreSQL certificates | | | | -| `clientCASecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientCASecret provides PgBouncer’s client_tls_ca_file, the root
CA for validating client certificates | | | | -| `clientTLSSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | ClientTLSSecret provides PgBouncer’s client_tls_key_file (private key)
and client_tls_cert_file (certificate) used to accept client connections | | | | -| `authQuerySecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | 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.
Deprecated. | | | | -| `authQuery` *string* | 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. | | | | -| `parameters` *object (keys:string, values:string)* | Additional parameters to be passed to PgBouncer - please check
the CNP documentation for a list of options you can configure | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file) | | | | -| `paused` *boolean* | 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. | | false | | - -#### PluginConfiguration - -PluginConfiguration specifies a plugin that need to be loaded for this -cluster to be reconciled - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [ExternalCluster](#externalcluster) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the plugin name | True | | | -| `enabled` *boolean* | Enabled is true if this plugin will be used | | true | | -| `isWALArchiver` *boolean* | Marks the plugin as the WAL archiver. At most one plugin can be
designated as a WAL archiver. This cannot be enabled if the
`.spec.backup.barmanObjectStore` configuration is present. | | false | | -| `parameters` *object (keys:string, values:string)* | Parameters is the configuration of the plugin | | | | - -#### PluginStatus - -PluginStatus is the status of a loaded plugin - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the plugin | True | | | -| `version` *string* | Version is the version of the plugin loaded by the
latest reconciliation loop | True | | | -| `capabilities` *string array* | Capabilities are the list of capabilities of the
plugin | | | | -| `operatorCapabilities` *string array* | OperatorCapabilities are the list of capabilities of the
plugin regarding the reconciler | | | | -| `walCapabilities` *string array* | WALCapabilities are the list of capabilities of the
plugin regarding the WAL management | | | | -| `backupCapabilities` *string array* | BackupCapabilities are the list of capabilities of the
plugin regarding the Backup management | | | | -| `restoreJobHookCapabilities` *string array* | RestoreJobHookCapabilities are the list of capabilities of the
plugin regarding the RestoreJobHook management | | | | -| `status` *string* | Status contain the status reported by the plugin through the SetStatusInCluster interface | | | | - -#### PodName - -*Underlying type:* *string* - -PodName is the name of a Pod - -*Appears in:* - -- [ClusterStatus](#clusterstatus) -- [Topology](#topology) - -#### PodSelectorRef - -PodSelectorRef defines a named pod label selector for use in pg_hba rules. -Pods matching the selector in the Cluster's namespace will have their IPs -resolved and made available for pg_hba address expansion via the -`${podselector:NAME}` syntax. - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------------------------------------------ | -| `name` *string* | Name is the identifier used to reference this selector in pg_hba rules
via the ${podselector:NAME} syntax in the address field. | True | | MinLength: 1
Pattern: `^[a-z]([a-z0-9_-]*[a-z0-9])?$`
| -| `selector` *[LabelSelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#labelselector-v1-meta)* | Selector is a label selector that identifies the pods whose IPs
should be resolved. Only pods in the Cluster's namespace are considered. | True | | | - -#### PodSelectorRefStatus - -PodSelectorRefStatus contains the resolved pod IPs for a named selector. - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| -------------------- | ------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------- | -| `name` *string* | Name corresponds to the name in the spec's PodSelectorRef. | True | | | -| `ips` *string array* | IPs is the list of pod IPs matching the selector.
Each IP is a single address (no CIDR notation). | | | | - -#### PodStatus - -*Underlying type:* *string* - -PodStatus represent the possible status of pods - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -#### 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: - - - - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[PodSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#podspec-v1-core)* | Specification of the desired behavior of the pod.
More info: | | | | - -#### PodTopologyLabels - -*Underlying type:* *object* - -PodTopologyLabels represent the topology of a Pod. map[labelName]labelValue - -*Appears in:* - -- [Topology](#topology) - -#### Pooler - -Pooler is the Schema for the poolers API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Pooler` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PoolerSpec](#poolerspec)* | Specification of the desired behavior of the Pooler.
More info: | True | | | -| `status` *[PoolerStatus](#poolerstatus)* | Most recently observed status of the Pooler. This data may not be up to
date. Populated by the system. Read-only.
More info: | | | | - -#### PoolerIntegrations - -PoolerIntegrations encapsulates the needed integration for the poolers referencing the cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------- | ----------- | -------- | ------- | ---------- | -| `pgBouncerIntegration` *[PgBouncerIntegrationStatus](#pgbouncerintegrationstatus)* | | | | | - -#### 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. - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enablePodMonitor` *boolean* | Enable or disable the `PodMonitor` | | false | | -| `podMonitorMetricRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of metric relabelings for the `PodMonitor`. Applied to samples before ingestion. | | | | -| `podMonitorRelabelings` *[RelabelConfig](https://pkg.go.dev/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/v1#RelabelConfig) array* | The list of relabelings for the `PodMonitor`. Applied to samples before scraping. | | | | - -#### PoolerSecrets - -PoolerSecrets contains the versions of all the secrets used - -*Appears in:* - -- [PoolerStatus](#poolerstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------- | -------------------------------------------- | -------- | ------- | ---------- | -| `clientTLS` *[SecretVersion](#secretversion)* | The client TLS secret version | | | | -| `serverTLS` *[SecretVersion](#secretversion)* | The server TLS secret version | | | | -| `serverCA` *[SecretVersion](#secretversion)* | The server CA secret version | | | | -| `clientCA` *[SecretVersion](#secretversion)* | The client CA secret version | | | | -| `pgBouncerSecrets` *[PgBouncerSecrets](#pgbouncersecrets)* | The version of the secrets used by PgBouncer | | | | - -#### PoolerSpec - -PoolerSpec defines the desired state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------------------------------------------------- | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | This is the cluster reference on which the Pooler will work.
Pooler name should never match with any cluster name within the same namespace. | True | | | -| `type` *[PoolerType](#poolertype)* | Type of service to forward traffic to. Default: `rw`. | | rw | Enum: [rw ro r]
| -| `instances` *integer* | The number of replicas we want. Default: 1. | | 1 | | -| `template` *[PodTemplateSpec](#podtemplatespec)* | The template of the Pod to be created | | | | -| `pgbouncer` *[PgBouncerSpec](#pgbouncerspec)* | The PgBouncer configuration | True | | | -| `deploymentStrategy` *[DeploymentStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#deploymentstrategy-v1-apps)* | The deployment strategy to use for pgbouncer to replace existing pods with new ones | | | | -| `monitoring` *[PoolerMonitoringConfiguration](#poolermonitoringconfiguration)* | The configuration of the monitoring infrastructure of this pooler.
Deprecated: This feature will be removed in an upcoming release. If
you need this functionality, you can create a PodMonitor manually. | | | | -| `serviceTemplate` *[ServiceTemplateSpec](#servicetemplatespec)* | Template for the Service to be created | | | | -| `serviceAccountName` *string* | Name of an existing ServiceAccount in the same namespace to use for the pooler.
When specified, the operator will not create a new ServiceAccount
but will use the provided one. This is useful for sharing a single
ServiceAccount across multiple poolers (e.g., for cloud IAM configurations).
If not specified, a ServiceAccount will be created with the pooler name. | | | MaxLength: 253
Pattern: `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`
| - -#### PoolerStatus - -PoolerStatus defines the observed state of Pooler - -*Appears in:* - -- [Pooler](#pooler) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ----------------------------------------- | -------- | ------- | ---------- | -| `secrets` *[PoolerSecrets](#poolersecrets)* | The resource version of the config object | | | | -| `instances` *integer* | The number of pods trying to be scheduled | | | | - -#### PoolerType - -*Underlying type:* *string* - -PoolerType is the type of the connection pool, meaning the service -we are targeting. Allowed values are `rw` and `ro`. - -*Validation:* - -- Enum: [rw ro r] - -*Appears in:* - -- [PoolerSpec](#poolerspec) - -#### PostgresConfiguration - -PostgresConfiguration defines the PostgreSQL configuration - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `parameters` *object (keys:string, values:string)* | PostgreSQL configuration options (postgresql.conf) | | | | -| `synchronous` *[SynchronousReplicaConfiguration](#synchronousreplicaconfiguration)* | Configuration of the PostgreSQL synchronous replication feature | | | | -| `pg_hba` *string array* | PostgreSQL Host Based Authentication rules (lines to be appended
to the pg_hba.conf file).
Use the ${podselector:NAME} syntax to reference a pod selector;
the rule will be expanded for each Pod IP matching that selector. | | | | -| `pg_ident` *string array* | PostgreSQL User Name Maps rules (lines to be appended
to the pg_ident.conf file) | | | | -| `epas` *[EPASConfiguration](#epasconfiguration)* | EDB Postgres Advanced Server specific configurations | | | | -| `syncReplicaElectionConstraint` *[SyncReplicaElectionConstraints](#syncreplicaelectionconstraints)* | Requirements to be met by sync replicas. This will affect how the "synchronous_standby_names" parameter will be
set up. | | | | -| `shared_preload_libraries` *string array* | Lists of shared preload libraries to add to the default ones | | | | -| `ldap` *[LDAPConfig](#ldapconfig)* | Options to specify LDAP configuration | | | | -| `promotionTimeout` *integer* | 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 | | | | -| `enableAlterSystem` *boolean* | If this parameter is true, the user will be able to invoke `ALTER SYSTEM`
on this {{name.ln}} Cluster.
This should only be used for debugging and troubleshooting.
Defaults to false. | | | | -| `extensions` *[ExtensionConfiguration](#extensionconfiguration) array* | The configuration of the extensions to be added | | | | - -#### PrimaryUpdateMethod - -*Underlying type:* *string* - -PrimaryUpdateMethod defines the method to use when upgrading -the primary instance of the cluster as part of rolling updates. -The default method is "restart" - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `switchover` | PrimaryUpdateMethodSwitchover means that the operator will switchover to another updated
replica when it needs to upgrade the primary instance.
Note: when using this method, the operator will reject updates that change both
the image name and PostgreSQL configuration parameters simultaneously to avoid
configuration mismatches during the switchover process.
| -| `restart` | PrimaryUpdateMethodRestart means that the operator will restart the primary instance in-place
when it needs to upgrade it
| - -#### PrimaryUpdateStrategy - -*Underlying type:* *string* - -PrimaryUpdateStrategy contains the strategy to follow when upgrading -the primary server of the cluster as part of rolling updates - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `supervised` | PrimaryUpdateStrategySupervised means that the operator need to wait for the
user to manually issue a switchover request before updating the primary
server (`supervised`)
| -| `unsupervised` | PrimaryUpdateStrategyUnsupervised means that the operator will proceed with the
selected PrimaryUpdateMethod to another updated replica and then automatically update
the primary server (`unsupervised`, default)
| - -#### Probe - -Probe describes a health check to be performed against a container to determine whether it is -alive or ready to receive traffic. - -*Appears in:* - -- [LivenessProbe](#livenessprobe) -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | - -#### ProbeStrategyType - -*Underlying type:* *string* - -ProbeStrategyType is the type of the strategy used to declare a PostgreSQL instance -ready - -*Appears in:* - -- [ProbeWithStrategy](#probewithstrategy) - -| Field | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `pg_isready` | ProbeStrategyPgIsReady means that the pg_isready tool is used to determine
whether PostgreSQL is started up
| -| `streaming` | ProbeStrategyStreaming means that pg_isready is positive and the replica is
connected via streaming replication to the current primary and the lag is, if specified,
within the limit.
| -| `query` | ProbeStrategyQuery means that the server is able to connect to the superuser database
and able to execute a simple query like "-- ping"
| - -#### ProbeWithStrategy - -ProbeWithStrategy is the configuration of the startup probe - -*Appears in:* - -- [ProbesConfiguration](#probesconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------------------- | -| `initialDelaySeconds` *integer* | Number of seconds after the container has started before liveness probes are initiated.
More info: | | | | -| `timeoutSeconds` *integer* | Number of seconds after which the probe times out.
Defaults to 1 second. Minimum value is 1.
More info: | | | | -| `periodSeconds` *integer* | How often (in seconds) to perform the probe.
Default to 10 seconds. Minimum value is 1. | | | | -| `successThreshold` *integer* | Minimum consecutive successes for the probe to be considered successful after having failed.
Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. | | | | -| `failureThreshold` *integer* | Minimum consecutive failures for the probe to be considered failed after having succeeded.
Defaults to 3. Minimum value is 1. | | | | -| `terminationGracePeriodSeconds` *integer* | Optional duration in seconds the pod needs to terminate gracefully upon probe failure.
The grace period is the duration in seconds after the processes running in the pod are sent
a termination signal and the time when the processes are forcibly halted with a kill signal.
Set this value longer than the expected cleanup time for your process.
If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this
value overrides the value provided by the pod spec.
Value must be non-negative integer. The value zero indicates stop immediately via
the kill signal (no opportunity to shut down).
This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate.
Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. | | | | -| `type` *[ProbeStrategyType](#probestrategytype)* | The probe strategy | | | Enum: [pg_isready streaming query]
| -| `maximumLag` *[Quantity](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#quantity-resource-api)* | Lag limit. Used only for `streaming` strategy | | | | - -#### ProbesConfiguration - -ProbesConfiguration represent the configuration for the probes -to be injected in the PostgreSQL Pods - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------- | --------------------------------- | -------- | ------- | ---------- | -| `startup` *[ProbeWithStrategy](#probewithstrategy)* | The startup probe configuration | True | | | -| `liveness` *[LivenessProbe](#livenessprobe)* | The liveness probe configuration | True | | | -| `readiness` *[ProbeWithStrategy](#probewithstrategy)* | The readiness probe configuration | True | | | - -#### Publication - -Publication is the Schema for the publications API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Publication` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[PublicationSpec](#publicationspec)* | | True | | | -| `status` *[PublicationStatus](#publicationstatus)* | | True | | | - -#### PublicationReclaimPolicy - -*Underlying type:* *string* - -PublicationReclaimPolicy defines a policy for end-of-life maintenance of Publications. - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `delete` | PublicationReclaimDelete means the publication will be deleted from Kubernetes on release
from its claim.
| -| `retain` | PublicationReclaimRetain means the publication will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### PublicationSpec - -PublicationSpec defines the desired state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "publisher" | True | | | -| `name` *string* | The name of the publication inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "publisher" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Publication parameters part of the `WITH` clause as expected by
PostgreSQL `CREATE PUBLICATION` command | | | | -| `target` *[PublicationTarget](#publicationtarget)* | Target of the publication as expected by PostgreSQL `CREATE PUBLICATION` command | True | | | -| `publicationReclaimPolicy` *[PublicationReclaimPolicy](#publicationreclaimpolicy)* | The policy for end-of-life maintenance of this publication | | retain | Enum: [delete retain]
| - -#### PublicationStatus - -PublicationStatus defines the observed state of Publication - -*Appears in:* - -- [Publication](#publication) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the publication was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### PublicationTarget - -PublicationTarget is what this publication should publish - -*Appears in:* - -- [PublicationSpec](#publicationspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------- | -| `allTables` *boolean* | Marks the publication as one that replicates changes for all tables
in the database, including tables created in the future.
Corresponding to `FOR ALL TABLES` in PostgreSQL. | | | | -| `objects` *[PublicationTargetObject](#publicationtargetobject) array* | Just the following schema objects | | | MaxItems: 100000
| - -#### PublicationTargetObject - -PublicationTargetObject is an object to publish - -*Appears in:* - -- [PublicationTarget](#publicationtarget) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `tablesInSchema` *string* | Marks the publication as one that replicates changes for all tables
in the specified list of schemas, including tables created in the
future. Corresponding to `FOR TABLES IN SCHEMA` in PostgreSQL. | | | | -| `table` *[PublicationTargetTable](#publicationtargettable)* | Specifies a list of tables to add to the publication. Corresponding
to `FOR TABLE` in PostgreSQL. | | | | - -#### PublicationTargetTable - -PublicationTargetTable is a table to publish - -*Appears in:* - -- [PublicationTargetObject](#publicationtargetobject) - -| Field | Description | Required | Default | Validation | -| ------------------------ | ----------------------------------------------------------------- | -------- | ------- | ---------- | -| `only` *boolean* | Whether to limit to the table only or include all its descendants | | | | -| `name` *string* | The table name | True | | | -| `schema` *string* | The schema name | | | | -| `columns` *string array* | The columns to publish | | | | - -#### RecoveryTarget - -RecoveryTarget allows to configure the moment where the recovery process -will stop. All the target options except TargetTLI are mutually exclusive. - -*Appears in:* - -- [BootstrapRecovery](#bootstraprecovery) - -| Field | Description | Required | Default | Validation | -| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `backupID` *string* | 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. | | | | -| `targetTLI` *string* | The target timeline ("latest" or a positive integer) | | | | -| `targetXID` *string* | The target transaction ID | | | | -| `targetName` *string* | The target name (to be previously created
with `pg_create_restore_point`) | | | | -| `targetLSN` *string* | The target LSN (Log Sequence Number) | | | | -| `targetTime` *string* | The target time as a timestamp in RFC3339 format or PostgreSQL timestamp format.
Timestamps without an explicit timezone are interpreted as UTC. | | | | -| `targetImmediate` *boolean* | End recovery as soon as a consistent state is reached | | | | -| `exclusive` *boolean* | Set the target to be exclusive. If omitted, defaults to false, so that
in Postgres, `recovery_target_inclusive` will be true | | | | - -#### ReplicaClusterConfiguration - -ReplicaClusterConfiguration encapsulates the configuration of a replica -cluster - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------- | -| `self` *string* | Self defines the name of this cluster. It is used to determine if this is a primary
or a replica cluster, comparing it with `primary` | | | | -| `primary` *string* | Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the
topology specified in externalClusters | | | | -| `source` *string* | The name of the external cluster which is the replication origin | True | | MinLength: 1
| -| `enabled` *boolean* | 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. | | | | -| `promotionToken` *string* | A demotion token generated by an external cluster used to
check if the promotion requirements are met. | | | | -| `minApplyDelay` *[Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta)* | When replica mode is enabled, this parameter allows you to replay
transactions only when the system time is at least the configured
time past the commit time. This provides an opportunity to correct
data loss errors. Note that when this parameter is set, a promotion
token cannot be used. | | | | - -#### ReplicationSlotsConfiguration - -ReplicationSlotsConfiguration encapsulates the configuration -of replication slots - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------- | -| `highAvailability` *[ReplicationSlotsHAConfiguration](#replicationslotshaconfiguration)* | Replication slots for high availability configuration | | | | -| `updateInterval` *integer* | Standby will update the status of the local replication slots
every `updateInterval` seconds (default 30). | | | Minimum: 1
| -| `synchronizeReplicas` *[SynchronizeReplicasConfiguration](#synchronizereplicasconfiguration)* | Configures the synchronization of the user defined physical replication slots | | | | - -#### 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. - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ------------------------------ | -| `enabled` *boolean* | 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. | | | | -| `slotPrefix` *string* | 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_`. | | | Pattern: `^[0-9a-z_]*$`
| -| `synchronizeLogicalDecoding` *boolean* | When enabled, the operator automatically manages synchronization of logical
decoding (replication) slots across high-availability clusters.
Requires one of the following conditions:
- PostgreSQL version 17 or later
- PostgreSQL version < 17 with pg_failover_slots extension enabled | | | | - -#### 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: - -*Appears in:* - -- [ManagedConfiguration](#managedconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the role | True | | | -| `comment` *string* | Description of the role | | | | -| `ensure` *[EnsureOption](#ensureoption)* | Ensure the role is `present` or `absent` - defaults to "present" | | present | Enum: [present absent]
| -| `passwordSecret` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | Secret containing the password of the role (if present)
If null, the password will be ignored unless DisablePassword is set | | | | -| `connectionLimit` *integer* | If the role can log in, this specifies how many concurrent
connections the role can make. `-1` (the default) means no limit. | | -1 | | -| `validUntil` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Date and time after which the role's password is no longer valid.
When omitted, the password will never expire (default). | | | | -| `inRoles` *string array* | List of one or more existing roles to which this role will be
immediately added as a new member. Default empty. | | | | -| `inherit` *boolean* | Whether a role "inherits" the privileges of roles it is a member of.
Defaults is `true`. | | true | | -| `disablePassword` *boolean* | DisablePassword indicates that a role's password should be set to NULL in Postgres | | | | -| `superuser` *boolean* | 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`. | | | | -| `createdb` *boolean* | 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. | | | | -| `createrole` *boolean* | 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`. | | | | -| `login` *boolean* | 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`. | | | | -| `replication` *boolean* | 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`. | | | | -| `bypassrls` *boolean* | Whether a role bypasses every row-level security (RLS) policy.
Default is `false`. | | | | - -#### RoleStatus - -*Underlying type:* *string* - -RoleStatus represents the status of a managed role in the cluster - -*Appears in:* - -- [ManagedRoles](#managedroles) - -| Field | Description | -| ------------------------ | ----------------------------------------------------------------------------------------------------- | -| `reconciled` | RoleStatusReconciled indicates the role in DB matches the Spec
| -| `not-managed` | RoleStatusNotManaged indicates the role is not in the Spec, therefore not managed
| -| `pending-reconciliation` | RoleStatusPendingReconciliation indicates the role in Spec requires updated/creation in DB
| -| `reserved` | RoleStatusReserved indicates this is one of the roles reserved by the operator. E.g. `postgres`
| - -#### SQLRefs - -SQLRefs holds references to ConfigMaps or Secrets -containing SQL files. The references are processed in a specific order: -first, all Secrets are processed, followed by all ConfigMaps. -Within each group, the processing order follows the sequence specified -in their respective arrays. - -*Appears in:* - -- [BootstrapInitDB](#bootstrapinitdb) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | -------- | ------- | ---------- | -| `secretRefs` *[SecretKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#SecretKeySelector) array* | SecretRefs holds a list of references to Secrets | | | | -| `configMapRefs` *[ConfigMapKeySelector](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#ConfigMapKeySelector) array* | ConfigMapRefs holds a list of references to ConfigMaps | | | | - -#### ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `ScheduledBackup` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[ScheduledBackupSpec](#scheduledbackupspec)* | Specification of the desired behavior of the ScheduledBackup.
More info: | True | | | -| `status` *[ScheduledBackupStatus](#scheduledbackupstatus)* | Most recently observed status of the ScheduledBackup. This data may not be up
to date. Populated by the system. Read-only.
More info: | | | | - -#### ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- | ------------------------------------------------------ | -| `suspend` *boolean* | If this backup is suspended or not | | | | -| `immediate` *boolean* | If the first backup has to be immediately start after creation or not | | | | -| `schedule` *string* | The schedule does not follow the same format used in Kubernetes CronJobs
as it includes an additional seconds specifier,
see | True | | | -| `cluster` *[LocalObjectReference](https://pkg.go.dev/github.com/cloudnative-pg/machinery/pkg/api#LocalObjectReference)* | The cluster to backup | True | | | -| `backupOwnerReference` *string* | 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
| | none | Enum: [none self cluster]
| -| `target` *[BackupTarget](#backuptarget)* | 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. | | | Enum: [primary prefer-standby]
| -| `method` *[BackupMethod](#backupmethod)* | The backup method to be used, possible options are `barmanObjectStore`,
`volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`. | | barmanObjectStore | Enum: [barmanObjectStore volumeSnapshot plugin]
| -| `pluginConfiguration` *[BackupPluginConfiguration](#backuppluginconfiguration)* | Configuration parameters passed to the plugin managing this backup | | | | -| `online` *boolean* | 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' | | | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots
Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza | | | | - -#### ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -*Appears in:* - -- [ScheduledBackup](#scheduledbackup) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `lastCheckTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | The latest time the schedule | | | | -| `lastScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Information when was the last time that backup was successfully scheduled. | | | | -| `nextScheduleTime` *[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)* | Next time we will run a backup | | | | - -#### SchemaSpec - -SchemaSpec configures a schema in a database - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `owner` *string* | The role name of the user who owns the schema inside PostgreSQL.
It maps to the `AUTHORIZATION` parameter of `CREATE SCHEMA` and the
`OWNER TO` command of `ALTER SCHEMA`. | True | | | - -#### SecretVersion - -SecretVersion contains a secret name and its ResourceVersion - -*Appears in:* - -- [PgBouncerSecrets](#pgbouncersecrets) -- [PoolerSecrets](#poolersecrets) - -| Field | Description | Required | Default | Validation | -| ------------------ | --------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the secret | | | | -| `version` *string* | The ResourceVersion of the secret | | | | - -#### SecretsResourceVersion - -SecretsResourceVersion is the resource versions of the secrets -managed by the operator - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `superuserSecretVersion` *string* | The resource version of the "postgres" user secret | | | | -| `replicationSecretVersion` *string* | The resource version of the "streaming_replica" user secret | | | | -| `applicationSecretVersion` *string* | The resource version of the "app" user secret | | | | -| `managedRoleSecretVersion` *object (keys:string, values:string)* | The resource versions of the managed roles secrets | | | | -| `caSecretVersion` *string* | Unused. Retained for compatibility with old versions. | | | | -| `clientCaSecretVersion` *string* | The resource version of the PostgreSQL client-side CA secret version | | | | -| `serverCaSecretVersion` *string* | The resource version of the PostgreSQL server-side CA secret version | | | | -| `serverSecretVersion` *string* | The resource version of the PostgreSQL server-side secret version | | | | -| `barmanEndpointCA` *string* | The resource version of the Barman Endpoint CA if provided | | | | -| `externalClusterSecretVersion` *object (keys:string, values:string)* | The resource versions of the external cluster secrets | | | | -| `metrics` *object (keys:string, values:string)* | A map with the versions of all the secrets used to pass metrics.
Map keys are the secret names, map values are the versions | | | | - -#### ServerSpec - -ServerSpec configures a server of a foreign data wrapper - -*Appears in:* - -- [DatabaseSpec](#databasespec) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ----------------------------- | -| `name` *string* | Name of the object (extension, schema, FDW, server) | True | | | -| `ensure` *[EnsureOption](#ensureoption)* | Specifies whether an object (e.g schema) should be present or absent
in the database. If set to `present`, the object will be created if
it does not exist. If set to `absent`, the extension/schema will be
removed if it exists. | | present | Enum: [present absent]
| -| `fdw` *string* | The name of the Foreign Data Wrapper (FDW) | True | | | -| `options` *[OptionSpec](#optionspec) array* | Options specifies the configuration options for the server
(key is the option name, value is the option value). | | | | -| `usage` *[UsageSpec](#usagespec) array* | List of roles for which `USAGE` privileges on the server are granted or revoked. | | | | - -#### ServiceAccountTemplate - -ServiceAccountTemplate contains the template needed to generate the service accounts - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------- | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | - -#### ServiceSelectorType - -*Underlying type:* *string* - -ServiceSelectorType describes a valid value for generating the service selectors. -It indicates which type of service the selector applies to, such as read-write, read, or read-only - -*Validation:* - -- Enum: [rw r ro] - -*Appears in:* - -- [ManagedService](#managedservice) -- [ManagedServices](#managedservices) - -| Field | Description | -| ----- | ----------------------------------------------------------- | -| `rw` | ServiceSelectorTypeRW selects the read-write service.
| -| `r` | ServiceSelectorTypeR selects the read service.
| -| `ro` | ServiceSelectorTypeRO selects the read-only service.
| - -#### ServiceTemplateSpec - -ServiceTemplateSpec is a structure allowing the user to set -a template for Service generation. - -*Appears in:* - -- [ManagedService](#managedservice) -- [PoolerSpec](#poolerspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `metadata` *[Metadata](#metadata)* | Refer to Kubernetes API documentation for fields of `metadata`. | | | | -| `spec` *[ServiceSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#servicespec-v1-core)* | Specification of the desired behavior of the service.
More info: | | | | - -#### ServiceUpdateStrategy - -*Underlying type:* *string* - -ServiceUpdateStrategy describes how the changes to the managed service should be handled - -*Validation:* - -- Enum: [patch replace] - -*Appears in:* - -- [ManagedService](#managedservice) - -#### SnapshotOwnerReference - -*Underlying type:* *string* - -SnapshotOwnerReference defines the reference type for the owner of the snapshot. -This specifies which owner the processed resources should relate to. - -*Appears in:* - -- [VolumeSnapshotConfiguration](#volumesnapshotconfiguration) - -| Field | Description | -| --------- | ------------------------------------------------------------------------------------------------- | -| `none` | SnapshotOwnerReferenceNone indicates that the snapshot does not have any owner reference.
| -| `backup` | SnapshotOwnerReferenceBackup indicates that the snapshot is owned by the backup resource.
| -| `cluster` | SnapshotOwnerReferenceCluster indicates that the snapshot is owned by the cluster resource.
| - -#### SnapshotType - -*Underlying type:* *string* - -SnapshotType is a type of allowed import - -*Appears in:* - -- [Import](#import) - -| Field | Description | -| -------------- | ----------------------------------------------------------------------------------- | -| `monolith` | MonolithSnapshotType indicates to execute the monolith clone typology
| -| `microservice` | MicroserviceSnapshotType indicates to execute the microservice clone typology
| - -#### StorageConfiguration - -StorageConfiguration is the configuration used to create and reconcile PVCs, -usable for WAL volumes, PGDATA volumes, or tablespaces - -*Appears in:* - -- [ClusterSpec](#clusterspec) -- [TablespaceConfiguration](#tablespaceconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `storageClass` *string* | 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` *string* | 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. | | | | -| `resizeInUseVolumes` *boolean* | Resize existent PVCs, defaults to true | | true | | -| `pvcTemplate` *[PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#persistentvolumeclaimspec-v1-core)* | Template to be used to generate the Persistent Volume Claim | | | | - -#### Subscription - -Subscription is the Schema for the subscriptions API - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | -------- | ------- | ---------- | -| `apiVersion` *string* | `postgresql.k8s.enterprisedb.io/v1` | True | | | -| `kind` *string* | `Subscription` | True | | | -| `metadata` *[ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#objectmeta-v1-meta)* | Refer to Kubernetes API documentation for fields of `metadata`. | True | | | -| `spec` *[SubscriptionSpec](#subscriptionspec)* | | True | | | -| `status` *[SubscriptionStatus](#subscriptionstatus)* | | True | | | - -#### SubscriptionReclaimPolicy - -*Underlying type:* *string* - -SubscriptionReclaimPolicy describes a policy for end-of-life maintenance of Subscriptions. - -*Appears in:* - -- [SubscriptionSpec](#subscriptionspec) - -| Field | Description | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `delete` | SubscriptionReclaimDelete means the subscription will be deleted from Kubernetes on release
from its claim.
| -| `retain` | SubscriptionReclaimRetain means the subscription will be left in its current phase for manual
reclamation by the administrator. The default policy is Retain.
| - -#### SubscriptionSpec - -SubscriptionSpec defines the desired state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------------------------- | -| `cluster` *[LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#localobjectreference-v1-core)* | The name of the PostgreSQL cluster that identifies the "subscriber" | True | | | -| `name` *string* | The name of the subscription inside PostgreSQL | True | | | -| `dbname` *string* | The name of the database where the publication will be installed in
the "subscriber" cluster | True | | | -| `parameters` *object (keys:string, values:string)* | Subscription parameters included in the `WITH` clause of the PostgreSQL
`CREATE SUBSCRIPTION` command. Most parameters cannot be changed
after the subscription is created and will be ignored if modified
later, except for a limited set documented at:
| | | | -| `publicationName` *string* | The name of the publication inside the PostgreSQL database in the
"publisher" | True | | | -| `publicationDBName` *string* | The name of the database containing the publication on the external
cluster. Defaults to the one in the external cluster definition. | | | | -| `externalClusterName` *string* | The name of the external cluster with the publication ("publisher") | True | | | -| `subscriptionReclaimPolicy` *[SubscriptionReclaimPolicy](#subscriptionreclaimpolicy)* | The policy for end-of-life maintenance of this subscription | | retain | Enum: [delete retain]
| - -#### SubscriptionStatus - -SubscriptionStatus defines the observed state of Subscription - -*Appears in:* - -- [Subscription](#subscription) - -| Field | Description | Required | Default | Validation | -| ------------------------------ | ---------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `observedGeneration` *integer* | A sequence number representing the latest
desired state that was synchronized | | | | -| `applied` *boolean* | Applied is true if the subscription was reconciled correctly | | | | -| `message` *string* | Message is the reconciliation output message | | | | - -#### SwitchReplicaClusterStatus - -SwitchReplicaClusterStatus contains all the statuses regarding the switch of a cluster to a replica cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ---------------------- | -------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `inProgress` *boolean* | InProgress indicates if there is an ongoing procedure of switching a cluster to a replica cluster. | | | | - -#### 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. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| --------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `nodeLabelsAntiAffinity` *string array* | A list of node labels values to extract and compare to evaluate if the pods reside in the same topology or not | | | | -| `enabled` *boolean* | This flag enables the constraints for sync replicas | True | | | - -#### SynchronizeReplicasConfiguration - -SynchronizeReplicasConfiguration contains the configuration for the synchronization of user defined -physical replication slots - -*Appears in:* - -- [ReplicationSlotsConfiguration](#replicationslotsconfiguration) - -| Field | Description | Required | Default | Validation | -| -------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | When set to true, every replication slot that is on the primary is synchronized on each standby | True | | | -| `excludePatterns` *string array* | List of regular expression patterns to match the names of replication slots to be excluded (by default empty) | | | | - -#### SynchronousReplicaConfiguration - -SynchronousReplicaConfiguration contains the configuration of the -PostgreSQL synchronous replication feature. -Important: at this moment, also `.spec.minSyncReplicas` and `.spec.maxSyncReplicas` -need to be considered. - -*Appears in:* - -- [PostgresConfiguration](#postgresconfiguration) - -| Field | Description | Required | Default | Validation | -| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | --------------------------------- | -| `method` *[SynchronousReplicaConfigurationMethod](#synchronousreplicaconfigurationmethod)* | Method to select synchronous replication standbys from the listed
servers, accepting 'any' (quorum-based synchronous replication) or
'first' (priority-based synchronous replication) as values. | True | | Enum: [any first]
| -| `number` *integer* | Specifies the number of synchronous standby servers that
transactions must wait for responses from. | True | | | -| `maxStandbyNamesFromCluster` *integer* | Specifies the maximum number of local cluster pods that can be
automatically included in the `synchronous_standby_names` option in
PostgreSQL. | | | | -| `standbyNamesPre` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` before local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `standbyNamesPost` *string array* | A user-defined list of application names to be added to
`synchronous_standby_names` after local cluster pods (the order is
only useful for priority-based synchronous replication). | | | | -| `dataDurability` *[DataDurabilityLevel](#datadurabilitylevel)* | If set to "required", data durability is strictly enforced. Write operations
with synchronous commit settings (`on`, `remote_write`, or `remote_apply`) will
block if there are insufficient healthy replicas, ensuring data persistence.
If set to "preferred", data durability is maintained when healthy replicas
are available, but the required number of instances will adjust dynamically
if replicas become unavailable. This setting relaxes strict durability enforcement
to allow for operational continuity. This setting is only applicable if both
`standbyNamesPre` and `standbyNamesPost` are unset (empty). | | | Enum: [required preferred]
| -| `failoverQuorum` *boolean* | FailoverQuorum enables a quorum-based check before failover, improving
data durability and safety during failover events in {{name.ln}}-managed
PostgreSQL clusters. | | | | - -#### SynchronousReplicaConfigurationMethod - -*Underlying type:* *string* - -SynchronousReplicaConfigurationMethod configures whether to use -quorum based replication or a priority list - -*Appears in:* - -- [SynchronousReplicaConfiguration](#synchronousreplicaconfiguration) - -#### TDEConfiguration - -TDEConfiguration contains the Transparent Data Encryption configuration - -*Appears in:* - -- [EPASConfiguration](#epasconfiguration) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `enabled` *boolean* | True if we want to have TDE enabled | | | | -| `secretKeyRef` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | Reference to the secret that contains the encryption key | | | | -| `wrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | WrapCommand is the encrypt command provided by the user | | | | -| `unwrapCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | UnwrapCommand is the decryption command provided by the user | | | | -| `passphraseCommand` *[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#secretkeyselector-v1-core)* | PassphraseCommand is the command executed to get the passphrase that will be
passed to the OpenSSL command to encrypt and decrypt | | | | - -#### TablespaceConfiguration - -TablespaceConfiguration is the configuration of a tablespace, and includes -the storage specification for the tablespace - -*Appears in:* - -- [ClusterSpec](#clusterspec) - -| Field | Description | Required | Default | Validation | -| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | The name of the tablespace | True | | | -| `storage` *[StorageConfiguration](#storageconfiguration)* | The storage configuration for the tablespace | True | | | -| `owner` *[DatabaseRoleRef](#databaseroleref)* | Owner is the PostgreSQL user owning the tablespace | | | | -| `temporary` *boolean* | When set to true, the tablespace will be added as a `temp_tablespaces`
entry 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. | | false | | - -#### TablespaceState - -TablespaceState represents the state of a tablespace in a cluster - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------- | -------------------------------------------------- | -------- | ------- | ---------- | -| `name` *string* | Name is the name of the tablespace | True | | | -| `owner` *string* | Owner is the PostgreSQL user owning the tablespace | | | | -| `state` *[TablespaceStatus](#tablespacestatus)* | State is the latest reconciliation state | True | | | -| `error` *string* | Error is the reconciliation error, if any | | | | - -#### TablespaceStatus - -*Underlying type:* *string* - -TablespaceStatus represents the status of a tablespace in the cluster - -*Appears in:* - -- [TablespaceState](#tablespacestate) - -| Field | Description | -| ------------ | -------------------------------------------------------------------------------------------------------- | -| `reconciled` | TablespaceStatusReconciled indicates the tablespace in DB matches the Spec
| -| `pending` | TablespaceStatusPendingReconciliation indicates the tablespace in Spec requires creation in the DB
| - -#### Topology - -Topology contains the cluster topology - -*Appears in:* - -- [ClusterStatus](#clusterstatus) - -| Field | Description | Required | Default | Validation | -| ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | ---------- | -| `instances` *object (keys:[PodName](#podname), values:[PodTopologyLabels](#podtopologylabels))* | Instances contains the pod topology of the instances | | | | -| `nodesUsed` *integer* | 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` *boolean* | SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors
in synchronous replica election in case of failures | | | | - -#### UsageSpec - -UsageSpec configures a usage for a foreign data wrapper - -*Appears in:* - -- [FDWSpec](#fdwspec) -- [ServerSpec](#serverspec) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------- | ----------------- | -------- | ------- | --------------------------- | -| `name` *string* | Name of the usage | True | | | -| `type` *[UsageSpecType](#usagespectype)* | The type of usage | | grant | Enum: [grant revoke]
| - -#### UsageSpecType - -*Underlying type:* *string* - -UsageSpecType describes the type of usage specified in the `usage` field of the -`Database` object. - -*Appears in:* - -- [UsageSpec](#usagespec) - -| Field | Description | -| -------- | -------------------------------------------------------------------------------------------------------- | -| `grant` | GrantUsageSpecType indicates a grant usage permission.
The default usage permission is grant.
| -| `revoke` | RevokeUsageSpecType indicates a revoke usage permission.
| - -#### VolumeSnapshotConfiguration - -VolumeSnapshotConfiguration represents the configuration for the execution of snapshot backups. - -*Appears in:* - -- [BackupConfiguration](#backupconfiguration) - -| Field | Description | Required | Default | Validation | -| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------- | ---------------------------------- | -| `labels` *object (keys:string, values:string)* | Labels are key-value pairs that will be added to .metadata.labels snapshot resources. | | | | -| `annotations` *object (keys:string, values:string)* | Annotations key-value pairs that will be added to .metadata.annotations snapshot resources. | | | | -| `className` *string* | 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` *string* | WalClassName specifies the Snapshot Class to be used for the PG_WAL PersistentVolumeClaim. | | | | -| `tablespaceClassName` *object (keys:string, values:string)* | TablespaceClassName specifies the Snapshot Class to be used for the tablespaces.
defaults to the PGDATA Snapshot Class, if set | | | | -| `snapshotOwnerReference` *[SnapshotOwnerReference](#snapshotownerreference)* | SnapshotOwnerReference indicates the type of owner reference the snapshot should have | | none | Enum: [none cluster backup]
| -| `online` *boolean* | Whether the default type of backup with volume snapshots is
online/hot (`true`, default) or offline/cold (`false`) | | true | | -| `onlineConfiguration` *[OnlineConfiguration](#onlineconfiguration)* | Configuration parameters to control the online/hot backup with volume snapshots | | { immediateCheckpoint:false waitForArchive:true } | | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.3.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.3.0.mdx deleted file mode 100644 index b06107c25b6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.3.0.mdx +++ /dev/null @@ -1,427 +0,0 @@ ---- -title: 'API Reference - v1.3.0' -navTitle: v1.3.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapRecovery](#BootstrapRecovery) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - -
- -## `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: | map[string]string | - -
- -## `Backup` - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - -
- -## `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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - -
- -## `BackupList` - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - -
- -## `BackupSpec` - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| `cluster` | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | - -
- -## `BackupStatus` - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | -| `error ` | The detected error | string | -| `commandOutput ` | The backup command output | string | -| `commandError ` | The backup command output | string | - -
- -## `BarmanObjectStoreConfiguration` - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - -
- -## `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | - -
- -## `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 | [\*corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | - -
- -## `BootstrapRecovery` - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `backup ` | The backup we need to restore - *mandatory* | [corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | -| `recoveryTarget` | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | [\*RecoveryTarget](#RecoveryTarget) | - -
- -## `Cluster` - -Cluster is the Schema for the PostgreSQL API - -| Name | Description | Type | -| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - -
- -## `ClusterList` - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - -
- -## `ClusterSpec` - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image | 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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | -| `imagePullSecrets ` | 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. | [\[\]corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | - -
- -## `ClusterStatus` - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `initializingPVC ` | List of all the PVCs that are being initialized by this cluster | \[]string | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | - -
- -## `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` or `bzip2`. | 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 | - -
- -## `MonitoringConfiguration` - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]corev1.ConfigMapKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#configmapkeyselector-v1-core) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) | - -
- -## `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) - *mandatory* | \*bool | - -
- -## `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 | - -
- -## `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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to true) | \*bool | - -
- -## `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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | - -
- -## `S3Credentials` - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) | - -
- -## `ScheduledBackup` - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - -
- -## `ScheduledBackupList` - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - -
- -## `ScheduledBackupSpec` - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | -| `suspend ` | If this backup is suspended of not | \*bool | -| `schedule` | The schedule in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | - -
- -## `ScheduledBackupStatus` - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | - -
- -## `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 - *mandatory* | string | -| `replicationSecretVersion` | The resource version of the "streaming_replication" user secret - *mandatory* | string | -| `applicationSecretVersion` | The resource version of the "app" user secret - *mandatory* | string | -| `caSecretVersion ` | The resource version of the "ca" secret version - *mandatory* | string | -| `serverSecretVersion ` | The resource version of the PostgreSQL server-side secret version - *mandatory* | string | - -
- -## `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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#persistentvolumeclaim-v1-core) | - -
- -## `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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.4.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.4.0.mdx deleted file mode 100644 index fb9e849a07f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.4.0.mdx +++ /dev/null @@ -1,427 +0,0 @@ ---- -title: 'API Reference - v1.4.0' -navTitle: v1.4.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapRecovery](#BootstrapRecovery) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - -
- -## `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: | map[string]string | - -
- -## `Backup` - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - -
- -## `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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - -
- -## `BackupList` - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - -
- -## `BackupSpec` - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| `cluster` | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | - -
- -## `BackupStatus` - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | -| `error ` | The detected error | string | -| `commandOutput ` | The backup command output | string | -| `commandError ` | The backup command output | string | - -
- -## `BarmanObjectStoreConfiguration` - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - -
- -## `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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | - -
- -## `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 | [\*corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | - -
- -## `BootstrapRecovery` - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `backup ` | The backup we need to restore - *mandatory* | [corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | -| `recoveryTarget` | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | [\*RecoveryTarget](#RecoveryTarget) | - -
- -## `Cluster` - -Cluster is the Schema for the PostgreSQL API - -| Name | Description | Type | -| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - -
- -## `ClusterList` - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - -
- -## `ClusterSpec` - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image | 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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | -| `imagePullSecrets ` | 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. | [\[\]corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | - -
- -## `ClusterStatus` - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `initializingPVC ` | List of all the PVCs that are being initialized by this cluster | \[]string | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | - -
- -## `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` or `bzip2`. | 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 | - -
- -## `MonitoringConfiguration` - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]corev1.ConfigMapKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#configmapkeyselector-v1-core) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) | - -
- -## `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) - *mandatory* | \*bool | - -
- -## `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 | - -
- -## `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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to true) | \*bool | - -
- -## `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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | - -
- -## `S3Credentials` - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) | - -
- -## `ScheduledBackup` - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - -
- -## `ScheduledBackupList` - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - -
- -## `ScheduledBackupSpec` - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | -| `suspend ` | If this backup is suspended of not | \*bool | -| `schedule` | The schedule in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) | - -
- -## `ScheduledBackupStatus` - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) | - -
- -## `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 - *mandatory* | string | -| `replicationSecretVersion` | The resource version of the "streaming_replication" user secret - *mandatory* | string | -| `applicationSecretVersion` | The resource version of the "app" user secret - *mandatory* | string | -| `caSecretVersion ` | The resource version of the "ca" secret version - *mandatory* | string | -| `serverSecretVersion ` | The resource version of the PostgreSQL server-side secret version - *mandatory* | string | - -
- -## `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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#persistentvolumeclaim-v1-core) | - -
- -## `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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.5.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.5.0.mdx deleted file mode 100644 index bd526d49411..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.5.0.mdx +++ /dev/null @@ -1,535 +0,0 @@ ---- -title: 'API Reference - v1.5.0' -navTitle: v1.5.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - -
- -## 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: | map[string]string | -| `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: | \[]corev1.Toleration | - -
- -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - -
- -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - -
- -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - -
- -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - -
- -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - -
- -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - -
- -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - -
- -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | - -
- -## 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 | - -
- -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `backup ` | The backup we need to restore - *mandatory* | [LocalObjectReference](#LocalObjectReference) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - -
- -## 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. | | - -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. | 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 - `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 | -| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | -| `clientCASecret ` | The secret containing the Client CA certificate. This secret contains a self-signed CA and is used to sign TLS certificates used for client authentication. | | - -Contains: - -- `ca.crt`: CA that should be used to validate the client certificate, used as `ssl_ca_file`. - `ca.key`: key used to sign client SSL certs. | string - `replicationTLSSecret` | The secret of type kubernetes.io/tls containing the TLS client certificate to authenticate as `streaming_replica` user. | string - `expirations ` | Expiration dates for all certificates. | map[string]string - -
- -## Cluster - -Cluster is the Schema for the PostgreSQL API - -| Name | Description | Type | -| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - -
- -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - -
- -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | 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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `certificates ` | The configuration for the CA and related certificates | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | - -
- -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `initializingPVC ` | List of all the PVCs that are being initialized by this cluster | \[]string | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | - -
- -## ConfigMapKeySelector - -ConfigMapKeySelector contains enough information to let you locate the key of a ConfigMap - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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` or `bzip2`. | 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 | - -
- -## ExternalCluster - -ExternalCluster represents the connection parameters of an external server which is used in the cluster 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | - -
- -## 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 | - -
- -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - -
- -## 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) - *mandatory* | \*bool | - -
- -## 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 | - -
- -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to true) | \*bool | - -
- -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - -
- -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - -
- -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - -
- -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - -
- -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------ | --------------------------------------------- | -| `suspend ` | If this backup is suspended of not | \*bool | -| `schedule` | The schedule in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - -
- -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - -
- -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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 - *mandatory* | string | -| `replicationSecretVersion` | The resource version of the "streaming_replication" user secret - *mandatory* | string | -| `applicationSecretVersion` | The resource version of the "app" user secret - *mandatory* | string | -| `caSecretVersion ` | Unused. Retained for compatibility with old versions. | string | -| `clientCaSecretVersion ` | The resource version of the PostgreSQL client-side CA secret version - *mandatory* | string | -| `serverCaSecretVersion ` | The resource version of the PostgreSQL server-side CA secret version - *mandatory* | string | -| `serverSecretVersion ` | The resource version of the PostgreSQL server-side secret version - *mandatory* | string | - -
- -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - -
- -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.5.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.5.1.mdx deleted file mode 100644 index b300b7b004c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.5.1.mdx +++ /dev/null @@ -1,537 +0,0 @@ ---- -title: 'API Reference - v1.5.1' -navTitle: v1.5.1 -pdfExclude: true ---- - -# API Reference - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - -
- -## 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: | map[string]string | -| `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: | \[]corev1.Toleration | - -
- -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - -
- -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - -
- -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - -
- -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - -
- -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - -
- -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - -
- -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - -
- -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | - -
- -## 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 | - -
- -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `backup ` | The backup we need to restore - *mandatory* | [LocalObjectReference](#LocalObjectReference) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - -
- -## 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. | | - -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. | 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 - `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 | -| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | -| `clientCASecret ` | The secret containing the Client CA certificate. This secret contains a self-signed CA and is used to sign TLS certificates used for client authentication. | | - -Contains: - -- `ca.crt`: CA that should be used to validate the client certificate, used as `ssl_ca_file`. - `ca.key`: key used to sign client SSL certs. | string - `replicationTLSSecret` | The secret of type kubernetes.io/tls containing the TLS client certificate to authenticate as `streaming_replica` user. | string - `expirations ` | Expiration dates for all certificates. | map[string]string - -
- -## Cluster - -Cluster is the Schema for the PostgreSQL API - -| Name | Description | Type | -| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - -
- -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - -
- -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | 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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `certificates ` | The configuration for the CA and related certificates | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | - -
- -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `initializingPVC ` | List of all the PVCs that are being initialized by this cluster | \[]string | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | - -
- -## ConfigMapKeySelector - -ConfigMapKeySelector contains enough information to let you locate the key of a ConfigMap - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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` or `bzip2`. | 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 | - -
- -## ExternalCluster - -ExternalCluster represents the connection parameters of an external server which is used in the cluster 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | - -
- -## 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 | - -
- -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - -
- -## 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) - *mandatory* | \*bool | - -
- -## 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 | - -
- -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to true) | \*bool | - -
- -## 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - -
- -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - -
- -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - -
- -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - -
- -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------ | --------------------------------------------- | -| `suspend ` | If this backup is suspended of not | \*bool | -| `schedule` | The schedule in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - -
- -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - -
- -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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_replication" user secret | string | -| `applicationSecretVersion` | The resource version of the "app" user secret | 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 | - -
- -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - -
- -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.6.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.6.0.mdx deleted file mode 100644 index 32209ef5040..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.6.0.mdx +++ /dev/null @@ -1,566 +0,0 @@ ---- -title: 'API Reference - v1.6.0' -navTitle: v1.6.0 -pdfExclude: true ---- - -# API Reference - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - -
- -## 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: | map[string]string | -| `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: | \[]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: | string | - -
- -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - -
- -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - -
- -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - -
- -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - -
- -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - -
- -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - -
- -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - -
- -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | - -
- -## 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 | - -
- -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `backup ` | The backup we need to restore - *mandatory* | [LocalObjectReference](#LocalObjectReference) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - -
- -## 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. | | - -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. | 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 - `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 | -| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | -| `clientCASecret ` | The secret containing the Client CA certificate. This secret contains a self-signed CA and is used to sign TLS certificates used for client authentication. | | - -Contains: - -- `ca.crt`: CA that should be used to validate the client certificate, used as `ssl_ca_file`. - `ca.key`: key used to sign client SSL certs. | string - `replicationTLSSecret` | The secret of type kubernetes.io/tls containing the TLS client certificate to authenticate as `streaming_replica` user. | string - `expirations ` | Expiration dates for all certificates. | map[string]string - -
- -## Cluster - -Cluster is the Schema for the PostgreSQL API - -| Name | Description | Type | -| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - -
- -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - -
- -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | 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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `certificates ` | The configuration for the CA and related certificates | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | - -
- -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | - -
- -## ConfigMapKeySelector - -ConfigMapKeySelector contains enough information to let you locate the key of a ConfigMap - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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` or `bzip2`. | 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 | - -
- -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - -
- -## ExternalCluster - -ExternalCluster represents the connection parameters of an external server which is used in the cluster 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | - -
- -## 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 | - -
- -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - -
- -## 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) - *mandatory* | \*bool | - -
- -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `promotionTimeout ` | Specifies the maximum number of seconds to wait when promoting an instance to primary | int32 | -| `shared_preload_libraries` | Lists of shared preload libraries to add to the default ones | \[]string | - -
- -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external server which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - -
- -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - -
- -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - -
- -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - -
- -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------ | --------------------------------------------- | -| `suspend ` | If this backup is suspended of not | \*bool | -| `schedule` | The schedule in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - -
- -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - -
- -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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_replication" user secret | string | -| `applicationSecretVersion` | The resource version of the "app" user secret | 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 | - -
- -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - -
- -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.7.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.7.0.mdx deleted file mode 100644 index 2b437417cae..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.7.0.mdx +++ /dev/null @@ -1,570 +0,0 @@ ---- -title: 'API Reference - v1.7.0' -navTitle: v1.7.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - -
- -## 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: | map[string]string | -| `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: | \[]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: | 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 | - -
- -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - -
- -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - -
- -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - -
- -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - -
- -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - -
- -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - -
- -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - -
- -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | - -
- -## 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 | - -
- -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `backup ` | The backup we need to restore - *mandatory* | [LocalObjectReference](#LocalObjectReference) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - -
- -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - -
- -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - -
- -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | 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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `certificates ` | The configuration for the CA and related certificates | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | - -
- -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | - -
- -## 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` or `bzip2`. | 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 | - -
- -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - -
- -## ExternalCluster - -ExternalCluster represents the connection parameters of an external server which is used in the cluster 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | - -
- -## 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 | - -
- -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - -
- -## 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) - *mandatory* | \*bool | - -
- -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `promotionTimeout ` | Specifies the maximum number of seconds to wait when promoting an instance to primary | int32 | -| `shared_preload_libraries` | Lists of shared preload libraries to add to the default ones | \[]string | - -
- -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external server which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - -
- -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - -
- -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - -
- -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - -
- -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------ | --------------------------------------------- | -| `suspend ` | If this backup is suspended of not | \*bool | -| `schedule` | The schedule in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - -
- -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - -
- -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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 | -| `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 | - -
- -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - -
- -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.7.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.7.1.mdx deleted file mode 100644 index f1289c2fa1c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.7.1.mdx +++ /dev/null @@ -1,571 +0,0 @@ ---- -title: 'API Reference - v1.7.1' -navTitle: v1.7.1 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 - *mandatory* | [S3Credentials](#S3Credentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - - - -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | -| `backup ` | The backup we need to restore - *mandatory* | [LocalObjectReference](#LocalObjectReference) | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | 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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `certificates ` | The configuration for the CA and related certificates | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | - - - -## 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` or `bzip2`. | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## ExternalCluster - -ExternalCluster represents the connection parameters of an external server which is used in the cluster 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | - - - -## 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 | - - - -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - - - -## 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) - *mandatory* | \*bool | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `promotionTimeout ` | Specifies the maximum number of seconds to wait when promoting an instance to primary | int32 | -| `shared_preload_libraries` | Lists of shared preload libraries to add to the default ones | \[]string | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external server which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## ScheduledBackupSpec - -ScheduledBackupSpec defines the desired state of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------ | --------------------------------------------- | -| `suspend ` | If this backup is suspended of not | \*bool | -| `schedule` | The schedule in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.8.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.8.0.mdx deleted file mode 100644 index 65547128bb4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.8.0.mdx +++ /dev/null @@ -1,597 +0,0 @@ ---- -title: 'API Reference - v1.8.0' -navTitle: v1.8.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to use to upload data in Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - - - -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint` | The first recoverability point, stored as a date in RFC3339 format | 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` or `bzip2`. | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | - - - -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - - - -## 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) - *mandatory* | \*bool | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `promotionTimeout ` | Specifies the maximum number of seconds to wait when promoting an instance to primary | int32 | -| `shared_preload_libraries` | Lists of shared preload libraries to add to the default ones | \[]string | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.0.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.0.mdx deleted file mode 100644 index 40b45d4230f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.0.mdx +++ /dev/null @@ -1,598 +0,0 @@ ---- -title: 'API Reference - v1.9.0' -navTitle: v1.9.0 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to use to upload data in Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - - - -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash` | The commit hash number of which this operator running | 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` or `bzip2`. | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | - - - -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - - - -## 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) - *mandatory* | \*bool | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `promotionTimeout ` | Specifies the maximum number of seconds to wait when promoting an instance to primary | int32 | -| `shared_preload_libraries` | Lists of shared preload libraries to add to the default ones | \[]string | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.1.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.1.mdx deleted file mode 100644 index fcbae01b69d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.1.mdx +++ /dev/null @@ -1,598 +0,0 @@ ---- -title: 'API Reference - v1.9.1' -navTitle: v1.9.1 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to use to upload data in Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - - - -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash` | The commit hash number of which this operator running | 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` or `bzip2`. | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | - - - -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - - - -## 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) - *mandatory* | \*bool | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `promotionTimeout ` | Specifies the maximum number of seconds to wait when promoting an instance to primary | int32 | -| `shared_preload_libraries` | Lists of shared preload libraries to add to the default ones | \[]string | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.2.mdx b/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.2.mdx deleted file mode 100644 index c720fafd8bb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/pg4k.v1/v1.9.2.mdx +++ /dev/null @@ -1,600 +0,0 @@ ---- -title: 'API Reference - v1.9.2' -navTitle: v1.9.2 -pdfExclude: true ---- - -Cloud Native PostgreSQL extends the Kubernetes API defining the following -custom resources: - -- [Backup](#backup) -- [Cluster](#cluster) -- [ScheduledBackup](#scheduledbackup) - -All the resources are defined in the `postgresql.k8s.enterprisedb.io/v1` -API. - -Please refer to the ["Configuration Samples" page](../samples.md)" of the -documentation for examples of usage. - -Below you will find a description of the defined resources: - - - -- [AffinityConfiguration](#AffinityConfiguration) -- [AzureCredentials](#AzureCredentials) -- [Backup](#Backup) -- [BackupConfiguration](#BackupConfiguration) -- [BackupList](#BackupList) -- [BackupSpec](#BackupSpec) -- [BackupStatus](#BackupStatus) -- [BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -- [BootstrapConfiguration](#BootstrapConfiguration) -- [BootstrapInitDB](#BootstrapInitDB) -- [BootstrapPgBaseBackup](#BootstrapPgBaseBackup) -- [BootstrapRecovery](#BootstrapRecovery) -- [CertificatesConfiguration](#CertificatesConfiguration) -- [CertificatesStatus](#CertificatesStatus) -- [Cluster](#Cluster) -- [ClusterList](#ClusterList) -- [ClusterSpec](#ClusterSpec) -- [ClusterStatus](#ClusterStatus) -- [ConfigMapKeySelector](#ConfigMapKeySelector) -- [ConfigMapResourceVersion](#ConfigMapResourceVersion) -- [DataBackupConfiguration](#DataBackupConfiguration) -- [EPASConfiguration](#EPASConfiguration) -- [ExternalCluster](#ExternalCluster) -- [LocalObjectReference](#LocalObjectReference) -- [MonitoringConfiguration](#MonitoringConfiguration) -- [NodeMaintenanceWindow](#NodeMaintenanceWindow) -- [PostgresConfiguration](#PostgresConfiguration) -- [RecoveryTarget](#RecoveryTarget) -- [ReplicaClusterConfiguration](#ReplicaClusterConfiguration) -- [RollingUpdateStatus](#RollingUpdateStatus) -- [S3Credentials](#S3Credentials) -- [ScheduledBackup](#ScheduledBackup) -- [ScheduledBackupList](#ScheduledBackupList) -- [ScheduledBackupSpec](#ScheduledBackupSpec) -- [ScheduledBackupStatus](#ScheduledBackupStatus) -- [SecretKeySelector](#SecretKeySelector) -- [SecretsResourceVersion](#SecretsResourceVersion) -- [StorageConfiguration](#StorageConfiguration) -- [WalBackupConfiguration](#WalBackupConfiguration) - - - -## 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: | map[string]string | -| `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: | \[]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: | 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 - -| Name | Description | Type | -| ------------------ | --------------------------------------------------------------------------------- | ----------------------------------------- | -| `connectionString` | The connection string to be used | [\*SecretKeySelector](#SecretKeySelector) | -| `storageAccount ` | The storage account where to upload data | [\*SecretKeySelector](#SecretKeySelector) | -| `storageKey ` | The storage account key to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | -| `storageSasToken ` | A shared-access-signature to be used in conjunction with the storage account name | [\*SecretKeySelector](#SecretKeySelector) | - - - -## Backup - -Backup is the Schema for the backups API - -| Name | Description | Type | -| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the backup. More info: | [BackupSpec](#BackupSpec) | -| `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: | [BackupStatus](#BackupStatus) | - - - -## 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 | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## BackupList - -BackupList contains a list of Backup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of backups - *mandatory* | [\[\]Backup](#Backup) | - - - -## BackupSpec - -BackupSpec defines the desired state of Backup - -| Name | Description | Type | -| --------- | --------------------- | --------------------------------------------- | -| `cluster` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## BackupStatus - -BackupStatus defines the observed state of Backup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `s3Credentials ` | The credentials to be used to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to be used to upload data to Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 - *mandatory* | 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 | -| `phase ` | The last backup status | BackupPhase | -| `startedAt ` | When the backup was started | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `stoppedAt ` | When the backup was terminated | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `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 | - - - -## BarmanObjectStoreConfiguration - -BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage - -| Name | Description | Type | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | -| `s3Credentials ` | The credentials to use to upload data to S3 | [\*S3Credentials](#S3Credentials) | -| `azureCredentials` | The credentials to use to upload data in Azure Blob Storage | [\*AzureCredentials](#AzureCredentials) | -| `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 | [\*SecretKeySelector](#SecretKeySelector) | -| `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. | [\*WalBackupConfiguration](#WalBackupConfiguration) | -| `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. | [\*DataBackupConfiguration](#DataBackupConfiguration) | - - - -## 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 | [\*BootstrapInitDB](#BootstrapInitDB) | -| `recovery ` | Bootstrap the cluster from a backup | [\*BootstrapRecovery](#BootstrapRecovery) | -| `pg_basebackup` | Bootstrap the cluster taking a physical backup of another compatible PostgreSQL instance | [\*BootstrapPgBaseBackup](#BootstrapPgBaseBackup) | - - - -## 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 | [\*LocalObjectReference](#LocalObjectReference) | -| `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | \*bool | -| `options ` | The list of options that must be passed to initdb when creating the cluster | \[]string | -| `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 | - - - -## 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 | - - - -## BootstrapRecovery - -BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. - -| Name | Description | Type | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| `backup ` | The backup we need to restore | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | string | -| `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: | [\*RecoveryTarget](#RecoveryTarget) | - - - -## 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.

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.
| 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.

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.
| 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` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the cluster. More info: | [ClusterSpec](#ClusterSpec) | -| `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: | [ClusterStatus](#ClusterStatus) | - - - -## ClusterList - -ClusterList contains a list of Cluster - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]Cluster](#Cluster) | - - - -## ClusterSpec - -ClusterSpec defines the desired state of Cluster - -| Name | Description | Type | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `description ` | Description of this PostgreSQL cluster | string | -| `imageName ` | Name of the container image, supporting both tags (`:`) and digests for deterministic and repeatable deployments (`:@sha256:`) | string | -| `imagePullPolicy ` | Image pull policy. One of `Always`, `Never` or `IfNotPresent`. If not defined, it defaults to `IfNotPresent`. Cannot be updated. More info: | corev1.PullPolicy | -| `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* | int32 | -| `minSyncReplicas ` | Minimum number of instances required in synchronous replication with the primary. Undefined or 0 allow writes to complete when no standby is available. | int32 | -| `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. | int32 | -| `postgresql ` | Configuration of the PostgreSQL server | [PostgresConfiguration](#PostgresConfiguration) | -| `bootstrap ` | Instructions to bootstrap this cluster | [\*BootstrapConfiguration](#BootstrapConfiguration) | -| `replica ` | Replica cluster configuration | [\*ReplicaClusterConfiguration](#ReplicaClusterConfiguration) | -| `superuserSecret ` | The secret containing the superuser password. If not defined a new secret will be created with a randomly generated password | [\*LocalObjectReference](#LocalObjectReference) | -| `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 | [\*CertificatesConfiguration](#CertificatesConfiguration) | -| `imagePullSecrets ` | 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. | [\[\]LocalObjectReference](#LocalObjectReference) | -| `storage ` | Configuration of the storage of the instances | [StorageConfiguration](#StorageConfiguration) | -| `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 node to gracefully shutdown (default 30) | int32 | -| `affinity ` | Affinity/Anti-affinity rules for Pods | [AffinityConfiguration](#AffinityConfiguration) | -| `resources ` | Resources requirements of every generated Pod. Please refer to for more information. | [corev1.ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#resourcerequirements-v1-core) | -| `primaryUpdateStrategy` | 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 | -| `backup ` | The configuration to be used for backups | [\*BackupConfiguration](#BackupConfiguration) | -| `nodeMaintenanceWindow` | Define a maintenance window for the Kubernetes nodes | [\*NodeMaintenanceWindow](#NodeMaintenanceWindow) | -| `licenseKey ` | 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. | string | -| `licenseKeySecret ` | The reference to the license key. When this is set it take precedence over LicenseKey. | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [\*MonitoringConfiguration](#MonitoringConfiguration) | -| `externalClusters ` | The list of external clusters which are used in the configuration | [\[\]ExternalCluster](#ExternalCluster) | -| `logLevel ` | The instances' log level, one of the following values: error, info (default), debug, trace | string | - - - -## ClusterStatus - -ClusterStatus defines the observed state of Cluster - -| Name | Description | Type | -| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| `instances ` | Total number of instances in the cluster | int32 | -| `readyInstances ` | Total number of ready instances in the cluster | int32 | -| `instancesStatus ` | Instances status | map[utils.PodStatus][]string | -| `latestGeneratedNode ` | ID of the latest generated node (used to avoid node name clashing) | int32 | -| `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 | -| `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 | -| `licenseStatus ` | Status of the license | licensekey.Status | -| `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 | [SecretsResourceVersion](#SecretsResourceVersion) | -| `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 | [ConfigMapResourceVersion](#ConfigMapResourceVersion) | -| `certificates ` | The configuration for the CA and related certificates, initialized with defaults. | [CertificatesStatus](#CertificatesStatus) | -| `firstRecoverabilityPoint ` | The first recoverability point, stored as a date in RFC3339 format | string | -| `cloudNativePostgresqlCommitHash` | The commit hash number of which this operator running | string | -| `currentPrimaryTimestamp ` | The timestamp when the last actual promotion to primary has occurred | string | -| `targetPrimaryTimestamp ` | The timestamp when the last request for a new primary has occurred | 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` or `bzip2`. | 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 | - - - -## EPASConfiguration - -EPASConfiguration contains EDB Postgres Advanced Server specific configurations - -| Name | Description | Type | -| ------- | --------------------------------- | ---- | -| `audit` | If true enables edb_audit logging | bool | - - - -## 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 | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslKey ` | The reference to an SSL private key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `sslRootCert ` | The reference to an SSL CA public key to be used to connect to this instance | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `password ` | The reference to the password to be used to connect to the server | [\*corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#secretkeyselector-v1-core) | -| `barmanObjectStore ` | The configuration for the barman-cloud tool suite | [\*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) | - - - -## 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 | - - - -## MonitoringConfiguration - -MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster - -| Name | Description | Type | -| ------------------------ | ----------------------------------------------------- | ------------------------------------------------- | -| `customQueriesConfigMap` | The list of config maps containing the custom queries | [\[\]ConfigMapKeySelector](#ConfigMapKeySelector) | -| `customQueriesSecret ` | The list of secrets containing the custom queries | [\[\]SecretKeySelector](#SecretKeySelector) | - - - -## 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) - *mandatory* | \*bool | - - - -## 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 | -| `epas ` | EDB Postgres Advanced Server specific configurations | [\*EPASConfiguration](#EPASConfiguration) | -| `promotionTimeout ` | Specifies the maximum number of seconds to wait when promoting an instance to primary | int32 | -| `shared_preload_libraries` | Lists of shared preload libraries to add to the default ones | \[]string | - - - -## 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 | -| ----------------- | ------------------------------------------------------------------------- | ------ | -| `targetTLI ` | The target timeline ("latest", "current" 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, in any unambiguous representation allowed by PostgreSQL | string | -| `targetImmediate` | End recovery as soon as a consistent state is reached | \*bool | -| `exclusive ` | Set the target to be exclusive (defaults to 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. A cluster of such type can be created only using bootstrap via pg_basebackup - *mandatory* | bool | -| `source ` | The name of the external cluster which is the replication origin - *mandatory* | 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 | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## S3Credentials - -S3Credentials is the type for the credentials to be used to upload files to S3 - -| Name | Description | Type | -| ----------------- | ---------------------------------------------------- | --------------------------------------- | -| `accessKeyId ` | The reference to the access key id - *mandatory* | [SecretKeySelector](#SecretKeySelector) | -| `secretAccessKey` | The reference to the secret access key - *mandatory* | [SecretKeySelector](#SecretKeySelector) | - - - -## ScheduledBackup - -ScheduledBackup is the Schema for the scheduledbackups API - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `metadata` | | [metav1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta) | -| `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: | [ScheduledBackupSpec](#ScheduledBackupSpec) | -| `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: | [ScheduledBackupStatus](#ScheduledBackupStatus) | - - - -## ScheduledBackupList - -ScheduledBackupList contains a list of ScheduledBackup - -| Name | Description | Type | -| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -| `metadata` | Standard list metadata. More info: | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#listmeta-v1-meta) | -| `items ` | List of clusters - *mandatory* | [\[\]ScheduledBackup](#ScheduledBackup) | - - - -## 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 in Cron format, see . - *mandatory* | string | -| `cluster ` | The cluster to backup | [LocalObjectReference](#LocalObjectReference) | - - - -## ScheduledBackupStatus - -ScheduledBackupStatus defines the observed state of ScheduledBackup - -| Name | Description | Type | -| ------------------ | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `lastCheckTime ` | The latest time the schedule | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | -| `nextScheduleTime` | Next time we will run a backup | [\*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#time-v1-meta) | - - - -## SecretKeySelector - -SecretKeySelector contains enough information to let you locate the key of a Secret - -| Name | Description | Type | -| ----- | ------------------------------- | ------ | -| `key` | The key to select - *mandatory* | 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 | -| `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 | - - - -## 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. - *mandatory* | string | -| `resizeInUseVolumes` | Resize existent PVCs, defaults to true | \*bool | -| `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [\*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#persistentvolumeclaim-v1-core) | - - - -## 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` or `bzip2`. | 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 | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/postgis.mdx b/product_docs/docs/postgres_for_kubernetes/preview/postgis.mdx deleted file mode 100644 index 1b31ce49ddc..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/postgis.mdx +++ /dev/null @@ -1,177 +0,0 @@ ---- -title: 'PostGIS' -originalFilePath: 'src/postgis.md' ---- - -[PostGIS](https://postgis.net/) is a very popular open source extension -for PostgreSQL that introduces support for storing GIS (Geographic Information -Systems) objects in the database and be queried via SQL. - -!!!info Important -This section assumes you are familiar with PostGIS and provides some basic -information about how to create a new PostgreSQL cluster with a PostGIS database -in Kubernetes via {{name.ln}}. -!!! - -The CloudNativePG Community maintains container images that are built on top -of the maintained [PostgreSQL Container images](https://github.com/cloudnative-pg/postgres-containers). -For more information, please visit: - -- The [`postgis-containers` project in GitHub](https://github.com/cloudnative-pg/postgis-containers) -- The [`postgis-containers` Container Registry in GitHub](https://github.com/cloudnative-pg/postgis-containers/pkgs/container/postgis) - -Additionally, EDB provides container images for: - -- Community PostgreSQL + PostGIS -- EDB Postgres Advanced Server (EPAS) + PostGIS -- EDB Postgres Extended (PGE) + PostGIS - -and makes them available in the official registry -at `docker.enterprisedb.com`, with the `-postgis` suffix. - -## Basic concepts about a PostGIS cluster - -Conceptually, a PostGIS-based PostgreSQL cluster (or simply a PostGIS cluster) -is like any other PostgreSQL cluster. The only differences are: - -- the presence in the system of PostGIS and related libraries -- the presence in the database(s) of the PostGIS extension - -Since {{name.ln}} is based on Immutable Application Containers, the only way -to provision PostGIS is to add it to the container image that you use for the -operand. The ["Container Image Requirements" section](container_images.md) provides -detailed instructions on how this is achieved. More simply, you can just use -the PostGIS container images from the Community, as in the examples below. - -The second step is to install the extension in the PostgreSQL database. You can -do this in two ways: - -- install it in the application database, which is the main and supposedly only - database you host in the cluster according to the microservice architecture, or -- install it in the `template1` database to make it available for all the - databases you end up creating in the cluster, in case you adopt the monolith - architecture where the instance is shared by multiple databases - -!!!info -For more information on the microservice vs monolith architecture in the database, -please refer to the ["How many databases should be hosted in a single PostgreSQL instance?" FAQ](faq.md) -or the ["Database import" section](database_import.md). -!!! - -## Create a new PostgreSQL cluster with PostGIS - -Let's suppose you want to create a new PostgreSQL 18 cluster with PostGIS 3.6. - -The first step is to ensure you use the right PostGIS container image for the -operand, and properly set the `.spec.imageName` option in the `Cluster` -resource. - -The [`postgis-example.yaml` manifest](../samples/postgis-example.yaml) below -provides some guidance on how the creation of a PostGIS cluster can be done. - -!!!warning -Please consider that, although convention over configuration applies in -{{name.ln}}, you should spend time configuring and tuning your system for -production. Also, the `imageName` in the example below deliberately points -to the latest available image for PostgreSQL 17 - you should use a specific -image name or, preferably, the SHA256 digest for true immutability. -!!! - -```yaml -apiVersion: postgresql.cnpg.io/v1 -kind: Cluster -metadata: - name: postgis-example -spec: - instances: 1 - imageName: docker.enterprisedb.com/k8s/postgresql:17-postgis-ubi9 - storage: - size: 1Gi - postgresql: - parameters: - log_statement: ddl ---- -apiVersion: postgresql.cnpg.io/v1 -kind: Database -metadata: - name: postgis-example-app -spec: - name: app - owner: app - cluster: - name: postgis-example - extensions: - - name: postgis - - name: postgis_topology - - name: fuzzystrmatch - - name: postgis_tiger_geocoder -``` - -The example leverages the `Database` resource's declarative extension -management to add the specified extensions to the `app` database. - -!!!info -Take some time and look at the available options in `.spec.bootstrap.initdb` -from the [API reference](pg4k.v1.md#bootstrapinitdb), such as -`postInitApplicationSQL`. -!!! - -!!!info -For more details, see the -["Managing Extensions in a Database" section](declarative_database_management.md#managing-extensions-in-a-database). -!!! - -!!! Info - For more details, see the - ["Managing Extensions in a Database" section](declarative_database_management.md#managing-extensions-in-a-database). - -You can easily verify the available version of PostGIS that is in the -container, by connecting to the `app` database (you might obtain different -values from the ones in this document): - -```console -$ kubectl cnpg psql postgis-example -- app -psql (18.0 (Debian 18.0-1.pgdg13+3)) -Type "help" for help. - -app=# SELECT * FROM pg_available_extensions WHERE name ~ '^postgis' ORDER BY 1; - name | default_version | installed_version | comment ---------------------------+-----------------+-------------------+------------------------------------------------------------ - postgis | 3.6.0 | 3.6.0 | PostGIS geometry and geography spatial types and functions - postgis-3 | 3.6.0 | | PostGIS geometry and geography spatial types and functions - postgis_raster | 3.6.0 | | PostGIS raster types and functions - postgis_raster-3 | 3.6.0 | | PostGIS raster types and functions - postgis_sfcgal | 3.6.0 | | PostGIS SFCGAL functions - postgis_sfcgal-3 | 3.6.0 | | PostGIS SFCGAL functions - postgis_tiger_geocoder | 3.6.0 | 3.6.0 | PostGIS tiger geocoder and reverse geocoder - postgis_tiger_geocoder-3 | 3.6.0 | | PostGIS tiger geocoder and reverse geocoder - postgis_topology | 3.6.0 | 3.6.0 | PostGIS topology spatial types and functions - postgis_topology-3 | 3.6.0 | | PostGIS topology spatial types and functions -(10 rows) -``` - -The next step is to verify that the extensions listed in the `Database` -resource have been correctly installed in the `app` database. - -```console -app=# \dx - List of installed extensions - Name | Version | Default version | Schema | Description -------------------------+---------+-----------------+------------+------------------------------------------------------------ - fuzzystrmatch | 1.2 | 1.2 | public | determine similarities and distance between strings - plpgsql | 1.0 | 1.0 | pg_catalog | PL/pgSQL procedural language - postgis | 3.6.0 | 3.6.0 | public | PostGIS geometry and geography spatial types and functions - postgis_tiger_geocoder | 3.6.0 | 3.6.0 | tiger | PostGIS tiger geocoder and reverse geocoder - postgis_topology | 3.6.0 | 3.6.0 | topology | PostGIS topology spatial types and functions -``` - -Finally: - -```console -app=# SELECT postgis_full_version(); - postgis_full_version ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- - POSTGIS="3.6.0 4c1967d" [EXTENSION] PGSQL="180" GEOS="3.13.1-CAPI-1.19.2" PROJ="9.6.0 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj. -db" (compiled against PROJ 9.6.0) LIBXML="2.9.14" LIBJSON="0.18" LIBPROTOBUF="1.5.1" WAGYU="0.5.0 (Internal)" TOPOLOGY -(1 row) -``` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/postgres_upgrades.mdx b/product_docs/docs/postgres_for_kubernetes/preview/postgres_upgrades.mdx deleted file mode 100644 index 905ebb68a74..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/postgres_upgrades.mdx +++ /dev/null @@ -1,354 +0,0 @@ ---- -title: 'PostgreSQL upgrades' -originalFilePath: 'src/postgres_upgrades.md' ---- - - - -PostgreSQL upgrades fall into two categories: - -- [Minor version upgrades](#minor-version-upgrades) (e.g., from 18.0 to 18.1) -- [Major version upgrades](#major-version-upgrades) (e.g., from 16.x to 18.0) - -## Minor Version Upgrades - -PostgreSQL version numbers follow a `major.minor` format. For instance, in -version 18.1: - -- `18` is the major version -- `1` is the minor version - -Minor releases are fully compatible with earlier and later minor releases of -the same major version. They include bug fixes and security updates but do not -introduce changes to the internal storage format. - -### Upgrading a Minor Version in {{name.ln}} - -To upgrade to a newer minor version, simply update the PostgreSQL container -image reference in your cluster definition, either directly or via image catalogs. -{{name.ln}} will trigger a [rolling update of the cluster](rolling_update.md), -replacing each instance one by one, starting with the replicas. Once all -replicas have been updated, it will perform either a switchover or a restart of -the primary to complete the process. - -## Major Version Upgrades - -Major PostgreSQL releases introduce changes to the internal data storage -format, requiring a more structured upgrade process. - -{{name.ln}} supports three methods for performing major upgrades: - -1. [Logical dump/restore](database_import.md) – Blue/green deployment, offline. -2. [Native logical replication](logical_replication.md#example-of-live-migration-and-major-postgres-upgrade-with-logical-replication) – Blue/green deployment, online. -3. Physical with `pg_upgrade` – In-place upgrade, offline (covered in the - ["Offline In-Place Major Upgrades" section](#offline-in-place-major-upgrades) below). - -Each method has trade-offs in terms of downtime, complexity, and data volume -handling. The best approach depends on your upgrade strategy and operational -constraints. - -!!!info Important -We strongly recommend testing all methods in a controlled environment -before proceeding with a production upgrade. -!!! - -## Offline In-Place Major Upgrades - -{{name.ln}} performs an **offline in-place major upgrade** when a new operand -container image with a higher PostgreSQL major version is declaratively -requested for a cluster. - -!!!info Important -Major upgrades are only supported between images based on the same -operating system distribution. For example, if your previous version uses a -`bullseye` image, you cannot upgrade to a `bookworm` image. -!!! - -!!!warning -There is a bug in PostgreSQL 17.0 through 17.5 that prevents successful upgrades -if the `max_slot_wal_keep_size` parameter is set to any value other than `-1`. -The upgrade process will fail with an error related to replication slot configuration. -This issue has been [fixed in PostgreSQL 17.6 and 18 or later versions](https://github.com/postgres/postgres/commit/f36e5774). -If you are using PostgreSQL 17.0 through 17.5, ensure that you upgrade to at least -PostgreSQL 17.6 before attempting a major upgrade, or make sure to temporarily set -the `max_slot_wal_keep_size` parameter to `-1` in your cluster configuration. -!!! - -You can trigger the upgrade in one of two ways: - -- By updating the major version in the image tag via the `.spec.imageName` - option. -- Using an [image catalog](image_catalog.md) to manage version changes. - -For details on supported image tags, see -["Image Tag Requirements"](container_images.md#image-tag-requirements). - -!!!warning -{{name.ln}} is not responsible for PostgreSQL extensions. You must ensure -that extensions in the source PostgreSQL image are compatible with those in the -target image and that upgrade paths are supported. Thoroughly test the upgrade -process in advance to avoid unexpected issues. -The [extensions management feature](declarative_database_management.md#managing-extensions-in-a-database) -can help manage extension upgrades declaratively. -!!! - -### Upgrade Process - -1. Shuts down all cluster pods to ensure data consistency. -2. Records the previous PostgreSQL version and image in the cluster’s status under - `.status.pgDataImageInfo`. -3. Initiates a new upgrade job, which: - - Verifies that the binaries in the image and the data files align with a - major upgrade request. - - Creates new directories for `PGDATA`, and where applicable, WAL files and - tablespaces. - - Performs the upgrade using `pg_upgrade` with the `--link` option. - - Upon successful completion, replaces the original directories with their - upgraded counterparts. - -!!!warning -During the upgrade process, the entire PostgreSQL cluster, including -replicas, is unavailable to applications. Ensure that your system can -tolerate this downtime before proceeding. -!!! - -!!!warning -Performing an in-place upgrade is an exceptional operation that carries inherent -risks. It is strongly recommended to take a full backup of the cluster before -initiating the upgrade process. -!!! - -!!!info -For detailed guidance on `pg_upgrade`, refer to the official -[PostgreSQL documentation](https://www.postgresql.org/docs/current/pgupgrade.html). -!!! - -### Post-Upgrade Actions - -If the upgrade is successful, {{name.ln}}: - -- Destroys the PVCs of replicas (if available). -- Scales up replicas as required. - -!!!warning -Re-cloning replicas can be time-consuming, especially for very large -databases. Plan accordingly to accommodate potential delays. After completing -the upgrade, take a new base backup as soon as possible. Pre-upgrade backups -and WAL files cannot be used for point-in-time recovery (PITR) across major -version boundaries. See [Backup and WAL Archive Considerations](#backup-and-wal-archive-considerations) -for more details. -!!! - -!!!warning -`pg_upgrade` doesn't transfer optimizer statistics. After the upgrade, you -may want to run `ANALYZE` on your databases to update them. -!!! - -If the upgrade fails, revert the image in the cluster's configuration to the -previous major version. The operator detects the rollback and automatically -deletes the failed upgrade job, allowing the cluster to restart on the original -version. - -!!!info Important -This process **protects your existing database from data loss**, as no data -is modified during the upgrade. If the upgrade fails, a rollback is -usually possible, without having to perform a full recovery from a backup. -Ensure you monitor the process closely and take corrective action if needed. -!!! - -#### Extensions during a major upgrade - -When a cluster declares image-volume extensions, the upgrade `Job` mounts both -the source-version and the target-version extension images side by side. -Source-version extensions are needed so the old server can start with its -existing shared libraries already in place. -Target-version extensions (built for the new PostgreSQL major) must also be -present so that `pg_upgrade` can properly perform the upgrade to the new major: - -- Source-version extensions are mounted at `/extensions/` (the - steady-state path), so `dynamic_library_path` and `extension_control_path` - GUCs in the old `PGDATA` keep the existing values. - This ensures that, in case of major upgrade failure, a revert to the old - major version will work seamlessly. -- Target-version extensions are temporarily mounted at `/new-extensions/` - just during the upgrade job, and `dynamic_library_path` and `extension_control_path` - are configured accordingly for the `PGDATA` of the new major. - -`LD_LIBRARY_PATH` and `PATH` are extended with both sets, so binaries and -shared objects from either version are reachable. -Environment variables declared via `extensions[].env` obey the rules -described in [Precedence and Conflict Resolution](imagevolume_extensions.md#precedence-and-conflict-resolution). - -!!!note - -Target-version entries are applied **after** source-version entries. When the -same variable is defined for both, the target-version value takes precedence. -!!! - -#### When `pg_upgrade` emits `update_extensions.sql` - -`pg_upgrade` emits an `update_extensions.sql` script inside the `PGDATA` -when a target cluster contains extensions whose `default_version` is -newer than the version `pg_upgrade` left installed. Until that script is -applied, the SQL-level extension metadata in `pg_catalog` lags the -shared libraries actually loaded by the running server. - -The script lives inside the primary pod's `PGDATA`. -You can execute it using the database superuser (`postgres`) to -update those extensions in all databases: - -```sh -PRIMARY=$(kubectl get cluster -o jsonpath='{.status.currentPrimary}') -SCRIPT=/var/lib/postgresql/data/pgdata/update_extensions.sql - -kubectl exec -i "$PRIMARY" -- psql -f "$SCRIPT" -``` - -!!!note - -The script path above assumes the default `PGDATA` location used by the -{{name.ln}} operand images. The operator also logs the resolved path when -`pg_upgrade` emits the script, so check the operator logs if your operand image -uses a different `PGDATA`. -!!! - -### Backup and WAL Archive Considerations - -When performing a major upgrade, `pg_upgrade` creates a new database system -with a new *System ID* and resets the PostgreSQL timeline to 1. This has -implications for backup and WAL archiving: - -- **Timeline file conflicts**: New timeline 1 files may overwrite timeline 1 - files from the original cluster. -- **Mixed version archives**: Without intervention, the archive will contain - WAL files and backups from both PostgreSQL versions. - -!!!warning -Point-in-time recovery (PITR) is not supported across major PostgreSQL version -boundaries. You cannot use pre-upgrade backups to recover to a point in time -after the upgrade. Take a new base backup as soon as possible after upgrading -to establish a recovery baseline for the new major version. -!!! - -How backup systems handle major upgrades depends on the plugin implementation. -Some plugins may automatically manage archive separation during upgrades, while -others require manual configuration to use different archive paths for each -major version. Consult your backup plugin documentation for its specific -behavior during major upgrades. - -#### Example: Manual archive path separation with the Barman Cloud plugin - -The Barman Cloud plugin does not automatically separate archives during major -upgrades. To preserve pre-upgrade backups and keep archives clean, change the -`serverName` parameter when you trigger the upgrade. - -Before upgrade (PostgreSQL 16): - -```yaml -spec: - imageName: docker.enterprisedb.com/k8s/postgresql:16-minimal-ubi9 - plugins: - - name: plugin-barman-cloud - enabled: true - parameters: - destinationPath: s3://my-bucket/ - serverName: cluster-example-pg16 -``` - -To trigger the upgrade, change both `imageName` and `serverName` together: - -```yaml -spec: - imageName: docker.enterprisedb.com/k8s/postgresql:18-minimal-ubi9 - plugins: - - name: plugin-barman-cloud - enabled: true - parameters: - destinationPath: s3://my-bucket/ - serverName: cluster-example-pg18 -``` - -With this configuration, the old archive at `cluster-example-pg16` remains -intact for pre-upgrade recovery, while the upgraded cluster writes to -`cluster-example-pg18`. - -!!!info -The deprecated in-tree `barmanObjectStore` implementation also requires manual -`serverName` changes to separate archives during major upgrades. -!!! - -### Example: Performing a Major Upgrade - -Consider the following PostgreSQL cluster running version 16: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - imageName: docker.enterprisedb.com/k8s/postgresql:16-minimal-ubi9 - instances: 3 - storage: - size: 1Gi -``` - -You can check the current PostgreSQL version using the following command: - -```sh -kubectl cnp psql cluster-example -- -qAt -c 'SELECT version()' -``` - -This will return output similar to: - -```console -PostgreSQL 16.x ... -``` - -To upgrade the cluster to version 18, update the `imageName` field by changing -the major version tag from `16` to `18`: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - imageName: docker.enterprisedb.com/k8s/postgresql:18-minimal-ubi9 - instances: 3 - storage: - size: 1Gi -``` - -### Upgrade Process - -1. Cluster shutdown – All cluster pods are terminated to ensure a consistent - upgrade. -2. Upgrade job execution – A new job is created with the name of the primary - pod, appended with the suffix `-major-upgrade`. This job runs `pg_upgrade` - on the primary’s persistent volume group. -3. Post-upgrade steps: - - The PVC groups of the replicas (`cluster-example-2` and - `cluster-example-3`) are removed. - - The primary pod is restarted. - - Two new replicas (`cluster-example-2` and `cluster-example-3`) are - re-cloned from the upgraded primary. - -Once the upgrade is complete, you can verify the new major version by running -the same command: - -```sh -kubectl cnp psql cluster-example -- -qAt -c 'SELECT version()' -``` - -This should now return output similar to: - -```console -PostgreSQL 18.x ... -``` - -You can now update the statistics by running `ANALYZE` on the `app` database: - -```sh -kubectl cnp psql cluster-example -- app -c 'ANALYZE' -``` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/postgresql_conf.mdx b/product_docs/docs/postgres_for_kubernetes/preview/postgresql_conf.mdx deleted file mode 100644 index 8063c043262..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/postgresql_conf.mdx +++ /dev/null @@ -1,796 +0,0 @@ ---- -title: 'PostgreSQL Configuration' -originalFilePath: 'src/postgresql_conf.md' ---- - - - -Users that are familiar with PostgreSQL are aware of the existence of the -following three files to configure an instance: - -- `postgresql.conf`: main run-time configuration file of PostgreSQL -- `pg_hba.conf`: clients authentication file -- `pg_ident.conf`: map external users to internal users - -Due to the concepts of declarative configuration and immutability of the PostgreSQL -containers, users are not allowed to directly touch those files. Configuration -is possible through the `postgresql` section of the `Cluster` resource definition -by defining custom `postgresql.conf`, `pg_hba.conf`, and `pg_ident.conf` settings -via the `parameters`, the `pg_hba`, and the `pg_ident` keys. - -These settings are the same across all instances. - -!!!warning -Please don't use the `ALTER SYSTEM` query to change the configuration of -the PostgreSQL instances in an imperative way. Changing some of the options -that are normally controlled by the operator might indeed lead to an -unpredictable/unrecoverable state of the cluster. -Moreover, `ALTER SYSTEM` changes are not replicated across the cluster. -See ["Enabling ALTER SYSTEM"](#enabling-alter-system) below for details. -!!! - -A reference for custom settings usage is included in the samples, see -[`cluster-example-custom.yaml`](../samples/cluster-example-custom.yaml). - -!!!warning -**OpenShift users:** due to a current limitation of the OpenShift user interface, -it is possible to change PostgreSQL settings from the YAML pane only. -!!! - -## The `postgresql` section - -The PostgreSQL instance in the pod starts with a default `postgresql.conf` file, -to which these settings are automatically added: - -```text -listen_addresses = '*' -include custom.conf -``` - -The `custom.conf` file will contain the user-defined settings in the -`postgresql` section, as in the following example: - -```yaml - # ... - postgresql: - parameters: - shared_buffers: "1GB" - # ... -``` - -!!!note PostgreSQL GUCs: Grand Unified Configuration -Refer to the PostgreSQL documentation for -[more information on the available parameters](https://www.postgresql.org/docs/current/runtime-config.html), -also known as GUC (Grand Unified Configuration). -Please note that {{name.ln}} accepts only strings for the PostgreSQL parameters. -!!! - -The content of `custom.conf` is automatically generated and maintained by the -operator by applying the following sections in this order: - -- Global default parameters -- Default parameters that depend on the PostgreSQL major version -- User-provided parameters -- Fixed parameters - -The **global default parameters** are: - -```text -archive_timeout = '5min' -dynamic_shared_memory_type = 'posix' -full_page_writes = 'on' -logging_collector = 'on' -log_destination = 'csvlog' -log_directory = '/controller/log' -log_filename = 'postgres' -log_rotation_age = '0' -log_rotation_size = '0' -log_truncate_on_rotation = 'false' -max_parallel_workers = '32' -max_replication_slots = '32' -max_worker_processes = '32' -shared_memory_type = 'mmap' -shared_preload_libraries = '' -ssl_max_protocol_version = 'TLSv1.3' -ssl_min_protocol_version = 'TLSv1.3' -wal_keep_size = '512MB' -wal_level = 'logical' -wal_log_hints = 'on' -wal_sender_timeout = '5s' -wal_receiver_timeout = '5s' -``` - -!!!warning -It is your duty to plan for WAL segments retention in your PostgreSQL -cluster and properly configure either `wal_keep_size` or `wal_keep_segments`, -depending on the server version, based on the expected and observed workloads. - -Alternatively, if the only streaming replication clients are the replica instances -running in the High Availability cluster, you can take advantage of the -replication slots feature, which adds support for replication slots at the -cluster level. You can enable the feature with the -`replicationSlots.highAvailability` option (for more information, please refer to the -["Replication" section](replication.md#replication-slots-for-high-availability).) - -Without replication slots nor continuous backups in place, configuring -`wal_keep_size` or `wal_keep_segments` is the only way to -protect standbys from falling out of sync. -If a standby did fall out of sync it would produce error -messages like: -`"could not receive data from WAL stream: ERROR: requested WAL segment ************************ has already been removed"`. -This will require you to dedicate a part of your `PGDATA`, or the volume -dedicated to storing WAL files, to keep older WAL segments for streaming -replication purposes. -!!! - -The following parameters are **fixed** and exclusively controlled by the operator: - -```text -archive_command = '/controller/manager wal-archive %p' -hot_standby = 'true' -listen_addresses = '*' -port = '5432' -restart_after_crash = 'false' -ssl = 'on' -ssl_ca_file = '/controller/certificates/client-ca.crt' -ssl_cert_file = '/controller/certificates/server.crt' -ssl_key_file = '/controller/certificates/server.key' -unix_socket_directories = '/controller/run' -``` - -Since the fixed parameters are added at the end, they can't be overridden by the -user via the YAML configuration. Those parameters are required for correct WAL -archiving and replication. - -### Write-Ahead Log Level - -The [`wal_level`](https://www.postgresql.org/docs/current/runtime-config-wal.html) -parameter in PostgreSQL determines the amount of information written to the -Write-Ahead Log (WAL). It accepts the following values: - -- `minimal`: Writes only the information required for crash recovery. -- `replica`: Adds sufficient information to support WAL archiving and streaming - replication, including the ability to run read-only queries on standby - instances. -- `logical`: Includes all information from `replica`, plus additional information - required for logical decoding and replication. - -By default, upstream PostgreSQL sets `wal_level` to `replica`. {{name.ln}}, -instead, sets `wal_level` to `logical` by default to enable logical replication -out of the box. This makes it easier to support use cases such as migrations -from external PostgreSQL servers. - -If your cluster does not require logical replication, it is recommended to set -`wal_level` to `replica` to reduce WAL volume and overhead. - -Finally, {{name.ln}} allows `wal_level` to be set to `minimal` only for -single-instance clusters with WAL archiving disabled. - -### Replication Settings - -The `primary_conninfo`, `restore_command`, and `recovery_target_timeline` -parameters are automatically managed by the operator based on the instance's -role within the cluster. These parameters are effectively applied only when the -instance is operating as a replica. - -```text -primary_conninfo = 'host= user=postgres dbname=postgres tcp_user_timeout=5000' -recovery_target_timeline = 'latest' -``` - -!!!info Important -By default, every standby sets `tcp_user_timeout` to **5 seconds**, as shown -above. This parameter defines how long transmitted data may remain -unacknowledged before the TCP connection is forcibly closed. Adjusting it lets -you control how quickly a standby reacts to network issues. -If the default value does not meet your requirements, you can override it -for all standbys managed by the operator using the -[`STANDBY_TCP_USER_TIMEOUT` operator configuration option](operator_conf.md#available-options). -For additional details on `tcp_user_timeout`, refer to the -[PostgreSQL documentation](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-TCP-USER-TIMEOUT). -!!! - -### Log control settings - -The operator requires PostgreSQL to output its log in CSV format, and the -instance manager automatically parses it and outputs it in JSON format. -As a result, certain PostgreSQL log settings, listed in [this section](#fixed-parameters), -are fixed and cannot be modified. - -For further information, please refer to the ["Logging" section](logging.md). - -### Shared Preload Libraries - -The `shared_preload_libraries` option in PostgreSQL exists to specify one or -more shared libraries to be pre-loaded at server start, in the form of a -comma-separated list. Typically, it is used in PostgreSQL to load those -extensions that need to be available to most database sessions in the whole system -(e.g. `pg_stat_statements`). - -In {{name.ln}} the `shared_preload_libraries` option is empty by -default. Although you can override the content of `shared_preload_libraries`, -we recommend that only expert Postgres users take advantage of this option. - -!!!info Important -In case a specified library is not found, the server fails to start, -preventing {{name.ln}} from any self-healing attempt and requiring -manual intervention. Please make sure you always test both the extensions and -the settings of `shared_preload_libraries` if you plan to directly manage its -content. -!!! - -{{name.ln}} is able to automatically manage the content of the -`shared_preload_libraries` option for some of the most used PostgreSQL -extensions (see the ["Managed extensions"](#managed-extensions) section below -for details). - -Specifically, as soon as the operator notices that a configuration parameter -requires one of the managed libraries, it will automatically add the needed -library. The operator will also remove the library as soon as no actual parameter -requires it. - -!!!info Important -Please always keep in mind that removing libraries from -`shared_preload_libraries` requires a restart of all instances in the cluster -in order to be effective. -!!! - -You can provide additional `shared_preload_libraries` via -`.spec.postgresql.shared_preload_libraries` as a list of strings: the operator -will merge them with the ones that it automatically manages. - -### Managed extensions - -As anticipated in the previous section, {{name.ln}} automatically -manages the content in `shared_preload_libraries` for some well-known and -supported extensions. The current list includes: - -- `auto_explain` -- `pg_stat_statements` -- `pgaudit` -- `pg_failover_slots` - -Some of these libraries also require additional objects in a database before -using them, normally views and/or functions managed via the `CREATE EXTENSION` -command to be run in a database (the `DROP EXTENSION` command typically removes -those objects). - -For such libraries, {{name.ln}} automatically handles the creation -and removal of the extension in all databases that accept a connection in the -cluster, identified by the following query: - -```sql -SELECT datname FROM pg_database WHERE datallowconn -``` - -!!!note -The above query also includes template databases like `template1`. -!!! - -!!!info Important -With the introduction of [declarative extensions](declarative_database_management.md#managing-extensions-in-a-database) -in the `Database` CRD, you can now manage extensions directly. As a result, -the managed extensions feature may undergo significant changes in future -versions of {{name.ln}}, and some functionalities might be deprecated. -!!! - -#### Enabling `auto_explain` - -The [`auto_explain`](https://www.postgresql.org/docs/current/auto-explain.html) -extension provides a means for logging execution plans of slow statements -automatically, without having to manually run `EXPLAIN` (helpful for tracking -down un-optimized queries). - -You can enable `auto_explain` by adding to the configuration a parameter -that starts with `auto_explain.` as in the following example excerpt (which -automatically logs execution plans of queries that take longer than 10 seconds -to complete): - -```yaml - # ... - postgresql: - parameters: - auto_explain.log_min_duration: "10s" - # ... -``` - -!!!note -Enabling auto_explain can lead to performance issues. Please refer to [`the auto explain documentation`](https://www.postgresql.org/docs/current/auto-explain.html) -!!! - -#### Enabling `pg_stat_statements` - -The [`pg_stat_statements`](https://www.postgresql.org/docs/current/pgstatstatements.html) -extension is one of the most important capabilities available in PostgreSQL for -real-time monitoring of queries. - -You can enable `pg_stat_statements` by adding to the configuration a parameter -that starts with `pg_stat_statements.` as in the following example excerpt: - -```yaml - # ... - postgresql: - parameters: - pg_stat_statements.max: "10000" - pg_stat_statements.track: all - # ... -``` - -As explained previously, the operator will automatically add -`pg_stat_statements` to `shared_preload_libraries` and run `CREATE EXTENSION IF -NOT EXISTS pg_stat_statements` on each database, enabling you to run queries -against the `pg_stat_statements` view. - -#### Enabling `pgaudit` - -The `pgaudit` extension provides detailed session and/or object audit logging via the standard PostgreSQL logging facility. - -{{name.ln}} has transparent and native support for -[PGAudit](https://www.pgaudit.org/) on PostgreSQL clusters. For further information, please refer to the ["PGAudit" logs section.](logging.md#pgaudit-logs) - -You can enable `pgaudit` by adding to the configuration a parameter -that starts with `pgaudit.` as in the following example excerpt: - -```yaml -# -postgresql: - parameters: - pgaudit.log: "all, -misc" - pgaudit.log_catalog: "off" - pgaudit.log_parameter: "on" - pgaudit.log_relation: "on" -# -``` - -#### Enabling `pg_failover_slots` - -The [`pg_failover_slots`](https://github.com/EnterpriseDB/pg_failover_slots) -extension by EDB ensures that logical replication slots can survive a -failover scenario. Failovers are normally implemented using physical -streaming replication, like in the case of {{name.ln}}. - -You can enable `pg_failover_slots` by adding to the configuration a parameter -that starts with `pg_failover_slots.`: as explained above, the operator will -transparently manage the `pg_failover_slots` entry in the -`shared_preload_libraries` option depending on this. - -Please refer to [`the `pg_failover_slots` documentation`](/pg_extensions/pg_failover_slots) -for details on this extension. - -Additionally, for each database that you intend to you use with `pg_failover_slots` -you need to add an entry in the `pg_hba` section that enables each replica to -connect to the primary. -For example, suppose that you want to use the `app` database with `pg_failover_slots`, -you need to add this entry in the `pg_hba` section: - -```yaml - postgresql: - pg_hba: - - hostssl app streaming_replica all cert -``` - -## The `pg_hba` section - -`pg_hba` is a list of PostgreSQL Host Based Authentication rules -used to create the `pg_hba.conf` used by the pods. - -!!!info Important -See the PostgreSQL documentation for -[more information on `pg_hba.conf`](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). -!!! - -Since the first matching rule is used for authentication, the `pg_hba.conf` file -generated by the operator can be seen as composed of four sections: - -1. Fixed rules -2. User-defined rules -3. Optional LDAP section -4. Default rules - -Fixed rules: - -```text -local all all peer - -hostssl postgres streaming_replica all cert map=cnp_streaming_replica -hostssl replication streaming_replica all cert map=cnp_streaming_replica -hostssl all cnp_pooler_pgbouncer all cert map=cnp_pooler_pgbouncer -``` - -Default rules: - -```text -host all all all -``` - -From PostgreSQL 14 the default value of the `password_encryption` -database parameter is set to `scram-sha-256`. Because of that, -the default authentication method is `scram-sha-256` from this -PostgreSQL version. - -PostgreSQL 13 and older will use `md5` as the default authentication -method. - -The resulting `pg_hba.conf` will look like this: - -```text -local all all peer - -hostssl postgres streaming_replica all cert map=cnp_streaming_replica -hostssl replication streaming_replica all cert map=cnp_streaming_replica -hostssl all cnp_pooler_pgbouncer all cert map=cnp_pooler_pgbouncer - - - - -host all all all scram-sha-256 # (or md5 for PostgreSQL version <= 13) -``` - -Inside the cluster manifest, `pg_hba` lines are added as list items -in `.spec.postgresql.pg_hba`, as in the following excerpt: - -```yaml - postgresql: - pg_hba: - - hostssl app app 10.244.0.0/16 md5 -``` - -In the above example we are enabling access for the `app` user to the `app` -database using MD5 password authentication (you can use `scram-sha-256` -if you prefer) via a secure channel (`hostssl`). - -### Dynamic address resolution with `podSelectorRefs` - -In Kubernetes, pod IPs are ephemeral. Manually updating `pg_hba` rules every -time a client pod restarts is unsustainable. The `.spec.podSelectorRefs` option -automates this by allowing you to define **named label selectors** that the -operator resolves into up-to-date IP addresses. - -#### How it Works - -1. **Define Selectors:** Map a friendly name to a standard Kubernetes - `labelSelector` for pods. -2. **Reference Selectors:** Use the `${podselector:NAME}` placeholder in your - `pg_hba` rules. -3. **Automatic Expansion:** The operator resolves matching pod IPs and the - instance manager expands each reference into individual CIDR entries - (`/32` for IPv4, `/128` for IPv6) within `pg_hba.conf`. - -#### Configuration Example - -The following snippet defines selectors for application and monitoring pods, -then applies them to the PostgreSQL access rules: - -```yaml -podSelectorRefs: - - name: app-pods - selector: - matchLabels: - app: myapp - - name: monitoring - selector: - matchLabels: - role: monitoring -postgresql: - pg_hba: - - "hostssl mydb myuser ${podselector:app-pods} scram-sha-256" - - "hostssl postgres monitor ${podselector:monitoring} scram-sha-256" -``` - -#### IP Expansion Mapping - -If the operator detects pods with IPs `10.0.0.5`, `10.0.0.12` (App), and -`10.0.1.3` (Monitoring), the instance manager transforms the template as -follows: - -```text -# Expanded from: hostssl mydb myuser ${podselector:app-pods} scram-sha-256 -hostssl mydb myuser 10.0.0.5/32 scram-sha-256 -hostssl mydb myuser 10.0.0.12/32 scram-sha-256 -# Expanded from: hostssl postgres monitor ${podselector:monitoring} scram-sha-256 -hostssl postgres monitor 10.0.1.3/32 scram-sha-256 -``` - -#### Key Constraints & Behavior - -- **Scope:** Selectors are restricted to the **same namespace** as the Cluster - for security. Cross-namespace lookups are not supported. -- **Placement:** The `${podselector:NAME}` syntax is valid **only in the - address field** of host-type entries (`host`, `hostssl`, `hostnossl`, - `hostgssenc`, `hostnogssenc`). -- **Reactivity:** The operator watches for pod lifecycle events (creation, - deletion, or IP updates). Updates trigger an automatic configuration - regeneration and a PostgreSQL `reload`. -- **Validation:** Selector names must follow the pattern - `^[a-z]([a-z0-9_-]*[a-z0-9])?$` and each `${podselector:NAME}` reference - in a `pg_hba` rule must correspond to a defined entry in `podSelectorRefs`. - The webhook validates both constraints. - -!!!warning - -When a selector matches zero pods, the corresponding `pg_hba` lines referencing -it are omitted from `pg_hba.conf`. Ensure that your default rules provide -appropriate fallback access. -!!! - -For a complete example, see -[`cluster-example-pod-selector-refs.yaml`](../samples/cluster-example-pod-selector-refs.yaml). - -### LDAP Configuration - -Under the `postgres` section of the cluster spec there is an optional `ldap` section available to define an LDAP -configuration to be converted into a rule added into the `pg_hba.conf` file. - -This will support two modes: `simple bind` mode which requires specifying a `server`, `prefix` and `suffix` in the LDAP -section and the `search+bind` mode which requires specifying `server`, `baseDN`, `binDN`, and a `bindPassword` which is -a secret containing the ldap password. Additionally, in `search+bind` mode you have the option to specify a -`searchFilter` or `searchAttribute`. If no `searchAttribute` is specified the default one of `uid` will be used. - -Additionally, both modes allow the specification of a `scheme` for ldapscheme and a `port`. Neither scheme nor port are -required, however. - -This section filled out for search+bind could look as follows: - -```yaml -postgresql: - ldap: - server: 'openldap.default.svc.cluster.local' - bindSearchAuth: - baseDN: 'ou=org,dc=example,dc=com' - bindDN: 'cn=admin,dc=example,dc=com' - bindPassword: - name: 'ldapBindPassword' - key: 'data' - searchAttribute: 'uid' -``` - -## The `pg_ident` section - -`pg_ident` is a list of PostgreSQL User Name Maps that {{name.ln}} uses to -generate and maintain the ident map file (known as `pg_ident.conf`) inside the -data directory. - -!!!info Important -See the PostgreSQL documentation for -[more information on `pg_ident.conf`](https://www.postgresql.org/docs/current/auth-username-maps.html). -!!! - -The `pg_ident.conf` file written by the operator is made up of the following -two sections: - -1. Fixed rules -2. User-defined rules - -Currently the only fixed rule, automatically generated by the operator, is: - -```text -local postgres -``` - -The instance manager detects the user running the PostgreSQL instance and -automatically adds a rule to map it to the `postgres` user in the database. - -If the `postgres` user is not properly configured inside the container, the -instance manager will allow any local user to connect and then log a warning -message like the following: - -```text -Unable to identify the current user. Falling back to insecure mapping. -``` - -The resulting `pg_ident.conf` will look like this: - -```text -local postgres - - -``` - -Inside the cluster manifest, `pg_ident` lines are added as list items -in `.spec.postgresql.pg_ident`. -For example: - -```yaml - postgresql: - pg_ident: - - "mymap /^(.*)@mydomain\\.com$ \\1" -``` - -## Changing configuration - -You can apply configuration changes by editing the `postgresql` section of -the `Cluster` resource. - -After the change, the cluster instances will immediately reload the -configuration to apply the changes. -If the change involves a parameter requiring a restart, the operator will -perform a rolling upgrade. - -## Enabling `ALTER SYSTEM` - -{{name.ln}} strongly advocates employing the Cluster manifest as the -exclusive method for altering the configuration of a PostgreSQL cluster. This -approach guarantees coherence across the entire high-availability cluster and -aligns with best practices for Infrastructure-as-Code. - -In {{name.ln}} the default configuration disables the use of `ALTER SYSTEM` -on new Postgres clusters. This decision is rooted in the recognition of -potential risks associated with this command. To enable the use of `ALTER SYSTEM`, -you can explicitly set `.spec.postgresql.enableAlterSystem` to `true`. - -!!!warning -Proceed with caution when utilizing `ALTER SYSTEM`. This command operates -directly on the connected instance and does not undergo replication. -{{name.ln}} assumes responsibility for certain fixed parameters and complete -control over others, emphasizing the need for careful consideration. -!!! - -Starting from PostgreSQL 17, the `.spec.postgresql.enableAlterSystem` setting -directly controls the [`allow_alter_system` GUC in PostgreSQL](https://www.postgresql.org/docs/17/runtime-config-compatible.html#GUC-ALLOW-ALTER-SYSTEM) -— a feature directly contributed by {{name.ln}} to PostgreSQL. - -Prior to PostgreSQL 17, when `.spec.postgresql.enableAlterSystem` is set to -`false`, the `postgresql.auto.conf` file is made read-only. Consequently, any -attempt to execute the `ALTER SYSTEM` command will result in an error. The -error message might look like this: - -```output -ERROR: could not open file "postgresql.auto.conf": Permission denied -``` - -## Dynamic Shared Memory settings - -PostgreSQL supports a few implementations for dynamic shared memory -management through the -[`dynamic_shared_memory_type`](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-DYNAMIC-SHARED-MEMORY-TYPE) -configuration option. In {{name.ln}} we recommend to limit ourselves to -any of the following two values: - -- `posix`: which relies on POSIX shared memory allocated using `shm_open` (default setting) -- `sysv`: which is based on System V shared memory allocated via `shmget` - -In PostgreSQL, this setting is particularly important for memory allocation in parallel queries. -For details, please refer to this -[thread from the `pgsql-general` mailing list](https://www.postgresql.org/message-id/CA%2BhUKGJOj7qzDLxeFPVvto8YEWop6FSQoTYPO9Z6Ee%3Di-nPS_Q%40mail.gmail.com). - -### POSIX shared memory - -The default setting of `posix` should be enough in most cases, considering that -the operator automatically mounts a *memory-bound `EmptyDir` volume* called `shm` -under `/dev/shm`. You can verify the size of such volume inside the running -Postgres container with: - -```sh -mount | grep shm -``` - -You should get something similar to the following output: - -```console -shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=******) -``` - -If you would like to set a maximum size for the `shm` volume, you can do so by -setting the `.spec.ephemeralVolumesSizeLimit.shm` field in the `Cluster` resource. -For example: - -```yaml -spec: - ephemeralVolumesSizeLimit: - shm: 1Gi -``` - -### System V shared memory - -In case your Kubernetes cluster has a high enough value for the `SHMMAX` -and `SHMALL` parameters, you can also set: - -```yaml -dynamic_shared_memory_type: "sysv" -``` - -You can check the `SHMMAX`/`SHMALL` from inside a PostgreSQL container, by running: - -```sh -ipcs -lm -``` - -For example: - -```console ------- Shared Memory Limits -------- -max number of segments = 4096 -max seg size (kbytes) = 18014398509465599 -max total shared memory (kbytes) = 18014398509481980 -min seg size (bytes) = 1 -``` - -As you can see, the very high number of `max total shared memory` recommends -setting `dynamic_shared_memory_type` to `sysv`. - -An alternate method is to run: - -```sh -cat /proc/sys/kernel/shmall -cat /proc/sys/kernel/shmmax -``` - -## Fixed parameters - -Some PostgreSQL configuration parameters should be managed exclusively by the -operator. The operator prevents the user from setting them using a webhook. - -Users are not allowed to set the following configuration parameters in the -`postgresql` section: - -- `allow_alter_system` -- `allow_system_table_mods` -- `archive_cleanup_command` -- `archive_command` -- `archive_mode` -- `bonjour` -- `bonjour_name` -- `cluster_name` -- `config_file` -- `data_directory` -- `data_sync_retry` -- `edb_audit` -- `edb_audit_destination` -- `edb_audit_directory` -- `edb_audit_filename` -- `edb_audit_rotation_day` -- `edb_audit_rotation_seconds` -- `edb_audit_rotation_size` -- `edb_audit_tag` -- `edb_log_every_bulk_value` -- `event_source` -- `external_pid_file` -- `hba_file` -- `hot_standby` -- `ident_file` -- `jit_provider` -- `listen_addresses` -- `log_destination` -- `log_directory` -- `log_file_mode` -- `log_filename` -- `log_rotation_age` -- `log_rotation_size` -- `log_truncate_on_rotation` -- `logging_collector` -- `port` -- `primary_conninfo` -- `primary_slot_name` -- `promote_trigger_file` -- `recovery_end_command` -- `recovery_min_apply_delay` -- `recovery_target` -- `recovery_target_action` -- `recovery_target_inclusive` -- `recovery_target_lsn` -- `recovery_target_name` -- `recovery_target_time` -- `recovery_target_timeline` -- `recovery_target_xid` -- `restart_after_crash` -- `restore_command` -- `shared_preload_libraries` -- `ssl` -- `ssl_ca_file` -- `ssl_cert_file` -- `ssl_crl_file` -- `ssl_dh_params_file` -- `ssl_ecdh_curve` -- `ssl_key_file` -- `ssl_passphrase_command` -- `ssl_passphrase_command_supports_reload` -- `ssl_prefer_server_ciphers` -- `stats_temp_directory` -- `synchronous_standby_names` -- `syslog_facility` -- `syslog_ident` -- `syslog_sequence_numbers` -- `syslog_split_messages` -- `unix_socket_directories` -- `unix_socket_group` -- `unix_socket_permissions` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/preview_version.mdx b/product_docs/docs/postgres_for_kubernetes/preview/preview_version.mdx deleted file mode 100644 index b4311abc970..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/preview_version.mdx +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: 'Preview Versions' -originalFilePath: 'src/preview_version.md' ---- - - - -{{name.ln}} candidate releases are pre-release versions made available for -testing before the community issues a new generally available (GA) release. -These versions are feature-frozen, meaning no new features are added, and are -intended for public testing prior to the final release. - -!!!warning Important -{{name.ln}} release candidates are **not intended for use in production** systems. -They should only be deployed in staging or dedicated testing environments. -!!! - -## Current Preview Version - -The current preview version is **1.30.0-rc1**. - -For more information on the current preview version and how to test, please view the links below: - -- [Announcement](/postgres_for_kubernetes/preview/rel_notes/1_30_0-rc1_rel_notes) -- [Documentation](/postgres_for_kubernetes/preview/) - -## Purpose of Release Candidates - -Release candidates are provided to the community for extensive testing before -the official release. While a release candidate aims to be identical to the -initial release of a new minor version of {{name.ln}}, additional changes may -be implemented before the GA release. - -### Mitigating Critical Issues - -The primary purpose of an RC is to catch serious defects and regressions that our -automated testing and internal manual checks might miss. **Specifically, community testing -is invaluable for validating real-world scenarios, such as:** - -- **Upgrade Paths:** Testing the process of upgrading an existing {{name.ln}} - cluster from the previous stable minor version to the RC version. This often - uncovers critical compatibility or migration issues, like those that affect PVC - ownership, which can only be reliably tested with diverse existing user setups. -- **Unique Configurations:** Validating compatibility with specific Kubernetes - versions, storage providers, networking setups, or custom PostgreSQL - extensions not covered by our standard test matrix. -- **Real-world Workloads:** Running the RC with your actual application - workload and traffic patterns to expose performance regressions or race - conditions. - -## Community Involvement: How to Help - -The stability of each {{name.ln}} minor release significantly depends on the -community's efforts to test the upcoming version with their workloads and -tools. Identifying bugs and regressions through user testing is crucial in -determining when we can finalize the release. - -### Your Call to Action - -If a Release Candidate is available, we encourage you to perform the following tests in a -non-production environment: - -- **New Deployment Test:** Deploy a new {{name.ln}} cluster using the RC version. -- **Upgrade Test (Crucial):** **Upgrade an existing cluster** (from the - preceding stable minor version) to the RC version, and verify all key - operational aspects (scaling, failover, backup/restore) function correctly. -- **Basic Operations:** Verify key features like rolling update, - backup/restore, instance failover, and connection pooling function as - expected. -- **Report Issues:** **Immediately report any issues or unexpected behavior** - by opening a GitHub issue and clearly marking it with a **`Release - Candidate`** tag or label, along with the RC version number - (e.g., `1.29.0-rc1`). - -## Usage Advisory - -The {{name.ln}} Community strongly advises against using preview versions of -{{name.ln}} in production environments or active development projects. Although -{{name.ln}} undergoes extensive automated and manual testing, beta releases -may contain serious bugs. Features in preview versions may change in ways that -are not backwards compatible and could be removed entirely. - -**By testing the Release Candidate, you are helping to prevent a potentially -critical bug from affecting the entire community upon the GA release.** diff --git a/product_docs/docs/postgres_for_kubernetes/preview/private_edb_registries.mdx b/product_docs/docs/postgres_for_kubernetes/preview/private_edb_registries.mdx deleted file mode 100644 index e052bfb38ac..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/private_edb_registries.mdx +++ /dev/null @@ -1,156 +0,0 @@ ---- -title: 'EDB private container registry' -originalFilePath: 'src/private_edb_registries.md' ---- - -The images for the *{{name.ln}}* operator, as well as various -operands, are kept in a private container image registry under -`docker.enterprisedb.com`. - -!!!info Important - -Access to the private registry requires an account with EDB and is -reserved to EDB customers with a valid [subscription plan](https://www.enterprisedb.com/products/plans-comparison#selfmanagedenterpriseplan). -Credentials will be funneled through your EDB account. -!!! - -!!!info Important - -There is a bandwidth quota of 10GB/month per registry. -!!! - -!!!note - -When installing the operator and operands from the private registry, the -[license keys](license_keys.md) are not needed. -!!! - -## Repository information - - - -Collect the following information: - -1. Your [EDB account token](/repos/getting_started/get_your_token/) -1. The name of the repository, which will be `k8s` -1. The repository server, which will be `docker.enterprisedb.com` - -For clarity, the following examples assume your token is in an environment variable named `EDB_SUBSCRIPTION_TOKEN`. - -### Example with `docker login` - -You can log in via Docker from your terminal. In this context, - -- The server is `docker.enterprisedb.com` -- The username is the repository, `k8s` -- The password is your EDB account token (stored in `$EDB_SUBSCRIPTION_TOKEN`) - -```sh -docker login docker.enterprisedb.com \ - --username k8s \ - --password "$EDB_SUBSCRIPTION_TOKEN" -__OUTPUT__ -WARNING! Using --password via the CLI is insecure. Use --password-stdin. -Login Succeeded -``` - -## Operand images - -{{name.ln}} supports various PostgreSQL distributions that have -images available from the same private registry: - -- Community PostgreSQL -- EDB Postgres Advanced (EPAS) -- EDB Postgres Extended (PGE) - -These images follow the requirements and the conventions described in the -["Container image requirements"](container_images.md) -page of the {{name.ln}} documentation. - -In the table below you can find the image name prefix for each Postgres distribution: - -| Postgres distribution | Image name | -| ---------------------------- | ----------------------- | -| Community PostgreSQL | `postgresql` | -| EDB Postgres Extended (PGE) | `edb-postgres-extended` | -| EDB Postgres Advanced (EPAS) | `edb-postgres-advanced` | - -## How to deploy clusters with EPAS or PGE operands - -If you have already installed the {{name.ln}} operator from the -private registry, you must have already set up an image pull secret. If you -haven't, the next section may be of interest to you. - -If you have an existing installation of the operator, in order to pull images -for EPAS or PGE from the private registry, you will need to create a -[`kubernetes.io/dockerconfigjson` pull secret](https://kubernetes.io/docs/concepts/configuration/secret/#secret-types). - -You can -[create a pull secret from credentials](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-secret-by-providing-credentials-on-the-command-line). - -```sh -kubectl create secret docker-registry registry-pullsecret \ - -n --docker-server=docker.enterprisedb.com \ - --docker-username=k8s \ - --docker-password="$EDB_SUBSCRIPTION_TOKEN" -``` - -As mentioned above, the `docker-username` is the name of your registry, i.e. -`k8s`. The `docker-password` is the token retrieved -from the [EDB portal](/repos/getting_started/get_your_token/). - -Once your pull secret is created, remember to set the `imagePullSecrets` field -in the cluster manifest in addition to the `imageName`. -The manifest below will create a cluster running PG Extended. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-extended-cluster -spec: - instances: 3 - imageName: docker.enterprisedb.com/k8s/edb-postgres-extended:18.1-standard-ubi9 - imagePullSecrets: - - name: registry-pullsecret - - storage: - storageClass: standard - size: 1Gi -``` - -## How to install the operator using the EDB private registry - -As mentioned above, the *username* for docker is the name of your repository, -and the token is the *password*. -The same credentials can be used for kubernetes to access the registry by -setting up a [`kubernetes.io/dockerconfigjson` pull secret](https://kubernetes.io/docs/concepts/configuration/secret/#secret-types). - -As mentioned in the [installation document](installation_upgrade.md), there -are several different ways to install the operator. - -If you are going to install using images from the private registry, you will -need to create a pull secret, as we have mentioned, and also customize the -`OPERATOR_IMAGE_NAME` parameter in the deployment manifest. - -We suggest to use the Helm chart for installation, which will take care of -creating the pull secret and customizing the operator image repository -for you. - -You can find more information in the [Helm chart](https://github.com/EnterpriseDB/edb-postgres-for-kubernetes-charts) page. - -As an example, the following command (provided the token) will install the {{name.abbr}} -operator when using the repository from the EDB EnterpriseDB Plan: - -```sh -helm upgrade --install edb-pg4k \ - --namespace postgresql-operator-system \ - --create-namespace \ - --set image.repository=docker.enterprisedb.com/k8s/edb-postgres-for-cloudnativepg \ - --set image.imageCredentials.username=k8s \ - --set image.imageCredentials.password="$EDB_SUBSCRIPTION_TOKEN" \ - --set image.imageCredentials.create=true \ - --set "imagePullSecrets[0].name"=postgresql-operator-pull-secret \ - --set config.data.PULL_SECRET_NAME=postgresql-operator-pull-secret \ - edb/edb-postgres-for-kubernetes -``` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/quickstart.mdx b/product_docs/docs/postgres_for_kubernetes/preview/quickstart.mdx deleted file mode 100644 index 10e0e7de161..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/quickstart.mdx +++ /dev/null @@ -1,400 +0,0 @@ ---- -title: 'Quickstart' -originalFilePath: 'src/quickstart.md' ---- - -This section guides you through testing a PostgreSQL cluster on your local machine by -deploying {{name.ln}} on a local Kubernetes cluster -using either [Kind](https://kind.sigs.k8s.io/) or -[Minikube](https://kubernetes.io/docs/setup/learning-environment/minikube/). - -Red Hat OpenShift Container Platform users can test the certified operator for -{{name.ln}} on the [Red Hat OpenShift Local](https://developers.redhat.com/products/openshift-local/overview) (formerly Red Hat CodeReady Containers). - -!!!warning -The instructions contained in this section are for demonstration, -testing, and practice purposes only and must not be used in production. -!!! - -Like any other Kubernetes application, {{name.ln}} is deployed using -regular manifests written in YAML. - -By following these instructions you should be able to start a PostgreSQL -cluster on your local Kubernetes/Openshift installation and experiment with it. - -!!!info Important -Make sure that you have `kubectl` installed on your machine in order -to connect to the Kubernetes cluster, or `oc` if using OpenShift Local. -Please follow the Kubernetes documentation on [how to install `kubectl`](https://kubernetes.io/docs/tasks/tools/install-kubectl/) -or the Openshift documentation on [how to install `oc`](https://docs.openshift.com/container-platform/4.6/cli_reference/openshift_cli/getting-started-cli.html). -!!! - -!!!note -If you are running Openshift, use `oc` every time `kubectl` is mentioned -in this documentation. `kubectl` commands are compatible with `oc` ones. -!!! - -## Part 1 - Setup the local Kubernetes/Openshift Local playground - -The first part is about installing Minikube, Kind, or OpenShift Local. Please spend some time reading about the systems and decide which one to proceed with. -After setting up one of them, please proceed with part 2. - -We also provide instructions for setting up monitoring with Prometheus and -Grafana for local testing/evaluation, in [part 4](#part-4-monitor-clusters-with-prometheus-and-grafana) - -### Minikube - -Minikube is a tool that makes it easy to run Kubernetes locally. Minikube runs a -single-node Kubernetes cluster inside a Virtual Machine (VM) on your laptop for -users looking to try out Kubernetes or develop with it day-to-day. Normally, it -is used in conjunction with VirtualBox. - -You can find more information in the official [Kubernetes documentation on how to -install Minikube](https://kubernetes.io/docs/tasks/tools/install-minikube) in your local personal environment. -When you installed it, run the following command to create a minikube cluster: - -```sh -minikube start -``` - -This will create the Kubernetes cluster, and you will be ready to use it. -Verify that it works with the following command: - -```sh -kubectl get nodes -``` - -You will see one node called `minikube`. - -### Kind - -If you do not want to use a virtual machine hypervisor, then Kind is a tool for running -local Kubernetes clusters using Docker container "nodes" (Kind stands for "Kubernetes IN Docker" indeed). - -Install `kind` on your environment following the instructions in the [Quickstart](https://kind.sigs.k8s.io/docs/user/quick-start), -then create a Kubernetes cluster with: - -```sh -kind create cluster --name pg -``` - -### OpenShift Local (formerly CodeReady Containers (CRC)) - -1. [Download OpenShift Local](https://developers.redhat.com/products/openshift-local/overview) - and move the binary inside a directory in your `PATH`. - -2. Run the following commands: - - ``` - crc setup - crc start - ``` - - The `crc start` output will explain how to proceed. - - - -3. Execute the output of the `crc oc-env` command. - -4. Log in as `kubeadmin` with the printed `oc login` - command. You can also open the web console running `crc console`. - User and password are the same as for the `oc login` command. - -5. OpenShift Local doesn't come with a StorageClass, so one has to be configured. - Follow the [Dynamic volume provisioning wiki page](https://github.com/code-ready/crc/wiki/Dynamic-volume-provisioning) - and install `rancher/local-path-provisioner`. - -## Part 2: Install {{name.ln}} - -Now that you have a Kubernetes installation up and running -on your laptop, you can proceed with {{name.ln}} installation. - -Unless specified in a cluster configuration file, {{name.ln}} will currently deploy Community Postgresql operands by default. See the section [Deploying EDB Postgres servers](#deploying-edb-postgres-servers) for more information. - -Refer to the ["Installation"](installation_upgrade.md) section and then proceed -with the deployment of a PostgreSQL cluster. - -## Part 3: Deploy a PostgreSQL cluster - -Unless specified in a cluster configuration file, {{name.ln}} will currently deploy Community Postgresql operands by default. See the section [Deploying EDB Postgres servers](#deploying-edb-postgres-servers) for more information. - -As with any other deployment in Kubernetes, to deploy a PostgreSQL cluster -you need to apply a configuration file that defines your desired `Cluster`. - -The [`cluster-example.yaml`](../samples/cluster-example.yaml) sample file -defines a simple `Cluster` using the default storage class to allocate -disk space: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - - storage: - size: 1Gi -``` - -!!!note There's more -For more detailed information about the available options, please refer -to the ["API Reference" section](pg4k.v1.md). -!!! - -In order to create the 3-node Community PostgreSQL cluster, you need to run the following command: - -```sh -kubectl apply -f cluster-example.yaml -``` - -You can check that the pods are being created with the `get pods` command: - -```sh -kubectl get pods -``` - -That will look for pods in the default namespace. To separate your cluster -from other workloads on your Kubernetes installation, you could always create -a new namespace to deploy clusters on. -Alternatively, you can use labels. The operator will apply the `k8s.enterprisedb.io/cluster` -label on all objects relevant to a particular cluster. For example: - -```sh -kubectl get pods -l k8s.enterprisedb.io/cluster= -``` - -!!!info Important -Note that we are using `k8s.enterprisedb.io/cluster` as the label. In the past you may -have seen or used `postgresql`. This label is being deprecated, and -will be dropped in the future. Please use `k8s.enterprisedb.io/cluster`. -!!! - -### Deploying EDB Postgres servers - -By default, the operator will install the latest available minor version -of the latest major version of Community PostgreSQL when the operator was released. -You can override this by setting the `imageName` key in the `spec` section of -the `Cluster` definition. For example, to install EDB Postgres Advanced 18.1 you can use: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - # [...] -spec: - # [...] - imageName: docker.enterprisedb.com/k8s/edb-postgres-advanced:18.1-standard-ubi9 - #[...] -``` - -And to install EDB Postgres Extended 18 you can use: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - # [...] -spec: - # [...] - imageName: docker.enterprisedb.com/k8s/edb-postgres-extended:18-standard-ubi9 - #[...] -``` - -!!!info Important -The immutable infrastructure paradigm requires that you always -point to a specific version of the container image. -Never use tags like `latest` or `13` in a production environment -as it might lead to unpredictable scenarios in terms of update -policies and version consistency in the cluster. -For strict deterministic and repeatable deployments, you can add the digests -to the image name, through the `:@sha256:` format. -!!! - -!!!note There's more -There are some examples cluster configurations bundled with the operator. -Please refer to the ["Examples" section](samples.md). -!!! - -## Part 4: Monitor clusters with Prometheus and Grafana - -!!!info Important -Installing Prometheus and Grafana is beyond the scope of this project. -The instructions in this section are provided for experimentation and -illustration only. -!!! - -In this section we show how to deploy Prometheus and Grafana for observability, -and how to create a Grafana Dashboard to monitor {{name.ln}} clusters, and a -set of Prometheus Rules defining alert conditions. - -We leverage the [Kube-Prometheus stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack) -Helm chart, which is maintained by the [Prometheus Community](https://github.com/prometheus-community). -Please refer to the project website for additional documentation and background. - -The Kube-Prometheus-stack Helm chart installs the [Prometheus Operator](https://prometheus-operator.dev), -including the [Alert Manager](https://prometheus.io/docs/alerting/latest/alertmanager/), -and a [Grafana](https://grafana.com) deployment. - -We include a configuration file for the deployment of this Helm chart that will -provide useful initial settings for observability of {{name.ln}} clusters. - -### Installation - -If you don't have [Helm](https://helm.sh) installed yet, please follow the -[instructions](https://helm.sh/docs/intro/quickstart/) to install it in your -system. - -We need to add the `prometheus-community` helm chart repository, and then -install the *Kube Prometheus stack* with our sample configuration -[`kube-stack-config.yaml`](.././samples/monitoring/kube-stack-config.yaml). - -We can accomplish this with the following commands: - -```sh -helm repo add prometheus-community \ - https://prometheus-community.github.io/helm-charts - -helm upgrade --install \ - -f https://raw.githubusercontent.com/EnterpriseDB/docs/main/product_docs/docs/postgres_for_kubernetes/1/samples/monitoring/kube-stack-config.yaml \ - prometheus-community \ - prometheus-community/kube-prometheus-stack -``` - -After completion, you will have Prometheus, Grafana, and Alert Manager, -configured with the `kube-stack-config.yaml` file: - -- From the Prometheus installation, you will have the Prometheus Operator - watching for **any** `PodMonitor` (see [*monitoring*](monitoring.md)). -- Alert Manager and Grafana are both enabled. - -!!!note Seealso -For further information about the above helm commands, refer to the [helm -install](https://helm.sh/docs/helm/helm_install/) -documentation. -!!! - -You can see several Custom Resources have been created: - -```sh -% kubectl get crds -NAME CREATED AT -… -alertmanagers.monitoring.coreos.com -… -prometheuses.monitoring.coreos.com -prometheusrules.monitoring.coreos.com -… -``` - -as well as a series of Services: - -```sh -% kubectl get svc -NAME TYPE PORT(S) -… … … -prometheus-community-grafana ClusterIP 80/TCP -prometheus-community-kube-alertmanager ClusterIP 9093/TCP -prometheus-community-kube-operator ClusterIP 443/TCP -prometheus-community-kube-prometheus ClusterIP 9090/TCP -``` - -### Viewing with Prometheus - -At this point, a {{name.ln}} cluster deployed with monitoring activated -would be observable via Prometheus. - -For example, you could deploy a simple cluster with `PodMonitor` enabled: - -```sh -kubectl apply -f - < New > Import). -You can now click on the `{{name.ln}}` dashboard just created: - -![local grafana](images/grafana-local.png) - -!!!warning -Some graphs in the previous dashboard make use of metrics that are in alpha stage by the time -this was created, like `kubelet_volume_stats_available_bytes` and `kubelet_volume_stats_capacity_bytes` -producing some graphs to show `No data`. -!!! - -Note that in our local setup, Prometheus and Grafana are configured to -automatically discover and monitor any {{name.ln}} clusters deployed with the -Monitoring feature enabled. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/recovery.mdx b/product_docs/docs/postgres_for_kubernetes/preview/recovery.mdx deleted file mode 100644 index c1f69c241ee..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/recovery.mdx +++ /dev/null @@ -1,637 +0,0 @@ ---- -title: 'Recovery' -originalFilePath: 'src/recovery.md' ---- - - - -In PostgreSQL, **recovery** refers to the process of starting an instance from -an existing physical backup. PostgreSQL's recovery system is robust and -feature-rich, supporting **Point-In-Time Recovery (PITR)**—the ability to -restore a cluster to any specific moment, from the earliest available backup to -the latest archived WAL file. - -!!!info Important -A valid WAL archive is required to perform PITR. -!!! - -In {{name.ln}}, recovery is **not performed in-place** on an existing -cluster. Instead, it is used to **bootstrap a new cluster** from a physical -backup. - -!!!note -For more details on configuring the `bootstrap` stanza, refer to -[Bootstrap](bootstrap.md). -!!! - -The `recovery` bootstrap mode allows you to initialize a cluster from a -physical base backup and replay the associated WAL files to bring the system to -a consistent and optionally point-in-time state. - -{{name.ln}} supports recovery via: - -- A **pluggable backup and recovery interface (CNPG-I)**, enabling integration - with external tools such as the [Barman Cloud Plugin](https://cloudnative-pg.io/plugin-barman-cloud/). -- **Native recovery from volume snapshots**, where supported by the underlying - Kubernetes storage infrastructure. -- **Native recovery from object stores via Barman Cloud**, which is - **deprecated** as of version 1.26 in favor of the plugin-based approach. - -With the deprecation of native Barman Cloud support in version 1.26, this -section now focuses on two supported recovery methods: using the **Barman Cloud -Plugin** for recovery from object stores, and the **native interface** for -recovery from volume snapshots. - -!!!info Important -For legacy documentation, see -[Appendix B – Recovery from an Object Store](backup_barmanobjectstore.md#recovery-from-an-object-store). -!!! - -## Recovery from an Object Store with the Barman Cloud Plugin - -This section outlines how to recover a PostgreSQL cluster from an object store -using the recommended Barman Cloud Plugin. - -!!!info Important -The object store must contain backup data produced by a {{name.ln}} -`Cluster`—either using the **deprecated native Barman Cloud integration** or -the **Barman Cloud Plugin**. -!!! - -!!!info -For full details, refer to the -[“Recovery of a Postgres Cluster” section in the Barman Cloud Plugin documentation](https://cloudnative-pg.io/plugin-barman-cloud/docs/concepts/#recovery-of-a-postgres-cluster). -!!! - -Begin by defining the object store that holds both your base backups and WAL -files. The Barman Cloud Plugin uses a custom `ObjectStore` resource for this -purpose. The following example shows how to configure one for Azure Blob -Storage: - -```yaml -apiVersion: barmancloud.cnpg.io/v1 -kind: ObjectStore -metadata: - name: cluster-example-backup -spec: - configuration: - destinationPath: https://STORAGEACCOUNTNAME.blob.core.windows.net/CONTAINERNAME/ - azureCredentials: - storageAccount: - name: recovery-object-store-secret - key: storage_account_name - storageKey: - name: recovery-object-store-secret - key: storage_account_key - wal: - maxParallel: 8 -``` - -Next, configure the `Cluster` resource to use the `ObjectStore` you defined. In -the `bootstrap` section, specify the recovery source, and define an -`externalCluster` entry that references the plugin: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - [...] - - superuserSecret: - name: superuser-secret - - bootstrap: - recovery: - source: origin - - externalClusters: - - name: origin - plugin: - name: barman-cloud.cloudnative-pg.io - parameters: - barmanObjectName: cluster-example-backup - serverName: cluster-example -``` - -## Recovery from `VolumeSnapshot` Objects - -!!!warning -When creating replicas after recovering a primary instance from a -`VolumeSnapshot`, the operator may fall back to using `pg_basebackup` to -synchronize them. This process can be significantly slower—especially for large -databases—because it involves a full base backup. This limitation will be -addressed in the future with support for online backups and PVC cloning in -the scale-up process. -!!! - -{{name.ln}} allows you to create a new cluster from a `VolumeSnapshot` of a -`PersistentVolumeClaim` (PVC) that belongs to an existing `Cluster`. -These snapshots are created using the declarative API for -[volume snapshot backups](backup_volumesnapshot.md). - -To complete the recovery process, the new cluster must also reference an -external cluster that provides access to the WAL archive needed to reapply -changes and finalize the recovery. - -The following example shows a cluster being recovered using both a -`VolumeSnapshot` for the base backup and a WAL archive accessed through the -Barman Cloud Plugin: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - [...] - - bootstrap: - recovery: - source: origin - volumeSnapshots: - storage: - name: - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - - externalClusters: - - name: origin - plugin: - name: barman-cloud.cloudnative-pg.io - parameters: - barmanObjectName: cluster-example-backup - serverName: cluster-example -``` - -In case the backed-up cluster was using a separate PVC to store the WAL files, -the recovery must include that too: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - [...] - - bootstrap: - recovery: - volumeSnapshots: - storage: - name: - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - - walStorage: - name: - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io -``` - -The previous example assumes that the application database and its owning user -are named `app` by default. If the PostgreSQL cluster being restored uses -different names, you must specify these names before exiting the recovery phase, -as documented in ["Configure the application database"](#configure-the-application-database). - -!!!warning -If bootstrapping a replica-mode cluster from snapshots, to leverage -snapshots for the standby instances and not just the primary, -we recommend that you: - -1. Start with a single instance replica cluster. The primary instance will - be recovered using the snapshot, and available WALs from the source cluster. -2. Take a snapshot of the primary in the replica cluster. -3. Increase the number of instances in the replica cluster as desired. -!!! - -## Recovery from a `Backup` object - -If a `Backup` resource is already available in the namespace in which you need -to create the cluster, you can specify the name using -`.spec.bootstrap.recovery.backup.name`, as in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb -spec: - instances: 3 - - bootstrap: - recovery: - backup: - name: backup-example - - storage: - size: 1Gi -``` - -This bootstrap method allows you to specify just a reference to the -backup that needs to be restored. - -The previous example assumes that the application database and its owning user -are named `app` by default. If the PostgreSQL cluster being restored uses -different names, you must specify these names before exiting the recovery phase, -as documented in ["Configure the application database"](#configure-the-application-database). - -## Additional Considerations - -Whether you recover from an object store, a volume snapshot, or an existing -`Backup` resource, no changes to the database, including the catalog, are -permitted until the `Cluster` is fully promoted to primary and accepts write -operations. This restriction includes any role overrides, which are deferred -until the `Cluster` transitions to primary. -As a result, the following considerations apply: - -- The application database name and user are copied from the backup being - restored. The operator does not currently back up the underlying secrets, as - this is part of the usual maintenance activity of the Kubernetes cluster. -- To preserve the original postgres user password, configure - `enableSuperuserAccess` and supply a `superuserSecret`. - -By default, recovery continues up to the latest available WAL on the default -target timeline (`latest`). You can optionally specify a `recoveryTarget` to -perform a point-in-time recovery (see [Point in Time Recovery (PITR)](#point-in-time-recovery-pitr)). - -!!!info Important -Consider using the `barmanObjectStore.wal.maxParallel` option to speed -up WAL fetching from the archive by concurrently downloading the transaction -logs from the recovery object store. -!!! - -## Point in time recovery (PITR) - -Instead of replaying all the WALs up to the latest one, after extracting a base -backup, you can ask PostgreSQL to stop replaying WALs at any given point in -time. PostgreSQL uses this technique to achieve PITR. The presence of a WAL -archive is mandatory. - -!!!info Important -PITR requires you to specify a recovery target by using the options -described in [Recovery targets](#recovery-targets). -!!! - -The operator generates the configuration parameters required for this -feature to work if you specify a recovery target. - -### PITR from an object store - -This example uses the same recovery object store in Azure defined earlier for -the Barman Cloud plugin, containing both the base backups and the WAL archive. -The recovery target is based on a requested timestamp. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore-pitr -spec: - instances: 3 - - storage: - size: 5Gi - - bootstrap: - recovery: - # Recovery object store containing WAL archive and base backups - source: origin - recoveryTarget: - # Time base target for the recovery - targetTime: "2023-08-11 11:14:21.00000+02" - - externalClusters: - - name: origin - plugin: - name: barman-cloud.cloudnative-pg.io - parameters: - barmanObjectName: cluster-example-backup - serverName: cluster-example -``` - -In this example, you had to specify only the `targetTime` in the form of a -timestamp. You didn't have to specify the base backup from which to start the -recovery. - -The `backupID` option is the one that allows you to specify the base backup -from which to initiate the recovery process. By default, this value is -empty. - -If you assign a value to it (in the form of a Barman backup ID), the operator -uses that backup as the base for the recovery. - -!!!info Important -You need to make sure that such a backup exists and is accessible. -!!! - -If you don't specify the backup ID, the operator detects the base backup for -the recovery as follows: - -- When you use `targetTime` or `targetLSN`, the operator selects the closest - backup that was completed before that target. -- Otherwise, the operator selects the last available backup, in chronological - order. - -### Point-in-Time Recovery (PITR) from `VolumeSnapshot` Objects - -The following example demonstrates how to perform a **Point-in-Time Recovery (PITR)** using: - -- A Kubernetes `VolumeSnapshot` of the `PGDATA` directory, which provides the - base backup. This snapshot is specified in the `recovery.volumeSnapshots` - section and is named `test-snapshot-1`. -- A recovery object store (in this case, MinIO) containing the archived WAL - files. The object store is defined via a Barman Cloud Plugin `ObjectStore` - resource (not shown here), and referenced using the `recovery.source` field, - which points to an external cluster configuration. - -The cluster will be restored to a specific point in time using the -`recoveryTarget.targetTime` option. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-snapshot -spec: - # ... - bootstrap: - recovery: - source: origin - volumeSnapshots: - storage: - name: test-snapshot-1 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - recoveryTarget: - targetTime: "2023-07-06T08:00:39Z" - externalClusters: - - name: origin - plugin: - name: barman-cloud.cloudnative-pg.io - parameters: - barmanObjectName: minio-backup - serverName: cluster-example -``` - -This setup enables {{name.ln}} to restore the base data from a volume -snapshot and apply WAL segments from the object store to reach the desired -recovery target. - -!!!note -If the backed-up cluster had `walStorage` enabled, you also must specify -the volume snapshot containing the `PGWAL` directory, as mentioned in -[Recovery from VolumeSnapshot objects](#recovery-from-volumesnapshot-objects). -!!! - -!!!warning -It's your responsibility to ensure that the end time of the base backup in -the volume snapshot is before the recovery target timestamp. -!!! - -!!!warning -If you added or removed a [tablespace](tablespaces.md) in your cluster -since the last base backup, replaying the WAL will fail. You need a base -backup between the time of the tablespace change and the recovery target -timestamp. -!!! - -### Recovery targets - -Here are the recovery target criteria you can use: - -targetTime -: Time stamp up to which recovery proceeds, expressed in - [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) format, or as a - [timestamp](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-RECOVERY-TARGET-TIME). - (The precise stopping point is also influenced by the `exclusive` option.) - -!!!note -Timestamps without an explicit timezone suffix -(e.g., `2023-07-06 08:00:39`) are interpreted as UTC. -!!! - -!!!warning -Always specify an explicit timezone in your timestamp to avoid ambiguity. -For example, use `2023-07-06T08:00:39Z` or `2023-07-06T08:00:39+02:00` -instead of `2023-07-06 08:00:39`. -!!! - -!!!warning -PostgreSQL recovery will stop when it encounters the first transaction that -occurs after the specified time. If no such transaction exists after the -target time, the recovery process will fail. -!!! - -targetXID -: Transaction ID up to which recovery proceeds. - (The precise stopping point is also influenced by the `exclusive` option.) - Keep in mind that while transaction IDs are assigned sequentially at - transaction start, transactions can complete in a different numeric order. - The transactions that are recovered are those that committed before - (and optionally including) the specified one. - -targetName -: Named restore point (created with `pg_create_restore_point()`) to which - recovery proceeds. - -targetLSN -: LSN of the write-ahead log location up to which recovery proceeds. - (The precise stopping point is also influenced by the `exclusive` option.) - -targetImmediate -: Recovery ends as soon as a consistent state is reached, that is, as early - as possible. When restoring from an online backup, this means the point where - taking the backup ended. - -!!!info Important -The operator can retrieve the closest backup when you specify either -`targetTime` or `targetLSN`. However, this isn't possible for the remaining -targets: `targetName`, `targetXID`, and `targetImmediate`. In such cases, it's -mandatory to specify `backupID`. -!!! - -This example uses a `targetName`-based recovery target: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] - bootstrap: - recovery: - source: origin - recoveryTarget: - backupID: 20220616T142236 - targetName: 'restore_point_1' -[...] -``` - -You can choose only a single one among the targets in each `recoveryTarget` -configuration. - -Additionally, you can specify `targetTLI` to force recovery to a specific -timeline. - -By default, the previous parameters are considered to be inclusive, stopping -just after the recovery target, matching -[the behavior in PostgreSQL](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-RECOVERY-TARGET-INCLUSIVE). - -You can request exclusive behavior, stopping right before the recovery target, -by setting the `exclusive` parameter to `true`. The following example shows -this behavior, relying on a blob container in Azure for both base backups and -the WAL archive: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore-pitr -spec: - instances: 3 - - storage: - size: 5Gi - - bootstrap: - recovery: - source: origin - recoveryTarget: - backupID: 20220616T142236 - targetName: "maintenance-activity" - exclusive: true - - externalClusters: - - name: origin - plugin: - name: barman-cloud.cloudnative-pg.io - parameters: - barmanObjectName: cluster-example-backup - serverName: cluster-example -``` - -## Configure the application database - -For the recovered cluster, you can configure the application database name and -credentials with additional configuration. To update application database -credentials, you can generate your own passwords, store them as secrets, and -update the database to use the secrets. Or you can also let the operator -generate a secret with a randomly secure password for use. -See [Bootstrap an empty cluster](bootstrap.md#bootstrap-an-empty-cluster-initdb) -for more information about secrets. - -!!!info Important -While the `Cluster` is in recovery mode, no changes to the database, -including the catalog, are permitted. This restriction includes any role -overrides, which are deferred until the `Cluster` transitions to primary. -During this phase, users remain as defined in the source cluster. -!!! - -The following example configures the `app` database with the owner `app` and -the password stored in the provided secret `app-secret`, following the -bootstrap from a live cluster. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -[...] -spec: - bootstrap: - recovery: - database: app - owner: app - secret: - name: app-secret - [...] -``` - -With the above configuration, the following will happen only **after recovery is -completed**: - -1. If the `app` database does not exist, it will be created. -2. If the `app` user does not exist, it will be created. -3. If the `app` user is not the owner of the `app` database, ownership will be - granted to the `app` user. -4. If the `owner` value matches the `username` value in the secret, the - password for the application user (the `app` user in this case) will be - updated to the `password` value in the secret. - -## How recovery works under the hood - - - - - -You can use the data uploaded to the object storage to *bootstrap* a new -cluster from an existing backup. The operator orchestrates the recovery process -using the `barman-cloud-restore` tool (for the base backup) and the -`barman-cloud-wal-restore` tool (for WAL files, including parallel support, if -requested). - -For details and instructions on the `recovery` bootstrap method, see -[Bootstrap from a backup](bootstrap.md#bootstrap-from-a-backup-recovery). - -!!!info Important -If you're not familiar with how -[PostgreSQL PITR](https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-PITR-RECOVERY) -works, we suggest that you configure the recovery cluster as the original -one when it comes to `.spec.postgresql.parameters`. Once the new cluster is -restored, you can then change the settings as desired. -!!! - -The way it works is that the operator injects an init container in the first -instance of the new cluster, and the init container starts recovering the -backup from the object storage. - -!!!info Important -The duration of the base backup copy in the new PVC depends on -the size of the backup, as well as the speed of both the network and the -storage. -!!! - -When the base backup recovery process is complete, the operator starts the -Postgres instance in recovery mode. In this phase, PostgreSQL is up, though not -able to accept connections, and the pod is healthy according to the -liveness probe. By way of the `restore_command`, PostgreSQL starts fetching WAL -files from the archive. You can speed up this phase by setting the -`maxParallel` option and enabling the parallel WAL restore capability. - -This phase terminates when PostgreSQL reaches the target, either the end of the -WAL or the required target in case of PITR. You can optionally specify a -`recoveryTarget` to perform a PITR. If left unspecified, the recovery continues -up to the latest available WAL on the default target timeline (`latest`). - -Once the recovery is complete, the operator sets the required superuser -password into the instance. The new primary instance starts as usual, and the -remaining instances join the cluster as replicas. - -The process is transparent for the user and is managed by the instance manager -running in the pods. - -## Restoring into a Cluster with a Backup Section - -When restoring a cluster, the manifest may include a `plugins` section with -Barman Cloud plugin pointing to a *backup* object store resource. This enables -the newly created cluster to begin archiving WAL files and taking backups -immediately after recovery—provided backup policies are configured. - -Avoid reusing the same `ObjectStore` configuration for both *backup* and -*recovery* in the same cluster. If you must, ensure that each cluster uses a -unique `serverName` to prevent accidental overwrites of backup or WAL archive -data. - -!!!warning -{{name.ln}} includes a safety check to prevent a cluster from overwriting -existing data in a shared storage bucket. If a conflict is detected, the -cluster remains in the `Setting up primary` state, and the associated pods will -fail with an error. The pod logs will display: -`ERROR: WAL archive check failed for server recoveredCluster: Expected empty archive`. -!!! - -!!!info Important -You can bypass this safety check by setting the -`k8s.enterprisedb.io/skipEmptyWalArchiveCheck` annotation to `enabled` on the recovered -cluster. However, this is strongly discouraged unless you are highly -familiar with PostgreSQL's recovery process. Skipping the check incorrectly can -lead to severe data loss. Use with caution and only in expert scenarios. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_0_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_0_1_rel_notes.mdx deleted file mode 100644 index 94432fc4ee2..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_0_1_rel_notes.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.0.1 release notes" -navTitle: "Version 0.0.1" ---- - -Released: 5 Mar 2020 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | PostgreSQL 12.2 container image. | -| Feature | Self-Healing capability, through failover of the primary instance, by promoting the most aligned replica. | -| Feature | Self-Healing capability, through automated recreation of a replica. | -| Feature | Planned switchover of the primary instance, by promoting a selected replica. | -| Feature | Scale up/down capabilities. | -| Feature | Definition of an arbitrary number of instances (minimum 1 - one primary server). | -| Feature | Definition of the *read-write* service, to connect your applications to the only primary server of the cluster. | -| Feature | Definition of the *read-only* service, to connect your applications to any of the instances for read workloads. | -| Feature | Support for Local Persistent Volumes with PVC templates. | -| Feature | Standard output logging of PostgreSQL error messages. | \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_1_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_1_0_rel_notes.mdx deleted file mode 100644 index c08693e8ac0..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_1_0_rel_notes.mdx +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.1 release notes" -navTitle: "Version 0.1" ---- - -Released: 3 Apr 2020 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | Reuse of existing persistent storage with Pods (required for rolling updates). | -| Feature | Independence between operator container image and PostgreSQL container image (required by rolling updates) - this enables usage of Community PostgreSQL images. | -| Feature | Rolling updates for the update of the operator and the entire cluster to a new version of PostgreSQL, by updating all the replicas first; switchover can be entirely managed by Kubernetes once replicas have been updated (`unsupervised` option), or manually triggered by the user (`supervised` option). | -| Feature | Check framework for update-in-progress of a Pod. | -| Enhancement | Improvements in cluster status information. | -| Enhancement | E2E tests for Kubernetes 1.18. | -| Enhancement | E2E performance tests for failover (< 5 seconds). | -| Enhancement | Improvements in E2E tests for switchover. | -| Feature | Support for PostgreSQL's `cluster_name` GUC. | -| Feature | New documentation section `Exposing Postgres services`. | -| Feature | New documentation section `Security`. | \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_2_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_2_0_rel_notes.mdx deleted file mode 100644 index 2254ea545df..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_2_0_rel_notes.mdx +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.2 release notes" -navTitle: "Version 0.2" ---- - -Released: 11 Aug 2020 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | PostgreSQL 10 and 11 are now supported, in addition to PostgreSQL 12. | -| Feature | Usage of UBI as base image of the operator (OpenShift support). | -| Feature | New Backup and ScheduledBackup CRD, allowing users to take a physical backup of the cluster in an object store that complies with the S3 protocol (such as AWS S3, MinIO, MinIO Gateway). | -| Feature | Support for WAL archiving to an object store that complies with the S3 protocol. | -| Enhancement | Improvements in the E2e tests infrastructure. | -| Fix | Bug fixes and minor improvements. | \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_3_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_3_0_rel_notes.mdx deleted file mode 100644 index 11263bd7dfa..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_3_0_rel_notes.mdx +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.3 release notes" -navTitle: "Version 0.3" ---- - -Released: 25 Sep 2020 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | Support for PostgreSQL 13. | -| Feature | Remove `emptyDir` volume storage support. | -| Feature | Node maintenance support for PostgreSQL clusters with local storage through the `nodeMaintenanceWindow` parameter. | -| Enhancement | Improve PostgreSQL configuration management through the usage of a dictionary supporting default, required and fixed values. | -| Feature | Use MD5 as authentication method for inter-cluster communication, with automated password creation in a secret. | -| Feature | Remove need for "trust" authentication method. | -| Feature | `spec.postgresql.pg_hba` is now optional, defaulting to MD5 authentication required for communication between Pods and `peer` for in-Pod communication. | -| Feature | Remove "unusable" annotation support, now PVC can just be removed followed by a deletion of the corresponding Pod. | -| Feature | Support for license keys, including implicit 30 day trial version. | -| Fix | Bug fixes and minor improvements. | -| Feature | Update from an earlier version not supported. | \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_4_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_4_0_rel_notes.mdx deleted file mode 100644 index 09bc395318a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_4_0_rel_notes.mdx +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.4 release notes" -navTitle: "Version 0.4" ---- - -Released: 5 Nov 2020 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | Support for full recovery from a backup. | -| Feature | Add `bootstrap` section to configure how to initiate a cluster: `initDB` or `fullRecovery`. | -| Feature | Introduce defaulting and validating webhooks. | -| Feature | Simplify configuration (convention over configuration). | -| Feature | Constrain rolling upgrades to the same PostgreSQL major version. | -| Feature | End-to-end tests run on GKE, AKS and GKS. | -| Enhancement | Documentation improvements. | -| Enhancement | Bug fixes and minor improvements. | \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_5_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_5_0_rel_notes.mdx deleted file mode 100644 index e82c7598d41..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_5_0_rel_notes.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.5 release notes" -navTitle: "Version 0.5" ---- - -Released: 20 Nov 2020 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | Automated provisioning of an independent Certification Authority (CA) for each PostgreSQL cluster. | -| Feature | Transparent and native support for TLS/SSL connections to encrypt client/server communications. | -| Enhancement | Improve the security of the standby streaming replication channel through a dedicated and fixed database user called `streaming_replica` with sole `REPLICATION` privileges and II. an automatically managed X.509 TLS certificate signed by the cluster Certification Authority to authenticate the `streaming_replica` user. | -| Enhancement | Improve the security of the standby streaming replication channel through an automatically managed X.509 TLS certificate signed by the cluster Certification Authority to authenticate the `streaming_replica` user. | -| Enhancement | Improve PostgreSQL configuration capability through a mutating webhook that prevents users from changing those parameters that are directly managed by the operator. | -| Enhancement | Improve PostgreSQL configuration capability through a defaulting webhook that integrates the users' supplied configuration options with default values in the cluster state. | -| Enhancement | Improve PostgreSQL configuration capability through automated management of the PostgreSQL instances reload and restart. | -| Feature | Enable custom and independent configuration of a PostgreSQL cluster following a recovery from a backup. | -| Feature | Convey the current status of the cluster (i.e. healthy, failover in progress, switchover in progress). | -| Feature | API change from k8s.2ndq.io to k8s.enterprisedb.io. | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_6_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_6_0_rel_notes.mdx deleted file mode 100644 index 6fc94dd1d6d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_6_0_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.6 release notes" -navTitle: "Version 0.6" ---- - -Released: 4 Dec 2020 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | Add Point-In-Time Recovery based on timestamp, target name, or transaction Id, as well as the specification of the timeline, through a new bootstrap method option called `recoveryTarget`. | -| Feature | Add Synchronous Streaming Replication support through the `minSyncReplicas` and `maxSyncReplicas` cluster options, defining respectively the expected minimum and maximum number of synchronous standby servers at any time (disabled by default) | -| Feature | Support EDB Postgres Advanced Server (EPAS). | -| Feature | Configure `initdb` options for the bootstrap of an empty cluster (`initDb`). | -| Feature | Enable/Disable Redwood compatibility level with EPAS. | -| Feature | Extend the instance manager with a new framework for the export of metrics for Prometheus - currently supporting pg_stat_archiver only. | -| Feature | Use Kubernetes jobs instead of init containers to perform cluster initialization procedures (including standby creation and recovery) and improve their observability. | -| Feature | Record Kubernetes events to be used by `kubectl describe` and `kubectl get events`. | -| Feature | Introduce Kubernetes expectations for Pods, PVCs, and Jobs to prevent race conditions. | -| Feature | Set `application_name` in PostgreSQL to the name of the Pod/instance. | -| Feature | The `fullRecovery` bootstrap mode has been renamed to `recovery` to address also Point-In-Time Recovery | -| Fix | Bug fixes and code improvements. | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_7_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_7_0_rel_notes.mdx deleted file mode 100644 index 1a51f4707da..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_7_0_rel_notes.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.7 release notes" -navTitle: "Version 0.7" ---- - -Released: 31 Dec 2020 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | Support `pg_rewind` if needed following a failover or switchover to let the former primary act as a standby. | -| Feature | Add persistent volume expansion support, if permitted by the storage class. | -| Enhancement | Enhance metrics exporter for PostgreSQL. | -| Feature | Add support for Kubernetes version 1.20. | -| Feature | Drop support for Kubernetes version 1.15. | -| Feature | Refactor E2E tests, including conversion to Github actions. | -| Fix | Bug fixes and code improvements. | \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_8_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_8_0_rel_notes.mdx deleted file mode 100644 index 51f9049476f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/0_8_0_rel_notes.mdx +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 0.8 release notes" -navTitle: "Version 0.8" ---- - -Released: 29 Jan 2021 - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | Upgraded API version to v1. | -| Feature | Implement node affinity via `nodeSelector`. | -| Feature | Activate `AntiAffinity` by default. | -| Feature | Remove completed `Jobs` from the cluster. | -| Feature | Upgrade controller-runtime to v0.8.1. | -| Change | Build container images using schema version 2. | -| Change | Enhance E2E tests by covering more cases, robustness, and reliability improvements. | -| Fix | Bug fixes and code improvements. | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_0_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_0_0_rel_notes.mdx deleted file mode 100644 index 7f9ae461bc6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_0_0_rel_notes.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.0 release notes" -navTitle: "Version 1.0" ---- - -Released: 04 Feb 2021 - -The first major release implements Cluster, Backup and ScheduledBackup in the API group postgresql.k8s.enterprisedb.io/v1. It uses these resources to create and manage PostgreSQL clusters inside Kubernetes with the following main capabilities: - -| Type | Description | -| ------- | ------------------------------------------------------------------------------------------------------------ | -| Feature | Direct integration with Kubernetes API server for High Availability, without requiring an external tool. | -| Feature | Failover of the primary instance by promoting the most aligned replica. | -| Feature | Automated recreation of a replica. | -| Feature | Planned switchover of the primary instance by promoting a selected replica. | -| Feature | Scale up/down capabilities. | -| Feature | Definition of an arbitrary number of instances (minimum 1 - one primary server). | -| Feature | Definition of the read-write service to connect your applications to the only primary server of the cluster. | -| Feature | Definition of the read service to connect your applications to any of the instances for reading workloads. | -| Feature | Support for Local Persistent Volumes with PVC templates. | -| Feature | Reuse of Persistent Volumes storage in Pods. | -| Feature | Rolling updates for PostgreSQL minor versions and operator upgrades. | -| Feature | TLS connections and client certificate authentication. | -| Feature | Continuous backup to an S3 compatible object store. | -| Feature | Full recovery and point-in-time recovery from an S3 compatible object store backup. | -| Feature | Support for synchronous replicas. | -| Feature | Support for node affinity via nodeSelector property. | -| Feature | Standard output logging of PostgreSQL error messages. | - - - - - - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_10_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_10_0_rel_notes.mdx deleted file mode 100644 index 5770db49ac2..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_10_0_rel_notes.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.10.0 release notes" -navTitle: "Version 1.10.0" ---- - -Released: 11 Nov 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Connection Pooling with PgBouncer: introduce the Pooler resource and controller to automatically manage a PgBouncer deployment to be used as a connection pooler for a local PostgreSQL Cluster. The feature includes TLS client/server connections, password authentication, High Availability, pod templates support, configuration of key PgBouncer parameters, PAUSE/RESUME, logging in JSON format, Prometheus exporter for stats, pools, and lists. | -| Feature | Backup Retention Policies: support definition of recovery window retention policies for backups (e.g. ‘30d’ to ensure a recovery window of 30 days). | -| Feature | In-Place updates of the operator: introduce an in-place online update of the instance manager, which removes the need to perform a rolling update of the entire cluster following an update of the operator. By default this option is disabled (please refer to the documentation for more detailed information). | -| Feature | Limit the list of options that can be customized in the initdb bootstrap method to dataChecksums, encoding, localeCollate, localeCType, walSegmentSize. This makes the options array obsolete and planned to be removed in the v2 API. | -| Feature | Introduce the postInitTemplateSQL option as part of the initdb bootstrap method to specify a list of SQL queries to be executed on the template1 database as a superuser immediately after the cluster has been created. This feature allows you to include default objects in all application databases created in the cluster. | -| Feature | New default metrics added to the instance Prometheus exporter: Postgres version, cluster name, and first point of recoverability according to the backup catalog. | -| Feature | Retry taking a backup after a failure. | -| Feature | Build awareness about Barman Cloud capabilities in order to prevent the operator from invoking recently introduced features (such as retention policies, or Azure Blob Container storage) that are not present in operand images that are not frequently updated. | -| Feature | Integrate the output of the status command of the cnp plugin with information about the backup. | -| Feature | Introduce a new annotation that reports the status of a PVC (being initialized or ready). | -| Feature | Set the cluster name in the k8s.enterprisedb.io/cluster label for every object generated in a Cluster, including Backup objects. | -| Feature | Drop support for deprecated API version postgresql.k8s.enterprisedb.io/v1alpha1 on the Cluster, Backup, and ScheduledBackup kinds. | -| Feature | Set default operand image to PostgreSQL 14.2. | -| Security fix | Set allowPrivilegeEscalation to false for the operator containers securityContext. | -| Bug fix | Disable primary PodDisruptionBudget during maintenance in single-instance clusters. | -| Bug fix | Use the correct certificate certification authority (CA) during recovery operations. | -| Bug fix | Prevent Postgres connection leaking when checking WAL archiving status before taking a backup. | -| Bug fix | Let WAL archive/restore sleep for 100ms following transient errors that would flood logs otherwise. | - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_11_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_11_0_rel_notes.mdx deleted file mode 100644 index 23a7ad26cc3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_11_0_rel_notes.mdx +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.11.0 release notes" -navTitle: "Version 1.11.0" ---- - -Released: 15 Dec 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Parallel WAL archiving and restore: allow the database to keep up with WAL generation on high write systems by introducing the backupObjectStore.maxParallel option to set the maximum number of parallel jobs to be executed during both WAL archiving (by PostgreSQL’s archive_command) and WAL restore (by restore_command). Using parallel restore option can allow newly promoted Standbys to get to a ready state faster by fetching needed WAL files to replay in parallel rather than sequentially. | -| Feature | Default set of metrics for monitoring: a new ConfigMap called default-monitoring is automatically deployed in the same namespace of the operator and, by default, added to any existing Postgres cluster. Such behavior can be changed globally by setting the MONITORING_QUERIES_CONFIGMAP parameter in the operator’s configuration, or at cluster level through the .spec.monitoring. | -| Feature | disableDefaultQueries option (by default set to false). | -| Feature | Introduce the enablePodMonitor option in the monitoring section of a cluster to automatically manage a PodMonitor resource and seamlessly integrate with Prometheus. | -| Feature | Improve the PostgreSQL shutdown procedure by trying to execute a smart shutdown for the first half of the desired stopDelay time, and a fast shutdown for the remaining half, before the pod is killed by Kubernetes. | -| Feature | Add the switchoverDelay option to control the time given to the former primary to shut down gracefully and archive all the WAL files before promoting the new primary (by default, Cloud Native PostgreSQL waits indefinitely to privilege data durability). | -| Feature | Handle changes to resource requests and limits for a PostgreSQL Cluster by issuing a rolling update. | -| Feature | Improve the status command of the cnp plugin for kubectl with additional information: streaming replication status, total size of the database, role of an instance in the cluster. | -| Feature | Enhance support of workloads with many parallel workers by enabling configuration of the dynamic_shared_memory_type and shared_memory_type parameters for PostgreSQL’s management of shared memory. | -| Feature | Propagate labels and annotations defined at cluster level to the associated resources, including pods (deletions are not supported). | -| Feature | Automatically remove pods that have been evicted by the Kubelet. | -| Feature | Manage automated resizing of persistent volumes in Azure through the ENABLE_AZURE_PVC_UPDATES operator configuration option, by issuing a rolling update of the cluster if needed (disabled by default). | -| Feature | Introduce thek8s.enterprisedb.io/reconciliationLoop annotation that, when set to disabled on a given Postgres cluster, prevents the reconciliation loop from running. | -| Feature | Introduce the postInitApplicationSQL option as part of the initdb bootstrap method to specify a list of SQL queries to be executed on the main application database as a superuser immediately after the cluster has been created. | -| Feature | Support for EDB Postgres Advanced 14.2. | -| Bug fix | Liveness probe now correctly handles the startup process of a PostgreSQL server. This fixes an issue reported by a few customers and affects a restarted standby server that needs to recover WAL files to reach a consistent state, but it was not able to do it before the timeout of liveness probe would kick in, leaving the pods in CrashLoopBackOff status. | -| Bug fix | Liveness probe now correctly handles the case of a former primary that needs to use pg_rewind to re-align with the current primary after a timeline diversion. This fixes the pod of the new standby from repeatedly being killed by Kubernetes. | -| Bug fix | Reduce client-side throttling from Postgres pods (e.g. Waited for 1.182388649s due to client-side throttling, not priority and fairness, request: GET). | -| Bug fix | Disable Public Key Infrastructure (PKI) initialization on OpenShift and OLM installations, by using the provided one. | -| Bug fix | When changing configuration parameters that require a restart, always leave the primary as last. | -| Bug fix | Mark a PVC to be ready only after a job has been completed successfully, preventing a race condition in PVC initialization. | -| Bug fix | Use the correct public key when renewing the expired webhook TLS secret. | -| Bug fix | Fix an overflow when parsing an LSN. | -| Bug fix | Remove stale PID files at startup. | -| Bug fix | Let the Pooler resource inherit the imagePullSecret defined in the operator, if exists. | - - - - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_12_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_12_0_rel_notes.mdx deleted file mode 100644 index d920ab7dd96..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_12_0_rel_notes.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.12.0 release notes" -navTitle: "Version 1.12.0" ---- - -Released: 11 Jan 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Add Kubernetes 1.23 to the list of supported Kubernetes distributions and remove end-to-end tests for 1.17, which ended support by the Kubernetes project in Dec 2020. | -| Feature | Improve the responsiveness of pod status checks in case of network issues by adding a connection timeout of 2 seconds and a communication timeout of 30 seconds. This change sets a limit on the time the operator waits for a pod to report its status before declaring it as failed, enhancing the robustness and predictability of a failover operation. | -| Feature | Introduce the .spec.inheritedMetadata field to the Cluster allowing the user to specify labels and annotations that will apply to all objects generated by the Cluster. | -| Feature | Reduce the number of queries executed when calculating the status of an instance. | -| Feature | Add a readiness probe for PgBouncer. | -| Feature | Add support for custom Certification Authority of the endpoint of Barman’s backup object store when using Azure protocol. | -| Bug fix | During a failover, wait to select a new primary until all the WAL streaming connections are closed. The operator now sets by default wal_sender_timeout and wal_receiver_timeout to 5 seconds to make sure standby nodes will quickly notice if the primary has network issues. | -| Bug fix | Change WAL archiving strategy in replica clusters to fix rolling updates by setting "archive_mode" to "always" for any PostgreSQL instance in a replica cluster. We then restrict the upload of the WAL only from the current and target designated primary. A WAL may be uploaded twice during switchovers, which is not an issue. | -| Bug fix | Fix support for custom Certification Authority of the endpoint of Barman’s backup object store in replica clusters source. | -| Bug fix | Use a fixed name for default monitoring config map in the cluster namespace. | -| Bug fix | If the defaulting webhook is not working for any reason, the operator now updates the Cluster with the defaults also during the reconciliation cycle. | -| Bug fix | Fix the comparison of resource requests and limits to fix a rare issue leading to an update of all the pods on every reconciliation cycle. | -| Bug fix | Improve log messages from webhooks to also include the object namespace. | -| Bug fix | Stop logging a “default” message at the start of every reconciliation loop. | -| Bug fix | Stop logging a PodMonitor deletion on every reconciliation cycle if enablePodMonitor is false. | -| Bug fix | Do not complain about possible architecture mismatch if a pod is not reachable. | - - - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_13_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_13_0_rel_notes.mdx deleted file mode 100644 index d3dc3cbfbb7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_13_0_rel_notes.mdx +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.13.0 release notes" -navTitle: "Version 1.13.0" ---- - -Released: 17 Feb 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Support for Snappy compression. Snappy is a fast compression option for backups that increase the speed of uploads to the object store using a lower compression ratio. | -| Feature | Support for tagging files uploaded to the Barman object store. This feature requires Barman 2.18 in the operand image. of backups after Cluster deletion. | -| Feature | Extension of the status of a Cluster with status.conditions. The condition ContinuousArchiving indicates that the Cluster has started to archive WAL files. | -| Feature | Improve the status command of the cnp plugin for kubectl with additional information: add a Cluster Summary section showing the status of the Cluster and a Certificates Status section including the status of the certificates used in the Cluster along with the time left to expire. | -| Feature | Support the new barman-cloud-check-wal-archive command to detect a non-empty backup destination when creating a new cluster. | -| Feature | Add support for using a Secret to add default monitoring queries through MONITORING_QUERIES_SECRET configuration variable. | -| Feature | Allow the user to restrict container’s permissions using AppArmor (on Kubernetes clusters deployed with AppArmor support). | -| Feature | Add Windows platform support to cnp plugin for kubectl, now the plugin is available on Windows x86 and ARM. | -| Feature | Drop support for Kubernetes 1.18 and deprecated API versions | -| Container images | PostgreSQL containers include Barman 2.18. | -| Security fix | Add coherence check of username field inside owner and superuser secrets; previously, a malicious user could have used the secrets to change the password of any PostgreSQL user. | -| Bug fix | Fix a memory leak in code fetching status from Postgres pods. | -| Bug fix | Disable PostgreSQL self-restart after a crash. The instance controller handles the lifecycle of the PostgreSQL instance. | -| Bug fix | Prevent modification of spec.postgresUID and spec.postgresGID fields in validation webhook. Changing these fields after Cluster creation makes PostgreSQL unable to start. | -| Bug fix | Reduce the log verbosity from the backup and WAL archiving handling code. | -| Bug fix | Correct a bug resulting in a Cluster being marked as Healthy when not initialized yet. | -| Bug fix | Allows standby servers in clusters with a very high WAL production rate to switch to streaming once they are aligned. | -| Bug fix | Fix a race condition during the startup of a PostgreSQL pod that could seldom lead to a crash. | -| Bug fix | Fix a race condition that could lead to a failure initializing the first PVC in a Cluster. | -| Bug fix | Remove an extra restart of a just demoted primary Pod before joining the Cluster as a replica. | -| Bug fix | Correctly handle replication-sensitive PostgreSQL configuration parameters when recovering from a backup. | -| Bug fix | Fix missing validation of PostgreSQL configurations during Cluster creation. | - - - - - - - - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_14_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_14_0_rel_notes.mdx deleted file mode 100644 index 3c6145c86b9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_14_0_rel_notes.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.14.0 release notes" -navTitle: "Version 1.14.0" ---- - -Released: 25 Mar 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Natively support Google Cloud Storage for backup and recovery, by taking advantage of the features introduced in Barman Cloud 2.19. | -| Feature | Improved observability of backups through the introduction of the LastBackupSucceeded condition for the Cluster object. | -| Feature | Support update of Hot Standby sensitive parameters: max_connections, max_prepared_transactions, max_locks_per_transaction, max_wal_senders, max_worker_processes.| -| Feature | Add the Online upgrade in progress phase in the Cluster object to show when an online upgrade of the operator is in progress.| -| Feature | Ability to inherit an AWS IAM Role as an alternative way to provide credentials for the S3 object storage.| -| Feature | Support for Opaque secrets for Pooler’s authQuerySecret and certificates.| -| Feature | Updated default PostgreSQL version to 14.2. | -| Feature | Add a new command to kubectl cnp plugin named maintenance to set maintenance window to cluster(s) in one or all namespaces across the Kubernetes cluster. | -| Container images | Latest PostgreSQL and EDB Postgres Advanced Server containers include Barman Cloud 2.19. | -| Security fix | Stronger RBAC enforcement for namespaced operator installations with Operator Lifecycle Manager, including OpenShift. OpenShift users are recommended to update to this version. | -| Bug fix | Allow the instance manager to retry an interrupted pg_rewind by preserving a copy of the original pg_control file. | -| Bug fix | Clean up stale PID files before running pg_rewind. | -| Bug fix | Force sorting by key in primary_conninfo to avoid random restarts with PostgreSQL versions prior to 13. | -| Bug fix | Preserve ServiceAccount changes (e.g., labels, annotations) upon reconciliation. | -| Bug fix | Disable enforcement of the imagePullPolicy default value. | -| Bug fix | Improve initDB validation for WAL segment size. | -| Bug fix | Properly handle the targetLSN option when recovering a cluster with the LSN specified. | -| Bug fix | Fix custom TLS certificates validation by allowing a certificates chain both in the server and CA certificates. | - - - - - - - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_0_rel_notes.mdx deleted file mode 100644 index b3664162a59..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_0_rel_notes.mdx +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.15.0 release notes" -navTitle: "Version 1.15.0" ---- - -Released: 21 Apr 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.15.0. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15/). | - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_1_rel_notes.mdx deleted file mode 100644 index c889f1149e4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_1_rel_notes.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.15.1 release notes" -navTitle: "Version 1.15.1" ---- - -Released: 27 May 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.15.1. See the community [Release Notes](https://cloudnative-pg.io/documentation/1.15/release_notes/#version-1151). | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_2_rel_notes.mdx deleted file mode 100644 index c923f94e941..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_2_rel_notes.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.15.2 release notes" -navTitle: "Version 1.15.2" ---- - -Released: 07 Jul 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.15.2. See the community [Release Notes](https://cloudnative-pg.io/documentation/1.15/release_notes/#version-1152). | -| Enhancement | New “stable-v1.15” channel available for OpenShift, providing update paths to the latest available patch release in the 1.15 release branch of EDB Postgres for Kubernetes. The “stable” channel is a synonym of “stable-v1.15”. See the following section for more information. | - - -## Important changes to our upgrade policy -We are adopting a new policy to support the last two minor versions of the product beginning with 1.16, in line with the CloudNativePG community. - -As a result, we are introducing the following head versions in the new OLM channels in OpenShift to manage the update streams for EDB Postgres for Kubernetes: - -* `fast`: the latest available patch release for the latest available minor release -* `stable-v1.16`: the latest available patch release of the 1.16 minor release -* `stable-v1.15`: the latest available patch release of the 1.15 minor release - -Prior to the release of 1.16, the only channel that we were supporting was the `stable` channel. This channel is now obsolete. However, for backward compatibility it is currently set as an alias of the `stable-v1.15` channel and it will be removed once version 1.15 goes End of Life. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_3_rel_notes.mdx deleted file mode 100644 index 80c136343b7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_3_rel_notes.mdx +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.15.3 release notes" -navTitle: "Version 1.15.3" ---- - -Released: 12 Aug 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.15.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15/). | - - -## Important changes to our upgrade policy -We are adopting a new policy to support the last two minor versions of the product beginning with 1.16, in line with the CloudNativePG community. - -As a result, we are introducing the following head versions in the new OLM channels in OpenShift to manage the update streams for EDB Postgres for Kubernetes: - -* `fast`: the latest available patch release for the latest available minor release -* `stable-v1.16`: the latest available patch release of the 1.16 minor release -* `stable-v1.15`: the latest available patch release of the 1.15 minor release - -Prior to the release of 1.16, the only channel that we were supporting was the `stable` channel. This channel is now obsolete. However, for backward compatibility it is currently set as an alias of the `stable-v1.15` channel and it will be removed once version 1.15 goes End of Life. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_4_rel_notes.mdx deleted file mode 100644 index f33772a7bd2..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_4_rel_notes.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.15.4 release notes" -navTitle: "Version 1.15.4" ---- - -Released: 06 Sep 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.15.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15/). | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_5_rel_notes.mdx deleted file mode 100644 index 5086870fe17..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_15_5_rel_notes.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.15.5 release notes" -navTitle: "Version 1.15.5" ---- - -Released: 07 Oct 2022 - -!!!warning - Version 1.15 has reached End-of-Life (EOL). Version 1.15.5 is the last release for the 1.15 minor version. - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.15.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15/). | -| Enhancement | Introduces `leaseDuration` and `renewDeadline` parameters in the controller manager to enhance configuration of the leader election in operator deployments. | -| Enhancement | Improves the mechanism that checks that the backup object store is empty before archiving a WAL file for the first time. A new file called `.check-empty-wal-archive` is placed in the `PGDATA` immediately after the cluster is bootstrapped. It is removed after the first WAL file is successfully archived. | -| Security | Explicitly sets permissions of the instance manager binary that is copied in the `distroless/static:nonroot` container image, by using the `nonroot:nonroot` user. | -| Bug fix | Makes the cluster's conditions compatible with `metav1.Conditions` struct. | -| Bug fix | Drops any active connection on a standby after it is promoted to primary. | -| Bug fix | Honors `MAPPEDMETRIC` and `DURATION` metric types conversion in the native Prometheus exporter. | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_0_rel_notes.mdx deleted file mode 100644 index 7de76f846d6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_0_rel_notes.mdx +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.16.0 release notes" -navTitle: "Version 1.16.0" ---- - -Released: 07 Jul 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.16. See the community [Release Notes](https://cloudnative-pg.io/documentation/1.16/release_notes/#version-1160). | -| Enhancement | New “fast” channel available for OpenShift, providing update paths to the latest available patch release in the latest available minor release of EDB Postgres for Kubernetes. See the following section for more information.| -| Enhancement | New “stable-v1.16” channel available for OpenShift, providing update paths to the latest available patch release in the 1.16 release branch of EDB Postgres for Kubernetes. See the following section for more information. | - - -## Important changes to our upgrade policy -We are adopting a new policy to support the last two minor versions of the product, in line with the CloudNativePG community. - -As a result, we are introducing the following head versions in the new OLM channels in OpenShift to manage the update streams for EDB Postgres for Kubernetes: - -* `fast`: the latest available patch release for the latest available minor release -* `stable-v1.16`: the latest available patch release of the 1.16 minor release -* `stable-v1.15`: the latest available patch release of the 1.15 minor release - -Prior to this release, the only channel that we were supporting was the `stable` channel. This channel is now obsolete. However, for backward compatibility it is currently set as an alias of the `stable-v1.15` channel. It will be removed once version 1.15 reaches End of Life. - -## Important information about upgrading to a 1.16.x operator version on Openshift - -We have made a change to the way conditions are represented in the status of -the operator in version 1.16.0 and onward. This change could cause an operator -upgrade to hang on Openshift if one of the old conditions are set during the -upgrade process because of the way the Operator Lifecycle Manager checks new -CRDs against existing CRs. - -Prior to installing 1.16.x on Openshift, if you are upgrading from a 1.15.x (or -earlier) version of the operator, we recommend uninstalling the existing -version of the operator, then deleting all of the old conditions out of the -statuses of all existing EDB Postgres for Kubernetes clusters. -This will have no effect on the operability of your existing EDB Postgres for -Kubernetes clusters. - -To remove the existing conditions run: - -```bash -while IFS=' ' read NS CLUSTER; do - kubectl -n ${NS} patch --type='json' ${CLUSTER} --subresource=status -p='[{"op": "remove", "path": "/status/conditions"}]'; -done < <(kubectl get cluster -A --no-headers=true -o jsonpath='{range .items[*]}{.metadata.namespace}{" cluster/"}{.metadata.name}{"\n"}{end}') -``` - -!!! Important - The kubectl command must be version 1.24 or higher. - If you get the output `The request is invalid` it means that the target cluster - didn't have any condition on it. - -This command will remove all of the conditions from all of the EDB Postgres for -Kubernetes clusters in your Openshift cluster. -Once the command completes, you can safely install version 1.16.x. - -If you have already tried to upgrade to 1.16.x from 1.15.x (or earlier) and -the install of 1.16.x shows as "Pending" and the earlier version shows as -"Cannot update", uninstall both versions of the operator and -run the command that removes the statuses. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_1_rel_notes.mdx deleted file mode 100644 index fe9be5ea8e9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_1_rel_notes.mdx +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.16.1 release notes" -navTitle: "Version 1.16.1" ---- - -Released: 12 Aug 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.16. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/). | - -## Important changes to our upgrade policy -We are adopting a new policy to support the last two minor versions of the product, in line with the CloudNativePG community. - -As a result, we are introducing the following head versions in the new OLM channels in OpenShift to manage the update streams for EDB Postgres for Kubernetes: - -* `fast`: the latest available patch release for the latest available minor release -* `stable-v1.16`: the latest available patch release of the 1.16 minor release -* `stable-v1.15`: the latest available patch release of the 1.15 minor release - -Prior to this release, the only channel that we were supporting was the `stable` channel. This channel is now obsolete. However, for backward compatibility it is currently set as an alias of the `stable-v1.15` channel. It will be removed once version 1.15 reaches End of Life. - -## Important information about upgrading to a 1.16.x operator version on Openshift - -We have made a change to the way conditions are represented in the status of -the operator in version 1.16.0 and onward. This change could cause an operator -upgrade to hang on Openshift if one of the old conditions are set during the -upgrade process because of the way the Operator Lifecycle Manager checks new -CRDs against existing CRs. - -Prior to installing 1.16.x on Openshift, if you are upgrading from a 1.15.x (or -earlier) version of the operator, we recommend uninstalling the existing -version of the operator, then deleting all of the old conditions out of the -statuses of all existing EDB Postgres for Kubernetes clusters. -This will have no effect on the operability of your existing EDB Postgres for -Kubernetes clusters. - -To remove the existing conditions run: - -```bash -while IFS=' ' read NS CLUSTER; do - kubectl -n ${NS} patch --type='json' ${CLUSTER} --subresource=status -p='[{"op": "remove", "path": "/status/conditions"}]'; -done < <(kubectl get cluster -A --no-headers=true -o jsonpath='{range .items[*]}{.metadata.namespace}{" cluster/"}{.metadata.name}{"\n"}{end}') -``` - -!!! Important - The kubectl command must be version 1.24 or higher. - If you get the output `The request is invalid` it means that the target cluster - didn't have any condition on it. - -This command will remove all of the conditions from all of the EDB Postgres for -Kubernetes clusters in your Openshift cluster. -Once the command completes, you can safely install version 1.16.x. - -If you have already tried to upgrade to 1.16.x from 1.15.x (or earlier) and -the install of 1.16.x shows as "Pending" and the earlier version shows as -"Cannot update", uninstall both versions of the operator and -run the command that removes the statuses. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_2_rel_notes.mdx deleted file mode 100644 index 2995a894c1d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_2_rel_notes.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.16.2 release notes" -navTitle: "Version 1.16.2" ---- - -Released: 06 Sep 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.16.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/). | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_3_rel_notes.mdx deleted file mode 100644 index d97a168a95b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_3_rel_notes.mdx +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.16.3 release notes" -navTitle: "Version 1.16.3" ---- - -Released: 07 Oct 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.16.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/). | -| Enhancement | Introduces `leaseDuration` and `renewDeadline` parameters in the controller manager to enhance configuration of the leader election in operator deployments. | -| Enhancement | Improves the mechanism that checks that the backup object store is empty before archiving a WAL file for the first time. A new file called `.check-empty-wal-archive` is placed in the `PGDATA` immediately after the cluster is bootstrapped. It is removed after the first WAL file is successfully archived. | -| Security | Explicitly sets permissions of the instance manager binary that is copied in the `distroless/static:nonroot` container image, by using the `nonroot:nonroot` user. | -| Bug fix | Drops any active connection on a standby after it is promoted to primary. | -| Bug fix | Honors `MAPPEDMETRIC` and `DURATION` metric types conversion in the native Prometheus exporter. | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_4_rel_notes.mdx deleted file mode 100644 index 590ca63f03d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_4_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.16.4 release notes" -navTitle: "Version 1.16.4" ---- - -Released: 14 Nov 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.16.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_5_rel_notes.mdx deleted file mode 100644 index 6130f674222..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_16_5_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.16.5 release notes" -navTitle: "Version 1.16.5" ---- - -Released: 21 Dec 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.16.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_0_rel_notes.mdx deleted file mode 100644 index 4d119356919..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_0_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.17.0 release notes" -navTitle: "Version 1.17.0" ---- - -Released: 06 Sep 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.17. See the community [Release Notes](https://cloudnative-pg.io/documentation/1.17/release_notes/#v1.17). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_1_rel_notes.mdx deleted file mode 100644 index fedaacf2e3a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_1_rel_notes.mdx +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.17.1 release notes" -navTitle: "Version 1.17.1" ---- - -Released: 07 Oct 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.17.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/). | -| Enhancement | Introduces `leaseDuration` and `renewDeadline` parameters in the controller manager to enhance configuration of the leader election in operator deployments. | -| Enhancement | Improves the mechanism that checks that the backup object store is empty before archiving a WAL file for the first time. A new file called `.check-empty-wal-archive` is placed in the `PGDATA` immediately after the cluster is bootstrapped. It is removed after the first WAL file is successfully archived. | -| Security | Explicitly sets permissions of the instance manager binary that is copied in the `distroless/static:nonroot` container image, by using the `nonroot:nonroot` user. | -| Bug fix | Drops any active connection on a standby after it is promoted to primary. | -| Bug fix | Honors `MAPPEDMETRIC` and `DURATION` metric types conversion in the native Prometheus exporter. | -| Bug fix | Ensures that timestamps that are specified with microsecond precision using the PostgreSQL format are correctly parsed. | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_2_rel_notes.mdx deleted file mode 100644 index f79eae65a44..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_2_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.17.2 release notes" -navTitle: "Version 1.17.2" ---- - -Released: 14 Nov 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.17.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_3_rel_notes.mdx deleted file mode 100644 index e633068ae34..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_3_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.17.3 release notes" -navTitle: "Version 1.17.3" ---- - -Released: 21 Dec 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | Merged with community CloudNativePG 1.17.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_4_rel_notes.mdx deleted file mode 100644 index 15572cfa43d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_4_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.17.4 release notes" -navTitle: "Version 1.17.4" ---- - -Released: 14 Feb 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.17.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_5_rel_notes.mdx deleted file mode 100644 index 57c807d31c2..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_17_5_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.17.5 release notes" -navTitle: "Version 1.17.5" ---- - -Released: 20 Mar 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.17.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_0_rel_notes.mdx deleted file mode 100644 index 21817340d05..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_0_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.0 release notes" -navTitle: "Version 1.18.0" ---- - -Released: 14 Nov 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.18. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_10_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_10_rel_notes.mdx deleted file mode 100644 index b5989178387..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_10_rel_notes.mdx +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.10 release notes" -navTitle: "Version 1.18.10" ---- - -Released: 02 Feb 2024 - -EDB Postgres for Kubernetes version 1.18.10 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------ | -| Enhancement | Tailor ephemeral volume storage in a Postgres cluster using a claim template through the `ephemeralVolumeSource` option ([#3678](https://github.com/cloudnative-pg/cloudnative-pg/pull/3678)). | -| Enhancement | Introduce the `pgadmin4` command in the `cnp` plugin for `kubectl`, providing a straightforward method to demonstrate connecting to a given database cluster and navigate its content in a local environment such as kind - for evaluation purposes only ([#3701](https://github.com/cloudnative-pg/cloudnative-pg/pull/3701)). | -| Enhancement | Allow customization of PostgreSQL's ident map file via the `.spec.postgresql.pg_ident` stanza, through a list of user name maps ([#3534](https://github.com/cloudnative-pg/cloudnative-pg/pull/3534)). | -| Bug fix | Prevent an unrecoverable issue with `pg_rewind` failing due to `postgresql.auto.conf` being read-only on clusters where the `ALTER SYSTEM` SQL command is disabled - the default ([#3728](https://github.com/cloudnative-pg/cloudnative-pg/pull/3728)). | -| Bug fix | Reduce the risk of disk space shortage when using the import facility of the `initdb` bootstrap method, by disabling the durability settings in the PostgreSQL instance for the duration of the import process ([#3743](https://github.com/cloudnative-pg/cloudnative-pg/pull/3743)). | -| Bug fix | Avoid pod restart due to erroneous resource quantity comparisons, e.g. "1 != 1000m" ([#3706](https://github.com/cloudnative-pg/cloudnative-pg/pull/3706)). | -| Bug fix | Properly escape reserved characters in `pgpass` connection fields ([#3713](https://github.com/cloudnative-pg/cloudnative-pg/pull/3713)). | -| Bug fix | Prevent systematic rollout of pods due to considering zero and nil different values in `.spec.projectedVolumeTemplate.sources` ([#3647](https://github.com/cloudnative-pg/cloudnative-pg/pull/3647)). | -| Bug fix | Ensure configuration coherence by pruning from `postgresql.auto.conf` any options now incorporated into `override.conf` ([#3773](https://github.com/cloudnative-pg/cloudnative-pg/pull/3773)). | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_11_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_11_rel_notes.mdx deleted file mode 100644 index 941a0bec12f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_11_rel_notes.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.11 release notes" -navTitle: "Version 1.18.11" ---- - -Released: 22 Mar 2024 - -EDB Postgres for Kubernetes version 1.18.11 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------ | -| Enhancement | Allow customization of the wal_level GUC in PostgreSQL ([#4020](https://github.com/cloudnative-pg/cloudnative-pg/pull/4020)). | -| Enhancement | Added the `cnpg.io/skipWalArchiving` annotation to disable WAL archiving when set to `enabled` ([#4055](https://github.com/cloudnative-pg/cloudnative-pg/pull/4055)). | -| Enhancement | Enriched the `cnpg` plugin for `kubectl` with the `publication` and `subscription` command groups to imperatively set up PostgreSQL native logical replication ([#4052](https://github.com/cloudnative-pg/cloudnative-pg/pull/4052)). | -| Enhancement | Allow customization of `CERTIFICATE_DURATION` and `EXPIRING_CHECK_THRESHOLD` for automated management of TLS certificates handled by the operator ([#3686](https://github.com/cloudnative-pg/cloudnative-pg/pull/3686)). | -| Enhancement | Now retrieves the correct architecture's binary from the corresponding catalog in the running operator image during in-place updates, enabling the operator to inject the correct binary into any Pod with a supported architecture ([#3840](https://github.com/cloudnative-pg/cloudnative-pg/pull/3840)). -| Security | Now uses `Role` instead of `ClusterRole` for operator permissions in OLM, requiring fewer privileges when installed on a per-namespace basis ([#3855](https://github.com/cloudnative-pg/cloudnative-pg/pull/3855), [#3990](https://github.com/cloudnative-pg/cloudnative-pg/pull/3990)). | -| Security | Now enforces fully-qualified object names in SQL queries for the PgBouncer pooler ([#4080](https://github.com/cloudnative-pg/cloudnative-pg/pull/4080)). | -| Bug fix | Now properly synchronizes PVC group labels with those on the pods, a critical aspect when all pods are deleted and the operator needs to decide which Pod to recreate first ([#3930](https://github.com/cloudnative-pg/cloudnative-pg/pull/3930)). | -| Bug fix | Now disables `wal_sender_timeout` when cloning a replica to prevent timeout errors due to slow connections ([#4080](https://github.com/cloudnative-pg/cloudnative-pg/pull/4080)). | -| Bug fix | Now ensures that backups are ready before initiating recovery bootstrap procedures, preventing an error condition where recovery with incomplete backups could enter an error loop ([#3663](https://github.com/cloudnative-pg/cloudnative-pg/pull/3663)). | -| Bug fix | Resolve a corner case in hibernation where the instance pod has been deleted, but the cluster status still has the hibernation condition set to false ([#3970](https://github.com/cloudnative-pg/cloudnative-pg/pull/3970)). | -| Bug fix | Correctly detect Google Cloud capabilities for Barman Cloud ([#3931](https://github.com/cloudnative-pg/cloudnative-pg/pull/3931)). | -| Update | Set the default operand image to PostgreSQL 16.2 ([#3823](https://github.com/cloudnative-pg/cloudnative-pg/pull/3823)). | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_12_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_12_rel_notes.mdx deleted file mode 100644 index 4f3da26f680..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_12_rel_notes.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.12 release notes" -navTitle: "Version 1.18.12" ---- - -Released: 24 Apr 2024 - -EDB Postgres for Kubernetes version 1.18.12 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------ | -| Enhancement | Added upgrade process from 1.18.x LTS to 1.22.x LTS | -| Enhancement | Documentation for Kubernetes 1.29.x or above ([#3729](https://github.com/cloudnative-pg/cloudnative-pg/pull/3729)) | -| Enhancement | Ensure pods with no ownership are deleted during cluster restore ([#4141](https://github.com/cloudnative-pg/cloudnative-pg/pull/4141)) | -| Bug fix | Properly handle LSN sorting when is empty on a replica ([#4283](https://github.com/cloudnative-pg/cloudnative-pg/pull/4283)) | -| Bug fix | Avoids stopping reconciliation loop when there is no instance status available ([#4132](https://github.com/cloudnative-pg/cloudnative-pg/pull/4132)) | -| Bug fix | Waits for elected replica to be in streaming mode before a switchover ([#4288](https://github.com/cloudnative-pg/cloudnative-pg/pull/4288)) | -| Bug fix | Allow backup hooks to be called while using Velero backup | -| Bug fix | Waits for the Restic init container to be completed | -| Security | Updated all Go dependencies to fix any latest security issues | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_13_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_13_rel_notes.mdx deleted file mode 100644 index 1b6a5f48133..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_13_rel_notes.mdx +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.13 release notes" -navTitle: "Version 1.18.13" ---- - -Released: 13 Jun 2024 - -EDB Postgres for Kubernetes version 1.18.13 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -!!! Warning - This is expected to be the last release in the 1.18.X series. - Users are encouraged to update to a newer minor version soon. - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------ | -| Enhancement | Enabled the configuration of the liveness probe timeout via the `.spec.livenessProbeTimeout` option ([#4719](https://github.com/cloudnative-pg/cloudnative-pg/pull/4719)) | -| Change | Default operand image set to PostgreSQL 16.3 ([#4584](https://github.com/cloudnative-pg/cloudnative-pg/pull/4584)) | -| Change | Removed all RBAC requirements on namespace objects ([#4753](https://github.com/cloudnative-pg/cloudnative-pg/pull/4753)) | -| Bug fix | Prevented fenced instances from entering an unnecessary loop and consuming all available CPU ([#4625](https://github.com/cloudnative-pg/cloudnative-pg/pull/4625)) | -| Bug fix | Resolved an issue where the instance manager on the primary would indefinitely wait for the instance to start after encountering a failure following a stop operation ([#4434](https://github.com/cloudnative-pg/cloudnative-pg/pull/4434)) | -| Bug fix | Fixed a panic in the backup controller that occurred when pod container statuses were missing ([#4765](https://github.com/cloudnative-pg/cloudnative-pg/pull/4765)) | -| Bug fix | Prevented unnecessary shutdown of the instance manager ([#4670](https://github.com/cloudnative-pg/cloudnative-pg/pull/4670)) | -| Bug fix | Prevented unnecessary reloads of PostgreSQL configuration when unchanged ([#4531](https://github.com/cloudnative-pg/cloudnative-pg/pull/4531)) | -| Bug fix | Prevented unnecessary reloads of the ident map by ensuring a consistent and unique method of writing its content ([#4648](https://github.com/cloudnative-pg/cloudnative-pg/pull/4648)) | -| Bug fix | Avoided conflicts during phase registration by patching the status of the resource instead of updating it ([#4637](https://github.com/cloudnative-pg/cloudnative-pg/pull/4637)) | -| Bug fix | Implemented a timeout when restarting PostgreSQL and lifting fencing ([#4504](https://github.com/cloudnative-pg/cloudnative-pg/pull/4504)) | -| Bug fix | Ensured that a replica cluster is restarted after promotion to properly set the archive mode ([#4399](https://github.com/cloudnative-pg/cloudnative-pg/pull/4399)) | -| Bug fix | Ensured correct parsing of the additional rows field returned when the `pgaudit.log_rows` option was enabled, preventing audit logs from being incorrectly routed to the normal log stream ([#4394](https://github.com/cloudnative-pg/cloudnative-pg/pull/4394)) | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_1_rel_notes.mdx deleted file mode 100644 index d1f7d592cc8..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_1_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.1 release notes" -navTitle: "Version 1.18.1" ---- - -Released: 21 Dec 2022 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.18.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_2_rel_notes.mdx deleted file mode 100644 index 6d28d56a465..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_2_rel_notes.mdx +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.2 release notes" -navTitle: "Version 1.18.2" ---- - -Released: 14 Feb 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.18.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/). | -| Feature | Support for [Transparent Data Encryption (TDE)](/tde/latest) with EDB Postgtres Advanced Server 15. TDE encrypts, transparently to the user, any user data stored in the database system. | -| Feature | New external backup adaptor to provide a generic way to integrate EDB Postgres for Kubernetes in a third-party tool for backups. See [External Backup Adapter](/postgres_for_kubernetes/latest/addons/#external-backup-adapter) for more information.| \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_3_rel_notes.mdx deleted file mode 100644 index 166091c8272..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_3_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.3 release notes" -navTitle: "Version 1.18.3" ---- - -Released: 20 Mar 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.18.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_4_rel_notes.mdx deleted file mode 100644 index afe22020fa7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_4_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.4 release notes" -navTitle: "Version 1.18.4" ---- - -Released: 27 Apr 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.18.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_5_rel_notes.mdx deleted file mode 100644 index 74f44de118c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_5_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.5 release notes" -navTitle: "Version 1.18.5" ---- - -Released: 13 Jun 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.18.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_6_rel_notes.mdx deleted file mode 100644 index 1b6d558327c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_6_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.6 release notes" -navTitle: "Version 1.18.6" ---- - -Released: 27 Jul 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------ | -| Enhancement | Added a metric and status field to monitor node usage by an EDB Postgres for Kubernetes cluster. | | -| Enhancement | Added troubleshooting instructions relating to hugepages to the documentation. | -| Enhancement | Extended the FAQs page in the documentation. | -| Enhancement | Added a check at the start of the restore process to ensure it can proceed; give improved error diagnostics if it cannot. | -| Bug fix | Ensured the logic of setting the recovery target matches that of Postgres. | -| Bug fix | Prevented taking over service accounts not owned by the cluster by setting ownerMetadata only during service account creation. | -| Bug fix | Prevented a possible crash of the instance manager during the configuration reload. | -| Bug fix | Prevented the LastFailedArchiveTime alert from triggering if a new backup has been successful after the failed ones. | -| Security fix | Updated all project dependencies to the latest versions | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_7_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_7_rel_notes.mdx deleted file mode 100644 index d890387b3da..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_7_rel_notes.mdx +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.7 release notes" -navTitle: "Version 1.18.7" ---- - -Released: 18 Oct 2023 - -EDB Postgres for Kubernetes version 1.8.7 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -## Highlights of EDB Postgres for Kubernetes 1.8.7 - -- Changed the default value of `stopDelay` to 1800 seconds instead of 30 seconds -- Introduced a new parameter, called `smartShutdownTimeout`, to control the - window of time reserved for the smart shutdown of Postgres to complete; the - general formula to compute the overall timeout to stop Postgres is - `max(stopDelay - smartShutdownTimeout, 30)` -- Changed the default value of `startDelay` to 3600, instead of 30 seconds -- Replaced the livenessProbe initial delay with a more proper Kubernetes - startup probe to deal with the start of a Postgres server -- Changed the default value of `switchoverDelay` to 3600 seconds instead of - 40000000 seconds - -Additionally, this release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------ | -| Security fix | Added a default `seccompProfile` to the operator deployment. | | -| Enhancement | Introduced the `k8s.enterprisedb.io/coredumpFilter` annotation to control the content of a core dump generated in the unlikely event of a PostgreSQL crash, by default set to exclude shared memory segments from the dump. | -| Enhancement | Allowed configuration of ephemeral-storage limits for the shared memory and temporary data ephemeral volumes. | -| Enhancement | Validation of resource limits and requests through the webhook. | -| Enhancement | Ensure that PostgreSQL's `shared_buffers` are coherent with the pods' allocated memory resources. | -| Enhancement | Added `uri` and `jdbc-uri` fields in the credential secrets to facilitate developers when connecting their applications to the database. | -| Enhancement | Added a new phase, `Waiting for the instances to become active`, for finer control of a cluster's state waiting for the replicas to be ready. | -| Enhancement | Improved detection of Pod rollout conditions through the `podSpec` annotation. | -| Enhancement | Added primary timestamp and uptime to the kubectl plugin's `status` command. | -| Technical enhancement | Replaced `k8s-api-docgen` with `gen-crd-api-reference-docs` to automatically build the API reference documentation. | -| Bug fix | Ensure that the primary instance is always recreated first by prioritizing ready PVCs with a primary role. | -| Bug fix | Honor the `k8s.enterprisedb.io/skipEmptyWalArchiveCheck` annotation during recovery to bypass the check for an empty WAL archive. | -| Bug fix | prevent a cluster from being stuck when the PostgreSQL server is down but the pod is up on the primary. | -| Bug fix | Avoid treating the designated primary in a replica cluster as a regular HA replica when replication slots are enabled. | -| Bug fix | Reconcile services every time the selectors change or when labels/annotations need to be changed. | -| Bug fix | Default to `app` for both the owner and database during recovery bootstrap. | -| Bug fix | Avoid write-read concurrency on cached cluster. | -| Bug fix | Remove empty items, make them unique and sort in the `ResourceName` sections of the generated roles. | -| Bug fix | Ensure that the `ContinuousArchiving` condition is properly set to 'failed' in case of errors. | -| Bug fix | Reconcile PodMonitor `labels` and `annotations`. | -| Bug fix | Fixed backup failure due to missing RBAC `resourceNames` on the `Role` object. | -| Observability | Added TCP port label to default `pg_stat_replication` metric. | -| Observability | Fixed the `pg_wal_stat` default metric for Prometheus. | -| Observability | Improved the `pg_replication` default metric for Prometheus | -| Observability | Used `alertInstanceLabelFilter` instead of `alertName` in the provided Grafana dashboard | -| Observability | Enforce `standard_conforming_strings` in metric collection. | -| Change | Set the default operand image to PostgreSQL 16.0. | -| Change | Fencing now uses PostgreSQL's fast shutdown instead of smart shutdown to halt an instance. | -| Change | Rename webhooks from kb.io to k8s.enterprisedb.io group. | -| Change | Added the `k8s.enterprisedb.io/instanceRole` label and deprecated the existing `role` label. | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_8_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_8_rel_notes.mdx deleted file mode 100644 index af0ff22ea3c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_8_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.8 release notes" -navTitle: "Version 1.18.8" ---- - -Released: 08 Nov 2023 - -EDB Postgres for Kubernetes version 1.8.8 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------ | -| Enhancement | Enhanced the `status` command of the `cnp` plugin for `kubectl` with progress information on active streaming base backups. | -| Enhancement | Allowed the configuration of `max_prepared_statements` with the pgBouncer `Pooler` resource. | -| Technical Enhancement | Use extended query protocol for PostgreSQL in the instance manager. | -| Bug fix | Suspend WAL archiving during a switchover and resume it when it is completed. | -| Bug fix | Ensured that the instance manager always uses `synchronous_commit = local` when managing the PostgreSQL cluster. | -| Bug fix | Custom certificates for streaming replication user through `.spec.certificates.replicationTLSSecret` are now working. | -| Bug fix | Set the `k8s.enterprisedb.io/cluster` label to the `Pooler` pods. | -| Change | Stopped using the `postgresql.auto.conf` file inside PGDATA to control Postgres replication settings, and replace it with a file named `override.conf`. | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_9_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_9_rel_notes.mdx deleted file mode 100644 index e4b5da4c251..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_18_9_rel_notes.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.18.9 release notes" -navTitle: "Version 1.18.9" ---- - -Released: 22 Dec 2023 - -EDB Postgres for Kubernetes version 1.18.9 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Subsystem | Description | -| ------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------------ | -| Security | | By default, TLSv1.3 is now enforced on all PostgreSQL 12 or higher installations. Additionally, users can configure the `ssl_ciphers`, `ssl_min_protocol_version`, and `ssl_max_protocol_version` GUCs ([#3408](https://github.com/cloudnative-pg/cloudnative-pg/pull/3408)). | -| Security | | Integrated Docker image scanning with Dockle to enhance security measures. | -| Defaults | | Default operand image is now PostgreSQL 16.1 ([#3270](https://github.com/cloudnative-pg/cloudnative-pg/pull/3270)). | -| Enhancement | | Improved reconciliation of external clusters ([#3533](https://github.com/cloudnative-pg/cloudnative-pg/pull/3533)). | -| Enhancement | | Introduced the ability to enable/disable the `ALTER SYSTEM` command ([#3535](https://github.com/cloudnative-pg/cloudnative-pg/pull/3535)). | -| Enhancement | | Added support for Prometheus' dynamic relabeling through the `podMonitorMetricRelabelings` and `podMonitorRelabelings` options in the `.spec.monitoring` stanza of the `Cluster` and `Pooler` resources ([#3075](https://github.com/cloudnative-pg/cloudnative-pg/pull/3075)). | -| Enhancement | | Eliminated the use of the `PGPASSFILE` environment variable when establishing a network connection to PostgreSQL ([#3522](https://github.com/cloudnative-pg/cloudnative-pg/pull/3522)). | -| Enhancement | | Improved `cnp report` plugin command by collecting a cluster's PVCs ([#3357](https://github.com/cloudnative-pg/cloudnative-pg/pull/3357)). | -| Enhancement | Connection pooler | Scaling down instances of a `Pooler` resource to 0 is now possible ([#3517](https://github.com/cloudnative-pg/cloudnative-pg/pull/3517)). | -| Enhancement | Connection pooler | Added the `k8s.enterprisedb.io/podRole` label with a value of 'pooler' to every pooler deployment, differentiating them from instance pods ([#3396](https://github.com/cloudnative-pg/cloudnative-pg/pull/3396)). | -| Bug fix | | Reconciled metadata, annotations, and labels of `PodDisruptionBudget` resources ([#3312](https://github.com/cloudnative-pg/cloudnative-pg/pull/3312) and [#3434](https://github.com/cloudnative-pg/cloudnative-pg/pull/3434)). | -| Bug fix | | Reconciled the metadata of the managed credential secrets ([#3316](https://github.com/cloudnative-pg/cloudnative-pg/pull/3316)). | -| Bug fix | | Disabled wal_sender_timeout when joining through pg_basebackup ([#3586](https://github.com/cloudnative-pg/cloudnative-pg/pull/3586)). | -| Bug fix | | Secrets labeled `cnpg.io/reload=true` and used by external clusters are now reloaded when they change ([#3565](https://github.com/cloudnative-pg/cloudnative-pg/pull/3565)). | -| Bug fix | Connection pooler | Ensured the controller watches all secrets owned by a `Pooler` resource ([#3428](https://github.com/cloudnative-pg/cloudnative-pg/pull/3428)). | -| Bug fix | Connection pooler | Reconciled `RoleBinding` for `Pooler` resources ([#3391](https://github.com/cloudnative-pg/cloudnative-pg/pull/3391)). | -| Bug fix | Connection pooler | Reconciled `imagePullSecret` for `Pooler` resources ([#3389](https://github.com/cloudnative-pg/cloudnative-pg/pull/3389)). | -| Bug fix | Connection pooler | Reconciled the service of a `Pooler` and addition of the required labels ([#3349](https://github.com/cloudnative-pg/cloudnative-pg/pull/3349)). | -| Bug fix | Connection pooler | Extended `Pooler` labels to the deployment as well, not just the pods ([#3350](https://github.com/cloudnative-pg/cloudnative-pg/pull/3350)). | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_0_rel_notes.mdx deleted file mode 100644 index 695294d7f6e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_0_rel_notes.mdx +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.19.0 release notes" -navTitle: "Version 1.19.0" ---- - -Released: 14 Feb 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.19.0. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/). | -| Feature | Support for [Transparent Data Encryption (TDE)](/tde/latest) with EDB Postgres Advanced Server 15. TDE encrypts, transparently to the user, any user data stored in the database system. | -| Feature | New external backup adaptor to provide a generic way to integrate EDB Postgres for Kubernetes in a third-party tool for backups. See [External Backup Adapter](/postgres_for_kubernetes/latest/addons/#external-backup-adapter) for more information.| \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_1_rel_notes.mdx deleted file mode 100644 index 1b4c16dd1ae..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_1_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.19.1 release notes" -navTitle: "Version 1.19.1" ---- - -Released: 20 Mar 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.19.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_2_rel_notes.mdx deleted file mode 100644 index 5ebbe052a43..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_2_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.19.2 release notes" -navTitle: "Version 1.19.2" ---- - -Released: 27 Apr 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.19.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_3_rel_notes.mdx deleted file mode 100644 index b7f88cc4aaf..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_3_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.19.3 release notes" -navTitle: "Version 1.19.3" ---- - -Released: 13 Jun 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.19.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_4_rel_notes.mdx deleted file mode 100644 index 368881e60e9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_4_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.19.4 release notes" -navTitle: "Version 1.19.4" ---- - -Released: 27 Jul 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.19.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_5_rel_notes.mdx deleted file mode 100644 index b001f090e99..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_5_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.19.5 release notes" -navTitle: "Version 1.19.5" ---- - -Released: 18 Oct 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.19.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_6_rel_notes.mdx deleted file mode 100644 index f1f585533e3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_19_6_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.19.6 release notes" -navTitle: "Version 1.19.6" ---- - -Released: 08 Nov 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.19.6. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_1_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_1_0_rel_notes.mdx deleted file mode 100644 index 002e64742bd..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_1_0_rel_notes.mdx +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.1 release notes" -navTitle: "Version 1.1" ---- - -Released: 03 Mar 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Add kubectl cnp status to pretty-print the status of a cluster, including JSON and YAML output. | -| Feature | Add kubectl cnp certificate to enable TLS authentication for client applications. | -| Feature | Add the -ro service to route connections to the available hot standby replicas only, enabling offload of read-only queries from the cluster's primary instance. | -| Feature | Rollback scaling down a cluster to a value lower than maxSyncReplicas. | -| Feature | Request a checkpoint before demoting a former primary. | -| Feature | Send SIGINT signal (fast shutdown) to PostgreSQL process on SIGTERM. | - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_0_rel_notes.mdx deleted file mode 100644 index a87d077d125..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_0_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.20.0 release notes" -navTitle: "Version 1.20.0" ---- - -Released: 27 Apr 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.20.0. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_1_rel_notes.mdx deleted file mode 100644 index 867b600abfe..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_1_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.20.1 release notes" -navTitle: "Version 1.20.1" ---- - -Released: 13 Jun 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.20.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_2_rel_notes.mdx deleted file mode 100644 index 9a2881ae2d6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_2_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.20.2 release notes" -navTitle: "Version 1.20.2" ---- - -Released: 27 Jul 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.20.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_3_rel_notes.mdx deleted file mode 100644 index c81b64311b0..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_3_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.20.3 release notes" -navTitle: "Version 1.20.3" ---- - -Released: 18 Oct 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.20.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_4_rel_notes.mdx deleted file mode 100644 index 41132f6ce52..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_4_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.20.4 release notes" -navTitle: "Version 1.20.4" ---- - -Released: 08 Nov 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.20.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_5_rel_notes.mdx deleted file mode 100644 index 0f3a5c4a8c7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_5_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.20.5 release notes" -navTitle: "Version 1.20.5" ---- - -Released: 22 Dec 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.20.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_6_rel_notes.mdx deleted file mode 100644 index bb4e630e82a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_20_6_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.20.6 release notes" -navTitle: "Version 1.20.6" ---- - -Released: 02 Feb 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.20.6. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_0_rel_notes.mdx deleted file mode 100644 index 664a0860063..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_0_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.21.0 release notes" -navTitle: "Version 1.21.0" ---- - -Released: 18 Oct 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.21.0. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_1_rel_notes.mdx deleted file mode 100644 index 5b514573b76..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_1_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.21.1 release notes" -navTitle: "Version 1.21.1" ---- - -Released: 08 Nov 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.21.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_2_rel_notes.mdx deleted file mode 100644 index 50e9b856724..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_2_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.21.2 release notes" -navTitle: "Version 1.21.2" ---- - -Released: 22 Dec 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.21.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_3_rel_notes.mdx deleted file mode 100644 index 2b8d3263be1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_3_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.21.3 release notes" -navTitle: "Version 1.21.3" ---- - -Released: 02 Feb 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.21.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_4_rel_notes.mdx deleted file mode 100644 index 7b47b483197..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_4_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.21.4 release notes" -navTitle: "Version 1.21.4" ---- - -Released: 22 Mar 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.21.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_5_rel_notes.mdx deleted file mode 100644 index d5a20196c71..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_5_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.21.5 release notes" -navTitle: "Version 1.21.5" ---- - -Released: 23 Apr 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.21.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_6_rel_notes.mdx deleted file mode 100644 index 7bbd3587935..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_21_6_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.21.6 release notes" -navTitle: "Version 1.21.6" ---- - -Released: 13 Jun 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.21.6. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_0_rel_notes.mdx deleted file mode 100644 index ce94033da1d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_0_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.0 release notes" -navTitle: "Version 1.22.0" ---- - -Released: 22 Dec 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.22.0. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_10_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_10_rel_notes.mdx deleted file mode 100644 index ce1599ffa8e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_10_rel_notes.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.22.10 release notes -navTitle: Version 1.22.10 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.22.10_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 23 May 2025 - -EDB Postgres for Kubernetes version 1.22.10 is an LTS release of EDB Postgres for Kubernetes; -there is no corresponding upstream release of CloudNativePG. - -!!! Warning - A new LTS release, version 1.25.2, is now available! - Please note that support for 1.22 will officially end on July 2025. - - We recommend starting your upgrade planning now to transition smoothly to - the 1.25 LTS release. - -This release of EDB CloudNativePG Cluster includes the following: - -## Enhancements - - - - - -
DescriptionAddresses
Implemented the k8s.enterprisedb.io/validation annotation

...enabling users to disable -the validation webhook on EDB Postgres for Kubernetes-managed resources. Use with caution, -as this allows unrestricted changes.

-
#7196
Added support for collecting `pg_stat_wal` metrics in PostgreSQL 18#7005
Added support for LZ4, XZ, and Zstandard compression methods

...when archiving -WAL files via Barman Cloud (deprecated).

-
#7151
- - -## Security Fixes - - - -
DescriptionAddresses
Set imagePullPolicy to Always for the operator deployment

...to ensure that images are always pulled from the registry, reducing the risk of using -outdated or potentially unsafe local images.

-
#7250
- - -## Changes - - - - -
DescriptionAddresses
Updated the default PostgreSQL version to 17.5 for new cluster definitions.#7556
Updated the default PgBouncer version to **1.24.1** for new `Pooler` deployments.#7399
- - -## Bug Fixes - - - - - - - - - -
DescriptionAddresses
Fixed native replication slot synchronization and logical replication failover for PostgreSQL 17

...by appending the dbname parameter to primary_conninfo in replica configurations.

-
#7298
Improved backup efficiency by introducing a fail-fast mechanism in WAL archiving

...allowing quicker detection of unexpected primary demotion and avoiding unnecessary retries.

-
#7483
Fixed an off-by-one error in parallel WAL archiving

...that could cause one extra worker process to be spawned beyond the requested number.

-
#7389
Resolved a race condition that caused the operator to perform two switchovers when updating the PostgreSQL configuration.#6991
Corrected the PodMonitor configuration by adjusting the matchLabels scope for the targeted pooler and cluster pods.

Previously, the matchLabels were too broad, inadvertently inheriting labels from the cluster and leading to data collection from unintended targets.

-
#7063
Added a webhook warning for clusters with a missing unit (e.g., MB, GB) in the shared_buffers configuration.

This will become an error in future releases. Users should update their configurations to include explicit units (e.g., 512MB instead of 512).

-
#7160
`cnp` plugin: ensured that the primary Pod is recreated during an imperative restart when `primaryUpdateMethod` is set to `restart`, aligning its definition with the replicas. -#7122
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_11_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_11_rel_notes.mdx deleted file mode 100644 index 3c6121f4e5b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_11_rel_notes.mdx +++ /dev/null @@ -1,50 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.22.11 release notes -navTitle: Version 1.22.11 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.22.11_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 25 July 2025 - -EDB Postgres for Kubernetes version 1.22.11 is an LTS release of EDB Postgres for Kubernetes; -there is no corresponding upstream release of CloudNativePG. - -*In memory of [DJ Walker-Morgan](https://www.linkedin.com/in/codepope/).* - -!!! Warning - This is expected to be the last release in the 1.22.x series. - Users are strongly encouraged to upgrade to a newer minor version, as 1.22 - is no longer supported. - -This release of EDB CloudNativePG Cluster includes the following: - -## Enhancements - - - - - -
DescriptionAddresses
Improved validation of shared_buffers by correctly considering HugePages settings

...ensuring accurate memory configuration checks.

-
#7864
Set oom_score_adj for PostgreSQL worker processes

...to improve prioritization during out-of-memory situations.

-
#7891
Added the systemID field and related condition in the Cluster status

...to track the PostgreSQL system identifier.

-
#7717
- - -## Changes - - - -
DescriptionAddresses
Removed 386 and ARM (v5/v6/v7) architectures from the cnp plugin build matrix

...reducing the number of published binaries.

-
#7648
- - -## Bug Fixes - - - -
DescriptionAddresses
Added a mutex in the connection pooler to protect concurrent access to the connections map

...improving stability in high-concurrency environments.

-
#7804
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_1_rel_notes.mdx deleted file mode 100644 index ff58a153b43..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_1_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.1 release notes" -navTitle: "Version 1.22.1" ---- - -Released: 02 Feb 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.22.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_2_rel_notes.mdx deleted file mode 100644 index 928b8f5281e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_2_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.2 release notes" -navTitle: "Version 1.22.2" ---- - -Released: 22 Mar 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.22.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_3_rel_notes.mdx deleted file mode 100644 index 9a4a4dd8147..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_3_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.3 release notes" -navTitle: "Version 1.22.3" ---- - -Released: 24 Apr 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.22.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_4_rel_notes.mdx deleted file mode 100644 index 895e2baf0ea..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_4_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.4 release notes" -navTitle: "Version 1.22.4" ---- - -Released: 13 Jun 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.22.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_5_rel_notes.mdx deleted file mode 100644 index c502be6dc38..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_5_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.5 release notes" -navTitle: "Version 1.22.5" ---- - -Released: 01 Aug 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.22.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_6_rel_notes.mdx deleted file mode 100644 index 04a105214bb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_6_rel_notes.mdx +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.6 release notes" -navTitle: "Version 1.22.6" ---- - -Released: 26 Aug 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -### Features - -* **Configuration of Pod Disruption Budgets (PDB)**: Introduced the `.spec.enablePDB` field to disable PDBs on the primary instance, allowing proper eviction of the pod during maintenance operations. This is particularly useful for single-instance deployments. This feature is intended to replace the node maintenance window feature. - -### Enhancements - -* **cnp plugin updates**: - * Enhance the install generate command by adding a --control-plane option, allowing deployment of the operator on control-plane nodes by setting node affinity and tolerations (\#5271). - * Enhance the destroy command to delete also any job related to the target instance (\#5298). - -### Fixes - -* Synchronous replication self-healing checks now exclude terminated pods, focusing only on active and functional pods (\#5210). -* The instance manager will now terminate all existing operator-related replication connections following a role change in a replica cluster (\#5209). -* Allow setting smartShutdownTimeout to zero, enabling immediate fast shutdown and bypassing the smart shutdown process when required (\#5347). \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_7_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_7_rel_notes.mdx deleted file mode 100644 index 64936aa632c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_7_rel_notes.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.7 release notes" -navTitle: "Version 1.22.7" ---- - -Released: 18 Oct 2024 - -EDB Postgres for Kubernetes version 1.22.7 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -This release of EDB Postgres for Kubernetes includes the following: - -### Enhancements: - - - Remove the use of `pg_database_size` from the status probe, as it caused high resource utilization by scanning the entire `PGDATA` directory to compute database sizes. The `kubectl status` plugin will now rely on `du` to provide detailed size information retrieval (\#5689). - - Add the ability to configure the `full_page_writes` parameter in PostgreSQL. This setting defaults to `on`, in line with PostgreSQL's recommendations (\#5516). - - Plugin: - - Add the `logs pretty` command in the `cnp` plugin to read a log stream from standard input and output a human-readable format, with options to filter log entries (\#5770) - - Enhance the `status` command by allowing multiple `-v` options to increase verbosity for more detailed output (\#5765). - - Add support for specifying a custom Docker image using the `--image` flag in the `pgadmin4` plugin command, giving users control over the Docker image used for pgAdmin4 deployments (\#5515). - -### Fixes: - - - Ensure that replica PodDisruptionBudgets (PDB) are removed when scaling down to two instances, enabling easier maintenance on the node hosting the replica (\#5487). - - Prioritize full rollout over inplace restarts (\#5407). - - Fix an issue that could lead to double failover in cases of lost connectivity (\#5788). - - Correctly set the `TMPDIR` and `PSQL_HISTORY` environment variables for pods and jobs, improving temporary file and history management (\#5503). - - Plugin: - - Resolve a race condition in the `logs cluster` command (\#5775). - - Display the `potential` sync status in the `status` plugin (\#5533). - - Fix the issue where pods deployed by the `pgadmin4` command didn’t have a writable home directory (\#5800). - -### Supported versions - - - PostgreSQL 17 (PostgreSQL 17.0 is the default image) \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_8_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_8_rel_notes.mdx deleted file mode 100644 index cb7c9f2fccb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_8_rel_notes.mdx +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.8 release notes" -navTitle: "Version 1.22.8" ---- - -Released: 23 Dec 2024 - -EDB Postgres for Kubernetes version 1.22.8 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -!!! Warning - A new LTS release, version 1.25.0, is now available! - Please note that support for 1.22 will officially end on July 2025. - - We recommend starting your upgrade planning now to transition smoothly to - the 1.25 LTS release. - -This release of EDB Postgres for Kubernetes includes the following: - -### Enhancements - -- Enable customization of startup, liveness, and readiness probes through the - `.spec.probes` stanza. ([#6266](https://github.com/cloudnative-pg/cloudnative-pg/pull/6266)) -- Add the `cnpg.io/userType` label to secrets generated for predefined users, - specifically `superuser` and `app`. ([#4392](https://github.com/cloudnative-pg/cloudnative-pg/pull/4392)) -- Improved validation for the `spec.schedule` field in ScheduledBackups, - raising warnings for potential misconfigurations. ([#5396](https://github.com/cloudnative-pg/cloudnative-pg/pull/5396)) -- `cnpg` plugin: - - Honor the `User-Agent` header in HTTP requests with the API server. ([#6153](https://github.com/cloudnative-pg/cloudnative-pg/pull/6153)) - -### Bug Fixes - -- Ensure the former primary flushes its WAL file queue to the archive before - re-synchronizing as a replica, reducing recovery times and enhancing data - consistency during failovers. ([#6141](https://github.com/cloudnative-pg/cloudnative-pg/pull/6141)) -- Clean the WAL volume along with the `PGDATA` volume during bootstrap. ([#6265](https://github.com/cloudnative-pg/cloudnative-pg/pull/6265)) -- Update the operator to set the cluster phase to `Unrecoverable` when - all previously generated `PersistentVolumeClaims` are missing. ([#6170](https://github.com/cloudnative-pg/cloudnative-pg/pull/6170)) -- Fix the parsing of the `synchronous_standby_names` GUC when - `.spec.postgresql.synchronous.method` is set to `first`. ([#5955](https://github.com/cloudnative-pg/cloudnative-pg/pull/5955)) -- Resolved a potential race condition when patching certain conditions - in CRD statuses, improving reliability in concurrent updates. ([#6328](https://github.com/cloudnative-pg/cloudnative-pg/pull/6328)) -- Correct role changes to apply at the transaction level instead of the - database context. ([#6064](https://github.com/cloudnative-pg/cloudnative-pg/pull/6064)) -- Remove the `primary_slot_name` definition from the `override.conf` file on - the primary to ensure it is always empty. ([#6219](https://github.com/cloudnative-pg/cloudnative-pg/pull/6219)) -- Configure libpq environment variables, including `PGHOST`, in PgBouncer pods - to enable seamless access to the `pgbouncer` virtual database using `psql` - from within the container. ([#6247](https://github.com/cloudnative-pg/cloudnative-pg/pull/6247)) -- Prevent panic during recovery from an external server without proper backup - configuration. ([#6300](https://github.com/cloudnative-pg/cloudnative-pg/pull/6300)) -- Resolved a key collision issue in structured logs, where the name field was - inconsistently used to log two distinct values. ([#6324](https://github.com/cloudnative-pg/cloudnative-pg/pull/6324)) -- Ensure proper quoting of the inRoles field in SQL statements to prevent - syntax errors in generated SQL during role management. ([#6346](https://github.com/cloudnative-pg/cloudnative-pg/pull/6346)) -- `cnpg` plugin: - - Ensure the `kubectl` context is properly passed in the `psql` command. ([#6257](https://github.com/cloudnative-pg/cloudnative-pg/pull/6257)) - - Avoid displaying physical backups block when empty with `status` command. ([#5998](https://github.com/cloudnative-pg/cloudnative-pg/pull/5998)) diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_9_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_9_rel_notes.mdx deleted file mode 100644 index cbb92f04898..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_22_9_rel_notes.mdx +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.22.9 release notes" -navTitle: "Version 1.22.9" ---- - -Released: 04 Mar 2025 - -EDB Postgres for Kubernetes version 1.22.9 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG. - -!!! Warning - A new LTS release, version 1.25.1, is now available! - Please note that support for 1.22 will officially end on July 2025. - - We recommend starting your upgrade planning now to transition smoothly to - the 1.25 LTS release. - -This release of EDB Postgres for Kubernetes includes the following: - -### Enhancements - -- Introduced a startup probe for the operator to enhance reliability and - prevent premature liveness probe failures during initialization. ([#7008](https://github.com/cloudnative-pg/cloudnative-pg/pull/7008)) -- Added support for using the `-r` service with the Pooler. ([#6868](https://github.com/cloudnative-pg/cloudnative-pg/pull/6868)) -- Introduced an optional `--ttl` flag for the `pgbench` plugin, enabling - automatic deletion of completed jobs after a user-defined duration. ([#6701](https://github.com/cloudnative-pg/cloudnative-pg/pull/6701)) -- Updated the default PostgreSQL version to 17.4 for new cluster - definitions. ([#6960](https://github.com/cloudnative-pg/cloudnative-pg/pull/6960)) - -### Security - -- The operator image build process has been enhanced to strengthen - security and transparency. Images are now signed with `cosign`, and - OCI attestations are generated, incorporating the Software Bill of - Materials (SBOM) and provenance data. Additionally, OCI annotations - have been added to improve traceability and ensure the integrity of - the images. - -### Bug Fixes - -- Fixed inconsistent behavior in default probe knob values when `.spec.probes` - is defined, ensuring users can override all settings, including - `failureThreshold`. If unspecified in the startup probe, `failureThreshold` is - now correctly derived from `.spec.startupDelay / periodSeconds` (default: `10`, - now overridable). The same logic applies to liveness probes via - `.spec.livenessProbeTimeout`. ([#6656](https://github.com/cloudnative-pg/cloudnative-pg/pull/6656)) -- Fixed an issue where WAL metrics were unavailable after an instance restart - until a configuration change was applied. ([#6816](https://github.com/cloudnative-pg/cloudnative-pg/pull/6816)) -- Fixed an issue in monolithic database import where role import was skipped if - no roles were specified. ([#6646](https://github.com/cloudnative-pg/cloudnative-pg/pull/6646)) -- Added support for new metrics introduced in PgBouncer 1.24. ([#6630](https://github.com/cloudnative-pg/cloudnative-pg/pull/6630)) -- Improved handling of replication-sensitive parameter reductions by ensuring - timely reconciliation after primary server restarts. ([#6440](https://github.com/cloudnative-pg/cloudnative-pg/pull/6440)) -- Ensured `override.conf` is consistently included in `postgresql.conf` during - replica cluster bootstrapping, preventing replication failures due to missing - configuration settings. ([#6808](https://github.com/cloudnative-pg/cloudnative-pg/pull/6808)) -- Ensured `override.conf` is correctly initialized before invoking `pg_rewind` - to prevent failures during primary role changes. ([#6670](https://github.com/cloudnative-pg/cloudnative-pg/pull/6670)) -- Enhanced webhook responses to return both warnings and errors when - applicable, improving diagnostic accuracy. ([#6579](https://github.com/cloudnative-pg/cloudnative-pg/pull/6579)) -- Ensured the operator version is correctly reconciled. ([#6496](https://github.com/cloudnative-pg/cloudnative-pg/pull/6496)) -- Improved PostgreSQL version detection by using a more precise check of the - data directory. ([#6659](https://github.com/cloudnative-pg/cloudnative-pg/pull/6659)) -- Volume Snapshot Backups: - - Fixed an issue where unused backup connections were not properly cleaned - up. ([#6882](https://github.com/cloudnative-pg/cloudnative-pg/pull/6882)) - - Ensured the instance manager closes stale PostgreSQL connections left by - failed volume snapshot backups. ([#6879](https://github.com/cloudnative-pg/cloudnative-pg/pull/6879)) - - Prevented the operator from starting a new volume snapshot backup while - another is already in progress. ([#6890](https://github.com/cloudnative-pg/cloudnative-pg/pull/6890)) -- `cnp` plugin: - - Restored functionality of the `promote` plugin command. ([#6476](https://github.com/cloudnative-pg/cloudnative-pg/pull/6476)) - - Enhanced `kubectl cnp report --logs ` to collect logs from all - containers, including sidecars. ([#6636](https://github.com/cloudnative-pg/cloudnative-pg/pull/6636)) - - Ensured `pgbench` jobs can run when a `Cluster` uses an `ImageCatalog`. - ([#6868](https://github.com/cloudnative-pg/cloudnative-pg/pull/6868)) - -### Technical Enhancements - -- Added support for Kubernetes `client-gen`, enabling automated generation of - Go clients for all EDB Postgres for Kubernetes CRDs. ([#6695](https://github.com/cloudnative-pg/cloudnative-pg/pull/6695)) diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_0_rel_notes.mdx deleted file mode 100644 index 30216ae16d7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_0_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.23.0 release notes" -navTitle: "Version 1.23.0" ---- - -Released: 24 Apr 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.23.0. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_1_rel_notes.mdx deleted file mode 100644 index eb4b0676f33..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_1_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.23.1 release notes" -navTitle: "Version 1.23.1" ---- - -Released: 29 Apr 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.23.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_2_rel_notes.mdx deleted file mode 100644 index 23aa5e037a5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_2_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.23.2 release notes" -navTitle: "Version 1.23.2" ---- - -Released: 13 Jun 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.23.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_3_rel_notes.mdx deleted file mode 100644 index b1c7a4f3d7d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_3_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.23.3 release notes" -navTitle: "Version 1.23.3" ---- - -Released: 01 Aug 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.23.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_4_rel_notes.mdx deleted file mode 100644 index f317c3aa54e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_4_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.23.4 release notes" -navTitle: "Version 1.23.4" ---- - -Released: 26 Aug 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.23.4. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_5_rel_notes.mdx deleted file mode 100644 index f7cb004793e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_5_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.23.5 release notes" -navTitle: "Version 1.23.5" ---- - -Released: 18 Oct 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.23.5. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_6_rel_notes.mdx deleted file mode 100644 index 41edcf6f2c5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_23_6_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.23.6 release notes" -navTitle: "Version 1.23.6" ---- - -Released: 23 Dec 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.23.6. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_0_rel_notes.mdx deleted file mode 100644 index a2e98f6dbb6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_0_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.24.0 release notes" -navTitle: "Version 1.24.0" ---- - -Released: 26 Aug 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.24.0. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_1_rel_notes.mdx deleted file mode 100644 index 1e826cb3ea3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_1_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.24.1 release notes" -navTitle: "Version 1.24.1" ---- - -Released: 18 Oct 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.24.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_2_rel_notes.mdx deleted file mode 100644 index a75ecc2ba5c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_2_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.24.2 release notes" -navTitle: "Version 1.24.2" ---- - -Released: 23 Dec 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.24.2. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_3_rel_notes.mdx deleted file mode 100644 index a91f47299dd..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_3_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.24.3 release notes" -navTitle: "Version 1.24.3" ---- - -Released: 04 Mar 2025 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.24.3. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_4_rel_notes.mdx deleted file mode 100644 index ef7782f04f7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_24_4_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.24.4 release notes -navTitle: Version 1.24.4 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.24.4_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 23 May 2025 - -This release of EDB CloudNativePG Cluster includes the following: - -## Changes - - - -
DescriptionAddresses
Merged with community CloudNativePG 1.24.4 upstream release. -See the community release notes -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_0_rel_notes.mdx deleted file mode 100644 index 7200447247a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_0_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.25.0 release notes" -navTitle: "Version 1.25.0" ---- - -Released: 23 Dec 2024 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.25.0. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_1_rel_notes.mdx deleted file mode 100644 index 3c1cb98b7c0..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_1_rel_notes.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.25.1 release notes" -navTitle: "Version 1.25.1" ---- - -Released: 04 Mar 2025 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Upstream merge | Merged with community CloudNativePG 1.25.1. See the community [Release Notes](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/). | diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_2_rel_notes.mdx deleted file mode 100644 index 304911eff0a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_2_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.25.2 release notes -navTitle: Version 1.25.2 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.2_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 23 May 2025 - -This release of EDB CloudNativePG Cluster includes the following: - -## Changes - - - -
DescriptionAddresses
Merged with community CloudNativePG 1.25.2 upstream release. -See the community release notes -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_3_rel_notes.mdx deleted file mode 100644 index df1de1a6ee6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_3_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.25.3 release notes -navTitle: Version 1.25.3 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.3_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 25 July 2025 - -This release of EDB CloudNativePG Cluster includes the following: - -## Changes - - - -
DescriptionAddresses
Merged with community CloudNativePG 1.25.3 upstream release. -See the community release notes -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_4_rel_notes.mdx deleted file mode 100644 index 095319e54d0..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_4_rel_notes.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.25.4 release notes -navTitle: Version 1.25.4 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.4_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 24 October 2025 - -This release of EDB CloudNativePG Cluster is built on the final community release of the 1.25.x series of CloudNativePG. -EDB will continue providing LTS releases in the 1.25.x series for the next 12 months, per our [Long-Term Support -policy](/postgres_for_kubernetes/1/#long-term-support). - -This release of EDB CloudNativePG Cluster includes the following: - -## Changes - - - -
DescriptionAddresses
Merged with community CloudNativePG 1.25.4 upstream release. -See the community release notes -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_5_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_5_rel_notes.mdx deleted file mode 100644 index 018c6efddfb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_5_rel_notes.mdx +++ /dev/null @@ -1,84 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.25.5 release notes -navTitle: Version 1.25.5 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.5_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 16 December 2025 - -This release of EDB CloudNativePG Cluster is built on the final community release of the 1.25.x series of CloudNativePG. -EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support -policy](/postgres_for_kubernetes/1/#long-term-support). - -This release of EDB CloudNativePG Cluster includes the following: - -## Highlights - -We've consolidated our [private container registry](../private_edb_registries) into a single location. This change simplifies access and deployment. -Starting with v1.25.5, any customer attempting an operator upgrade, MUST configure the new unified repository pull secret! -For details and instructions, follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/). - -## Enhancements - - - - -
DescriptionAddresses
Added support for 1.28 CRD fields, bringing forward compatibility improvements -from the 1.28 release. -

This includes enhanced Database CRD with foreign data wrapper support, -improved cluster security contexts, failover quorum configurations, TLS -configurations for Pooler, and the majorVersion field in Backup -resources.

-
1109
Improved `cnp report` to generate more shell-friendly file names. -#8984
- - -## Changes - - - - -
DescriptionAddresses
Updated the default PostgreSQL version to `18.1-standard-ubi9`. -#9178
Updated the default PgBouncer version to **1.25.1**, which carries -a fix for **CVE-2025-12819**, for new Pooler deployments. -#9367
- - -## Bug Fixes - - - - - - - - - -
DescriptionAddresses
Fixed the CheckEmptyWalArchive safeguard to run correctly when restoring -from a volume snapshot using CNP-I backup/WAL plugins (e.g., -plugin-barman-cloud). -

Previously, this check was skipped for plugin-based implementations.

-
#9306
Fixed TLS certificate verification issues when connecting to CNP-I plugins -by adding the k8s.enterprisedb.io/pluginServerName annotation. -

This allows customizing the DNS name used for certificate verification in -environments where the plugin's certificate uses a different DNS name than -the Service name.

-
#9222
Fixed an issue where the instance manager controller could fail to restart -after an error, reporting a "controller already exists" message. -

The controller now uses SkipNameValidation for subsequent initialization -attempts. -Contributed by @mateusoliveira43.

-
#9123
Fixed incorrect WAL restore path handling in plugins when the destination -path is absolute, preventing path duplication issues. -

Contributed by @Endevir.

-
#9093
Fixed the CREATE PUBLICATION SQL generation for multi-table publications to be backward-compatible with PostgreSQL 13+. -

The previously generated syntax -was only valid for PostgreSQL 15+ and caused syntax errors on older versions.

-
#8888
Fixed backup failures in complex pod definitions by reliably selecting the `postgres` container by name instead of by index. -#8964
cnp plugin: Fixed bugs in cnp report log collection, especially when fetching previous logs. -

The collector now correctly fetches previous and current logs in separate requests and gracefully handles missing previous logs (e.g., on containers with no restart history), ensuring current logs are always collected.

-
#8992
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_6_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_6_rel_notes.mdx deleted file mode 100644 index 284a29f65d6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_6_rel_notes.mdx +++ /dev/null @@ -1,100 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.25.6 release notes -navTitle: Version 1.25.6 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.6_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 10 February 2026 - -This release of EDB CloudNativePG Cluster is built on the final community release of the 1.25.x series of CloudNativePG. -EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support -policy](/postgres_for_kubernetes/1/#long-term-support). - -This release of EDB CloudNativePG Cluster includes the following: - -## Enhancements - - - -
DescriptionAddresses
Added support for Azure's DefaultAzureCredential authentication mechanism -for backup and recovery operations. -

This can be enabled by setting -azureCredentials.useDefaultAzureCredentials: true in the backup -configuration, simplifying authentication in Azure environments without -requiring explicit storage account keys or SAS tokens.

-
#9468
- - -## Bug Fixes - - - - - - - - - - - - - - - - - -
DescriptionAddresses
Fixed a bug where replicas could enter a crash-loop by attempting to download -timeline history files from future timelines. -

This occurred when stale files -remained in the WAL archive from a previous cluster life, and replicas would -incorrectly try to fetch them during recovery.

-
#9650
Fixed a race condition in `replica_cluster` setups during designated primary -transitions, preventing transient "no primary" states in the replica cluster. -#9601
Fixed a validation gap in Azure object store configurations where the -storageAccount was not required when using explicit credentials (such as a -storage key or SAS token). -

The operator now enforces that a storage account -name is provided in these cases and that connectionString is mutually -exclusive with other authentication parameters.

-
#9604
Optimized the deletion path so the operator begins cleaning up resources -immediately when a cluster is marked for deletion. -

This significantly reduces the time a cluster remains in Terminating status -while waiting for internal reconciliation loops.

-
#9555
Fixed an issue where replication slots were not properly dropped from -replicas when the feature was disabled or the cluster was reconfigured. -

This ensures that unused slots do not cause WAL build-up on the primary.

-
#9381
Fixed an issue where imagePullSecrets were not added to the ServiceAccount -created for the Pooler. -

Previously, these secrets were applied to the -Deployment but not the SA, which caused image pull failures in restricted -environments using certain security policies.

-
#9427
Added a check to verify ownership before the operator deletes a PodMonitor. -

This prevents the operator from accidentally deleting manually managed -monitoring resources that happen to share a name with expected CNP -resources. Contributed by @juliamertz.

-
#9340
Fixed a bug where pg_stat_archiver metrics would continue to report stale -data on standby instances after a switchover. -

The exporter now skips these metrics on standbys, as PostgreSQL only provides -valid archiver stats on the primary.

-
#9411
Clarified the interpretation of timestamp formats for recovery targetTime. -

Timestamps provided without an explicit timezone are now consistently -interpreted as UTC. Contributed by @pchovelon.

-
#8937
Fixed backup status updates to prevent "resource has been modified" errors -during concurrent updates. -#9551
Fixed event reporting to use the correct pod name when a backup pod is not -found. -#9552
Improved performance of scheduled backup operations for clusters with a very -high number of historical backups. -#9489
Fixed error handling when removing finalizers on `Database` objects. -#9431
Updated the status command to display "Disabled" when the -skipWalArchiving annotation is present on a cluster. -

This replaces -confusing "starting up" or "unknown" states when WAL archiving is -intentionally bypassed.

-
#9709
Fixed the `logs --follow` command to continue polling for new pods instead -of exiting prematurely when all current log streams complete. -#9599
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_7_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_7_rel_notes.mdx deleted file mode 100644 index 72276bc448d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_7_rel_notes.mdx +++ /dev/null @@ -1,122 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.25.7 release notes -navTitle: Version 1.25.7 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.7_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 2 April 2026 - -This release of EDB CloudNativePG Cluster is built on the final community release of the 1.25.x series of CloudNativePG. -EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support -policy](/postgres_for_kubernetes/1/#long-term-support). - -!!! Warning EDB CloudNativePG Cluster 1.25 reaches End-of-Life in June 2026. - -Users are encouraged to start planning their upgrade to a newer minor -version before that date. - -!!! - -This release of EDB CloudNativePG Cluster includes the following: - -## Enhancements - - - - - -
DescriptionAddresses
Improved the Pooler CRD with support for granular configuration of TLS -cipher suites and minimum/maximum TLS versions. -

This enables administrators -to meet strict security compliance requirements for pooler-to-client and -pooler-to-server connections. -Contributed by @alex1989hu.

-
#9571
Improved role management by verifying the instance is the primary before -each reconciliation cycle -

...avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas.

-
#9971
The operator now honors the `primaryUpdateMethod` when adding new PVCs to a -cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is -respected during storage expansion or additions. -#9720
- - -## Security Fixes - - - - - -
DescriptionAddresses
Security best practices integration**: integrated the OpenSSF baseline -scanner and added a `SECURITY-INSIGHTS.yaml` file to the repository to align -with industry-standard security reporting. -#10054, #10062
SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software -Artifacts) provenance to release binaries and container images. -

Additionally, -enabled Software Bill of Materials (SBOM) generation within the GoReleaser -pipeline for improved dependency transparency.

-
#10048, #10074
Password leak prevention**: fixed a potential security risk where PostgreSQL -could leak role passwords in the logs during specific reconciliation phases. -#9950
- - -## Changes - - - -
DescriptionAddresses
Updated the default PostgreSQL version to 18.3 (image `18.3-standard-ubi9`). -#10090
- - -## Bug Fixes - - - - - - - - - - - - -
DescriptionAddresses
Fixed an issue where replicas would get stuck in a Pending state if the -VolumeSnapshot used for the initial bootstrap had been deleted. -

The operator now validates snapshot existence before use; if a snapshot is missing, -it attempts to use the next available candidate or falls back to -pg_basebackup.

-
#10192
Prevented the "supervised primary" rollout strategy from consuming all -available rollout slots, which previously caused delays in scheduled updates. -Contributed by @ermakov-oleg. -#9977
Fixed an issue where certain hot-standby parameter changes were not being -correctly applied to replica clusters. -#9952
Fixed webhook validation of bootstrap recovery sources to accept external -clusters configured with ConnectionParameters (for pg_basebackup-based -recovery). -

Previously, these were incorrectly rejected unless a Barman -object store or CNPG-i plugin was also configured.

-
#10268
When hibernating a non-healthy cluster, the operator now reports a -`WaitingForHealthy` condition, making the deferred hibernation state visible -#10193
Fixed fencing to work correctly even when the target pod does not exist. -

Fencing operates on a cluster-level annotation and should not depend on pod -existence; instance name validation is now performed only in the cnp fencing on command.

-
#10035
Fixed the cluster and pooler service reconcilers to correctly handle changes -to all spec fields when using the patch update strategy. The reconciler now -uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields -(such as `loadBalancerClass`) from being inadvertently removed. -#10190, #10311
Fixed a race condition in the deprecated in-tree Barman Cloud backup -implementation affecting parallel WAL restore, where prefetched files could -be read while still being downloaded, causing PostgreSQL recovery to fail -with "invalid checkpoint record" errors. -#10285
Fixed the timeline history file validation to also apply to plugin-based WAL restore. -

Previously, the protection introduced in -#9650 only -covered in-tree restores, allowing plugins to bypass the check and download -future timeline history files, causing timeline mismatch errors on replicas.

-
#9849
The cnp plugin now correctly propagates ImagePullSecrets to the - `pgbench` Job pod template. -#10174
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_8_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_8_rel_notes.mdx deleted file mode 100644 index d952c357068..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_25_8_rel_notes.mdx +++ /dev/null @@ -1,138 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.25.8 release notes -navTitle: Version 1.25.8 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.8_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 8 May 2026 - -This release of EDB CloudNativePG Cluster is part of the LTS series for 1.25.x. -EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support -policy](/postgres_for_kubernetes/1/#long-term-support). - -!!! Warning EDB CloudNativePG Cluster 1.25 reaches End-of-Life in June 2026. - -Users are encouraged to start planning their upgrade to a newer minor -version before that date. - -!!! - -This release of EDB CloudNativePG Cluster includes the following: - -## Highlights - -**`CVE-2026-44477` / `GHSA-423p-g724-fr39`: metrics exporter privilege -escalation.** The metrics exporter no longer authenticates as the -`postgres` superuser. It now uses a dedicated `cnp_metrics_exporter` role -with `pg_monitor` privileges only, closing a chain that let a low-privilege -database user gain PostgreSQL superuser. -([`GHSA-423p-g724-fr39`](https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-423p-g724-fr39)) - -Upgrade impact: custom monitoring queries that read user-owned tables, or -use `target_databases: '*'` against databases where `PUBLIC CONNECT` has -been revoked, need explicit `GRANT` statements to `cnp_metrics_exporter`. -See ["Custom query privileges and safety"](../monitoring/#custom-query-privileges-and-safety) -and ["Manually creating the metrics exporter role"](../monitoring/#manually-creating-the-metrics-exporter-role) -in the monitoring documentation. - -For replica clusters, upgrade the source primary cluster before any -replica clusters that consume from it. The `cnp_metrics_exporter` role -is created on the source primary and replicates downstream; a replica -cluster upgraded first will scrape against a missing role until the -source primary upgrades. The manual-recovery section linked above also -covers replica clusters. - -## Security Fixes - - - - - - - -
DescriptionAddresses
Schema-qualified catalog references in default monitoring queries -

Hardened the shipped monitoring configuration and documentation samples by -qualifying every pg_catalog object explicitly. Unqualified references -resolve through search_path, which a database user can manipulate to -shadow built-in objects.

-
#10576
Discoverable SBOM and provenance attestations -

SBOM and SLSA provenance attached to operator container images now follow -the OCI 1.1 Referrers spec, so standard registry tooling and supply-chain -scanners can discover them automatically.

-
#10601
CVE remediation in github.com/jackc/pgx/v5 -

Bumped to v5.9.2 to pick up upstream fixes for CVE-2026-33816 -(memory-safety in pgproto3) and GHSA-j88v-2chj-qfwx (SQL injection via -simple-protocol dollar-quoted string handling).

-
#10435, #10497
CVE remediation in the Go runtime -

Built with Go 1.26.3 to pick up upstream fixes in crypto/x509, -crypto/tls, net/http, and net (CVE-2026-32280, CVE-2026-32281, -CVE-2026-33810, CVE-2026-33814, CVE-2026-33811, CVE-2026-39825).

-
#10461, #10647
Build pipeline hardening -

The Go 1.26.3 bump also addresses CVE-2026-42501 (cmd/go module-checksum -validation), reducing supply-chain exposure during release builds. The -affected code paths are not reachable from the running operator.

-
#10647
- - -## Changes - - - -
DescriptionAddresses
Switched TLS peer verification from VerifyPeerCertificate to -VerifyConnection, which runs on every completed handshake (the former is -skipped on resumed TLS 1.3 sessions). -

Session resumption is not enabled in EDB Postgres for Kubernetes today, so -this has no observable effect, but it future-proofs verification if -session caching is introduced later.

-
#10478
- - -## Bug Fixes - - - - - - - - - - -
DescriptionAddresses
Fixed a failover window where the former primary kept its primary label. -

If the former primary returned during failover (for example, after a -transient network partition), the -rw service kept routing to it, -replicas could reconnect, and committed writes were lost to pg_rewind. -The old primary is now labeled unhealthy to isolate it from service -traffic during failover.

-
#10409
Fixed failover not being triggered when the node hosting the primary -becomes unreachable. -

The operator now reads the pod's Ready condition (flipped to False by -the node controller when the kubelet stops reporting) instead of -ContainersReady, which stays stale as True in that scenario. Combined -with the spurious-failover guard -(#10445), -failover triggers only when Kubernetes itself marks the pod not Ready.

-
#10448
Fixed spurious failovers caused by transient failures on the primary's -HTTP status endpoint. -#10445
Fixed escaping of backslashes and control characters in PostgreSQL -configuration values. -

Previously, such characters in parameters like log_line_prefix could -corrupt the configuration file or be silently stripped at runtime.

-
#10515
Fixed restore_command construction to shell-quote each argument. -

Values such as a destinationPath containing whitespace (for example, -s3://my bucket/wal) were word-split by the POSIX shell and passed to the -WAL restore tool as separate arguments.

-
#10518
Tightened recoveryTarget validation in the admission webhook. -

targetXID must now be a non-negative 32-bit integer, and targetName -must be shorter than 64 bytes and free of ASCII control characters. -Malformed values are rejected at admission instead of failing later during -PostgreSQL recovery.

-
#10565
Fixed snapshot restores failing when leftover `pgsql_tmp*` directories -were present in the data directory. -#10447
Fixed a deadlock occurring when PVC storage size and resource requests -are changed simultaneously. -#10427
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_0_rel_notes.mdx deleted file mode 100644 index 7a499cb5ca5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_0_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.26.0 release notes -navTitle: Version 1.26.0 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.0_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 23 May 2025 - -This release of EDB CloudNativePG Cluster includes the following: - -## Changes - - - -
DescriptionAddresses
Merged with community CloudNativePG 1.26.0 upstream release. -See the community release notes -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_1_rel_notes.mdx deleted file mode 100644 index 910f02c6135..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_1_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.26.1 release notes -navTitle: Version 1.26.1 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.1_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 25 July 2025 - -This release of EDB CloudNativePG Cluster includes the following: - -## Changes - - - -
DescriptionAddresses
Merged with community CloudNativePG 1.26.1 upstream release. -See the community release notes -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_2_rel_notes.mdx deleted file mode 100644 index 428e31d7074..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_2_rel_notes.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.26.2 release notes -navTitle: Version 1.26.2 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.2_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 24 October 2025 - -This release of EDB CloudNativePG Cluster includes the following: - -## Changes - - - -
DescriptionAddresses
Merged with community CloudNativePG 1.26.2 upstream release. -See the community release notes -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_3_rel_notes.mdx deleted file mode 100644 index 285766ffd75..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_26_3_rel_notes.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.26.3 release notes -navTitle: Version 1.26.3 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.3_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 16 December 2025 - -This release of EDB CloudNativePG Cluster includes the following: - -## Highlights - -We've consolidated our [private container registry](../private_edb_registries) into a single location. This change simplifies access and deployment. -Starting with v1.26.3, any customer attempting an operator upgrade, MUST configure the new unified repository pull secret! -For details and instructions, follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/). - -## Changes - - - - - -
DescriptionAddresses
Updated the default PgBouncer version to `1.25.1`, which carries a fix for CVE-2025-12819, for new Pooler deployments. -#9367
Merged with community CloudNativePG 1.26.3 upstream release. -See the community release notes -
Updated the default PostgreSQL version to `18.1-standard-ubi9`. -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_0_rel_notes.mdx deleted file mode 100644 index 49fd8345f7b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_0_rel_notes.mdx +++ /dev/null @@ -1,66 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.27.0 release notes -navTitle: Version 1.27.0 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.0_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 19 August 2025 - -### Important changes - -The default behavior of the [liveness probe](../instance_manager.md#liveness-probe) has been updated. -An [isolated primary is now forcibly shut down](../instance_manager.md#primary-isolation) -within the configured `livenessProbeTimeout` (default: 30 seconds). - -This release includes the following: - -## Features - - - - - -
DescriptionAddresses
Dynamic loading of PostgreSQL extensions, packaged as OCI-compliant container images, is now supported. -

The .spec.postgresql.extensions stanza allows you to mount PostgreSQL extensions as read-only and immutable volumes inside instance pods. -This enables dynamic extension management without rebuilding base images.

-
#7991
Logical decoding slot synchronization in HA clusters

Added the synchronizeLogicalDecoding field under spec.replicationSlots.highAvailability to enable automatic synchronization of logical decoding slots across high-availability clusters. -This ensures that logical replication subscribers continue seamlessly after a publisher failover.

-
#7931
Primary Isolation Check

Promoted to stable the liveness pinger experimental feature introduced in 1.26, -adding the .spec.probes.liveness.isolationCheck section to enable primary isolation checks -in the liveness probe by default. -This improves the detection and handling of primary connectivity issues in Kubernetes environments.

-
#7845
- - -## Enhancements - - - - - - - - - -
DescriptionAddresses
Introduced an opt-in experimental feature that enables quorum-based failover

...to improve safety and data durability during failover events. -This feature, also called failover quorum, can be activated via the alpha.k8s.enterprisedb.io/failoverQuorum annotation.

-
#7572
Added support for user maps for predefined users such as streaming_replica

...allowing the use of self-managed client certificates with different Common Names in environments with strict policies or shared CAs, -while still enabling replicas to join clusters using the streaming_replica role.

-
#7725
Added a new PhaseFailurePlugin phase in the Cluster status

...to improve observability of plugin-related failures.

-
#7988
Made the Backup.spec field immutable after creation

...ensuring consistency and predictability in backup operations.

-
#7904
Added fqdn-uri and fqdn-jdbc-uri fields in the user secret

...to simplify the retrieval of fully qualified domain name-based connection strings.

-
#7852
Added Postgres interface support to the CNP-I operator

...continuing the transition toward a plugin-based architecture.

-
#7179
Added metrics capabilities to the CNP-I instance webserver

...enabling metrics exposure directly from the instance for better observability.

-
#8033
- - -## Bug Fixes - - - -
DescriptionAddresses
Unblocked rollouts when migrating to the barman-cloud plugin using the switchover strategy

Former primary Pods now restart correctly after WAL archiving fails due to missing plugin support.

-
#8236
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_1_rel_notes.mdx deleted file mode 100644 index 6aea9707cc2..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_1_rel_notes.mdx +++ /dev/null @@ -1,89 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.27.1 release notes -navTitle: Version 1.27.1 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.1_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 24 October 2025 - -This release includes the following: - -## Enhancements - - - - - - - - - - - -
DescriptionAddresses
Added support for overriding the PgBouncer auth_type, server_tls_sslmode, and client_tls_sslmode settings

which were previously hardcoded. Default values remain consistent with the former behavior but can now be customized when required.

-
#8674
Added a CHECKPOINT step before PostgreSQL smart and fast shutdowns

to reduce shutdown duration and replica promotion time, especially on systems with a high checkpoint_timeout.

-
#8867
Added a warning in the instance manager for deprecated or unsupported OS versions

based on the official postgres-containers project.

-
#8601
Improved certificate parsing error reporting

Failures now log specific errors instead of a generic message, aiding troubleshooting. -This is particularly relevant after the CVE-2025-58187 fix in Go 1.25.2 and 1.24.8, -which may trigger parsing failures for invalid DNS SANs.

-
#8801
Added a check to ensure the destination WAL archive path is empty when bootstrapping a cluster using the pg_basebackup method

consistent with other bootstrap methods.

-
#8895
Added validation to prevent backups from running on hibernated clusters

Backups attempted on such clusters now fail with reason ClusterIsHibernated, -following the standard prerequisite check pattern.

-
#8870
Added support for pprof profiling

Instances can now enable the pprof tool by adding the alpha.k8s.enterprisedb.io/enableInstancePprof annotation -to the Cluster resource for advanced debugging.

-
#7876
Updated the Flexible I/O Tester (FIO) image in the cnp plugin

to wallnerryan/fiotools-aio:v2, as provided by Ryan Wallner.

-
#8847
Enhanced the `cnp status backup` command to provide more detailed status information when using a `barman-cloud`-based backup plugin#8780, #8690
- - -## Changes - - - - - -
DescriptionAddresses
Delayed the decommissioning of native in-core support for Barman Cloud to at -least version 1.29. -#8670
Adopted the new format of postgres-containers and postgis-containers -images and image catalog artifacts -

and updated the default PostgreSQL -version to 18.0-system-trixie (PostgreSQL 18 is now supported).

-
#8578, #8760, #8558
Deprecated the monitoring.enablePodMonitor field

in the Cluster and Pooler resources. This field will be removed in a future release. Users who -rely on PodMonitor resources should create them manually instead.

-
#8753
- - -## Bug Fixes - - - - - - - - - - - - - -
DescriptionAddresses
Fixed backup restoration failures when using custom WAL segment sizes with parallel WAL recovery.

The operator no longer manages the end-of-WAL file marker during restoration, -preventing errors when backups span multiple WAL segments.

-
#8873
Fixed a bug in major upgrades where a volume snapshot from a previous minor version -could be incorrectly used to optimize replica creation. -#8475
Fixed initdb to wait for the application user secret before bootstrapping a new cluster

preventing potential race conditions.

-
#8663
Fixed quorum-based failover to work correctly in clusters with only two -instances using synchronous replication. -#8680
Fixed configuration hash calculation to ignore internal configuration fields

preventing unnecessary reconciliations.

-
#8868
Fixed the connection retry logic in the cnpgi plugin

The reconciliation loop now detects connection pool changes correctly and uses exponential -backoff to reduce "closed pool" errors.

-
#8554
Fixed volume snapshot usage during replica scaling to work with backup plugins.

Previously, this optimization was only available with the in-tree backup -implementation, but now clusters using backup plugins can also leverage volume -snapshots when creating new replicas.

-
#8506
Fixed the `Pooler` templating to correctly inherit settings for the bootstrap controller init container.#8394
Fixed webhook errors to use the correct API group

(postgresql.k8s.enterprisedb.io) in Pooler and backup webhooks, ensuring consistent API error reporting.

-
#8485
Fixed a potential nil pointer dereference in the hibernation reconciler

when handling errors. Contributed by @PascalBourdier.

-
#8756
Fixed an issue in the environment cache where callers could inadvertently modify shared data.

The LoadEnv function now returns a copy of cached environment slices to prevent mutations from affecting the cache.

-
#8880
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_2_rel_notes.mdx deleted file mode 100644 index 7bc7309abef..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_2_rel_notes.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.27.2 release notes -navTitle: Version 1.27.2 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.2_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 16 December 2025 - -This release of EDB CloudNativePG Cluster includes the following: - -## Highlights - -We've consolidated our [private container registry](../private_edb_registries) into a single location. This change simplifies access and deployment. -Starting with v1.27.2, any customer attempting an operator upgrade, MUST configure the new unified repository pull secret! -For details and instructions, follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/). - -## Changes - - - - - -
DescriptionAddresses
Updated the default PgBouncer version to `1.25.1`, which carries a fix for CVE-2025-12819, for new Pooler deployments. -#9367
Merged with community CloudNativePG 1.27.2 upstream release. -See the community release notes -
Updated the default PostgreSQL version to `18.1-standard-ubi9`. -
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_3_rel_notes.mdx deleted file mode 100644 index 1dd510b8dff..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_3_rel_notes.mdx +++ /dev/null @@ -1,116 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.27.3 release notes -navTitle: Version 1.27.3 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.3_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 10 February 2026 - -This release of EDB CloudNativePG Cluster includes the following: - -## Enhancements - - - -
DescriptionAddresses
Added support for Azure's DefaultAzureCredential authentication mechanism -for backup and recovery operations. -

This can be enabled by setting -azureCredentials.useDefaultAzureCredentials: true in the backup -configuration, simplifying authentication in Azure environments without -requiring explicit storage account keys or SAS tokens.

-
#9468
- - -## Bug Fixes - - - - - - - - - - - - - - - - - - - - -
DescriptionAddresses
Fixed validation of PostgreSQL extension names containing underscores (e.g., -pg_partman, pg_ivm). -

Extension names with underscores are -automatically sanitized to use hyphens for Kubernetes volume names while -preserving the original name in mount paths. Webhook validation prevents -naming conflicts after sanitization. Contributed by @shusaan.

-
#9386
Fixed a critical issue where the TimelineID in the cluster status was not -reset to 1 after a major version upgrade. -

Because pg_upgrade initializes a -new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt -to restore incompatible history files from object storage, leading to fatal -"requested timeline is not a child of this server's history" errors.

-
#9830
Fixed a bug where replicas could enter a crash-loop by attempting to download -timeline history files from future timelines. -

This occurred when stale files -remained in the WAL archive from a previous cluster life, and replicas would -incorrectly try to fetch them during recovery.

-
#9650
Fixed a race condition in `replica_cluster` setups during designated primary -transitions, preventing transient "no primary" states in the replica cluster. -#9601
The backup controller now uses the unique instance session ID to detect -instance manager restarts. -

This prevents the operator from incorrectly -assuming a backup is still progressing if the underlying container has crashed -and restarted, which previously led to orphaned backup objects.

-
#9370
Fixed a validation gap in Azure object store configurations where the -storageAccount was not required when using explicit credentials (such as a -storage key or SAS token). -

The operator now enforces that a storage account -name is provided in these cases and that connectionString is mutually -exclusive with other authentication parameters.

-
#9604
Optimized the deletion path so the operator begins cleaning up resources -immediately when a cluster is marked for deletion. -

This significantly reduces the time a cluster remains in Terminating status -while waiting for internal reconciliation loops.

-
#9555
Fixed an issue where replication slots were not properly dropped from -replicas when the feature was disabled or the cluster was reconfigured. -

This ensures that unused slots do not cause WAL build-up on the primary.

-
#9381
Fixed an issue where imagePullSecrets were not added to the ServiceAccount -created for the Pooler. -

Previously, these secrets were applied to the -Deployment but not the SA, which caused image pull failures in restricted -environments using certain security policies.

-
#9427
Added a check to verify ownership before the operator deletes a PodMonitor. -

This prevents the operator from accidentally deleting manually managed -monitoring resources that happen to share a name with expected CNP -resources. Contributed by @juliamertz.

-
#9340
Fixed a bug where pg_stat_archiver metrics would continue to report stale -data on standby instances after a switchover. -

The exporter now skips these metrics on standbys, as PostgreSQL only provides -valid archiver stats on the primary.

-
#9411
Clarified the interpretation of timestamp formats for recovery targetTime. -

Timestamps provided without an explicit timezone are now consistently -interpreted as UTC. Contributed by @pchovelon.

-
#8937
Fixed backup status updates to prevent "resource has been modified" errors -during concurrent updates. -#9551
Fixed event reporting to use the correct pod name when a backup pod is not -found. -#9552
Improved performance of scheduled backup operations for clusters with a very -high number of historical backups. -#9489
Fixed error handling when removing finalizers on `Database` objects. -#9431
Updated the status command to display "Disabled" when the -skipWalArchiving annotation is present on a cluster. -

This replaces -confusing "starting up" or "unknown" states when WAL archiving is -intentionally bypassed.

-
#9709
Fixed the `logs --follow` command to continue polling for new pods instead -of exiting prematurely when all current log streams complete. -#9599
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_4_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_4_rel_notes.mdx deleted file mode 100644 index 5735067d137..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_27_4_rel_notes.mdx +++ /dev/null @@ -1,141 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.27.4 release notes -navTitle: Version 1.27.4 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.4_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 31 March 2026 - -This release of EDB CloudNativePG Cluster includes the following: - -## Highlights - -Updated the deprecation notice for native (in-tree) Barman Cloud support to -reflect that it will now be removed in EDB Postgres for Kubernetes 1.30.0, rather than -1.29.0. Users are still encouraged to migrate to the Barman Cloud Plugin. -([#10167](https://github.com/cloudnative-pg/cloudnative-pg/pull/10167)) - -## Enhancements - - - - - - -
DescriptionAddresses
Improved the Pooler CRD with support for granular configuration of TLS -cipher suites and minimum/maximum TLS versions. -

This enables administrators -to meet strict security compliance requirements for pooler-to-client and -pooler-to-server connections. -Contributed by @alex1989hu.

-
#9571
Improved the reliability of major upgrades by setting BackoffLimit=0 on the -upgrade job, preventing unnecessary retries of a failed pg_upgrade. -

The operator now automatically deletes the failed job when a user reverts the -container image, allowing the cluster to restart gracefully on the original -version.

-
#10104, #10298
Improved role management by verifying the instance is the primary before -each reconciliation cycle -

...avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas.

-
#9971
The operator now honors the `primaryUpdateMethod` when adding new PVCs to a -cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is -respected during storage expansion or additions. -#9720
- - -## Security Fixes - - - - - -
DescriptionAddresses
Security best practices integration**: integrated the OpenSSF baseline -scanner and added a `SECURITY-INSIGHTS.yaml` file to the repository to align -with industry-standard security reporting. -#10054, #10062
SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software -Artifacts) provenance to release binaries and container images. -

Additionally, -enabled Software Bill of Materials (SBOM) generation within the GoReleaser -pipeline for improved dependency transparency.

-
#10048, #10074
Password leak prevention**: fixed a potential security risk where PostgreSQL -could leak role passwords in the logs during specific reconciliation phases. -#9950
- - -## Changes - - - -
DescriptionAddresses
Updated the default PostgreSQL version to 18.3 (image `18.3-standard-ubi9`). -#10090
- - -## Bug Fixes - - - - - - - - - - - - - - - - -
DescriptionAddresses
Fixed an issue where fencing annotations could not be processed when the WAL -disk was full -

...because the disk space check blocked the instance manager from -starting. The check is now performed later in the lifecycle loop, after -fencing is evaluated.

-
#10302
Fixed an issue where replicas would get stuck in a Pending state if the -VolumeSnapshot used for the initial bootstrap had been deleted. -

The operator now validates snapshot existence before use; if a snapshot is missing, -it attempts to use the next available candidate or falls back to -pg_basebackup.

-
#10192
Prevented the "supervised primary" rollout strategy from consuming all -available rollout slots, which previously caused delays in scheduled updates. -Contributed by @ermakov-oleg. -#9977
Fixed an issue where certain hot-standby parameter changes were not being -correctly applied to replica clusters. -#9952
Fixed a bug in the CNPG-I reconciler hook that could lead to skipping -subsequent plugins when a "continue" result was returned. -Contributed by @sharifmshaker. -#9978
Fixed a deadlock scenario that occurred when attempting to resize a -filesystem on a PVC that was not currently attached to a Pod. -Contributed by @jmealo. -#9981
Fixed webhook validation of bootstrap recovery sources to accept external -clusters configured with ConnectionParameters (for pg_basebackup-based -recovery). -

Previously, these were incorrectly rejected unless a Barman -object store or CNPG-i plugin was also configured.

-
#10268
Volume names for extensions and tablespaces are now prefixed to avoid naming -collisions with standard cluster volumes. -#9973
When hibernating a non-healthy cluster, the operator now reports a -`WaitingForHealthy` condition, making the deferred hibernation state visible -#10193
Fixed fencing to work correctly even when the target pod does not exist. -

Fencing operates on a cluster-level annotation and should not depend on pod -existence; instance name validation is now performed only in the cnp fencing on command.

-
#10035
Fixed the cluster and pooler service reconcilers to correctly handle changes -to all spec fields when using the patch update strategy. The reconciler now -uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields -(such as `loadBalancerClass`) from being inadvertently removed. -#10190, #10311
Fixed a race condition in the deprecated in-tree Barman Cloud backup -implementation affecting parallel WAL restore, where prefetched files could -be read while still being downloaded, causing PostgreSQL recovery to fail -with "invalid checkpoint record" errors. -#10285
Fixed the timeline history file validation to also apply to plugin-based WAL restore. -

Previously, the protection introduced in -#9650 only -covered in-tree restores, allowing plugins to bypass the check and download -future timeline history files, causing timeline mismatch errors on replicas.

-
#9849
The cnp plugin now correctly propagates ImagePullSecrets to the - `pgbench` Job pod template. -#10174
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_0_rel_notes.mdx deleted file mode 100644 index c28840e9fcf..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_0_rel_notes.mdx +++ /dev/null @@ -1,178 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.28.0 release notes -navTitle: Version 1.28.0 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.0_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 16 December 2025 - -This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: - -## Highlights - -We've consolidated our [private container registry](../private_edb_registries) into a single location. This change simplifies access and deployment. -Starting with v1.28.0, any customer attempting an operator upgrade, MUST configure the new unified repository pull secret! -For details and instructions, follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/). - -## Features - - - - -
DescriptionAddresses
Quorum-Based Failover Promoted to Stable -

Promoted the quorum-based failover feature, introduced experimentally in 1.27.0, to a stable API. -This data-driven failover mechanism is now configured via the spec.postgresql.synchronous.failoverQuorum field, graduating from the previous alpha.k8s.enterprisedb.io/failoverQuorum annotation.

-
#8589
Declarative Foreign Data Management -

Introduced comprehensive declarative management for Foreign Data Wrappers (FDW) by extending the Database CRD. -This feature adds the .spec.fdws and .spec.servers fields, allowing you to manage FDW extensions and their corresponding foreign servers directly from the Database resource. -This work was implemented by Ying Zhu (@EdwinaZhu) as part of the LFX Mentorship Program 2025 Term 2.

-
#7942, #8401
- - -## Enhancements - - - - - - - - - - - - - - - -
DescriptionAddresses
Enabled simultaneous image and configuration changes when using primaryUpdateMethod: restart -

allowing you to update the container image (including PostgreSQL version or extensions) and -PostgreSQL configuration settings in the same operation. -Note that when using primaryUpdateMethod: switchover, image and -configuration changes must still be performed separately to avoid configuration -mismatches during the switchover process.

-
#8241
Improved network failure detection for replica instances by setting the -default tcp_user_timeout to 5 seconds. -

This change helps replicas detect -and recover from silent network drops more quickly. Previously, replicas could -wait up to 127 seconds before detecting such failures; with the new timeout, -they reconnect to the primary within 5 seconds. To preserve the previous -behavior, set STANDBY_TCP_USER_TIMEOUT to 0 in the operator configuration.

-
#9317
Adopted standard Kubernetes recommended labels -

(e.g., app.kubernetes.io/name) for all resources generated by EDB Postgres for Kubernetes -(Clusters, Backups, Poolers, etc.). Contributed by @JefeDavis.

-
#8087
Introduced securityContext at the pod level and containerSecurityContext -for individual containers (including postgres, init, and sidecars). -

This provides granular control over security settings, replacing the previous -cluster-wide postgres and operator user settings. Contributed by @x0ddf.

-
#6614
Introduced the alpha.k8s.enterprisedb.io/unrecoverable=true annotation for replica -pods. -

When applied, this annotation instructs the operator to permanently -delete the instance by removing its Pod and PVCs, after which it will recreate -the replica from the primary.

-
#8178
Introduced a new caching layer for user-defined monitoring queries to reduce load on the PostgreSQL database. -#8003
Enhanced PgBouncer integration by automatically setting `auth_dbname` to the -`pgbouncer` database, simplifying auth setup. -#8671
Allowed providing stage-specific pg_restore options during database import. -

(Stage-specific options are preRestore, postRestore, dataRestore.) Contributed by -@hanshal101.

-
#7690
Added the PostgreSQL `majorVersion` to the `Backup` object's status for easier identification and management. -#8464
Enhanced cluster restore to wait for all init containers to complete before starting the restore process. -

This ensures that backup tools running in init containers finish preparing the data before the restore begins. -The implementation correctly handles Kubernetes init container sidecars by ignoring those with RestartPolicy=Always.

-
#9026
Added the PGBOUNCER_IMAGE_NAME operator configuration parameter to allow overriding the default PgBouncer image. -

This is useful for air-gapped environments or when using internal registries.

-
#9232
CNP plugin: Added a --timeout flag to the kubectl cnp status command -

for configuring the timeout for filesystem operations such as calculating -cluster size. The default remains 10 seconds but can be adjusted for -large clusters where operations may take longer.

-
#9201
Improved `cnp report` to generate more shell-friendly file names. -#8984
- - -## Security Fixes - - - - - -
DescriptionAddresses
Allowed providing fine-grained custom TLS configurations for PgBouncer -

The Pooler CRD was extended with clientTLSSecret, clientCASecret, -serverTLSSecret, and serverCASecret fields under .spec.pgbouncer. -These fields enable users to supply their own certificates for both -client-to-pooler and pooler-to-server connections, taking precedence over the -operator-generated certificates.

-
#8692
Added optional TLS support for the operator's metrics server (port 8080) -

This feature is opt-in and enabled by setting the METRICS_CERT_DIR -environment variable, which instructs the operator to look for tls.crt and -tls.key files in the specified directory. When unset, the server continues to -use HTTP for backward compatibility.

-
#8997
Enabled cnp_report_operator to work with minimal permissions by making -only the operator deployment required -

All other resources (pods, secrets, config maps, events, webhooks, and OLM data) are now optional and collected on -a best-efforts basis. The command gracefully handles permission errors for -those resources by logging clear warnings and continuing report generation with -available data, rather than failing completely. This enables least-privileged -access, where users may have limited, namespace-scoped permissions.

-
#8982
- - -## Changes - - - - -
DescriptionAddresses
Updated the default PostgreSQL version to `18.1-standard-ubi9`. -#9178
Updated the default PgBouncer version to **1.25.1**, which carries -a fix for **CVE-2025-12819**, for new Pooler deployments. -#9367
- - -## Bug Fixes - - - - - - - - - - - -
DescriptionAddresses
Improved resilience of all probe types (liveness, readiness, and startup) to -transient Kubernetes API server connectivity issues. -

Probes now use a caching mechanism that falls back to cached cluster definitions -during brief network interruptions, preventing unnecessary pod restarts and -probe failures.

-
#9148
Fixed the CheckEmptyWalArchive safeguard to run correctly when restoring -from a volume snapshot using CNP-I backup/WAL plugins (e.g., -plugin-barman-cloud). -

Previously, this check was skipped for plugin-based implementations.

-
#9306
Improved error detection and reporting when ImageCatalog retrieval fails. -

The operator now emits a Warning event and logs errors for all failure types, -not just NotFound errors, improving visibility into configuration issues.

-
#9266
Fixed TLS certificate verification issues when connecting to CNP-I plugins -by adding the k8s.enterprisedb.io/pluginServerName annotation. -

This allows customizing the DNS name used for certificate verification in -environments where the plugin's certificate uses a different DNS name than -the Service name.

-
#9222
Fixed an issue where the instance manager controller could fail to restart -after an error, reporting a "controller already exists" message. -

The controller now uses SkipNameValidation for subsequent initialization -attempts. -Contributed by @mateusoliveira43.

-
#9123
Fixed incorrect WAL restore path handling in plugins when the destination -path is absolute, preventing path duplication issues. -

Contributed by @Endevir.

-
#9093
Fixed the CREATE PUBLICATION SQL generation for multi-table publications to be backward-compatible with PostgreSQL 13+. -

The previously generated syntax -was only valid for PostgreSQL 15+ and caused syntax errors on older versions.

-
#8888
Fixed backup failures in complex pod definitions by reliably selecting the `postgres` container by name instead of by index. -#8964
cnp plugin: Fixed bugs in cnp report log collection, especially when fetching previous logs. -

The collector now correctly fetches previous and current logs in separate requests and gracefully handles missing previous logs (e.g., on containers with no restart history), ensuring current logs are always collected.

-
#8992
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_1_rel_notes.mdx deleted file mode 100644 index 387b1462bd9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_1_rel_notes.mdx +++ /dev/null @@ -1,125 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.28.1 release notes -navTitle: Version 1.28.1 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.1_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 10 February 2026 - -This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: - -## Enhancements - - - -
DescriptionAddresses
Added support for Azure's DefaultAzureCredential authentication mechanism -for backup and recovery operations. -

This can be enabled by setting -azureCredentials.useDefaultAzureCredentials: true in the backup -configuration, simplifying authentication in Azure environments without -requiring explicit storage account keys or SAS tokens.

-
#9468
- - -## Bug Fixes - - - - - - - - - - - - - - - - - - - - - -
DescriptionAddresses
Fixed validation of PostgreSQL extension names containing underscores (e.g., -pg_partman, pg_ivm). -

Extension names with underscores are -automatically sanitized to use hyphens for Kubernetes volume names while -preserving the original name in mount paths. Webhook validation prevents -naming conflicts after sanitization. Contributed by @shusaan.

-
#9386
Fixed a critical issue where the TimelineID in the cluster status was not -reset to 1 after a major version upgrade. -

Because pg_upgrade initializes a -new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt -to restore incompatible history files from object storage, leading to fatal -"requested timeline is not a child of this server's history" errors.

-
#9830
Fixed an issue where stale TLS status fields in the Pooler were not cleared -after being removed from the specification. -

This was particularly critical -when upgrading to v1.28.0, where the ServerTLS field was repurposed, causing -PgBouncer to use incorrect certificates and resulting in "unsupported -certificate" errors that blocked all application connectivity. -The operator now explicitly clears ServerCA, ClientCA, ClientTLS, and -ServerTLS status fields when they are no longer configured.

-
#9397
Fixed a bug where replicas could enter a crash-loop by attempting to download -timeline history files from future timelines. -

This occurred when stale files -remained in the WAL archive from a previous cluster life, and replicas would -incorrectly try to fetch them during recovery.

-
#9650
Fixed a race condition in `replica_cluster` setups during designated primary -transitions, preventing transient "no primary" states in the replica cluster. -#9601
The backup controller now uses the unique instance session ID to detect -instance manager restarts. -

This prevents the operator from incorrectly -assuming a backup is still progressing if the underlying container has crashed -and restarted, which previously led to orphaned backup objects.

-
#9370
Fixed a validation gap in Azure object store configurations where the -storageAccount was not required when using explicit credentials (such as a -storage key or SAS token). -

The operator now enforces that a storage account -name is provided in these cases and that connectionString is mutually -exclusive with other authentication parameters.

-
#9604
Optimized the deletion path so the operator begins cleaning up resources -immediately when a cluster is marked for deletion. -

This significantly reduces the time a cluster remains in Terminating status -while waiting for internal reconciliation loops.

-
#9555
Fixed an issue where replication slots were not properly dropped from -replicas when the feature was disabled or the cluster was reconfigured. -

This ensures that unused slots do not cause WAL build-up on the primary.

-
#9381
Fixed an issue where imagePullSecrets were not added to the ServiceAccount -created for the Pooler. -

Previously, these secrets were applied to the -Deployment but not the SA, which caused image pull failures in restricted -environments using certain security policies.

-
#9427
Added a check to verify ownership before the operator deletes a PodMonitor. -

This prevents the operator from accidentally deleting manually managed -monitoring resources that happen to share a name with expected CNP -resources. Contributed by @juliamertz.

-
#9340
Fixed a bug where pg_stat_archiver metrics would continue to report stale -data on standby instances after a switchover. -

The exporter now skips these metrics on standbys, as PostgreSQL only provides -valid archiver stats on the primary.

-
#9411
Clarified the interpretation of timestamp formats for recovery targetTime. -

Timestamps provided without an explicit timezone are now consistently -interpreted as UTC. Contributed by @pchovelon.

-
#8937
Fixed backup status updates to prevent "resource has been modified" errors -during concurrent updates. -#9551
Fixed event reporting to use the correct pod name when a backup pod is not -found. -#9552
Improved performance of scheduled backup operations for clusters with a very -high number of historical backups. -#9489
Fixed error handling when removing finalizers on `Database` objects. -#9431
Updated the status command to display "Disabled" when the -skipWalArchiving annotation is present on a cluster. -

This replaces -confusing "starting up" or "unknown" states when WAL archiving is -intentionally bypassed.

-
#9709
Fixed the `logs --follow` command to continue polling for new pods instead -of exiting prematurely when all current log streams complete. -#9599
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_2_rel_notes.mdx deleted file mode 100644 index 6fb28df5f5a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_2_rel_notes.mdx +++ /dev/null @@ -1,149 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.28.2 release notes -navTitle: Version 1.28.2 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.2_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 31 March 2026 - -This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: - -## Highlights - -Updated the deprecation notice for native (in-tree) Barman Cloud support to -reflect that it will now be removed in EDB Postgres for Kubernetes 1.30.0, rather than -1.29.0. Users are still encouraged to migrate to the Barman Cloud Plugin. -([#10167](https://github.com/cloudnative-pg/cloudnative-pg/pull/10167)) - -## Enhancements - - - - - - - -
DescriptionAddresses
Improved the Pooler CRD with support for granular configuration of TLS -cipher suites and minimum/maximum TLS versions. -

This enables administrators -to meet strict security compliance requirements for pooler-to-client and -pooler-to-server connections. -Contributed by @alex1989hu.

-
#9571
Improved the reliability of major upgrades by setting BackoffLimit=0 on the -upgrade job, preventing unnecessary retries of a failed pg_upgrade. -

The operator now automatically deletes the failed job when a user reverts the -container image, allowing the cluster to restart gracefully on the original -version.

-
#10104, #10298
Improved role management by verifying the instance is the primary before -each reconciliation cycle -

...avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas.

-
#9971
The operator now honors the `primaryUpdateMethod` when adding new PVCs to a -cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is -respected during storage expansion or additions. -#9720
Refined the `alpha.k8s.enterprisedb.io/unrecoverable` annotation logic to allow it to -function even on pods that have not yet reached the `Ready` state, -facilitating the recovery of stuck instances. -#9968
- - -## Security Fixes - - - - - -
DescriptionAddresses
Security best practices integration**: integrated the OpenSSF baseline -scanner and added a `SECURITY-INSIGHTS.yaml` file to the repository to align -with industry-standard security reporting. -#10054, #10062
SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software -Artifacts) provenance to release binaries and container images. -

Additionally, -enabled Software Bill of Materials (SBOM) generation within the GoReleaser -pipeline for improved dependency transparency.

-
#10048, #10074
Password leak prevention**: fixed a potential security risk where PostgreSQL -could leak role passwords in the logs during specific reconciliation phases. -#9950
- - -## Changes - - - -
DescriptionAddresses
Updated the default PostgreSQL version to 18.3 (image `18.3-standard-ubi9`). -#10090
- - -## Bug Fixes - - - - - - - - - - - - - - - - - -
DescriptionAddresses
Fixed a deadlock during operator upgrades affecting clusters using synchronous replication -

...where pods running the old and new operator versions computed different PostgreSQL configuration hashes, causing the -uniformity check to block indefinitely and preventing both rolling updates and in-place upgrades from proceeding.

-
#10342
Fixed an issue where fencing annotations could not be processed when the WAL -disk was full -

...because the disk space check blocked the instance manager from -starting. The check is now performed later in the lifecycle loop, after -fencing is evaluated.

-
#10302
Fixed an issue where replicas would get stuck in a Pending state if the -VolumeSnapshot used for the initial bootstrap had been deleted. -

The operator now validates snapshot existence before use; if a snapshot is missing, -it attempts to use the next available candidate or falls back to -pg_basebackup.

-
#10192
Prevented the "supervised primary" rollout strategy from consuming all -available rollout slots, which previously caused delays in scheduled updates. -Contributed by @ermakov-oleg. -#9977
Fixed an issue where certain hot-standby parameter changes were not being -correctly applied to replica clusters. -#9952
Fixed a bug in the CNPG-I reconciler hook that could lead to skipping -subsequent plugins when a "continue" result was returned. -Contributed by @sharifmshaker. -#9978
Fixed a deadlock scenario that occurred when attempting to resize a -filesystem on a PVC that was not currently attached to a Pod. -Contributed by @jmealo. -#9981
Fixed webhook validation of bootstrap recovery sources to accept external -clusters configured with ConnectionParameters (for pg_basebackup-based -recovery). -

Previously, these were incorrectly rejected unless a Barman -object store or CNPG-i plugin was also configured.

-
#10268
Volume names for extensions and tablespaces are now prefixed to avoid naming -collisions with standard cluster volumes. -#9973
When hibernating a non-healthy cluster, the operator now reports a -`WaitingForHealthy` condition, making the deferred hibernation state visible -#10193
Fixed fencing to work correctly even when the target pod does not exist. -

Fencing operates on a cluster-level annotation and should not depend on pod -existence; instance name validation is now performed only in the cnp fencing on command.

-
#10035
Fixed the cluster and pooler service reconcilers to correctly handle changes -to all spec fields when using the patch update strategy. The reconciler now -uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields -(such as `loadBalancerClass`) from being inadvertently removed. -#10190, #10311
Fixed a race condition in the deprecated in-tree Barman Cloud backup -implementation affecting parallel WAL restore, where prefetched files could -be read while still being downloaded, causing PostgreSQL recovery to fail -with "invalid checkpoint record" errors. -#10285
Fixed the timeline history file validation to also apply to plugin-based WAL restore. -

Previously, the protection introduced in -#9650 only -covered in-tree restores, allowing plugins to bypass the check and download -future timeline history files, causing timeline mismatch errors on replicas.

-
#9849
The cnp plugin now correctly propagates ImagePullSecrets to the - `pgbench` Job pod template. -#10174
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_3_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_3_rel_notes.mdx deleted file mode 100644 index 3caf5c931af..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_28_3_rel_notes.mdx +++ /dev/null @@ -1,127 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.28.3 release notes -navTitle: Version 1.28.3 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.3_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 8 May 2026 - -This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: - -## Highlights - -**`CVE-2026-44477` / `GHSA-423p-g724-fr39`: metrics exporter privilege -escalation.** The metrics exporter no longer authenticates as the -`postgres` superuser. It now uses a dedicated `cnp_metrics_exporter` role -with `pg_monitor` privileges only, closing a chain that let a low-privilege -database user gain PostgreSQL superuser. -([`GHSA-423p-g724-fr39`](https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-423p-g724-fr39)) - -Upgrade impact: custom monitoring queries that read user-owned tables, or -use `target_databases: '*'` against databases where `PUBLIC CONNECT` has -been revoked, need explicit `GRANT` statements to `cnp_metrics_exporter`. -See ["Custom query privileges and safety"](../monitoring/#custom-query-privileges-and-safety) -and ["Manually creating the metrics exporter role"](../monitoring/#manually-creating-the-metrics-exporter-role) -in the monitoring documentation. - -For replica clusters, upgrade the source primary cluster before any -replica clusters that consume from it. The `cnp_metrics_exporter` role -is created on the source primary and replicates downstream; a replica -cluster upgraded first will scrape against a missing role until the -source primary upgrades. The manual-recovery section linked above also -covers replica clusters. - -## Security Fixes - - - - - - - -
DescriptionAddresses
Schema-qualified catalog references in default monitoring queries -

Hardened the shipped monitoring configuration and documentation samples by -qualifying every pg_catalog object explicitly. Unqualified references -resolve through search_path, which a database user can manipulate to -shadow built-in objects.

-
#10576
Discoverable SBOM and provenance attestations -

SBOM and SLSA provenance attached to operator container images now follow -the OCI 1.1 Referrers spec, so standard registry tooling and supply-chain -scanners can discover them automatically.

-
#10601
CVE remediation in github.com/jackc/pgx/v5 -

Bumped to v5.9.2 to pick up upstream fixes for CVE-2026-33816 -(memory-safety in pgproto3) and GHSA-j88v-2chj-qfwx (SQL injection via -simple-protocol dollar-quoted string handling).

-
#10436, #10498
CVE remediation in the Go runtime -

Built with Go 1.26.3 to pick up upstream fixes in crypto/x509, -crypto/tls, net/http, and net (CVE-2026-32280, CVE-2026-32281, -CVE-2026-33810, CVE-2026-33814, CVE-2026-33811, CVE-2026-39825).

-
#10462, #10647
Build pipeline hardening -

The Go 1.26.3 bump also addresses CVE-2026-42501 (cmd/go module-checksum -validation), reducing supply-chain exposure during release builds. The -affected code paths are not reachable from the running operator.

-
#10647
- - -## Changes - - - -
DescriptionAddresses
Switched TLS peer verification from VerifyPeerCertificate to -VerifyConnection, which runs on every completed handshake (the former is -skipped on resumed TLS 1.3 sessions). -

Session resumption is not enabled in EDB Postgres for Kubernetes today, so -this has no observable effect, but it future-proofs verification if -session caching is introduced later.

-
#10478
- - -## Bug Fixes - - - - - - - - - - -
DescriptionAddresses
Fixed a failover window where the former primary kept its primary label. -

If the former primary returned during failover (for example, after a -transient network partition), the -rw service kept routing to it, -replicas could reconnect, and committed writes were lost to pg_rewind. -The old primary is now labeled unhealthy to isolate it from service -traffic during failover.

-
#10409
Fixed failover not being triggered when the node hosting the primary -becomes unreachable. -

The operator now reads the pod's Ready condition (flipped to False by -the node controller when the kubelet stops reporting) instead of -ContainersReady, which stays stale as True in that scenario. Combined -with the spurious-failover guard -(#10445), -failover triggers only when Kubernetes itself marks the pod not Ready.

-
#10448
Fixed spurious failovers caused by transient failures on the primary's -HTTP status endpoint. -#10445
Fixed escaping of backslashes and control characters in PostgreSQL -configuration values. -

Previously, such characters in parameters like log_line_prefix could -corrupt the configuration file or be silently stripped at runtime.

-
#10515
Fixed restore_command construction to shell-quote each argument. -

Values such as a destinationPath containing whitespace (for example, -s3://my bucket/wal) were word-split by the POSIX shell and passed to the -WAL restore tool as separate arguments.

-
#10518
Tightened recoveryTarget validation in the admission webhook. -

targetXID must now be a non-negative 32-bit integer, and targetName -must be shorter than 64 bytes and free of ASCII control characters. -Malformed values are rejected at admission instead of failing later during -PostgreSQL recovery.

-
#10565
Fixed snapshot restores failing when leftover `pgsql_tmp*` directories -were present in the data directory. -#10447
Fixed a deadlock occurring when PVC storage size and resource requests -are changed simultaneously. -#10427
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_29_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_29_0_rel_notes.mdx deleted file mode 100644 index 5d6bef9d32f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_29_0_rel_notes.mdx +++ /dev/null @@ -1,218 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.29.0 release notes -navTitle: Version 1.29.0 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.29.0_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 31 March 2026 - -This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: - -## Highlights - -Updated the deprecation notice for native (in-tree) Barman Cloud support to -reflect that it will now be removed in EDB Postgres for Kubernetes 1.30.0, rather than -1.29.0. Users are still encouraged to migrate to the Barman Cloud Plugin. -([#10167](https://github.com/cloudnative-pg/cloudnative-pg/pull/10167)) - -## Features - - - - - -
DescriptionAddresses
PostgreSQL extensions in image catalogs -

extended the ImageCatalog -functionality to support PostgreSQL extensions. This allows users to define -and manage extension-specific images within a catalog, simplifying the -deployment of customized PostgreSQL builds.

-
#9781
Dynamic network access control via pod selectors -

introduced the -declarative definition of podSelectorRefs to manage pg_hba.conf rules -dynamically. By using label selectors to identify client pods, the operator -automatically resolves their ephemeral IP addresses and updates the PostgreSQL -host-based authentication rules accordingly. This ensures that only authorized -workloads in the same namespace can connect to the database, eliminating the -need for manual IP management or static CIDR ranges.

-
#9781
Shared ServiceAccount support -

added an optional serviceAccountName -field to both Cluster and Pooler specifications. This allows multiple -resources to share a pre-existing ServiceAccount, facilitating one-time IAM -configurations (such as AWS IRSA, GCP Workload Identity, or Azure Workload -Identity) across all clusters and poolers. Contributed by @bozkayasalihx.

-
#9287
- - -## Enhancements - - - - - - - - - - - - - - - -
DescriptionAddresses
Improved the Pooler CRD with support for granular configuration of TLS -cipher suites and minimum/maximum TLS versions. -

This enables administrators -to meet strict security compliance requirements for pooler-to-client and -pooler-to-server connections. -Contributed by @alex1989hu.

-
#9571
Improved the reliability of major upgrades by setting BackoffLimit=0 on the -upgrade job, preventing unnecessary retries of a failed pg_upgrade. -

The operator now automatically deletes the failed job when a user reverts the -container image, allowing the cluster to restart gracefully on the original -version.

-
#10104, #10298
Improved the operator's observability by emitting native Kubernetes events -during key phases of the reconciliation loop. -

This provides visibility into the operator's decision-making process and -the lifecycle of managed resources directly through kubectl get events.

-
#10040
Extended support for the k8s.enterprisedb.io/reconciliationDisabled annotation on -Backup resources. -

This allows administrators to temporarily freeze the -operator's reconciliation logic for specific backup objects. -Contributed by @GabriFedi97.

-
#10020
Added a bin_path field to the postgresql.extensions stanza, as well as in -ImageCatalog and ClusterImageCatalog resources. -

This allows extensions to -specify directory paths for external binaries, which are automatically appended -to the PATH environment variable of the Postgres process.

-
#10250
Added an env field to the postgresql.extensions stanza, as well as in -ImageCatalog and ClusterImageCatalog resources. -

This allows cluster administrators to define custom environment variables for the -Postgres process. This field supports the ${image_root} placeholder to -dynamically resolve to the extension's absolute mount path.

-
#10375
Implemented a finalizer for plugins to ensure that resources managed by a -plugin are gracefully cleaned up when the corresponding service is deleted. -#9560
Improved role management by verifying the instance is the primary before -each reconciliation cycle -

...avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas.

-
#9971
The operator now honors the `primaryUpdateMethod` when adding new PVCs to a -cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is -respected during storage expansion or additions. -#9720
Refined the `alpha.k8s.enterprisedb.io/unrecoverable` annotation logic to allow it to -function even on pods that have not yet reached the `Ready` state, -facilitating the recovery of stuck instances. -#9968
Introduced a "Terminal Error" phase for backups that encounter unrecoverable -issues (such as invalid credentials or non-existent cloud buckets). -

This ensures the operator stops retrying doomed operations, preventing -resource exhaustion and providing immediate, clear feedback in the status.

-
#9353
Improved monitoring of long-running backups by introducing -reconciliationStartedAt and reconciliationTerminatedAt fields to the -Backup status. -

This change separates the operator's internal lifecycle from -the actual backup tool's execution timing (startedAt/stoppedAt), allowing -users to track when the operator begins processing a request.

-
#9351
Added a `Pending` phase to the `Backup` status to explicitly indicate when a -backup is queued and waiting for an available worker or instance availability. -#9364
- - -## Security Fixes - - - - - -
DescriptionAddresses
Security best practices integration**: integrated the OpenSSF baseline -scanner and added a `SECURITY-INSIGHTS.yaml` file to the repository to align -with industry-standard security reporting. -#10054, #10062
SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software -Artifacts) provenance to release binaries and container images. -

Additionally, -enabled Software Bill of Materials (SBOM) generation within the GoReleaser -pipeline for improved dependency transparency.

-
#10048, #10074
Password leak prevention**: fixed a potential security risk where PostgreSQL -could leak role passwords in the logs during specific reconciliation phases. -#9950
- - -## Changes - - - -
DescriptionAddresses
Updated the default PostgreSQL version to 18.3 (image `18.3-standard-ubi9`). -#10090
- - -## Bug Fixes - - - - - - - - - - - - - - - - - -
DescriptionAddresses
Fixed a deadlock during operator upgrades affecting clusters using synchronous replication -

...where pods running the old and new operator versions computed different PostgreSQL configuration hashes, causing the -uniformity check to block indefinitely and preventing both rolling updates and in-place upgrades from proceeding.

-
#10342
Fixed an issue where fencing annotations could not be processed when the WAL -disk was full -

...because the disk space check blocked the instance manager from -starting. The check is now performed later in the lifecycle loop, after -fencing is evaluated.

-
#10302
Fixed an issue where replicas would get stuck in a Pending state if the -VolumeSnapshot used for the initial bootstrap had been deleted. -

The operator now validates snapshot existence before use; if a snapshot is missing, -it attempts to use the next available candidate or falls back to -pg_basebackup.

-
#10192
Prevented the "supervised primary" rollout strategy from consuming all -available rollout slots, which previously caused delays in scheduled updates. -Contributed by @ermakov-oleg. -#9977
Fixed an issue where certain hot-standby parameter changes were not being -correctly applied to replica clusters. -#9952
Fixed a bug in the CNPG-I reconciler hook that could lead to skipping -subsequent plugins when a "continue" result was returned. -Contributed by @sharifmshaker. -#9978
Fixed a deadlock scenario that occurred when attempting to resize a -filesystem on a PVC that was not currently attached to a Pod. -Contributed by @jmealo. -#9981
Fixed webhook validation of bootstrap recovery sources to accept external -clusters configured with ConnectionParameters (for pg_basebackup-based -recovery). -

Previously, these were incorrectly rejected unless a Barman -object store or CNPG-i plugin was also configured.

-
#10268
Volume names for extensions and tablespaces are now prefixed to avoid naming -collisions with standard cluster volumes. -#9973
When hibernating a non-healthy cluster, the operator now reports a -`WaitingForHealthy` condition, making the deferred hibernation state visible -#10193
Fixed fencing to work correctly even when the target pod does not exist. -

Fencing operates on a cluster-level annotation and should not depend on pod -existence; instance name validation is now performed only in the cnp fencing on command.

-
#10035
Fixed the cluster and pooler service reconcilers to correctly handle changes -to all spec fields when using the patch update strategy. The reconciler now -uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields -(such as `loadBalancerClass`) from being inadvertently removed. -#10190, #10311
Fixed a race condition in the deprecated in-tree Barman Cloud backup -implementation affecting parallel WAL restore, where prefetched files could -be read while still being downloaded, causing PostgreSQL recovery to fail -with "invalid checkpoint record" errors. -#10285
Fixed the timeline history file validation to also apply to plugin-based WAL restore. -

Previously, the protection introduced in -#9650 only -covered in-tree restores, allowing plugins to bypass the check and download -future timeline history files, causing timeline mismatch errors on replicas.

-
#9849
The cnp plugin now correctly propagates ImagePullSecrets to the - `pgbench` Job pod template. -#10174
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_29_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_29_1_rel_notes.mdx deleted file mode 100644 index d1d38e0f3d3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_29_1_rel_notes.mdx +++ /dev/null @@ -1,127 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster 1.29.1 release notes -navTitle: Version 1.29.1 -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.29.1_rel_notes.yml -editTarget: originalFilePath ---- - -Released: 8 May 2026 - -This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: - -## Highlights - -**`CVE-2026-44477` / `GHSA-423p-g724-fr39`: metrics exporter privilege -escalation.** The metrics exporter no longer authenticates as the -`postgres` superuser. It now uses a dedicated `cnp_metrics_exporter` role -with `pg_monitor` privileges only, closing a chain that let a low-privilege -database user gain PostgreSQL superuser. -([`GHSA-423p-g724-fr39`](https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-423p-g724-fr39)) - -Upgrade impact: custom monitoring queries that read user-owned tables, or -use `target_databases: '*'` against databases where `PUBLIC CONNECT` has -been revoked, need explicit `GRANT` statements to `cnp_metrics_exporter`. -See ["Custom query privileges and safety"](../monitoring/#custom-query-privileges-and-safety) -and ["Manually creating the metrics exporter role"](../monitoring/#manually-creating-the-metrics-exporter-role) -in the monitoring documentation. - -For replica clusters, upgrade the source primary cluster before any -replica clusters that consume from it. The `cnp_metrics_exporter` role -is created on the source primary and replicates downstream; a replica -cluster upgraded first will scrape against a missing role until the -source primary upgrades. The manual-recovery section linked above also -covers replica clusters. - -## Security Fixes - - - - - - - -
DescriptionAddresses
Schema-qualified catalog references in default monitoring queries -

Hardened the shipped monitoring configuration and documentation samples by -qualifying every pg_catalog object explicitly. Unqualified references -resolve through search_path, which a database user can manipulate to -shadow built-in objects.

-
#10576
Discoverable SBOM and provenance attestations -

SBOM and SLSA provenance attached to operator container images now follow -the OCI 1.1 Referrers spec, so standard registry tooling and supply-chain -scanners can discover them automatically.

-
#10601
CVE remediation in github.com/jackc/pgx/v5 -

Bumped to v5.9.2 to pick up upstream fixes for CVE-2026-33816 -(memory-safety in pgproto3) and GHSA-j88v-2chj-qfwx (SQL injection via -simple-protocol dollar-quoted string handling).

-
#10437, #10499
CVE remediation in the Go runtime -

Built with Go 1.26.3 to pick up upstream fixes in crypto/x509, -crypto/tls, net/http, and net (CVE-2026-32280, CVE-2026-32281, -CVE-2026-33810, CVE-2026-33814, CVE-2026-33811, CVE-2026-39825).

-
#10463, #10647
Build pipeline hardening -

The Go 1.26.3 bump also addresses CVE-2026-42501 (cmd/go module-checksum -validation), reducing supply-chain exposure during release builds. The -affected code paths are not reachable from the running operator.

-
#10647
- - -## Changes - - - -
DescriptionAddresses
Switched TLS peer verification from VerifyPeerCertificate to -VerifyConnection, which runs on every completed handshake (the former is -skipped on resumed TLS 1.3 sessions). -

Session resumption is not enabled in EDB Postgres for Kubernetes today, so -this has no observable effect, but it future-proofs verification if -session caching is introduced later.

-
#10478
- - -## Bug Fixes - - - - - - - - - - -
DescriptionAddresses
Fixed a failover window where the former primary kept its primary label. -

If the former primary returned during failover (for example, after a -transient network partition), the -rw service kept routing to it, -replicas could reconnect, and committed writes were lost to pg_rewind. -The old primary is now labeled unhealthy to isolate it from service -traffic during failover.

-
#10409
Fixed failover not being triggered when the node hosting the primary -becomes unreachable. -

The operator now reads the pod's Ready condition (flipped to False by -the node controller when the kubelet stops reporting) instead of -ContainersReady, which stays stale as True in that scenario. Combined -with the spurious-failover guard -(#10445), -failover triggers only when Kubernetes itself marks the pod not Ready.

-
#10448
Fixed spurious failovers caused by transient failures on the primary's -HTTP status endpoint. -#10445
Fixed escaping of backslashes and control characters in PostgreSQL -configuration values. -

Previously, such characters in parameters like log_line_prefix could -corrupt the configuration file or be silently stripped at runtime.

-
#10515
Fixed restore_command construction to shell-quote each argument. -

Values such as a destinationPath containing whitespace (for example, -s3://my bucket/wal) were word-split by the POSIX shell and passed to the -WAL restore tool as separate arguments.

-
#10518
Tightened recoveryTarget validation in the admission webhook. -

targetXID must now be a non-negative 32-bit integer, and targetName -must be shorter than 64 bytes and free of ASCII control characters. -Malformed values are rejected at admission instead of failing later during -PostgreSQL recovery.

-
#10565
Fixed snapshot restores failing when leftover `pgsql_tmp*` directories -were present in the data directory. -#10447
Fixed a deadlock occurring when PVC storage size and resource requests -are changed simultaneously. -#10427
- - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_2_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_2_0_rel_notes.mdx deleted file mode 100644 index bebdd48aab3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_2_0_rel_notes.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.2.0 release notes" -navTitle: "Version 1.2.0" ---- - -Released: 31 Mar 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Introduce experimental support for custom monitoring queries as ConfigMap and Secret objects using a compatible syntax with postgres_exporter for Prometheus. | -| Feature | Support Operator Lifecycle Manager (OLM) deployments, with the subsequent presence on OperatorHub.io. | -| Feature | Expand license key support for company-wide usage (previous restrictions limited only to a single cluster namespace). | -| Feature | Enhance container security by applying guidelines from the US Department of Defense (DoD)'s Defense Information Systems Agency (DISA) and the Center for Internet Security (CIS) and verifying them directly in the pipeline with Dockle. | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_2_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_2_1_rel_notes.mdx deleted file mode 100644 index 73ad098f500..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_2_1_rel_notes.mdx +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.2.1 release notes" -navTitle: "Version 1.2.1" ---- - -Released: 06 Apr 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ----------------------------------------------------------------------------------------------------------------------------------- | -| Feature | ScheduledBackup are no longer owners of the Backups, meaning that backups are not removed when ScheduledBackup objects are deleted. | -| Security fix | Update on ubi8-minimal image to solve RHSA-2021:1024 (Security Advisory: Important). | - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_3_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_3_0_rel_notes.mdx deleted file mode 100644 index 9403bfb5be3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_3_0_rel_notes.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.3.0 release notes" -navTitle: "Version 1.3.0" ---- - -Released: 23 Apr 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ | -| Feature | Inheritance of labels and annotations. | -| Feature | Set resource limits for every container. | -| Security fix | Support for restricted security context constraint on Red Hat OpenShift to limit pod execution to a namespace allocated UID and SELinux context. | -| Security fix | Pod security contexts explicitly defined by the operator to run as non-root, non-privileged and without privilege escalation. | -| Change | Prometheus exporter endpoint listening on port 9187 (port 8000 is now reserved to instance coordination with API server). | - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_4_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_4_0_rel_notes.mdx deleted file mode 100644 index 6ae34489cb3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_4_0_rel_notes.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.4.0 release notes" -navTitle: "Version 1.4.0" ---- - -Released: 18 May 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Standard output logging of PostgreSQL error messages in JSON format. | -| Feature | Provide a basic set of PostgreSQL metrics for the Prometheus exporter. | -| Feature | Add the restart command to the cnp plugin for kubectl to restart the pods of a given PostgreSQL cluster in a rollout fashion. | -| Security fix | Set readOnlyRootFilesystem security context for pods. | -| Change | IMPORTANT: If you have previously deployed the Cloud Native PostgreSQL operator using the YAML manifest, you must delete the existing operator deployment before installing the new version. This is required to avoid conflicts with other Kubernetes API's due to a change in labels and label selectors being directly managed by the operator. Please refer to the Cloud Native PostgreSQL documentation for additional detail on upgrading to 1.4.0. | -| Change | Fix the labels that are automatically defined by the operator, renaming them from control-plane: controller-manager to app.kubernetes.io/name: cloud-native-postgresql. | -| Change | Assign the metrics name to the TCP port for the Prometheus exporter. | -| Change | Set cnp_metrics_exporter as the application_name to the metrics exporter connection in PostgreSQL. | -| Change | When available, use the application database for monitoring queries of the Prometheus exporter instead of the postgres database. | -| Documentation fixes | Customization of monitoring queries. | -| Documentation fixes | Operator upgrade instructions. | -| Bug fix | Avoid using -R when calling pg_basebackup. | -| Bug fix | Remove stack trace from error log when getting the status. | - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_5_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_5_0_rel_notes.mdx deleted file mode 100644 index 95d589a3337..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_5_0_rel_notes.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.5.0 release notes" -navTitle: "Version 1.5.0" ---- - -Released: 17 Jun 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Introduce the pg_basebackup bootstrap method to create a new PostgreSQL cluster as a copy of an existing PostgreSQL instance of the same major version, even outside Kubernetes. | -| Feature | Add support for Kubernetes’ tolerations in the Affinity section of the Cluster resource, allowing users to distribute PostgreSQL instances on Kubernetes nodes with the required taint. | -| Feature | Enable specification of a digest to an image name, through the `:@sha256:` format, for more deterministic and repeatable deployments. | -| Security fix | Customize TLS certificates to authenticate the PostgreSQL server by defining secrets for the server certificate and the related Certification Authority that signed it. | -| Security fix | Raise the sslmode for the WAL receiver process of internal and automatically managed streaming replicas from require to verify-ca. | -| Change | Enhance the promote subcommand of the cnp plugin for kubectl to accept just the node number rather than the whole name of the pod. | -| Change | Adopt DNS-1035 validation scheme for cluster names (from which service names are inherited). | -| Change | Enforce streaming replication connection when cloning a standby instance or when bootstrapping using the pg_basebackup method. | -| Change | Integrate the Backup resource with beginWal, endWal, beginLSN, endLSN, startedAt and stoppedAt regarding the physical base backup. | -| Documentation fix | Provide a list of ports exposed by the operator and the operand container. | -| Documentation fix | Introduce the cnp-bench helm charts and guidelines for benchmarking the storage and PostgreSQL for database workloads. | -| E2E test fix | Test Kubernetes 1.21. | -| E2E test fix | Add test for High Availability of the operator. | -| E2E test fix | Add test for node draining. | -| Bug fix | Timeout to pg_ctl start during recovery operations too short. | -| Bug fix | Operator not watching over direct events on PVCs. | -| Bug fix | Fix handling of immediateCheckpoint and jobs parameter in barmanObjectStore backups. | -| Bug fix | Empty logs when recovering from a backup. | - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_5_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_5_1_rel_notes.mdx deleted file mode 100644 index c525f953fb8..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_5_1_rel_notes.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.5.1 release notes" -navTitle: "Version 1.5.1" ---- - -Released: 11 Jun 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Change | Fix a bug with CRD validation preventing auto-update with Operator Deployments on Red Hat OpenShift. | -| Change | Allow passing operator's configuration using a Secret. | - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_6_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_6_0_rel_notes.mdx deleted file mode 100644 index 30790f70165..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_6_0_rel_notes.mdx +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.6.0 release notes" -navTitle: "Version 1.6.0" ---- - -Released: 12 Jul 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Replica mode (EXPERIMENTAL): allow a cluster to be created as a replica of a source cluster. A replica cluster has a designated primary and any number of standbys. | -| Feature | EDB Audit support on EDB Postgres Advanced Server images. | -| Feature | Add the .spec.postgresql.promotionTimeout parameter to specify the maximum amount of seconds to wait when promoting an instance to primary, defaulting to 40000000 seconds. | -| Feature | Add the .spec.affinity.podAntiAffinityType parameter. It can be set to preferred (default), resulting in preferredDuringSchedulingIgnoredDuringExecution being used, or to required, resulting in requiredDuringSchedulingIgnoredDuringExecution. | -| Security fix | Prevent license keys from appearing in the logs. | -| Change | Fixed a race condition when deleting a PVC and a pod which prevented the operator from creating a new pod. | -| Change | Fixed a race condition preventing the manager from detecting the need for a PostgreSQL restart on a configuration change. | -| Change | Fixed a panic in kubectl-cnp on clusters without annotations. | -| Change | Lowered the level of some log messages to debug. | -| Change | E2E tests for server CA and TLS injection. | - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_7_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_7_0_rel_notes.mdx deleted file mode 100644 index 72672f6f3ae..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_7_0_rel_notes.mdx +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.7.0 release notes" -navTitle: "Version 1.7.0" ---- - -Released: 28 Jul 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Add native support to PGAudit with a new type of logger called pgaudit directly available in the JSON output. | -| Feature | Native support for the pg_stat_statements and auto_explain extensions. | -| Feature | The target_databases option in the Prometheus exporter to run a user-defined metric query on one or more databases (including auto-discovery of databases through shell-like pattern matching). | -| Feature | Exposure of the manual_switchover_required metric to promptly report whether a cluster with primaryUpdateStrategy set to supervised requires a manual switchover. | -| Feature | Transparently handle shared_preload_libraries for pg_audit, auto_explain and pg_stat_statements. | -| Feature | Automatic configuration of shared_preload_libraries for PostgreSQL when pg_stat_statements, pgaudit or auto_explain options are added to the postgresql parameters section. | -| Feature | Support the k8s.enterprisedb.io/reload label to finely control the automated reload of config maps and secrets, including those used for custom monitoring/alerting metrics in the Prometheus exporter or to store certificates. | -| Feature | Add the reload command to the cnp plugin for kubectl to trigger a reconciliation loop on the instances. | -| Feature | Improve control of pod affinity and anti-affinity configurations through additionalPodAffinity and additionalPodAntiAffinity. | -| Feature | Introduce a separate PodDisruptionBudget for primary instances, by requiring at least a primary instance to run at any time. | -| Security fix | Add the .spec.certificates.clientCASecret and spec.certificates.replicationTLSSecret options to define custom client Certification. | -| Security fix | Authority and certificate for the PostgreSQL server, to be used to authenticate client certificates and secure communication between PostgreSQL nodes. | -| Security fix | Add the .spec.backup.barmanObjectStore.endpointCA option to define the custom Certification Authority bundle of the endpoint of Barman’s backup object store. | -| Bug fix | Correctly parse histograms in the Prometheus exporter. | -| Bug fix | Reconcile services created by the operator for a cluster. | - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_7_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_7_1_rel_notes.mdx deleted file mode 100644 index fe6bd15f050..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_7_1_rel_notes.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.7.1 release notes" -navTitle: "Version 1.7.1" ---- - -Released: 11 Aug 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Prefer self-healing over configuration with regards to synchronous replication, empowering the operator to temporarily override minSyncReplicas and maxSyncReplicas settings in case the cluster is not able to meet the requirements during self-healing operations. | -| Feature | Introduce the postInitSQL option as part of the initdb bootstrap method to specify a list of SQL queries to be executed as a superuser immediately after the cluster has been created. | -| Bug fix | Allow the operator to failover when the primary is not ready (bug introduced in 1.7.0). | -| Bug fix | Execute administrative queries using the LOCAL synchronous commit level. | -| Bug fix | Correctly parse multi-line log entries in PGAudit. | - - - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_8_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_8_0_rel_notes.mdx deleted file mode 100644 index 2f8b4020b6a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_8_0_rel_notes.mdx +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.8.0 release notes" -navTitle: "Version 1.8.0" ---- - -Released: 13 Sep 2023 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Bootstrap a new cluster via full or Point-In-Time Recovery directly from an object store defined in the external cluster section, eliminating the previous requirement to have a Backup CR defined. | -| Feature | Introduce the immediate option in scheduled backups to request a backup immediately after the first Postgres instance running, adding the capability to rewind to the very beginning of a cluster when Point-In-Time Recovery is configured. | -| Feature | Add the firstRecoverabilityPoint in the cluster status to report the oldest consistent point in time to request a recovery based on the backup object store’s content. | -| Feature | Enhance the default Prometheus exporter for a PostgreSQL instance by exposing the following new metrics: number of WAL files and computed total size on disk, number of WAL files and computed total size on disk, number of .ready and .done files in the archive status folder, flag for replica mode, number of requested minimum/maximum synchronous replicas, as well as the expected and actually observed ones. | -| Feature | Add support for the runonserver option when defining custom metrics in the Prometheus exporter to limit the collection of a metric to a range of PostgreSQL versions. | -| Feature | Natively support Azure Blob Storage for backup and recovery, by taking advantage of the feature introduced in Barman 2.13 for Barman Cloud. | -| Feature | Rely on pg_isready for the liveness probe. | -| Feature | Support RFC3339 format for timestamp specification in recovery target times. | -| Feature | Introduce .spec.imagePullPolicy to control the pull policy of image containers for all pods and jobs created for a cluster. | -| Feature | Add support for OpenShift 4.8, which replaces OpenShift 4.5. | -| Feature | Support PostgreSQL 14 (beta). | -| Feature | Enhance the replica cluster feature with cross-cluster replication from an object store defined in an external cluster section, without requiring a streaming connection (experimental). | -| Feature | Introduce logLevel option to the cluster's spec to specify one of the following levels: error, info, debug or trace. | -| Security fix | Introduce .spec.enableSuperuserAccess to enable/disable network access with the postgres user through password authentication. | -| Security fix | Enable specification of a license key in a secret with spec.licenseKeySecret. | -| Bug fix | Properly inform users when a cluster enters an unrecoverable state and requires human intervention. | - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_0_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_0_rel_notes.mdx deleted file mode 100644 index e7418d0abc4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_0_rel_notes.mdx +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.9.0 release notes" -navTitle: "Version 1.9.0" ---- - -Released: 28 Sep 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Add Kubernetes 1.22 to the list of supported Kubernetes distributions, and remove 1.16. | -| Feature | Introduce support for the --restore-target-wal option in pg_rewind, in order to fetch WAL files from the backup archive, if necessary (available only with PostgreSQL/EPAS 13+). | -| Feature | Version 1.9.0 is not available on OpenShift due to delays with the release process and the subsequent release of version 1.9.1. | -| Feature | Expose a default metric for the Prometheus exporter that estimates the number of pages in the pg_catalog.pg_largeobject table in each database. | -| Feature | Enhance the performance of WAL archiving and fetching, through local in-memory cache. | -| Bug fix | Explicitly set the postgres user when invoking pg_isready - required by restricted SCC in OpenShift. | -| Bug fix | Properly update the FirstRecoverabilityPoint in the status. | -| Bug fix | Set archive_mode = always on the designated primary if backup is requested. | - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_1_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_1_rel_notes.mdx deleted file mode 100644 index 9d26a4aa094..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_1_rel_notes.mdx +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.9.1 release notes" -navTitle: "Version 1.9.1" ---- - -Released: 30 Sep 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | This release is to celebrate the launch of PostgreSQL 14 by making it the default major version when a new Cluster is created without defining a specific image name. | -| Bug fix | Fix issue causing Error while getting barman endpoint CA secret message to appear in the logs of the primary pod, which prevented the backup to work correctly. | -| Bug fix | Properly retry requesting a new backup in case of temporary communication issues with the instance manager. | - - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_2_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_2_rel_notes.mdx deleted file mode 100644 index 31f9857c4b4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/1_9_2_rel_notes.mdx +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: "EDB Postgres for Kubernetes 1.9.2 release notes" -navTitle: "Version 1.9.2" ---- - -Released: 15 Oct 2021 - -This release of EDB Postgres for Kubernetes includes the following: - -| Type | Description | -| -------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Feature | Enhance JSON log with two new loggers: wal-archive for PostgreSQL's archive_command, and wal-restore for restore_command in a standby. | -| Bug fix | Enable WAL archiving during the standby promotion (prevented .history files from being archived). | -| Bug fix | Pass the --cloud-provider option to Barman Cloud tools only when using Barman 2.13 or higher to avoid errors with older operands. | -| Bug fix | Wait for the pod of the primary to be ready before triggering a backup. | - - - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/index.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/index.mdx deleted file mode 100644 index b0a249ca474..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/index.mdx +++ /dev/null @@ -1,284 +0,0 @@ ---- -# IMPORTANT: Do not edit this file directly - it is generated from yaml source. -title: EDB CloudNativePG Cluster release notes -navTitle: Release notes -description: Release notes for EDB CloudNativePG Cluster -indexCards: none -redirects: - - ../release_notes -navigation: - - 1_30_0-rc1_rel_notes - - 1_29_1_rel_notes - - 1_29_0_rel_notes - - 1_28_3_rel_notes - - 1_28_2_rel_notes - - 1_28_1_rel_notes - - 1_28_0_rel_notes - - 1_27_4_rel_notes - - 1_27_3_rel_notes - - 1_27_2_rel_notes - - 1_27_1_rel_notes - - 1_27_0_rel_notes - - 1_26_3_rel_notes - - 1_26_2_rel_notes - - 1_26_1_rel_notes - - 1_26_0_rel_notes - - 1_25_8_rel_notes - - 1_25_7_rel_notes - - 1_25_6_rel_notes - - 1_25_5_rel_notes - - 1_25_4_rel_notes - - 1_25_3_rel_notes - - 1_25_2_rel_notes - - 1_25_1_rel_notes - - 1_25_0_rel_notes - - 1_24_4_rel_notes - - 1_24_3_rel_notes - - 1_24_2_rel_notes - - 1_24_1_rel_notes - - 1_24_0_rel_notes - - 1_23_6_rel_notes - - 1_23_5_rel_notes - - 1_23_4_rel_notes - - 1_23_3_rel_notes - - 1_23_2_rel_notes - - 1_23_1_rel_notes - - 1_23_0_rel_notes - - 1_22_11_rel_notes - - 1_22_10_rel_notes - - 1_22_9_rel_notes - - 1_22_8_rel_notes - - 1_22_7_rel_notes - - 1_22_6_rel_notes - - 1_22_5_rel_notes - - 1_22_4_rel_notes - - 1_22_3_rel_notes - - 1_22_2_rel_notes - - 1_22_1_rel_notes - - 1_22_0_rel_notes - - 1_21_6_rel_notes - - 1_21_5_rel_notes - - 1_21_4_rel_notes - - 1_21_3_rel_notes - - 1_21_2_rel_notes - - 1_21_1_rel_notes - - 1_21_0_rel_notes - - 1_20_6_rel_notes - - 1_20_5_rel_notes - - 1_20_4_rel_notes - - 1_20_3_rel_notes - - 1_20_2_rel_notes - - 1_20_1_rel_notes - - 1_20_0_rel_notes - - 1_19_6_rel_notes - - 1_19_5_rel_notes - - 1_19_4_rel_notes - - 1_19_3_rel_notes - - 1_19_2_rel_notes - - 1_19_1_rel_notes - - 1_19_0_rel_notes - - 1_18_13_rel_notes - - 1_18_12_rel_notes - - 1_18_11_rel_notes - - 1_18_10_rel_notes - - 1_18_9_rel_notes - - 1_18_8_rel_notes - - 1_18_7_rel_notes - - 1_18_6_rel_notes - - 1_18_5_rel_notes - - 1_18_4_rel_notes - - 1_18_3_rel_notes - - 1_18_2_rel_notes - - 1_18_1_rel_notes - - 1_18_0_rel_notes - - 1_17_5_rel_notes - - 1_17_4_rel_notes - - 1_17_3_rel_notes - - 1_17_2_rel_notes - - 1_17_1_rel_notes - - 1_17_0_rel_notes - - 1_16_5_rel_notes - - 1_16_4_rel_notes - - 1_16_3_rel_notes - - 1_16_2_rel_notes - - 1_16_1_rel_notes - - 1_16_0_rel_notes - - 1_15_5_rel_notes - - 1_15_4_rel_notes - - 1_15_3_rel_notes - - 1_15_2_rel_notes - - 1_15_1_rel_notes - - 1_15_0_rel_notes - - 1_14_0_rel_notes - - 1_13_0_rel_notes - - 1_12_0_rel_notes - - 1_11_0_rel_notes - - 1_10_0_rel_notes - - 1_9_2_rel_notes - - 1_9_1_rel_notes - - 1_9_0_rel_notes - - 1_8_0_rel_notes - - 1_7_1_rel_notes - - 1_7_0_rel_notes - - 1_6_0_rel_notes - - 1_5_1_rel_notes - - 1_5_0_rel_notes - - 1_4_0_rel_notes - - 1_3_0_rel_notes - - 1_2_1_rel_notes - - 1_2_0_rel_notes - - 1_1_0_rel_notes - - 1_0_0_rel_notes - - 0_8_0_rel_notes - - 0_7_0_rel_notes - - 0_6_0_rel_notes - - 0_5_0_rel_notes - - 0_4_0_rel_notes - - 0_3_0_rel_notes - - 0_2_0_rel_notes - - 0_1_0_rel_notes - - 0_0_1_rel_notes -originalFilePath: product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/meta.yml -editTarget: originalFilePath ---- - - -The EDB Postgres for Kubernetes documentation describes the major version of EDB Postgres for Kubernetes, including minor releases and patches. The release notes provide information on what is new in each release. For new functionality introduced in a minor or patch release, the content also indicates the release that introduced the feature. - - -| Version | Release date | Upstream merges | -|---|---|---| -| [1.30.0-rc1](./1_30_0-rc1_rel_notes) | 19 Jun 2026 | Upstream [1.30.0-rc1](https://cloudnative-pg.io/docs/1.30/release_notes/v1.30/) | -| [1.29.1](./1_29_1_rel_notes) | 08 May 2026 | Upstream [1.29.1](https://cloudnative-pg.io/docs/1.29/release_notes/v1.29/) | -| [1.29.0](./1_29_0_rel_notes) | 31 Mar 2026 | Upstream [1.29.0](https://cloudnative-pg.io/releases/cloudnative-pg-1-29.0-released/) | -| [1.28.3](./1_28_3_rel_notes) | 08 May 2026 | Upstream [1.28.3](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) | -| [1.28.2](./1_28_2_rel_notes) | 31 Mar 2026 | Upstream [1.28.2](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) | -| [1.28.1](./1_28_1_rel_notes) | 10 Feb 2026 | Upstream [1.28.1](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) | -| [1.28.0](./1_28_0_rel_notes) | 16 Dec 2025 | Upstream [1.28.0](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) | -| [1.27.4](./1_27_4_rel_notes) | 31 Mar 2026 | Upstream [1.27.4](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) | -| [1.27.3](./1_27_3_rel_notes) | 10 Feb 2026 | Upstream [1.27.3](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) | -| [1.27.2](./1_27_2_rel_notes) | 16 Dec 2025 | Upstream [1.27.2](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) | -| [1.27.1](./1_27_1_rel_notes) | 24 Oct 2025 | Upstream [1.27.1](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) | -| [1.27.0](./1_27_0_rel_notes) | 19 Aug 2025 | Upstream [1.27.0](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) | -| [1.26.3](./1_26_3_rel_notes) | 16 Dec 2025 | Upstream [1.26.3](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) | -| [1.26.2](./1_26_2_rel_notes) | 24 Oct 2025 | Upstream [1.26.2](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) | -| [1.26.1](./1_26_1_rel_notes) | 25 Jul 2025 | Upstream [1.26.1](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) | -| [1.26.0](./1_26_0_rel_notes) | 23 May 2025 | Upstream [1.26.0](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) | -| [1.25.8](./1_25_8_rel_notes) | 08 May 2026 | None | -| [1.25.7](./1_25_7_rel_notes) | 02 Apr 2026 | None | -| [1.25.6](./1_25_6_rel_notes) | 10 Feb 2026 | None | -| [1.25.5](./1_25_5_rel_notes) | 16 Dec 2025 | None | -| [1.25.4](./1_25_4_rel_notes) | 24 Oct 2025 | Upstream [1.25.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) | -| [1.25.3](./1_25_3_rel_notes) | 25 Jul 2025 | Upstream [1.25.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) | -| [1.25.2](./1_25_2_rel_notes) | 23 May 2025 | Upstream [1.25.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) | -| [1.25.1](./1_25_1_rel_notes) | 04 Mar 2025 | Upstream [1.25.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) | -| [1.25.0](./1_25_0_rel_notes) | 23 Dec 2024 | Upstream [1.25.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) | -| [1.24.4](./1_24_4_rel_notes) | 23 May 2025 | Upstream [1.24.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) | -| [1.24.3](./1_24_3_rel_notes) | 04 Mar 2025 | Upstream [1.24.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) | -| [1.24.2](./1_24_2_rel_notes) | 23 Dec 2024 | Upstream [1.24.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) | -| [1.24.1](./1_24_1_rel_notes) | 18 Oct 2024 | Upstream [1.24.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) | -| [1.24.0](./1_24_0_rel_notes) | 26 Aug 2024 | Upstream [1.24.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) | -| [1.23.6](./1_23_6_rel_notes) | 23 Dec 2024 | Upstream [1.23.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) | -| [1.23.5](./1_23_5_rel_notes) | 18 Oct 2024 | Upstream [1.23.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) | -| [1.23.4](./1_23_4_rel_notes) | 26 Aug 2024 | Upstream [1.23.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) | -| [1.23.3](./1_23_3_rel_notes) | 01 Aug 2024 | Upstream [1.23.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) | -| [1.23.2](./1_23_2_rel_notes) | 13 Jun 2024 | Upstream [1.23.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) | -| [1.23.1](./1_23_1_rel_notes) | 29 Apr 2024 | Upstream [1.23.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) | -| [1.23.0](./1_23_0_rel_notes) | 24 Apr 2024 | Upstream [1.23.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) | -| [1.22.11](./1_22_11_rel_notes) | 25 Jul 2025 | None | -| [1.22.10](./1_22_10_rel_notes) | 23 May 2025 | None | -| [1.22.9](./1_22_9_rel_notes) | 04 Mar 2025 | None | -| [1.22.8](./1_22_8_rel_notes) | 23 Dec 2024 | None | -| [1.22.7](./1_22_7_rel_notes) | 18 Oct 2024 | None | -| [1.22.6](./1_22_6_rel_notes) | 26 Aug 2024 | Upstream [1.22.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) | -| [1.22.5](./1_22_5_rel_notes) | 01 Aug 2024 | Upstream [1.22.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) | -| [1.22.4](./1_22_4_rel_notes) | 13 Jun 2024 | Upstream [1.22.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) | -| [1.22.3](./1_22_3_rel_notes) | 24 Apr 2024 | Upstream [1.22.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) | -| [1.22.2](./1_22_2_rel_notes) | 22 Mar 2024 | Upstream [1.22.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) | -| [1.22.1](./1_22_1_rel_notes) | 02 Feb 2024 | Upstream [1.22.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) | -| [1.22.0](./1_22_0_rel_notes) | 22 Dec 2023 | Upstream [1.22.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) | -| [1.21.6](./1_21_6_rel_notes) | 13 Jun 2024 | Upstream [1.21.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) | -| [1.21.5](./1_21_5_rel_notes) | 24 Apr 2024 | Upstream [1.21.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) | -| [1.21.4](./1_21_4_rel_notes) | 22 Mar 2024 | Upstream [1.21.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) | -| [1.21.3](./1_21_3_rel_notes) | 02 Feb 2024 | Upstream [1.21.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) | -| [1.21.2](./1_21_2_rel_notes) | 22 Dec 2023 | Upstream [1.21.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) | -| [1.21.1](./1_21_1_rel_notes) | 08 Nov 2023 | Upstream [1.21.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) | -| [1.21.0](./1_21_0_rel_notes) | 18 Oct 2023 | Upstream [1.21.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) | -| [1.20.6](./1_20_6_rel_notes) | 02 Feb 2024 | Upstream [1.20.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) | -| [1.20.5](./1_20_5_rel_notes) | 22 Dec 2023 | Upstream [1.20.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) | -| [1.20.4](./1_20_4_rel_notes) | 08 Nov 2023 | Upstream [1.20.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) | -| [1.20.3](./1_20_3_rel_notes) | 18 Oct 2023 | Upstream [1.20.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) | -| [1.20.2](./1_20_2_rel_notes) | 27 Jul 2023 | Upstream [1.20.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) | -| [1.20.1](./1_20_1_rel_notes) | 13 Jun 2023 | Upstream [1.20.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) | -| [1.20.0](./1_20_0_rel_notes) | 27 Apr 2023 | Upstream [1.20.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) | -| [1.19.6](./1_19_6_rel_notes) | 08 Nov 2023 | Upstream [1.19.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) | -| [1.19.5](./1_19_5_rel_notes) | 18 Oct 2023 | Upstream [1.19.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) | -| [1.19.4](./1_19_4_rel_notes) | 27 Jul 2023 | Upstream [1.19.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) | -| [1.19.3](./1_19_3_rel_notes) | 13 Jun 2023 | Upstream [1.19.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) | -| [1.19.2](./1_19_2_rel_notes) | 27 Apr 2023 | Upstream [1.19.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) | -| [1.19.1](./1_19_1_rel_notes) | 20 Mar 2023 | Upstream [1.19.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) | -| [1.19.0](./1_19_0_rel_notes) | 14 Feb 2023 | Upstream [1.19.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) | -| [1.18.13](./1_18_13_rel_notes) | 13 Jun 2024 | None | -| [1.18.12](./1_18_12_rel_notes) | 24 Apr 2024 | None | -| [1.18.11](./1_18_11_rel_notes) | 22 Mar 2024 | None | -| [1.18.10](./1_18_10_rel_notes) | 02 Feb 2024 | None | -| [1.18.9](./1_18_9_rel_notes) | 22 Dec 2023 | None | -| [1.18.8](./1_18_8_rel_notes) | 08 Nov 2023 | None | -| [1.18.7](./1_18_7_rel_notes) | 18 Oct 2023 | None | -| [1.18.6](./1_18_6_rel_notes) | 27 Jul 2023 | None | -| [1.18.5](./1_18_5_rel_notes) | 13 Jun 2023 | Upstream [1.18.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) | -| [1.18.4](./1_18_4_rel_notes) | 27 Apr 2023 | Upstream [1.18.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) | -| [1.18.3](./1_18_3_rel_notes) | 20 Mar 2023 | Upstream [1.18.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) | -| [1.18.2](./1_18_2_rel_notes) | 14 Feb 2023 | Upstream [1.18.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) | -| [1.18.1](./1_18_1_rel_notes) | 21 Dec 2022 | Upstream [1.18.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) | -| [1.18.0](./1_18_0_rel_notes) | 14 Nov 2022 | Upstream [1.18.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) | -| [1.17.5](./1_17_5_rel_notes) | 20 Mar 2023 | Upstream [1.17.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) | -| [1.17.4](./1_17_4_rel_notes) | 14 Feb 2023 | Upstream [1.17.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) | -| [1.17.3](./1_17_3_rel_notes) | 21 Dec 2022 | Upstream [1.17.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) | -| [1.17.2](./1_17_2_rel_notes) | 14 Nov 2022 | Upstream [1.17.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) | -| [1.17.1](./1_17_1_rel_notes) | 07 Oct 2022 | Upstream [1.17.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) | -| [1.17.0](./1_17_0_rel_notes) | 06 Sep 2022 | Upstream [1.17.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) | -| [1.16.5](./1_16_5_rel_notes) | 21 Dec 2022 | Upstream [1.16.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) | -| [1.16.4](./1_16_4_rel_notes) | 14 Nov 2022 | Upstream [1.16.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) | -| [1.16.3](./1_16_3_rel_notes) | 07 Oct 2022 | Upstream [1.16.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) | -| [1.16.2](./1_16_2_rel_notes) | 06 Sep 2022 | Upstream [1.16.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) | -| [1.16.1](./1_16_1_rel_notes) | 12 Aug 2022 | Upstream [1.16.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) | -| [1.16.0](./1_16_0_rel_notes) | 07 Jul 2022 | Upstream [1.16.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16) | -| [1.15.5](./1_15_5_rel_notes) | 07 Oct 2022 | Upstream [1.15.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) | -| [1.15.4](./1_15_4_rel_notes) | 06 Sep 2022 | Upstream [1.15.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) | -| [1.15.3](./1_15_3_rel_notes) | 12 Aug 2022 | Upstream [1.15.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) | -| [1.15.2](./1_15_2_rel_notes) | 07 Jul 2022 | Upstream [1.15.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) | -| [1.15.1](./1_15_1_rel_notes) | 27 May 2022 | Upstream [1.15.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) | -| [1.15.0](./1_15_0_rel_notes) | 21 Apr 2022 | Upstream [1.15.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) | -| [1.14.0](./1_14_0_rel_notes) | 25 Mar 2022 | NA | -| [1.13.0](./1_13_0_rel_notes) | 17 Feb 2022 | NA | -| [1.12.0](./1_12_0_rel_notes) | 11 Jan 2022 | NA | -| [1.11.0](./1_11_0_rel_notes) | 15 Dec 2021 | NA | -| [1.10.0](./1_10_0_rel_notes) | 11 Nov 2021 | NA | -| [1.9.2](./1_9_2_rel_notes) | 15 Oct 2021 | NA | -| [1.9.1](./1_9_1_rel_notes) | 30 Sep 2021 | NA | -| [1.9.0](./1_9_0_rel_notes) | 28 Sep 2021 | NA | -| [1.8.0](./1_8_0_rel_notes) | 13 Sep 2021 | NA | -| [1.7.1](./1_7_1_rel_notes) | 11 Aug 2021 | NA | -| [1.7.0](./1_7_0_rel_notes) | 28 Jul 2021 | NA | -| [1.6.0](./1_6_0_rel_notes) | 12 Jul 2021 | NA | -| [1.5.1](./1_5_1_rel_notes) | 11 Jun 2021 | NA | -| [1.5.0](./1_5_0_rel_notes) | 17 Jun 2021 | NA | -| [1.4.0](./1_4_0_rel_notes) | 18 May 2021 | NA | -| [1.3.0](./1_3_0_rel_notes) | 23 Apr 2021 | NA | -| [1.2.1](./1_2_1_rel_notes) | 06 Apr 2021 | NA | -| [1.2.0](./1_2_0_rel_notes) | 31 Mar 2021 | NA | -| [1.1.0](./1_1_0_rel_notes) | 03 Mar 2021 | NA | -| [1.0.0](./1_0_0_rel_notes) | 04 Feb 2021 | NA | -| [0.8.0](./0_8_0_rel_notes) | 29 Jan 2021 | NA | -| [0.7.0](./0_7_0_rel_notes) | 31 Dec 2020 | NA | -| [0.6.0](./0_6_0_rel_notes) | 04 Dec 2020 | NA | -| [0.5.0](./0_5_0_rel_notes) | 20 Nov 2020 | NA | -| [0.4.0](./0_4_0_rel_notes) | 05 Nov 2020 | NA | -| [0.3.0](./0_3_0_rel_notes) | 25 Sep 2020 | NA | -| [0.2.0](./0_2_0_rel_notes) | 11 Aug 2020 | NA | -| [0.1.0](./0_1_0_rel_notes) | 03 Apr 2020 | NA | -| [0.0.1](./0_0_1_rel_notes) | 05 Mar 2020 | NA | -!!! Info Versions prior to 1.0.0 - EDB Postgres for Kubernetes was made generally available on February 4, 2021. - Earlier versions were made available to selected customers prior to the GA release. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.22.10_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.22.10_rel_notes.yml deleted file mode 100644 index 89fc38533d1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.22.10_rel_notes.yml +++ /dev/null @@ -1,109 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.22.10 -date: 23 May 2025 -intro: | - EDB Postgres for Kubernetes version 1.22.10 is an LTS release of EDB Postgres for Kubernetes; - there is no corresponding upstream release of CloudNativePG. - - !!! Warning - A new LTS release, version 1.25.2, is now available! - Please note that support for 1.22 will officially end on July 2025. - - We recommend starting your upgrade planning now to transition smoothly to - the 1.25 LTS release. - - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.22.10 - "CNP plugin": 1.22.10 - upstream-merge: None - -relnotes: -- relnote: Implemented the `k8s.enterprisedb.io/validation` annotation - details: | - ...enabling users to disable - the validation webhook on EDB Postgres for Kubernetes-managed resources. Use with caution, - as this allows unrestricted changes. - jira: - addresses: #7196 - type: Enhancement - impact: High -- relnote: Added support for collecting `pg_stat_wal` metrics in PostgreSQL 18 - jira: - addresses: #7005 - type: Enhancement - impact: High -- relnote: Added support for LZ4, XZ, and Zstandard compression methods - details: | - ...when archiving - WAL files via Barman Cloud (*deprecated*). - jira: - addresses: #7151 - type: Enhancement - impact: High -- relnote: Set `imagePullPolicy` to `Always` for the operator deployment - details: | - ...to ensure that images are always pulled from the registry, reducing the risk of using - outdated or potentially unsafe local images. - jira: - addresses: #7250 - type: Security - impact: High -- relnote: Fixed native replication slot synchronization and logical replication failover for PostgreSQL 17 - details: | - ...by appending the `dbname` parameter to `primary_conninfo` in replica configurations. - jira: - addresses: #7298 - type: Bug fix - impact: High -- relnote: Improved backup efficiency by introducing a fail-fast mechanism in WAL archiving - details: | - ...allowing quicker detection of unexpected primary demotion and avoiding unnecessary retries. - jira: - addresses: #7483 - type: Bug fix - impact: High -- relnote: Fixed an off-by-one error in parallel WAL archiving - details: | - ...that could cause one extra worker process to be spawned beyond the requested number. - jira: - addresses: #7389 - type: Bug fix - impact: High -- relnote: Resolved a race condition that caused the operator to perform two switchovers when updating the PostgreSQL configuration. - jira: - addresses: #6991 - type: Bug fix - impact: High -- relnote: Corrected the `PodMonitor` configuration by adjusting the `matchLabels` scope for the targeted pooler and cluster pods. - details: | - Previously, the `matchLabels` were too broad, inadvertently inheriting labels from the cluster and leading to data collection from unintended targets. - jira: - addresses: #7063 - type: Bug fix - impact: High -- relnote: Added a webhook warning for clusters with a missing unit (e.g., MB, GB) in the `shared_buffers` configuration. - details: | - This will become an error in future releases. Users should update their configurations to include explicit units (e.g., `512MB` instead of `512`). - jira: - addresses: #7160 - type: Bug fix - impact: High -- relnote: | - `cnp` plugin: ensured that the primary Pod is recreated during an imperative restart when `primaryUpdateMethod` is set to `restart`, aligning its definition with the replicas. - component: CNP plugin - jira: - addresses: #7122 - type: Bug fix - impact: High -- relnote: Updated the default PostgreSQL version to 17.5 for new cluster definitions. - jira: - addresses: #7556 - type: Change - impact: High -- relnote: Updated the default PgBouncer version to **1.24.1** for new `Pooler` deployments. - jira: - addresses: #7399 - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.22.11_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.22.11_rel_notes.yml deleted file mode 100644 index 02ba3841c72..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.22.11_rel_notes.yml +++ /dev/null @@ -1,57 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.22.11 -date: 25 July 2025 -intro: | - EDB Postgres for Kubernetes version 1.22.11 is an LTS release of EDB Postgres for Kubernetes; - there is no corresponding upstream release of CloudNativePG. - - *In memory of [DJ Walker-Morgan](https://www.linkedin.com/in/codepope/).* - - !!! Warning - This is expected to be the last release in the 1.22.x series. - Users are strongly encouraged to upgrade to a newer minor version, as 1.22 - is no longer supported. - - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.22.11 - "CNP plugin": 1.22.11 - upstream-merge: None - -relnotes: -- relnote: Removed `386` and ARM (v5/v6/v7) architectures from the `cnp` plugin build matrix - details: | - ...reducing the number of published binaries. - jira: - addresses: #7648 - type: Change - impact: High -- relnote: Improved validation of `shared_buffers` by correctly considering `HugePages` settings - details: | - ...ensuring accurate memory configuration checks. - jira: - addresses: #7864 - type: Enhancement - impact: High -- relnote: Set `oom_score_adj` for PostgreSQL worker processes - details: | - ...to improve prioritization during out-of-memory situations. - jira: - addresses: #7891 - type: Enhancement - impact: High -- relnote: Added the `systemID` field and related condition in the `Cluster` status - details: | - ...to track the PostgreSQL system identifier. - jira: - addresses: #7717 - type: Enhancement - impact: High -- relnote: Added a mutex in the connection pooler to protect concurrent access to the connections map - details: | - ...improving stability in high-concurrency environments. - jira: - addresses: #7804 - type: Bug fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.24.4_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.24.4_rel_notes.yml deleted file mode 100644 index ff96636afc1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.24.4_rel_notes.yml +++ /dev/null @@ -1,19 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.24.4 -date: 23 May 2025 -upstream-merge: Upstream [1.24.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.24.4 - "CNP plugin": 1.24.4 - upstream-merge: Upstream [1.24.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) -relnotes: -- relnote: | - Merged with community CloudNativePG 1.24.4 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.2_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.2_rel_notes.yml deleted file mode 100644 index e76bcde9c7d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.2_rel_notes.yml +++ /dev/null @@ -1,19 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.25.2 -date: 23 May 2025 -upstream-merge: Upstream [1.25.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.25.2 - "CNP plugin": 1.25.2 - upstream-merge: Upstream [1.25.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) -relnotes: -- relnote: | - Merged with community CloudNativePG 1.25.2 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.3_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.3_rel_notes.yml deleted file mode 100644 index a2b26087548..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.3_rel_notes.yml +++ /dev/null @@ -1,19 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.25.3 -date: 25 July 2025 -upstream-merge: Upstream [1.25.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.25.3 - "CNP plugin": 1.25.3 - upstream-merge: Upstream [1.25.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) -relnotes: -- relnote: | - Merged with community CloudNativePG 1.25.3 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.4_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.4_rel_notes.yml deleted file mode 100644 index 648afbd1cc4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.4_rel_notes.yml +++ /dev/null @@ -1,23 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.25.4 -date: 24 October 2025 -upstream-merge: Upstream [1.25.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) -intro: | - This release of EDB CloudNativePG Cluster is built on the final community release of the 1.25.x series of CloudNativePG. - EDB will continue providing LTS releases in the 1.25.x series for the next 12 months, per our [Long-Term Support - policy](/postgres_for_kubernetes/1/#long-term-support). - - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.25.4 - "CNP plugin": 1.25.4 - upstream-merge: Upstream [1.25.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) -relnotes: -- relnote: | - Merged with community CloudNativePG 1.25.4 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.5_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.5_rel_notes.yml deleted file mode 100644 index 3efffbc368a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.5_rel_notes.yml +++ /dev/null @@ -1,116 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.25.5 -date: 16 December 2025 -intro: | - This release of EDB CloudNativePG Cluster is built on the final community release of the 1.25.x series of CloudNativePG. - EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support - policy](/postgres_for_kubernetes/1/#long-term-support). - - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.25.5 - "CNP plugin": 1.25.5 - upstream-merge: None -highlights: | - We've consolidated our [private container registry](../private_edb_registries) into a single location. This change simplifies access and deployment. - Starting with v1.25.5, any customer attempting an operator upgrade, MUST configure the new unified repository pull secret! - For details and instructions, follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/). -relnotes: -- relnote: | - Added support for 1.28 CRD fields, bringing forward compatibility improvements - from the 1.28 release. - details: | - This includes enhanced `Database` CRD with foreign data wrapper support, - improved cluster security contexts, failover quorum configurations, TLS - configurations for `Pooler`, and the `majorVersion` field in `Backup` - resources. - jira: - addresses: 1109 - type: Enhancement - impact: High -- relnote: | - Improved `cnp report` to generate more shell-friendly file names. - component: CNP plugin - jira: - addresses: #8984 - type: Enhancement - impact: High -- relnote: | - Fixed the `CheckEmptyWalArchive` safeguard to run correctly when restoring - from a volume snapshot using CNP-I backup/WAL plugins (e.g., - `plugin-barman-cloud`). - details: | - Previously, this check was skipped for plugin-based implementations. - jira: - addresses: #9306 - type: Bug Fix - impact: High -- relnote: | - Fixed TLS certificate verification issues when connecting to CNP-I plugins - by adding the `k8s.enterprisedb.io/pluginServerName` annotation. - details: | - This allows customizing the DNS name used for certificate verification in - environments where the plugin's certificate uses a different DNS name than - the Service name. - jira: - addresses: #9222 - type: Bug Fix - impact: High -- relnote: | - Fixed an issue where the instance manager controller could fail to restart - after an error, reporting a "controller already exists" message. - details: | - The controller now uses `SkipNameValidation` for subsequent initialization - attempts. - Contributed by @mateusoliveira43. - jira: - addresses: #9123 - type: Bug Fix - impact: High -- relnote: | - Fixed incorrect WAL restore path handling in plugins when the destination - path is absolute, preventing path duplication issues. - details: | - Contributed by @Endevir. - jira: - addresses: #9093 - type: Bug Fix - impact: High -- relnote: | - Fixed the `CREATE PUBLICATION` SQL generation for multi-table publications to be backward-compatible with PostgreSQL 13+. - details: | - The previously generated syntax - was only valid for PostgreSQL 15+ and caused syntax errors on older versions. - jira: - addresses: #8888 - type: Bug Fix - impact: High -- relnote: | - Fixed backup failures in complex pod definitions by reliably selecting the `postgres` container by name instead of by index. - jira: - addresses: #8964 - type: Bug Fix - impact: High -- relnote: | - `cnp` plugin: Fixed bugs in `cnp report` log collection, especially when fetching previous logs. - details: | - The collector now correctly fetches previous and current logs in separate requests and gracefully handles missing previous logs (e.g., on containers with no restart history), ensuring current logs are always collected. - component: CNP plugin - jira: - addresses: #8992 - type: Bug Fix - impact: High -- relnote: | - Updated the default PostgreSQL version to `18.1-standard-ubi9`. - jira: - addresses: #9178 - type: Change - impact: High -- relnote: | - Updated the default PgBouncer version to **1.25.1**, which carries - a fix for **CVE-2025-12819**, for new Pooler deployments. - jira: - addresses: #9367 - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.6_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.6_rel_notes.yml deleted file mode 100644 index d9bbb56d3fe..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.6_rel_notes.yml +++ /dev/null @@ -1,176 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.25.6 -date: 10 February 2026 -intro: | - This release of EDB CloudNativePG Cluster is built on the final community release of the 1.25.x series of CloudNativePG. - EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support - policy](/postgres_for_kubernetes/1/#long-term-support). - - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.25.6 - "CNP plugin": 1.25.6 - upstream-merge: None -relnotes: -- relnote: | - Added support for Azure's `DefaultAzureCredential` authentication mechanism - for backup and recovery operations. - details: | - This can be enabled by setting - `azureCredentials.useDefaultAzureCredentials: true` in the backup - configuration, simplifying authentication in Azure environments without - requiring explicit storage account keys or SAS tokens. - jira: - addresses: #9468 - type: Enhancement - impact: High -- relnote: | - Fixed a bug where replicas could enter a crash-loop by attempting to download - timeline history files from future timelines. - details: | - This occurred when stale files - remained in the WAL archive from a previous cluster life, and replicas would - incorrectly try to fetch them during recovery. - jira: - addresses: #9650 - type: Bug Fix - impact: High -- relnote: | - Fixed a race condition in `replica_cluster` setups during designated primary - transitions, preventing transient "no primary" states in the replica cluster. - jira: - addresses: #9601 - type: Bug Fix - impact: High - -- relnote: | - Fixed a validation gap in Azure object store configurations where the - `storageAccount` was not required when using explicit credentials (such as a - storage key or SAS token). - details: | - The operator now enforces that a storage account - name is provided in these cases and that `connectionString` is mutually - exclusive with other authentication parameters. - jira: - addresses: #9604 - type: Bug Fix - impact: High - -- relnote: | - Optimized the deletion path so the operator begins cleaning up resources - immediately when a cluster is marked for deletion. - details: | - This significantly reduces the time a cluster remains in `Terminating` status - while waiting for internal reconciliation loops. - jira: - addresses: #9555 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where replication slots were not properly dropped from - replicas when the feature was disabled or the cluster was reconfigured. - details: | - This ensures that unused slots do not cause WAL build-up on the primary. - jira: - addresses: #9381 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where `imagePullSecrets` were not added to the `ServiceAccount` - created for the `Pooler`. - details: | - Previously, these secrets were applied to the - Deployment but not the SA, which caused image pull failures in restricted - environments using certain security policies. - jira: - addresses: #9427 - type: Bug Fix - impact: High - -- relnote: | - Added a check to verify ownership before the operator deletes a `PodMonitor`. - details: | - This prevents the operator from accidentally deleting manually managed - monitoring resources that happen to share a name with expected CNP - resources. Contributed by @juliamertz. - jira: - addresses: #9340 - type: Bug Fix - impact: High - -- relnote: | - Fixed a bug where `pg_stat_archiver` metrics would continue to report stale - data on standby instances after a switchover. - details: | - The exporter now skips these metrics on standbys, as PostgreSQL only provides - valid archiver stats on the primary. - jira: - addresses: #9411 - type: Bug Fix - impact: High - -- relnote: | - Clarified the interpretation of timestamp formats for recovery `targetTime`. - details: | - Timestamps provided without an explicit timezone are now consistently - interpreted as UTC. Contributed by @pchovelon. - jira: - addresses: #8937 - type: Bug Fix - impact: High - -- relnote: | - Fixed backup status updates to prevent "resource has been modified" errors - during concurrent updates. - jira: - addresses: #9551 - type: Bug Fix - impact: High - -- relnote: | - Fixed event reporting to use the correct pod name when a backup pod is not - found. - jira: - addresses: #9552 - type: Bug Fix - impact: High - -- relnote: | - Improved performance of scheduled backup operations for clusters with a very - high number of historical backups. - jira: - addresses: #9489 - type: Bug Fix - impact: High - -- relnote: | - Fixed error handling when removing finalizers on `Database` objects. - jira: - addresses: #9431 - type: Bug Fix - impact: High - -- relnote: | - Updated the `status` command to display "Disabled" when the - `skipWalArchiving` annotation is present on a cluster. - details: | - This replaces - confusing "starting up" or "unknown" states when WAL archiving is - intentionally bypassed. - jira: - addresses: #9709 - component: CNP plugin - type: Bug Fix - impact: High - -- relnote: | - Fixed the `logs --follow` command to continue polling for new pods instead - of exiting prematurely when all current log streams complete. - jira: - addresses: #9599 - component: CNP plugin - type: Bug Fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.7_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.7_rel_notes.yml deleted file mode 100644 index 444d818eb46..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.7_rel_notes.yml +++ /dev/null @@ -1,190 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.25.7 -date: 2 April 2026 -intro: | - This release of EDB CloudNativePG Cluster is built on the final community release of the 1.25.x series of CloudNativePG. - EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support - policy](/postgres_for_kubernetes/1/#long-term-support). - - !!! Warning EDB CloudNativePG Cluster 1.25 reaches End-of-Life in June 2026. - - Users are encouraged to start planning their upgrade to a newer minor - version before that date. - - !!! - - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.25.7 - "CNP plugin": 1.25.7 - upstream-merge: None -relnotes: -- relnote: | - Improved the `Pooler` CRD with support for granular configuration of TLS - cipher suites and minimum/maximum TLS versions. - details: | - This enables administrators - to meet strict security compliance requirements for pooler-to-client and - pooler-to-server connections. - Contributed by @alex1989hu. - jira: - addresses: #9571 - type: Enhancement - impact: High - -- relnote: | - Improved role management by verifying the instance is the primary before - each reconciliation cycle - details: | - ...avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas. - jira: - addresses: #9971 - type: Enhancement - impact: High - -- relnote: | - The operator now honors the `primaryUpdateMethod` when adding new PVCs to a - cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is - respected during storage expansion or additions. - jira: - addresses: #9720 - type: Enhancement - impact: High - -- relnote: | - Security best practices integration**: integrated the OpenSSF baseline - scanner and added a `SECURITY-INSIGHTS.yaml` file to the repository to align - with industry-standard security reporting. - jira: - addresses: #10054, #10062 - type: Security - impact: High - -- relnote: | - SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software - Artifacts) provenance to release binaries and container images. - details: | - Additionally, - enabled Software Bill of Materials (SBOM) generation within the GoReleaser - pipeline for improved dependency transparency. - jira: - addresses: #10048, #10074 - type: Security - impact: High - -- relnote: | - Password leak prevention**: fixed a potential security risk where PostgreSQL - could leak role passwords in the logs during specific reconciliation phases. - jira: - addresses: #9950 - type: Security - impact: High - -- relnote: | - Updated the default PostgreSQL version to 18.3 (image `18.3-standard-ubi9`). - jira: - addresses: #10090 - type: Change - impact: High - -- relnote: | - Fixed an issue where replicas would get stuck in a `Pending` state if the - `VolumeSnapshot` used for the initial bootstrap had been deleted. - details: | - The operator now validates snapshot existence before use; if a snapshot is missing, - it attempts to use the next available candidate or falls back to - `pg_basebackup`. - jira: - addresses: #10192 - type: Bug Fix - impact: High - -- relnote: | - Prevented the "supervised primary" rollout strategy from consuming all - available rollout slots, which previously caused delays in scheduled updates. - Contributed by @ermakov-oleg. - jira: - addresses: #9977 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where certain hot-standby parameter changes were not being - correctly applied to replica clusters. - jira: - addresses: #9952 - type: Bug Fix - impact: High - -- relnote: | - Fixed webhook validation of bootstrap recovery sources to accept external - clusters configured with `ConnectionParameters` (for `pg_basebackup`-based - recovery). - details: | - Previously, these were incorrectly rejected unless a Barman - object store or CNPG-i plugin was also configured. - jira: - addresses: #10268 - type: Bug Fix - impact: High - -- relnote: | - When hibernating a non-healthy cluster, the operator now reports a - `WaitingForHealthy` condition, making the deferred hibernation state visible - jira: - addresses: #10193 - type: Bug Fix - impact: High - -- relnote: | - Fixed fencing to work correctly even when the target pod does not exist. - details: | - Fencing operates on a cluster-level annotation and should not depend on pod - existence; instance name validation is now performed only in the `cnp - fencing on` command. - jira: - addresses: #10035 - type: Bug Fix - impact: High - -- relnote: | - Fixed the cluster and pooler service reconcilers to correctly handle changes - to all spec fields when using the patch update strategy. The reconciler now - uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields - (such as `loadBalancerClass`) from being inadvertently removed. - jira: - addresses: #10190, #10311 - type: Bug Fix - impact: High - -- relnote: | - Fixed a race condition in the deprecated in-tree Barman Cloud backup - implementation affecting parallel WAL restore, where prefetched files could - be read while still being downloaded, causing PostgreSQL recovery to fail - with "invalid checkpoint record" errors. - jira: - addresses: #10285 - type: Bug Fix - impact: High - -- relnote: | - Fixed the timeline history file validation to also apply to plugin-based WAL restore. - details: | - Previously, the protection introduced in - [#9650](https://github.com/cloudnative-pg/cloudnative-pg/pull/9650) only - covered in-tree restores, allowing plugins to bypass the check and download - future timeline history files, causing timeline mismatch errors on replicas. - jira: - addresses: #9849 - type: Bug Fix - impact: High - -- relnote: | - The cnp plugin now correctly propagates ImagePullSecrets to the - `pgbench` Job pod template. - jira: - component: CNP plugin - addresses: #10174 - type: Bug Fix - impact: High \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.8_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.8_rel_notes.yml deleted file mode 100644 index 63e9f23090c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.25.8_rel_notes.yml +++ /dev/null @@ -1,197 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.25.8 -date: 8 May 2026 -intro: | - This release of EDB CloudNativePG Cluster is part of the LTS series for 1.25.x. - EDB will continue providing LTS releases in the 1.25.x series according to our [Long-Term Support - policy](/postgres_for_kubernetes/1/#long-term-support). - - !!! Warning EDB CloudNativePG Cluster 1.25 reaches End-of-Life in June 2026. - - Users are encouraged to start planning their upgrade to a newer minor - version before that date. - - !!! - - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.25.8 - "CNP plugin": 1.25.8 - upstream-merge: None -highlights: | - **`CVE-2026-44477` / `GHSA-423p-g724-fr39`: metrics exporter privilege - escalation.** The metrics exporter no longer authenticates as the - `postgres` superuser. It now uses a dedicated `cnp_metrics_exporter` role - with `pg_monitor` privileges only, closing a chain that let a low-privilege - database user gain PostgreSQL superuser. - ([`GHSA-423p-g724-fr39`](https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-423p-g724-fr39)) - - Upgrade impact: custom monitoring queries that read user-owned tables, or - use `target_databases: '*'` against databases where `PUBLIC CONNECT` has - been revoked, need explicit `GRANT` statements to `cnp_metrics_exporter`. - See ["Custom query privileges and safety"](../monitoring/#custom-query-privileges-and-safety) - and ["Manually creating the metrics exporter role"](../monitoring/#manually-creating-the-metrics-exporter-role) - in the monitoring documentation. - - For replica clusters, upgrade the source primary cluster before any - replica clusters that consume from it. The `cnp_metrics_exporter` role - is created on the source primary and replicates downstream; a replica - cluster upgraded first will scrape against a missing role until the - source primary upgrades. The manual-recovery section linked above also - covers replica clusters. -relnotes: -- relnote: | - Schema-qualified catalog references in default monitoring queries - details: | - Hardened the shipped monitoring configuration and documentation samples by - qualifying every `pg_catalog` object explicitly. Unqualified references - resolve through `search_path`, which a database user can manipulate to - shadow built-in objects. - jira: - addresses: #10576 - type: Security - impact: High - -- relnote: | - Discoverable SBOM and provenance attestations - details: | - SBOM and SLSA provenance attached to operator container images now follow - the OCI 1.1 Referrers spec, so standard registry tooling and supply-chain - scanners can discover them automatically. - jira: - addresses: #10601 - type: Security - impact: High - -- relnote: | - CVE remediation in `github.com/jackc/pgx/v5` - details: | - Bumped to v5.9.2 to pick up upstream fixes for `CVE-2026-33816` - (memory-safety in `pgproto3`) and `GHSA-j88v-2chj-qfwx` (SQL injection via - simple-protocol dollar-quoted string handling). - jira: - addresses: #10435, #10497 - type: Security - impact: High - -- relnote: | - CVE remediation in the Go runtime - details: | - Built with Go 1.26.3 to pick up upstream fixes in `crypto/x509`, - `crypto/tls`, `net/http`, and `net` (CVE-2026-32280, CVE-2026-32281, - CVE-2026-33810, CVE-2026-33814, CVE-2026-33811, CVE-2026-39825). - jira: - addresses: #10461, #10647 - type: Security - impact: High - -- relnote: | - Build pipeline hardening - details: | - The Go 1.26.3 bump also addresses CVE-2026-42501 (`cmd/go` module-checksum - validation), reducing supply-chain exposure during release builds. The - affected code paths are not reachable from the running operator. - jira: - addresses: #10647 - type: Security - impact: High - -- relnote: | - Switched TLS peer verification from `VerifyPeerCertificate` to - `VerifyConnection`, which runs on every completed handshake (the former is - skipped on resumed TLS 1.3 sessions). - details: | - Session resumption is not enabled in EDB Postgres for Kubernetes today, so - this has no observable effect, but it future-proofs verification if - session caching is introduced later. - jira: - addresses: #10478 - type: Change - impact: High - -- relnote: | - Fixed a failover window where the former primary kept its primary label. - details: | - If the former primary returned during failover (for example, after a - transient network partition), the `-rw` service kept routing to it, - replicas could reconnect, and committed writes were lost to `pg_rewind`. - The old primary is now labeled `unhealthy` to isolate it from service - traffic during failover. - jira: - addresses: #10409 - type: Bug Fix - impact: High - -- relnote: | - Fixed failover not being triggered when the node hosting the primary - becomes unreachable. - details: | - The operator now reads the pod's `Ready` condition (flipped to `False` by - the node controller when the kubelet stops reporting) instead of - `ContainersReady`, which stays stale as `True` in that scenario. Combined - with the spurious-failover guard - ([#10445](https://github.com/cloudnative-pg/cloudnative-pg/pull/10445)), - failover triggers only when Kubernetes itself marks the pod not Ready. - jira: - addresses: #10448 - type: Bug Fix - impact: High - -- relnote: | - Fixed spurious failovers caused by transient failures on the primary's - HTTP status endpoint. - jira: - addresses: #10445 - type: Bug Fix - impact: High - -- relnote: | - Fixed escaping of backslashes and control characters in PostgreSQL - configuration values. - details: | - Previously, such characters in parameters like `log_line_prefix` could - corrupt the configuration file or be silently stripped at runtime. - jira: - addresses: #10515 - type: Bug Fix - impact: High - -- relnote: | - Fixed `restore_command` construction to shell-quote each argument. - details: | - Values such as a `destinationPath` containing whitespace (for example, - `s3://my bucket/wal`) were word-split by the POSIX shell and passed to the - WAL restore tool as separate arguments. - jira: - addresses: #10518 - type: Bug Fix - impact: High - -- relnote: | - Tightened `recoveryTarget` validation in the admission webhook. - details: | - `targetXID` must now be a non-negative 32-bit integer, and `targetName` - must be shorter than 64 bytes and free of ASCII control characters. - Malformed values are rejected at admission instead of failing later during - PostgreSQL recovery. - jira: - addresses: #10565 - type: Bug Fix - impact: High - -- relnote: | - Fixed snapshot restores failing when leftover `pgsql_tmp*` directories - were present in the data directory. - jira: - addresses: #10447 - type: Bug Fix - impact: High - -- relnote: | - Fixed a deadlock occurring when PVC storage size and resource requests - are changed simultaneously. - jira: - addresses: #10427 - type: Bug Fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.0_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.0_rel_notes.yml deleted file mode 100644 index 18e33966ed4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.0_rel_notes.yml +++ /dev/null @@ -1,18 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.26.0 -date: 23 May 2025 -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.26.0 - "CNP plugin": 1.26.0 - upstream-merge: Upstream [1.26.0](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) -relnotes: -- relnote: | - Merged with community CloudNativePG 1.26.0 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.1_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.1_rel_notes.yml deleted file mode 100644 index 63274a37796..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.1_rel_notes.yml +++ /dev/null @@ -1,18 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.26.1 -date: 25 July 2025 -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.26.1 - "CNP plugin": 1.26.1 - upstream-merge: Upstream [1.26.1](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) -relnotes: -- relnote: | - Merged with community CloudNativePG 1.26.1 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.2_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.2_rel_notes.yml deleted file mode 100644 index b198d2f41e7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.2_rel_notes.yml +++ /dev/null @@ -1,18 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.26.2 -date: 24 October 2025 -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.26.2 - "CNP plugin": 1.26.2 - upstream-merge: Upstream [1.26.2](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) -relnotes: -- relnote: | - Merged with community CloudNativePG 1.26.2 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.3_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.3_rel_notes.yml deleted file mode 100644 index c5c5f2d037b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.26.3_rel_notes.yml +++ /dev/null @@ -1,35 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.26.3 -date: 16 December 2025 -upstream-merge: Upstream [1.26.3](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.26.3 - "CNP plugin": 1.26.3 - upstream-merge: Upstream [1.26.3](https://cloudnative-pg.io/docs/devel/release_notes/v1.26/) -highlights: | - We've consolidated our [private container registry](../private_edb_registries) into a single location. This change simplifies access and deployment. - Starting with v1.26.3, any customer attempting an operator upgrade, MUST configure the new unified repository pull secret! - For details and instructions, follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/). -relnotes: -- relnote: | - Updated the default PostgreSQL version to `18.1-standard-ubi9`. - jira: - addresses: "" - type: Change - impact: Medium -- relnote: | - Updated the default PgBouncer version to `1.25.1`, which carries a fix for CVE-2025-12819, for new Pooler deployments. - jira: - addresses: #9367 - type: Change - impact: High -- relnote: | - Merged with community CloudNativePG 1.26.3 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.0_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.0_rel_notes.yml deleted file mode 100644 index 57ba2ce9b62..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.0_rel_notes.yml +++ /dev/null @@ -1,105 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.27.0 -date: 19 August 2025 -intro: | - ### Important changes - - The default behavior of the [liveness probe](../instance_manager.md#liveness-probe) has been updated. - An [isolated primary is now forcibly shut down](../instance_manager.md#primary-isolation) - within the configured `livenessProbeTimeout` (default: 30 seconds). - - This release includes the following: -components: - "Operator": 1.27.0 - "CNP plugin": 1.27.0 - upstream-merge: Upstream [1.27.0](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) -relnotes: -- relnote: | - Dynamic loading of PostgreSQL extensions, packaged as OCI-compliant container images, is now supported. - details: | - The `.spec.postgresql.extensions` stanza allows you to mount PostgreSQL extensions as read-only and immutable volumes inside instance pods. - This enables dynamic extension management without rebuilding base images. - jira: - addresses: #7991 - type: Feature - impact: High -- relnote: Logical decoding slot synchronization in HA clusters - details: | - Added the `synchronizeLogicalDecoding` field under `spec.replicationSlots.highAvailability` to enable automatic synchronization of logical decoding slots across high-availability clusters. - This ensures that logical replication subscribers continue seamlessly after a publisher failover. - jira: - addresses: #7931 - type: Feature - impact: High -- relnote: Primary Isolation Check - details: | - Promoted to stable the liveness pinger experimental feature introduced in 1.26, - adding the `.spec.probes.liveness.isolationCheck` section to enable primary isolation checks - in the liveness probe by default. - This improves the detection and handling of primary connectivity issues in Kubernetes environments. - jira: - addresses: #7845 - type: Feature - impact: High -- relnote: Introduced an opt-in experimental feature that enables quorum-based failover - details: | - ...to improve safety and data durability during failover events. - This feature, also called failover quorum, can be activated via the `alpha.k8s.enterprisedb.io/failoverQuorum` annotation. - jira: - addresses: #7572 - type: Enhancement - impact: High -- relnote: Added support for user maps for predefined users such as `streaming_replica` - details: | - ...allowing the use of self-managed client certificates with different Common Names in environments with strict policies or shared CAs, - while still enabling replicas to join clusters using the `streaming_replica` role. - jira: - addresses: #7725 - type: Enhancement - impact: High -- relnote: Added a new `PhaseFailurePlugin` phase in the `Cluster` status - details: | - ...to improve observability of plugin-related failures. - jira: - addresses: #7988 - type: Enhancement - impact: High -- relnote: Made the `Backup.spec` field immutable after creation - details: | - ...ensuring consistency and predictability in backup operations. - jira: - addresses: #7904 - type: Enhancement - impact: High -- relnote: Added `fqdn-uri` and `fqdn-jdbc-uri` fields in the user secret - details: | - ...to simplify the retrieval of fully qualified domain name-based connection strings. - jira: - addresses: #7852 - type: Enhancement - impact: High -- relnote: Added `Postgres` interface support to the CNP-I operator - details: | - ...continuing the transition toward a plugin-based architecture. - jira: - addresses: #7179 - type: Enhancement - impact: High - component: CNP-I -- relnote: Added `metrics` capabilities to the CNP-I instance webserver - details: | - ...enabling metrics exposure directly from the instance for better observability. - jira: - addresses: #8033 - type: Enhancement - impact: High - component: CNP-I -- relnote: Unblocked rollouts when migrating to the `barman-cloud` plugin using the `switchover` strategy - details: | - Former primary Pods now restart correctly after WAL archiving fails due to missing plugin support. - jira: - addresses: #8236 - type: Bug fix - impact: High - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.1_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.1_rel_notes.yml deleted file mode 100644 index cf6541ba055..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.1_rel_notes.yml +++ /dev/null @@ -1,186 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.27.1 -date: 24 October 2025 -intro: | - This release includes the following: -components: - "Operator": 1.27.1 - "CNP plugin": 1.27.1 - upstream-merge: Upstream [1.27.1](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) -relnotes: -- relnote: | - Delayed the decommissioning of native in-core support for Barman Cloud to at - least version 1.29. - jira: - addresses: #8670 - type: Change - impact: High -- relnote: | - Adopted the new format of `postgres-containers` and `postgis-containers` - images and image catalog artifacts - details: | - and **updated** the default PostgreSQL - version to `18.0-system-trixie` (PostgreSQL 18 is now supported). - jira: - addresses: #8578, - #8760, - #8558 - type: Change - impact: High -- relnote: Deprecated the `monitoring.enablePodMonitor` field - details: | - in the `Cluster` and `Pooler` resources. This field will be removed in a future release. Users who - rely on `PodMonitor` resources should create them manually instead. - jira: - addresses: #8753 - type: Change - impact: High -- relnote: Added support for overriding the PgBouncer `auth_type`, `server_tls_sslmode`, and `client_tls_sslmode` settings - details: | - which were previously hardcoded. Default values remain consistent with the former behavior but can now be customized when required. - jira: - addresses: #8674 - type: Enhancement - impact: High -- relnote: Added a `CHECKPOINT` step before PostgreSQL smart and fast shutdowns - details: | - to reduce shutdown duration and replica promotion time, especially on systems with a high `checkpoint_timeout`. - jira: - addresses: #8867 - type: Enhancement - impact: High -- relnote: Added a warning in the instance manager for deprecated or unsupported OS versions - details: | - based on the official `postgres-containers` project. - jira: - addresses: #8601 - type: Enhancement - impact: High -- relnote: Improved certificate parsing error reporting - details: | - Failures now log specific errors instead of a generic message, aiding troubleshooting. - This is particularly relevant after the CVE-2025-58187 fix in Go 1.25.2 and 1.24.8, - which may trigger parsing failures for invalid DNS SANs. - jira: - addresses: #8801 - type: Enhancement - impact: High -- relnote: Added a check to ensure the destination WAL archive path is empty when bootstrapping a cluster using the `pg_basebackup` method - details: | - consistent with other bootstrap methods. - jira: - addresses: #8895 - type: Enhancement - impact: High -- relnote: Added validation to prevent backups from running on hibernated clusters - details: | - Backups attempted on such clusters now fail with reason `ClusterIsHibernated`, - following the standard prerequisite check pattern. - jira: - addresses: #8870 - type: Enhancement - impact: High -- relnote: Added support for `pprof` profiling - details: | - Instances can now enable the `pprof` tool by adding the `alpha.k8s.enterprisedb.io/enableInstancePprof` annotation - to the `Cluster` resource for advanced debugging. - jira: - addresses: #7876 - type: Enhancement - impact: High -- relnote: Updated the Flexible I/O Tester (FIO) image in the `cnp` plugin - details: | - to `wallnerryan/fiotools-aio:v2`, as provided by Ryan Wallner. - jira: - addresses: #8847 - component: CNP plugin - type: Enhancement - impact: High -- relnote: Enhanced the `cnp status backup` command to provide more detailed status information when using a `barman-cloud`-based backup plugin - jira: - addresses: #8780, - #8690 - type: Enhancement - impact: High - component: CNP plugin - -- relnote: Fixed backup restoration failures when using custom WAL segment sizes with parallel WAL recovery. - details: | - The operator no longer manages the end-of-WAL file marker during restoration, - preventing errors when backups span multiple WAL segments. - jira: - addresses: #8873 - type: Bug fix - impact: High -- relnote: | - Fixed a bug in major upgrades where a volume snapshot from a previous minor version - could be incorrectly used to optimize replica creation. - jira: - addresses: #8475 - type: Bug fix - impact: High -- relnote: Fixed `initdb` to wait for the application user secret before bootstrapping a new cluster - details: | - preventing potential race conditions. - jira: - addresses: #8663 - type: Bug fix - impact: High -- relnote: | - Fixed quorum-based failover to work correctly in clusters with only two - instances using synchronous replication. - jira: - addresses: #8680 - type: Bug fix - impact: High -- relnote: Fixed configuration hash calculation to ignore internal configuration fields - details: | - preventing unnecessary reconciliations. - jira: - addresses: #8868 - type: Bug fix - impact: High -- relnote: Fixed the connection retry logic in the `cnpgi` plugin - details: | - The reconciliation loop now detects connection pool changes correctly and uses exponential - backoff to reduce "closed pool" errors. - jira: - addresses: #8554 - type: Bug fix - impact: High -- relnote: Fixed volume snapshot usage during replica scaling to work with backup plugins. - details: | - Previously, this optimization was only available with the in-tree backup - implementation, but now clusters using backup plugins can also leverage volume - snapshots when creating new replicas. - jira: - addresses: #8506 - type: Bug fix - impact: High -- relnote: Fixed the `Pooler` templating to correctly inherit settings for the bootstrap controller init container. - jira: - addresses: #8394 - type: Bug fix - impact: High -- relnote: Fixed webhook errors to use the correct API group - details: | - (`postgresql.k8s.enterprisedb.io`) in `Pooler` and backup webhooks, ensuring consistent API error reporting. - jira: - addresses: #8485 - type: Bug fix - impact: High -- relnote : Fixed a potential nil pointer dereference in the hibernation reconciler - details: | - when handling errors. Contributed by @PascalBourdier. - jira: - addresses: #8756 - type: Bug fix - impact: High -- relnote: Fixed an issue in the environment cache where callers could inadvertently modify shared data. - details: | - The `LoadEnv` function now returns a copy of cached environment slices to prevent mutations from affecting the cache. - jira: - addresses: #8880 - type: Bug fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.2_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.2_rel_notes.yml deleted file mode 100644 index c4c55da75ed..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.2_rel_notes.yml +++ /dev/null @@ -1,34 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.27.2 -date: 16 December 2025 -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.27.2 - "CNP plugin": 1.27.2 - upstream-merge: Upstream [1.27.2](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) -highlights: | - We've consolidated our [private container registry](../private_edb_registries) into a single location. This change simplifies access and deployment. - Starting with v1.27.2, any customer attempting an operator upgrade, MUST configure the new unified repository pull secret! - For details and instructions, follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/). -relnotes: -- relnote: | - Updated the default PostgreSQL version to `18.1-standard-ubi9`. - jira: - addresses: "" - type: Change - impact: Medium -- relnote: | - Updated the default PgBouncer version to `1.25.1`, which carries a fix for CVE-2025-12819, for new Pooler deployments. - jira: - addresses: #9367 - type: Change - impact: High -- relnote: | - Merged with community CloudNativePG 1.27.2 upstream release. - See the community release notes - jira: - addresses: "" - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.3_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.3_rel_notes.yml deleted file mode 100644 index ae2c429dc9c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.3_rel_notes.yml +++ /dev/null @@ -1,210 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.27.3 -date: 10 February 2026 -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.27.3 - "CNP plugin": 1.27.3 - upstream-merge: Upstream [1.27.3](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) -relnotes: -- relnote: | - Added support for Azure's `DefaultAzureCredential` authentication mechanism - for backup and recovery operations. - details: | - This can be enabled by setting - `azureCredentials.useDefaultAzureCredentials: true` in the backup - configuration, simplifying authentication in Azure environments without - requiring explicit storage account keys or SAS tokens. - jira: - addresses: #9468 - type: Enhancement - impact: High -- relnote: | - Fixed validation of PostgreSQL extension names containing underscores (e.g., - `pg_partman`, `pg_ivm`). - details: | - Extension names with underscores are - automatically sanitized to use hyphens for Kubernetes volume names while - preserving the original name in mount paths. Webhook validation prevents - naming conflicts after sanitization. Contributed by @shusaan. - jira: - addresses: #9386 - type: Bug Fix - impact: High - -- relnote: | - Fixed a critical issue where the `TimelineID` in the cluster status was not - reset to 1 after a major version upgrade. - details: | - Because `pg_upgrade` initializes a - new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt - to restore incompatible history files from object storage, leading to fatal - "requested timeline is not a child of this server's history" errors. - jira: - addresses: #9830 - type: Bug Fix - impact: High - -- relnote: | - Fixed a bug where replicas could enter a crash-loop by attempting to download - timeline history files from future timelines. - details: | - This occurred when stale files - remained in the WAL archive from a previous cluster life, and replicas would - incorrectly try to fetch them during recovery. - jira: - addresses: #9650 - type: Bug Fix - impact: High -- relnote: | - Fixed a race condition in `replica_cluster` setups during designated primary - transitions, preventing transient "no primary" states in the replica cluster. - jira: - addresses: #9601 - type: Bug Fix - impact: High - -- relnote: | - The backup controller now uses the unique instance session ID to detect - instance manager restarts. - details: | - This prevents the operator from incorrectly - assuming a backup is still progressing if the underlying container has crashed - and restarted, which previously led to orphaned backup objects. - jira: - addresses: #9370 - type: Bug Fix - impact: High - -- relnote: | - Fixed a validation gap in Azure object store configurations where the - `storageAccount` was not required when using explicit credentials (such as a - storage key or SAS token). - details: | - The operator now enforces that a storage account - name is provided in these cases and that `connectionString` is mutually - exclusive with other authentication parameters. - jira: - addresses: #9604 - type: Bug Fix - impact: High - -- relnote: | - Optimized the deletion path so the operator begins cleaning up resources - immediately when a cluster is marked for deletion. - details: | - This significantly reduces the time a cluster remains in `Terminating` status - while waiting for internal reconciliation loops. - jira: - addresses: #9555 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where replication slots were not properly dropped from - replicas when the feature was disabled or the cluster was reconfigured. - details: | - This ensures that unused slots do not cause WAL build-up on the primary. - jira: - addresses: #9381 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where `imagePullSecrets` were not added to the `ServiceAccount` - created for the `Pooler`. - details: | - Previously, these secrets were applied to the - Deployment but not the SA, which caused image pull failures in restricted - environments using certain security policies. - jira: - addresses: #9427 - type: Bug Fix - impact: High - -- relnote: | - Added a check to verify ownership before the operator deletes a `PodMonitor`. - details: | - This prevents the operator from accidentally deleting manually managed - monitoring resources that happen to share a name with expected CNP - resources. Contributed by @juliamertz. - jira: - addresses: #9340 - type: Bug Fix - impact: High - -- relnote: | - Fixed a bug where `pg_stat_archiver` metrics would continue to report stale - data on standby instances after a switchover. - details: | - The exporter now skips these metrics on standbys, as PostgreSQL only provides - valid archiver stats on the primary. - jira: - addresses: #9411 - type: Bug Fix - impact: High - -- relnote: | - Clarified the interpretation of timestamp formats for recovery `targetTime`. - details: | - Timestamps provided without an explicit timezone are now consistently - interpreted as UTC. Contributed by @pchovelon. - jira: - addresses: #8937 - type: Bug Fix - impact: High - -- relnote: | - Fixed backup status updates to prevent "resource has been modified" errors - during concurrent updates. - jira: - addresses: #9551 - type: Bug Fix - impact: High - -- relnote: | - Fixed event reporting to use the correct pod name when a backup pod is not - found. - jira: - addresses: #9552 - type: Bug Fix - impact: High - -- relnote: | - Improved performance of scheduled backup operations for clusters with a very - high number of historical backups. - jira: - addresses: #9489 - type: Bug Fix - impact: High - -- relnote: | - Fixed error handling when removing finalizers on `Database` objects. - jira: - addresses: #9431 - type: Bug Fix - impact: High - -- relnote: | - Updated the `status` command to display "Disabled" when the - `skipWalArchiving` annotation is present on a cluster. - details: | - This replaces - confusing "starting up" or "unknown" states when WAL archiving is - intentionally bypassed. - jira: - addresses: #9709 - component: CNP plugin - type: Bug Fix - impact: High - -- relnote: | - Fixed the `logs --follow` command to continue polling for new pods instead - of exiting prematurely when all current log streams complete. - jira: - addresses: #9599 - component: CNP plugin - type: Bug Fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.4_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.4_rel_notes.yml deleted file mode 100644 index 37dbcfea0ed..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.27.4_rel_notes.yml +++ /dev/null @@ -1,236 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.27.4 -date: 31 March 2026 -intro: | - This release of EDB CloudNativePG Cluster includes the following: -components: - "Operator": 1.27.4 - "CNP plugin": 1.27.4 - upstream-merge: Upstream [1.27.4](https://cloudnative-pg.io/docs/1.27/release_notes/v1.27/) -highlights: | - Updated the deprecation notice for native (in-tree) Barman Cloud support to - reflect that it will now be removed in EDB Postgres for Kubernetes 1.30.0, rather than - 1.29.0. Users are still encouraged to migrate to the Barman Cloud Plugin. - ([#10167](https://github.com/cloudnative-pg/cloudnative-pg/pull/10167)) -relnotes: - -- relnote: | - Improved the `Pooler` CRD with support for granular configuration of TLS - cipher suites and minimum/maximum TLS versions. - details: | - This enables administrators - to meet strict security compliance requirements for pooler-to-client and - pooler-to-server connections. - Contributed by @alex1989hu. - jira: - addresses: #9571 - type: Enhancement - impact: High - -- relnote: | - Improved the reliability of major upgrades by setting `BackoffLimit=0` on the - upgrade job, preventing unnecessary retries of a failed `pg_upgrade`. - details: | - The operator now automatically deletes the failed job when a user reverts the - container image, allowing the cluster to restart gracefully on the original - version. - jira: - addresses: #10104, #10298 - type: Enhancement - impact: High - -- relnote: | - Improved role management by verifying the instance is the primary before - each reconciliation cycle - details: | - ...avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas. - jira: - addresses: #9971 - type: Enhancement - impact: High - -- relnote: | - The operator now honors the `primaryUpdateMethod` when adding new PVCs to a - cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is - respected during storage expansion or additions. - jira: - addresses: #9720 - type: Enhancement - impact: High - -- relnote: | - Security best practices integration**: integrated the OpenSSF baseline - scanner and added a `SECURITY-INSIGHTS.yaml` file to the repository to align - with industry-standard security reporting. - jira: - addresses: #10054, #10062 - type: Security - impact: High - -- relnote: | - SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software - Artifacts) provenance to release binaries and container images. - details: | - Additionally, - enabled Software Bill of Materials (SBOM) generation within the GoReleaser - pipeline for improved dependency transparency. - jira: - addresses: #10048, #10074 - type: Security - impact: High - -- relnote: | - Password leak prevention**: fixed a potential security risk where PostgreSQL - could leak role passwords in the logs during specific reconciliation phases. - jira: - addresses: #9950 - type: Security - impact: High - -- relnote: | - Updated the default PostgreSQL version to 18.3 (image `18.3-standard-ubi9`). - jira: - addresses: #10090 - type: Change - impact: High - - -- relnote: | - Fixed an issue where fencing annotations could not be processed when the WAL - disk was full - details: | - ...because the disk space check blocked the instance manager from - starting. The check is now performed later in the lifecycle loop, after - fencing is evaluated. - jira: - addresses: #10302 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where replicas would get stuck in a `Pending` state if the - `VolumeSnapshot` used for the initial bootstrap had been deleted. - details: | - The operator now validates snapshot existence before use; if a snapshot is missing, - it attempts to use the next available candidate or falls back to - `pg_basebackup`. - jira: - addresses: #10192 - type: Bug Fix - impact: High - -- relnote: | - Prevented the "supervised primary" rollout strategy from consuming all - available rollout slots, which previously caused delays in scheduled updates. - Contributed by @ermakov-oleg. - jira: - addresses: #9977 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where certain hot-standby parameter changes were not being - correctly applied to replica clusters. - jira: - addresses: #9952 - type: Bug Fix - impact: High - -- relnote: | - Fixed a bug in the CNPG-I reconciler hook that could lead to skipping - subsequent plugins when a "continue" result was returned. - Contributed by @sharifmshaker. - jira: - addresses: #9978 - type: Bug Fix - impact: High - -- relnote: | - Fixed a deadlock scenario that occurred when attempting to resize a - filesystem on a PVC that was not currently attached to a Pod. - Contributed by @jmealo. - jira: - addresses: #9981 - type: Bug Fix - impact: High - -- relnote: | - Fixed webhook validation of bootstrap recovery sources to accept external - clusters configured with `ConnectionParameters` (for `pg_basebackup`-based - recovery). - details: | - Previously, these were incorrectly rejected unless a Barman - object store or CNPG-i plugin was also configured. - jira: - addresses: #10268 - type: Bug Fix - impact: High - -- relnote: | - Volume names for extensions and tablespaces are now prefixed to avoid naming - collisions with standard cluster volumes. - jira: - addresses: #9973 - type: Bug Fix - impact: High - -- relnote: | - When hibernating a non-healthy cluster, the operator now reports a - `WaitingForHealthy` condition, making the deferred hibernation state visible - jira: - addresses: #10193 - type: Bug Fix - impact: High - -- relnote: | - Fixed fencing to work correctly even when the target pod does not exist. - details: | - Fencing operates on a cluster-level annotation and should not depend on pod - existence; instance name validation is now performed only in the `cnp - fencing on` command. - jira: - addresses: #10035 - type: Bug Fix - impact: High - -- relnote: | - Fixed the cluster and pooler service reconcilers to correctly handle changes - to all spec fields when using the patch update strategy. The reconciler now - uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields - (such as `loadBalancerClass`) from being inadvertently removed. - jira: - addresses: #10190, #10311 - type: Bug Fix - impact: High - -- relnote: | - Fixed a race condition in the deprecated in-tree Barman Cloud backup - implementation affecting parallel WAL restore, where prefetched files could - be read while still being downloaded, causing PostgreSQL recovery to fail - with "invalid checkpoint record" errors. - jira: - addresses: #10285 - type: Bug Fix - impact: High - -- relnote: | - Fixed the timeline history file validation to also apply to plugin-based WAL restore. - details: | - Previously, the protection introduced in - [#9650](https://github.com/cloudnative-pg/cloudnative-pg/pull/9650) only - covered in-tree restores, allowing plugins to bypass the check and download - future timeline history files, causing timeline mismatch errors on replicas. - jira: - addresses: #9849 - type: Bug Fix - impact: High - -- relnote: | - The cnp plugin now correctly propagates ImagePullSecrets to the - `pgbench` Job pod template. - jira: - component: CNP plugin - addresses: #10174 - type: Bug Fix - impact: High \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.0_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.0_rel_notes.yml deleted file mode 100644 index 9da26b10ac6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.0_rel_notes.yml +++ /dev/null @@ -1,286 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.28.0 -date: 16 December 2025 -intro: | - This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: -components: - "Operator": 1.28.0 - "CNP plugin": 1.28.0 - upstream-merge: Upstream [1.28.0](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) -highlights: | - We've consolidated our [private container registry](../private_edb_registries) into a single location. This change simplifies access and deployment. - Starting with v1.28.0, any customer attempting an operator upgrade, MUST configure the new unified repository pull secret! - For details and instructions, follow the [Central Migration Guide](/repos/working_with_repos/migrating_edb_registries/). -relnotes: -- relnote: | - Quorum-Based Failover Promoted to Stable - details: | - Promoted the quorum-based failover feature, introduced experimentally in 1.27.0, to a stable API. - This data-driven failover mechanism is now configured via the `spec.postgresql.synchronous.failoverQuorum` field, graduating from the previous `alpha.k8s.enterprisedb.io/failoverQuorum` annotation. - jira: - addresses: #8589 - type: Feature - impact: High -- relnote: | - Declarative Foreign Data Management - details: | - Introduced comprehensive declarative management for Foreign Data Wrappers (FDW) by extending the `Database` CRD. - This feature adds the `.spec.fdws` and `.spec.servers` fields, allowing you to manage FDW extensions and their corresponding foreign servers directly from the `Database` resource. - This work was implemented by Ying Zhu (@EdwinaZhu) as part of the LFX Mentorship Program 2025 Term 2. - jira: - addresses: #7942, #8401 - type: Feature - impact: High -- relnote: | - Enabled simultaneous image and configuration changes when using `primaryUpdateMethod: restart` - details: | - allowing you to update the container image (including PostgreSQL version or extensions) and - PostgreSQL configuration settings in the same operation. - Note that when using `primaryUpdateMethod: switchover`, image and - configuration changes must still be performed separately to avoid configuration - mismatches during the switchover process. - jira: - addresses: #8241 - type: Enhancement - impact: High -- relnote: | - Improved network failure detection for replica instances by setting the - default `tcp_user_timeout` to 5 seconds. - details: | - This change helps replicas detect - and recover from silent network drops more quickly. Previously, replicas could - wait up to 127 seconds before detecting such failures; with the new timeout, - they reconnect to the primary within 5 seconds. To preserve the previous - behavior, set `STANDBY_TCP_USER_TIMEOUT` to `0` in the operator configuration. - jira: - addresses: #9317 - type: Enhancement - impact: High -- relnote: | - Adopted standard Kubernetes recommended labels - details: | - (e.g., `app.kubernetes.io/name`) for all resources generated by EDB Postgres for Kubernetes - (Clusters, Backups, Poolers, etc.). Contributed by @JefeDavis. - jira: - addresses: #8087 - type: Enhancement - impact: High -- relnote: | - Introduced `securityContext` at the pod level and `containerSecurityContext` - for individual containers (including `postgres`, `init`, and sidecars). - details: | - This provides granular control over security settings, replacing the previous - cluster-wide `postgres` and `operator` user settings. Contributed by @x0ddf. - jira: - addresses: #6614 - type: Enhancement - impact: High -- relnote: | - Introduced the `alpha.k8s.enterprisedb.io/unrecoverable=true` annotation for replica - pods. - details: | - When applied, this annotation instructs the operator to permanently - delete the instance by removing its Pod and PVCs, after which it will recreate - the replica from the primary. - jira: - addresses: #8178 - type: Enhancement - impact: High -- relnote: | - Introduced a new caching layer for user-defined monitoring queries to reduce load on the PostgreSQL database. - jira: - addresses: #8003 - type: Enhancement - impact: High -- relnote: | - Enhanced PgBouncer integration by automatically setting `auth_dbname` to the - `pgbouncer` database, simplifying auth setup. - jira: - addresses: #8671 - type: Enhancement - impact: High -- relnote: | - Allowed providing stage-specific `pg_restore` options during database import. - details: | - (Stage-specific options are `preRestore`, `postRestore`, `dataRestore`.) Contributed by - @hanshal101. - jira: - addresses: #7690 - type: Enhancement - impact: High -- relnote: | - Added the PostgreSQL `majorVersion` to the `Backup` object's status for easier identification and management. - jira: - addresses: #8464 - type: Enhancement - impact: High -- relnote: | - Enhanced cluster restore to wait for all init containers to complete before starting the restore process. - details: | - This ensures that backup tools running in init containers finish preparing the data before the restore begins. - The implementation correctly handles Kubernetes init container sidecars by ignoring those with `RestartPolicy=Always`. - jira: - addresses: #9026 - type: Enhancement - impact: High -- relnote: | - Added the `PGBOUNCER_IMAGE_NAME` operator configuration parameter to allow overriding the default PgBouncer image. - details: | - This is useful for air-gapped environments or when using internal registries. - jira: - addresses: #9232 - type: Enhancement - impact: High -- relnote: | - CNP plugin: Added a `--timeout` flag to the `kubectl cnp status` command - details: | - for configuring the timeout for filesystem operations such as calculating - cluster size. The default remains 10 seconds but can be adjusted for - large clusters where operations may take longer. - component: CNP plugin - jira: - addresses: #9201 - type: Enhancement - impact: High -- relnote: | - Improved `cnp report` to generate more shell-friendly file names. - component: CNP plugin - jira: - addresses: #8984 - type: Enhancement - impact: High -- relnote: | - Allowed providing fine-grained custom TLS configurations for PgBouncer - details: | - The `Pooler` CRD was extended with `clientTLSSecret`, `clientCASecret`, - `serverTLSSecret`, and `serverCASecret` fields under `.spec.pgbouncer`. - These fields enable users to supply their own certificates for both - client-to-pooler and pooler-to-server connections, taking precedence over the - operator-generated certificates. - jira: - addresses: #8692 - type: Security - impact: High -- relnote: | - Added optional TLS support for the operator's metrics server (port 8080) - details: | - This feature is opt-in and enabled by setting the `METRICS_CERT_DIR` - environment variable, which instructs the operator to look for `tls.crt` and - `tls.key` files in the specified directory. When unset, the server continues to - use HTTP for backward compatibility. - jira: - addresses: #8997 - type: Security - impact: High -- relnote: | - Enabled `cnp_report_operator` to work with minimal permissions by making - only the operator deployment required - details: | - All other resources (pods, secrets, config maps, events, webhooks, and OLM data) are now optional and collected on - a best-efforts basis. The command gracefully handles permission errors for - those resources by logging clear warnings and continuing report generation with - available data, rather than failing completely. This enables least-privileged - access, where users may have limited, namespace-scoped permissions. - jira: - addresses: #8982 - type: Security - impact: High -- relnote: | - Improved resilience of all probe types (liveness, readiness, and startup) to - transient Kubernetes API server connectivity issues. - details: | - Probes now use a caching mechanism that falls back to cached cluster definitions - during brief network interruptions, preventing unnecessary pod restarts and - probe failures. - jira: - addresses: #9148 - type: Bug Fix - impact: High -- relnote: | - Fixed the `CheckEmptyWalArchive` safeguard to run correctly when restoring - from a volume snapshot using CNP-I backup/WAL plugins (e.g., - `plugin-barman-cloud`). - details: | - Previously, this check was skipped for plugin-based implementations. - jira: - addresses: #9306 - type: Bug Fix - impact: High -- relnote: | - Improved error detection and reporting when ImageCatalog retrieval fails. - details: | - The operator now emits a Warning event and logs errors for all failure types, - not just `NotFound` errors, improving visibility into configuration issues. - jira: - addresses: #9266 - type: Bug Fix - impact: High -- relnote: | - Fixed TLS certificate verification issues when connecting to CNP-I plugins - by adding the `k8s.enterprisedb.io/pluginServerName` annotation. - details: | - This allows customizing the DNS name used for certificate verification in - environments where the plugin's certificate uses a different DNS name than - the Service name. - jira: - addresses: #9222 - type: Bug Fix - impact: High -- relnote: | - Fixed an issue where the instance manager controller could fail to restart - after an error, reporting a "controller already exists" message. - details: | - The controller now uses `SkipNameValidation` for subsequent initialization - attempts. - Contributed by @mateusoliveira43. - jira: - addresses: #9123 - type: Bug Fix - impact: High -- relnote: | - Fixed incorrect WAL restore path handling in plugins when the destination - path is absolute, preventing path duplication issues. - details: | - Contributed by @Endevir. - jira: - addresses: #9093 - type: Bug Fix - impact: High -- relnote: | - Fixed the `CREATE PUBLICATION` SQL generation for multi-table publications to be backward-compatible with PostgreSQL 13+. - details: | - The previously generated syntax - was only valid for PostgreSQL 15+ and caused syntax errors on older versions. - jira: - addresses: #8888 - type: Bug Fix - impact: High -- relnote: | - Fixed backup failures in complex pod definitions by reliably selecting the `postgres` container by name instead of by index. - jira: - addresses: #8964 - type: Bug Fix - impact: High -- relnote: | - `cnp` plugin: Fixed bugs in `cnp report` log collection, especially when fetching previous logs. - details: | - The collector now correctly fetches previous and current logs in separate requests and gracefully handles missing previous logs (e.g., on containers with no restart history), ensuring current logs are always collected. - component: CNP plugin - jira: - addresses: #8992 - type: Bug Fix - impact: High -- relnote: | - Updated the default PostgreSQL version to `18.1-standard-ubi9`. - jira: - addresses: #9178 - type: Change - impact: High -- relnote: | - Updated the default PgBouncer version to **1.25.1**, which carries - a fix for **CVE-2025-12819**, for new Pooler deployments. - jira: - addresses: #9367 - type: Change - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.1_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.1_rel_notes.yml deleted file mode 100644 index 45553fdf1e9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.1_rel_notes.yml +++ /dev/null @@ -1,225 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.28.1 -date: 10 February 2026 -intro: | - This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: -components: - "Operator": 1.28.1 - "CNP plugin": 1.28.1 - upstream-merge: Upstream [1.28.1](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) -relnotes: -- relnote: | - Added support for Azure's `DefaultAzureCredential` authentication mechanism - for backup and recovery operations. - details: | - This can be enabled by setting - `azureCredentials.useDefaultAzureCredentials: true` in the backup - configuration, simplifying authentication in Azure environments without - requiring explicit storage account keys or SAS tokens. - jira: - addresses: #9468 - type: Enhancement - impact: High -- relnote: | - Fixed validation of PostgreSQL extension names containing underscores (e.g., - `pg_partman`, `pg_ivm`). - details: | - Extension names with underscores are - automatically sanitized to use hyphens for Kubernetes volume names while - preserving the original name in mount paths. Webhook validation prevents - naming conflicts after sanitization. Contributed by @shusaan. - jira: - addresses: #9386 - type: Bug Fix - impact: High - -- relnote: | - Fixed a critical issue where the `TimelineID` in the cluster status was not - reset to 1 after a major version upgrade. - details: | - Because `pg_upgrade` initializes a - new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt - to restore incompatible history files from object storage, leading to fatal - "requested timeline is not a child of this server's history" errors. - jira: - addresses: #9830 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where stale TLS status fields in the `Pooler` were not cleared - after being removed from the specification. - details: | - This was particularly critical - when upgrading to v1.28.0, where the `ServerTLS` field was repurposed, causing - PgBouncer to use incorrect certificates and resulting in "unsupported - certificate" errors that blocked all application connectivity. - The operator now explicitly clears `ServerCA`, `ClientCA`, `ClientTLS`, and - `ServerTLS` status fields when they are no longer configured. - jira: - addresses: #9397 - type: Bug Fix - impact: High - -- relnote: | - Fixed a bug where replicas could enter a crash-loop by attempting to download - timeline history files from future timelines. - details: | - This occurred when stale files - remained in the WAL archive from a previous cluster life, and replicas would - incorrectly try to fetch them during recovery. - jira: - addresses: #9650 - type: Bug Fix - impact: High -- relnote: | - Fixed a race condition in `replica_cluster` setups during designated primary - transitions, preventing transient "no primary" states in the replica cluster. - jira: - addresses: #9601 - type: Bug Fix - impact: High - -- relnote: | - The backup controller now uses the unique instance session ID to detect - instance manager restarts. - details: | - This prevents the operator from incorrectly - assuming a backup is still progressing if the underlying container has crashed - and restarted, which previously led to orphaned backup objects. - jira: - addresses: #9370 - type: Bug Fix - impact: High - -- relnote: | - Fixed a validation gap in Azure object store configurations where the - `storageAccount` was not required when using explicit credentials (such as a - storage key or SAS token). - details: | - The operator now enforces that a storage account - name is provided in these cases and that `connectionString` is mutually - exclusive with other authentication parameters. - jira: - addresses: #9604 - type: Bug Fix - impact: High - -- relnote: | - Optimized the deletion path so the operator begins cleaning up resources - immediately when a cluster is marked for deletion. - details: | - This significantly reduces the time a cluster remains in `Terminating` status - while waiting for internal reconciliation loops. - jira: - addresses: #9555 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where replication slots were not properly dropped from - replicas when the feature was disabled or the cluster was reconfigured. - details: | - This ensures that unused slots do not cause WAL build-up on the primary. - jira: - addresses: #9381 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where `imagePullSecrets` were not added to the `ServiceAccount` - created for the `Pooler`. - details: | - Previously, these secrets were applied to the - Deployment but not the SA, which caused image pull failures in restricted - environments using certain security policies. - jira: - addresses: #9427 - type: Bug Fix - impact: High - -- relnote: | - Added a check to verify ownership before the operator deletes a `PodMonitor`. - details: | - This prevents the operator from accidentally deleting manually managed - monitoring resources that happen to share a name with expected CNP - resources. Contributed by @juliamertz. - jira: - addresses: #9340 - type: Bug Fix - impact: High - -- relnote: | - Fixed a bug where `pg_stat_archiver` metrics would continue to report stale - data on standby instances after a switchover. - details: | - The exporter now skips these metrics on standbys, as PostgreSQL only provides - valid archiver stats on the primary. - jira: - addresses: #9411 - type: Bug Fix - impact: High - -- relnote: | - Clarified the interpretation of timestamp formats for recovery `targetTime`. - details: | - Timestamps provided without an explicit timezone are now consistently - interpreted as UTC. Contributed by @pchovelon. - jira: - addresses: #8937 - type: Bug Fix - impact: High - -- relnote: | - Fixed backup status updates to prevent "resource has been modified" errors - during concurrent updates. - jira: - addresses: #9551 - type: Bug Fix - impact: High - -- relnote: | - Fixed event reporting to use the correct pod name when a backup pod is not - found. - jira: - addresses: #9552 - type: Bug Fix - impact: High - -- relnote: | - Improved performance of scheduled backup operations for clusters with a very - high number of historical backups. - jira: - addresses: #9489 - type: Bug Fix - impact: High - -- relnote: | - Fixed error handling when removing finalizers on `Database` objects. - jira: - addresses: #9431 - type: Bug Fix - impact: High - -- relnote: | - Updated the `status` command to display "Disabled" when the - `skipWalArchiving` annotation is present on a cluster. - details: | - This replaces - confusing "starting up" or "unknown" states when WAL archiving is - intentionally bypassed. - jira: - addresses: #9709 - component: CNP plugin - type: Bug Fix - impact: High - -- relnote: | - Fixed the `logs --follow` command to continue polling for new pods instead - of exiting prematurely when all current log streams complete. - jira: - addresses: #9599 - component: CNP plugin - type: Bug Fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.2_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.2_rel_notes.yml deleted file mode 100644 index fa12a80f0cf..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.2_rel_notes.yml +++ /dev/null @@ -1,255 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.28.2 -date: 31 March 2026 -intro: | - This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: -components: - "Operator": 1.28.2 - "CNP plugin": 1.28.2 - upstream-merge: Upstream [1.28.2](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) -highlights: | - Updated the deprecation notice for native (in-tree) Barman Cloud support to - reflect that it will now be removed in EDB Postgres for Kubernetes 1.30.0, rather than - 1.29.0. Users are still encouraged to migrate to the Barman Cloud Plugin. - ([#10167](https://github.com/cloudnative-pg/cloudnative-pg/pull/10167)) -relnotes: - -- relnote: | - Improved the `Pooler` CRD with support for granular configuration of TLS - cipher suites and minimum/maximum TLS versions. - details: | - This enables administrators - to meet strict security compliance requirements for pooler-to-client and - pooler-to-server connections. - Contributed by @alex1989hu. - jira: - addresses: #9571 - type: Enhancement - impact: High - -- relnote: | - Improved the reliability of major upgrades by setting `BackoffLimit=0` on the - upgrade job, preventing unnecessary retries of a failed `pg_upgrade`. - details: | - The operator now automatically deletes the failed job when a user reverts the - container image, allowing the cluster to restart gracefully on the original - version. - jira: - addresses: #10104, #10298 - type: Enhancement - impact: High - -- relnote: | - Improved role management by verifying the instance is the primary before - each reconciliation cycle - details: | - ...avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas. - jira: - addresses: #9971 - type: Enhancement - impact: High - -- relnote: | - The operator now honors the `primaryUpdateMethod` when adding new PVCs to a - cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is - respected during storage expansion or additions. - jira: - addresses: #9720 - type: Enhancement - impact: High - -- relnote: | - Refined the `alpha.k8s.enterprisedb.io/unrecoverable` annotation logic to allow it to - function even on pods that have not yet reached the `Ready` state, - facilitating the recovery of stuck instances. - jira: - addresses: #9968 - type: Enhancement - impact: High - -- relnote: | - Security best practices integration**: integrated the OpenSSF baseline - scanner and added a `SECURITY-INSIGHTS.yaml` file to the repository to align - with industry-standard security reporting. - jira: - addresses: #10054, #10062 - type: Security - impact: High - -- relnote: | - SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software - Artifacts) provenance to release binaries and container images. - details: | - Additionally, - enabled Software Bill of Materials (SBOM) generation within the GoReleaser - pipeline for improved dependency transparency. - jira: - addresses: #10048, #10074 - type: Security - impact: High - -- relnote: | - Password leak prevention**: fixed a potential security risk where PostgreSQL - could leak role passwords in the logs during specific reconciliation phases. - jira: - addresses: #9950 - type: Security - impact: High - -- relnote: | - Updated the default PostgreSQL version to 18.3 (image `18.3-standard-ubi9`). - jira: - addresses: #10090 - type: Change - impact: High - - -- relnote: | - Fixed a deadlock during operator upgrades affecting clusters using synchronous replication - details: | - ...where pods running the old and new operator versions computed different PostgreSQL configuration hashes, causing the - uniformity check to block indefinitely and preventing both rolling updates and in-place upgrades from proceeding. - jira: - addresses: #10342 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where fencing annotations could not be processed when the WAL - disk was full - details: | - ...because the disk space check blocked the instance manager from - starting. The check is now performed later in the lifecycle loop, after - fencing is evaluated. - jira: - addresses: #10302 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where replicas would get stuck in a `Pending` state if the - `VolumeSnapshot` used for the initial bootstrap had been deleted. - details: | - The operator now validates snapshot existence before use; if a snapshot is missing, - it attempts to use the next available candidate or falls back to - `pg_basebackup`. - jira: - addresses: #10192 - type: Bug Fix - impact: High - -- relnote: | - Prevented the "supervised primary" rollout strategy from consuming all - available rollout slots, which previously caused delays in scheduled updates. - Contributed by @ermakov-oleg. - jira: - addresses: #9977 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where certain hot-standby parameter changes were not being - correctly applied to replica clusters. - jira: - addresses: #9952 - type: Bug Fix - impact: High - -- relnote: | - Fixed a bug in the CNPG-I reconciler hook that could lead to skipping - subsequent plugins when a "continue" result was returned. - Contributed by @sharifmshaker. - jira: - addresses: #9978 - type: Bug Fix - impact: High - -- relnote: | - Fixed a deadlock scenario that occurred when attempting to resize a - filesystem on a PVC that was not currently attached to a Pod. - Contributed by @jmealo. - jira: - addresses: #9981 - type: Bug Fix - impact: High - -- relnote: | - Fixed webhook validation of bootstrap recovery sources to accept external - clusters configured with `ConnectionParameters` (for `pg_basebackup`-based - recovery). - details: | - Previously, these were incorrectly rejected unless a Barman - object store or CNPG-i plugin was also configured. - jira: - addresses: #10268 - type: Bug Fix - impact: High - -- relnote: | - Volume names for extensions and tablespaces are now prefixed to avoid naming - collisions with standard cluster volumes. - jira: - addresses: #9973 - type: Bug Fix - impact: High - -- relnote: | - When hibernating a non-healthy cluster, the operator now reports a - `WaitingForHealthy` condition, making the deferred hibernation state visible - jira: - addresses: #10193 - type: Bug Fix - impact: High - -- relnote: | - Fixed fencing to work correctly even when the target pod does not exist. - details: | - Fencing operates on a cluster-level annotation and should not depend on pod - existence; instance name validation is now performed only in the `cnp - fencing on` command. - jira: - addresses: #10035 - type: Bug Fix - impact: High - -- relnote: | - Fixed the cluster and pooler service reconcilers to correctly handle changes - to all spec fields when using the patch update strategy. The reconciler now - uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields - (such as `loadBalancerClass`) from being inadvertently removed. - jira: - addresses: #10190, #10311 - type: Bug Fix - impact: High - -- relnote: | - Fixed a race condition in the deprecated in-tree Barman Cloud backup - implementation affecting parallel WAL restore, where prefetched files could - be read while still being downloaded, causing PostgreSQL recovery to fail - with "invalid checkpoint record" errors. - jira: - addresses: #10285 - type: Bug Fix - impact: High - -- relnote: | - Fixed the timeline history file validation to also apply to plugin-based WAL restore. - details: | - Previously, the protection introduced in - [#9650](https://github.com/cloudnative-pg/cloudnative-pg/pull/9650) only - covered in-tree restores, allowing plugins to bypass the check and download - future timeline history files, causing timeline mismatch errors on replicas. - jira: - addresses: #9849 - type: Bug Fix - impact: High - -- relnote: | - The cnp plugin now correctly propagates ImagePullSecrets to the - `pgbench` Job pod template. - jira: - component: CNP plugin - addresses: #10174 - type: Bug Fix - impact: High \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.3_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.3_rel_notes.yml deleted file mode 100644 index 3f1a98ff707..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.28.3_rel_notes.yml +++ /dev/null @@ -1,186 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.28.3 -date: 8 May 2026 -intro: | - This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: -components: - "Operator": 1.28.3 - "CNP plugin": 1.28.3 - upstream-merge: Upstream [1.28.3](https://cloudnative-pg.io/docs/1.28/release_notes/v1.28/) -highlights: | - **`CVE-2026-44477` / `GHSA-423p-g724-fr39`: metrics exporter privilege - escalation.** The metrics exporter no longer authenticates as the - `postgres` superuser. It now uses a dedicated `cnp_metrics_exporter` role - with `pg_monitor` privileges only, closing a chain that let a low-privilege - database user gain PostgreSQL superuser. - ([`GHSA-423p-g724-fr39`](https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-423p-g724-fr39)) - - Upgrade impact: custom monitoring queries that read user-owned tables, or - use `target_databases: '*'` against databases where `PUBLIC CONNECT` has - been revoked, need explicit `GRANT` statements to `cnp_metrics_exporter`. - See ["Custom query privileges and safety"](../monitoring/#custom-query-privileges-and-safety) - and ["Manually creating the metrics exporter role"](../monitoring/#manually-creating-the-metrics-exporter-role) - in the monitoring documentation. - - For replica clusters, upgrade the source primary cluster before any - replica clusters that consume from it. The `cnp_metrics_exporter` role - is created on the source primary and replicates downstream; a replica - cluster upgraded first will scrape against a missing role until the - source primary upgrades. The manual-recovery section linked above also - covers replica clusters. -relnotes: -- relnote: | - Schema-qualified catalog references in default monitoring queries - details: | - Hardened the shipped monitoring configuration and documentation samples by - qualifying every `pg_catalog` object explicitly. Unqualified references - resolve through `search_path`, which a database user can manipulate to - shadow built-in objects. - jira: - addresses: #10576 - type: Security - impact: High - -- relnote: | - Discoverable SBOM and provenance attestations - details: | - SBOM and SLSA provenance attached to operator container images now follow - the OCI 1.1 Referrers spec, so standard registry tooling and supply-chain - scanners can discover them automatically. - jira: - addresses: #10601 - type: Security - impact: High - -- relnote: | - CVE remediation in `github.com/jackc/pgx/v5` - details: | - Bumped to v5.9.2 to pick up upstream fixes for `CVE-2026-33816` - (memory-safety in `pgproto3`) and `GHSA-j88v-2chj-qfwx` (SQL injection via - simple-protocol dollar-quoted string handling). - jira: - addresses: #10436, #10498 - type: Security - impact: High - -- relnote: | - CVE remediation in the Go runtime - details: | - Built with Go 1.26.3 to pick up upstream fixes in `crypto/x509`, - `crypto/tls`, `net/http`, and `net` (CVE-2026-32280, CVE-2026-32281, - CVE-2026-33810, CVE-2026-33814, CVE-2026-33811, CVE-2026-39825). - jira: - addresses: #10462, #10647 - type: Security - impact: High - -- relnote: | - Build pipeline hardening - details: | - The Go 1.26.3 bump also addresses CVE-2026-42501 (`cmd/go` module-checksum - validation), reducing supply-chain exposure during release builds. The - affected code paths are not reachable from the running operator. - jira: - addresses: #10647 - type: Security - impact: High - -- relnote: | - Switched TLS peer verification from `VerifyPeerCertificate` to - `VerifyConnection`, which runs on every completed handshake (the former is - skipped on resumed TLS 1.3 sessions). - details: | - Session resumption is not enabled in EDB Postgres for Kubernetes today, so - this has no observable effect, but it future-proofs verification if - session caching is introduced later. - jira: - addresses: #10478 - type: Change - impact: High - -- relnote: | - Fixed a failover window where the former primary kept its primary label. - details: | - If the former primary returned during failover (for example, after a - transient network partition), the `-rw` service kept routing to it, - replicas could reconnect, and committed writes were lost to `pg_rewind`. - The old primary is now labeled `unhealthy` to isolate it from service - traffic during failover. - jira: - addresses: #10409 - type: Bug Fix - impact: High - -- relnote: | - Fixed failover not being triggered when the node hosting the primary - becomes unreachable. - details: | - The operator now reads the pod's `Ready` condition (flipped to `False` by - the node controller when the kubelet stops reporting) instead of - `ContainersReady`, which stays stale as `True` in that scenario. Combined - with the spurious-failover guard - ([#10445](https://github.com/cloudnative-pg/cloudnative-pg/pull/10445)), - failover triggers only when Kubernetes itself marks the pod not Ready. - jira: - addresses: #10448 - type: Bug Fix - impact: High - -- relnote: | - Fixed spurious failovers caused by transient failures on the primary's - HTTP status endpoint. - jira: - addresses: #10445 - type: Bug Fix - impact: High - -- relnote: | - Fixed escaping of backslashes and control characters in PostgreSQL - configuration values. - details: | - Previously, such characters in parameters like `log_line_prefix` could - corrupt the configuration file or be silently stripped at runtime. - jira: - addresses: #10515 - type: Bug Fix - impact: High - -- relnote: | - Fixed `restore_command` construction to shell-quote each argument. - details: | - Values such as a `destinationPath` containing whitespace (for example, - `s3://my bucket/wal`) were word-split by the POSIX shell and passed to the - WAL restore tool as separate arguments. - jira: - addresses: #10518 - type: Bug Fix - impact: High - -- relnote: | - Tightened `recoveryTarget` validation in the admission webhook. - details: | - `targetXID` must now be a non-negative 32-bit integer, and `targetName` - must be shorter than 64 bytes and free of ASCII control characters. - Malformed values are rejected at admission instead of failing later during - PostgreSQL recovery. - jira: - addresses: #10565 - type: Bug Fix - impact: High - -- relnote: | - Fixed snapshot restores failing when leftover `pgsql_tmp*` directories - were present in the data directory. - jira: - addresses: #10447 - type: Bug Fix - impact: High - -- relnote: | - Fixed a deadlock occurring when PVC storage size and resource requests - are changed simultaneously. - jira: - addresses: #10427 - type: Bug Fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.29.0_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.29.0_rel_notes.yml deleted file mode 100644 index 77511eceb00..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.29.0_rel_notes.yml +++ /dev/null @@ -1,379 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.29.0 -date: 31 March 2026 -intro: | - This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: -components: - "Operator": 1.29.0 - "CNP plugin": 1.29.0 - upstream-merge: Upstream [1.29.0](https://cloudnative-pg.io/releases/cloudnative-pg-1-29.0-released/) -highlights: | - Updated the deprecation notice for native (in-tree) Barman Cloud support to - reflect that it will now be removed in EDB Postgres for Kubernetes 1.30.0, rather than - 1.29.0. Users are still encouraged to migrate to the Barman Cloud Plugin. - ([#10167](https://github.com/cloudnative-pg/cloudnative-pg/pull/10167)) -relnotes: -- relnote: | - PostgreSQL extensions in image catalogs - details: | - extended the `ImageCatalog` - functionality to support PostgreSQL extensions. This allows users to define - and manage extension-specific images within a catalog, simplifying the - deployment of customized PostgreSQL builds. - jira: - addresses: #9781 - type: Feature - impact: High -- relnote: | - Dynamic network access control via pod selectors - details: | - introduced the - declarative definition of `podSelectorRefs` to manage `pg_hba.conf` rules - dynamically. By using label selectors to identify client pods, the operator - automatically resolves their ephemeral IP addresses and updates the PostgreSQL - host-based authentication rules accordingly. This ensures that only authorized - workloads in the same namespace can connect to the database, eliminating the - need for manual IP management or static CIDR ranges. - jira: - addresses: #9781 - type: Feature - impact: High - -- relnote: | - Shared `ServiceAccount` support - details: | - added an optional `serviceAccountName` - field to both `Cluster` and `Pooler` specifications. This allows multiple - resources to share a pre-existing ServiceAccount, facilitating one-time IAM - configurations (such as AWS IRSA, GCP Workload Identity, or Azure Workload - Identity) across all clusters and poolers. Contributed by @bozkayasalihx. - jira: - addresses: #9287 - type: Feature - impact: High - -- relnote: | - Improved the `Pooler` CRD with support for granular configuration of TLS - cipher suites and minimum/maximum TLS versions. - details: | - This enables administrators - to meet strict security compliance requirements for pooler-to-client and - pooler-to-server connections. - Contributed by @alex1989hu. - jira: - addresses: #9571 - type: Enhancement - impact: High - -- relnote: | - Improved the reliability of major upgrades by setting `BackoffLimit=0` on the - upgrade job, preventing unnecessary retries of a failed `pg_upgrade`. - details: | - The operator now automatically deletes the failed job when a user reverts the - container image, allowing the cluster to restart gracefully on the original - version. - jira: - addresses: #10104, #10298 - type: Enhancement - impact: High - -- relnote: | - Improved the operator's observability by emitting native Kubernetes events - during key phases of the reconciliation loop. - details: | - This provides visibility into the operator's decision-making process and - the lifecycle of managed resources directly through `kubectl get events`. - jira: - addresses: #10040 - type: Enhancement - impact: High - -- relnote: | - Extended support for the `k8s.enterprisedb.io/reconciliationDisabled` annotation on - Backup resources. - details: | - This allows administrators to temporarily freeze the - operator's reconciliation logic for specific backup objects. - Contributed by @GabriFedi97. - jira: - addresses: #10020 - type: Enhancement - impact: High - -- relnote: | - Added a `bin_path` field to the `postgresql.extensions` stanza, as well as in - `ImageCatalog` and `ClusterImageCatalog` resources. - details: | - This allows extensions to - specify directory paths for external binaries, which are automatically appended - to the `PATH` environment variable of the Postgres process. - jira: - addresses: #10250 - type: Enhancement - impact: High - -- relnote: | - Added an `env` field to the `postgresql.extensions` stanza, as well as in - `ImageCatalog` and `ClusterImageCatalog` resources. - details: | - This allows cluster administrators to define custom environment variables for the - Postgres process. This field supports the `${image_root}` placeholder to - dynamically resolve to the extension's absolute mount path. - jira: - addresses: #10375 - type: Enhancement - impact: High - -- relnote: | - Implemented a finalizer for plugins to ensure that resources managed by a - plugin are gracefully cleaned up when the corresponding service is deleted. - jira: - addresses: #9560 - type: Enhancement - impact: High - -- relnote: | - Improved role management by verifying the instance is the primary before - each reconciliation cycle - details: | - ...avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas. - jira: - addresses: #9971 - type: Enhancement - impact: High - -- relnote: | - The operator now honors the `primaryUpdateMethod` when adding new PVCs to a - cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is - respected during storage expansion or additions. - jira: - addresses: #9720 - type: Enhancement - impact: High - -- relnote: | - Refined the `alpha.k8s.enterprisedb.io/unrecoverable` annotation logic to allow it to - function even on pods that have not yet reached the `Ready` state, - facilitating the recovery of stuck instances. - jira: - addresses: #9968 - type: Enhancement - impact: High - -- relnote: | - Introduced a "Terminal Error" phase for backups that encounter unrecoverable - issues (such as invalid credentials or non-existent cloud buckets). - details: | - This ensures the operator stops retrying doomed operations, preventing - resource exhaustion and providing immediate, clear feedback in the status. - jira: - addresses: #9353 - type: Enhancement - impact: High - -- relnote: | - Improved monitoring of long-running backups by introducing - `reconciliationStartedAt` and `reconciliationTerminatedAt` fields to the - `Backup` status. - details: | - This change separates the operator's internal lifecycle from - the actual backup tool's execution timing (`startedAt`/`stoppedAt`), allowing - users to track when the operator begins processing a request. - jira: - addresses: #9351 - type: Enhancement - impact: High - -- relnote: | - Added a `Pending` phase to the `Backup` status to explicitly indicate when a - backup is queued and waiting for an available worker or instance availability. - jira: - addresses: #9364 - type: Enhancement - impact: High - -- relnote: | - Security best practices integration**: integrated the OpenSSF baseline - scanner and added a `SECURITY-INSIGHTS.yaml` file to the repository to align - with industry-standard security reporting. - jira: - addresses: #10054, #10062 - type: Security - impact: High - -- relnote: | - SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software - Artifacts) provenance to release binaries and container images. - details: | - Additionally, - enabled Software Bill of Materials (SBOM) generation within the GoReleaser - pipeline for improved dependency transparency. - jira: - addresses: #10048, #10074 - type: Security - impact: High - -- relnote: | - Password leak prevention**: fixed a potential security risk where PostgreSQL - could leak role passwords in the logs during specific reconciliation phases. - jira: - addresses: #9950 - type: Security - impact: High - -- relnote: | - Updated the default PostgreSQL version to 18.3 (image `18.3-standard-ubi9`). - jira: - addresses: #10090 - type: Change - impact: High - - -- relnote: | - Fixed a deadlock during operator upgrades affecting clusters using synchronous replication - details: | - ...where pods running the old and new operator versions computed different PostgreSQL configuration hashes, causing the - uniformity check to block indefinitely and preventing both rolling updates and in-place upgrades from proceeding. - jira: - addresses: #10342 - type: Bug Fix - impact: High -- relnote: | - Fixed an issue where fencing annotations could not be processed when the WAL - disk was full - details: | - ...because the disk space check blocked the instance manager from - starting. The check is now performed later in the lifecycle loop, after - fencing is evaluated. - jira: - addresses: #10302 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where replicas would get stuck in a `Pending` state if the - `VolumeSnapshot` used for the initial bootstrap had been deleted. - details: | - The operator now validates snapshot existence before use; if a snapshot is missing, - it attempts to use the next available candidate or falls back to - `pg_basebackup`. - jira: - addresses: #10192 - type: Bug Fix - impact: High - -- relnote: | - Prevented the "supervised primary" rollout strategy from consuming all - available rollout slots, which previously caused delays in scheduled updates. - Contributed by @ermakov-oleg. - jira: - addresses: #9977 - type: Bug Fix - impact: High - -- relnote: | - Fixed an issue where certain hot-standby parameter changes were not being - correctly applied to replica clusters. - jira: - addresses: #9952 - type: Bug Fix - impact: High - -- relnote: | - Fixed a bug in the CNPG-I reconciler hook that could lead to skipping - subsequent plugins when a "continue" result was returned. - Contributed by @sharifmshaker. - jira: - addresses: #9978 - type: Bug Fix - impact: High - -- relnote: | - Fixed a deadlock scenario that occurred when attempting to resize a - filesystem on a PVC that was not currently attached to a Pod. - Contributed by @jmealo. - jira: - addresses: #9981 - type: Bug Fix - impact: High - -- relnote: | - Fixed webhook validation of bootstrap recovery sources to accept external - clusters configured with `ConnectionParameters` (for `pg_basebackup`-based - recovery). - details: | - Previously, these were incorrectly rejected unless a Barman - object store or CNPG-i plugin was also configured. - jira: - addresses: #10268 - type: Bug Fix - impact: High - -- relnote: | - Volume names for extensions and tablespaces are now prefixed to avoid naming - collisions with standard cluster volumes. - jira: - addresses: #9973 - type: Bug Fix - impact: High - -- relnote: | - When hibernating a non-healthy cluster, the operator now reports a - `WaitingForHealthy` condition, making the deferred hibernation state visible - jira: - addresses: #10193 - type: Bug Fix - impact: High - -- relnote: | - Fixed fencing to work correctly even when the target pod does not exist. - details: | - Fencing operates on a cluster-level annotation and should not depend on pod - existence; instance name validation is now performed only in the `cnp - fencing on` command. - jira: - addresses: #10035 - type: Bug Fix - impact: High - -- relnote: | - Fixed the cluster and pooler service reconcilers to correctly handle changes - to all spec fields when using the patch update strategy. The reconciler now - uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields - (such as `loadBalancerClass`) from being inadvertently removed. - jira: - addresses: #10190, #10311 - type: Bug Fix - impact: High - -- relnote: | - Fixed a race condition in the deprecated in-tree Barman Cloud backup - implementation affecting parallel WAL restore, where prefetched files could - be read while still being downloaded, causing PostgreSQL recovery to fail - with "invalid checkpoint record" errors. - jira: - addresses: #10285 - type: Bug Fix - impact: High - -- relnote: | - Fixed the timeline history file validation to also apply to plugin-based WAL restore. - details: | - Previously, the protection introduced in - [#9650](https://github.com/cloudnative-pg/cloudnative-pg/pull/9650) only - covered in-tree restores, allowing plugins to bypass the check and download - future timeline history files, causing timeline mismatch errors on replicas. - jira: - addresses: #9849 - type: Bug Fix - impact: High - -- relnote: | - The cnp plugin now correctly propagates ImagePullSecrets to the - `pgbench` Job pod template. - jira: - component: CNP plugin - addresses: #10174 - type: Bug Fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.29.1_rel_notes.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.29.1_rel_notes.yml deleted file mode 100644 index e3e114a3843..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/1.29.1_rel_notes.yml +++ /dev/null @@ -1,186 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json -product: EDB CloudNativePG Cluster -version: 1.29.1 -date: 8 May 2026 -intro: | - This release of EDB Postgres® AI for CloudNativePG™ Cluster includes the following: -components: - "Operator": 1.29.1 - "CNP plugin": 1.29.1 - upstream-merge: Upstream [1.29.1](https://cloudnative-pg.io/docs/1.29/release_notes/v1.29/) -highlights: | - **`CVE-2026-44477` / `GHSA-423p-g724-fr39`: metrics exporter privilege - escalation.** The metrics exporter no longer authenticates as the - `postgres` superuser. It now uses a dedicated `cnp_metrics_exporter` role - with `pg_monitor` privileges only, closing a chain that let a low-privilege - database user gain PostgreSQL superuser. - ([`GHSA-423p-g724-fr39`](https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-423p-g724-fr39)) - - Upgrade impact: custom monitoring queries that read user-owned tables, or - use `target_databases: '*'` against databases where `PUBLIC CONNECT` has - been revoked, need explicit `GRANT` statements to `cnp_metrics_exporter`. - See ["Custom query privileges and safety"](../monitoring/#custom-query-privileges-and-safety) - and ["Manually creating the metrics exporter role"](../monitoring/#manually-creating-the-metrics-exporter-role) - in the monitoring documentation. - - For replica clusters, upgrade the source primary cluster before any - replica clusters that consume from it. The `cnp_metrics_exporter` role - is created on the source primary and replicates downstream; a replica - cluster upgraded first will scrape against a missing role until the - source primary upgrades. The manual-recovery section linked above also - covers replica clusters. -relnotes: -- relnote: | - Schema-qualified catalog references in default monitoring queries - details: | - Hardened the shipped monitoring configuration and documentation samples by - qualifying every `pg_catalog` object explicitly. Unqualified references - resolve through `search_path`, which a database user can manipulate to - shadow built-in objects. - jira: - addresses: #10576 - type: Security - impact: High - -- relnote: | - Discoverable SBOM and provenance attestations - details: | - SBOM and SLSA provenance attached to operator container images now follow - the OCI 1.1 Referrers spec, so standard registry tooling and supply-chain - scanners can discover them automatically. - jira: - addresses: #10601 - type: Security - impact: High - -- relnote: | - CVE remediation in `github.com/jackc/pgx/v5` - details: | - Bumped to v5.9.2 to pick up upstream fixes for `CVE-2026-33816` - (memory-safety in `pgproto3`) and `GHSA-j88v-2chj-qfwx` (SQL injection via - simple-protocol dollar-quoted string handling). - jira: - addresses: #10437, #10499 - type: Security - impact: High - -- relnote: | - CVE remediation in the Go runtime - details: | - Built with Go 1.26.3 to pick up upstream fixes in `crypto/x509`, - `crypto/tls`, `net/http`, and `net` (CVE-2026-32280, CVE-2026-32281, - CVE-2026-33810, CVE-2026-33814, CVE-2026-33811, CVE-2026-39825). - jira: - addresses: #10463, #10647 - type: Security - impact: High - -- relnote: | - Build pipeline hardening - details: | - The Go 1.26.3 bump also addresses CVE-2026-42501 (`cmd/go` module-checksum - validation), reducing supply-chain exposure during release builds. The - affected code paths are not reachable from the running operator. - jira: - addresses: #10647 - type: Security - impact: High - -- relnote: | - Switched TLS peer verification from `VerifyPeerCertificate` to - `VerifyConnection`, which runs on every completed handshake (the former is - skipped on resumed TLS 1.3 sessions). - details: | - Session resumption is not enabled in EDB Postgres for Kubernetes today, so - this has no observable effect, but it future-proofs verification if - session caching is introduced later. - jira: - addresses: #10478 - type: Change - impact: High - -- relnote: | - Fixed a failover window where the former primary kept its primary label. - details: | - If the former primary returned during failover (for example, after a - transient network partition), the `-rw` service kept routing to it, - replicas could reconnect, and committed writes were lost to `pg_rewind`. - The old primary is now labeled `unhealthy` to isolate it from service - traffic during failover. - jira: - addresses: #10409 - type: Bug Fix - impact: High - -- relnote: | - Fixed failover not being triggered when the node hosting the primary - becomes unreachable. - details: | - The operator now reads the pod's `Ready` condition (flipped to `False` by - the node controller when the kubelet stops reporting) instead of - `ContainersReady`, which stays stale as `True` in that scenario. Combined - with the spurious-failover guard - ([#10445](https://github.com/cloudnative-pg/cloudnative-pg/pull/10445)), - failover triggers only when Kubernetes itself marks the pod not Ready. - jira: - addresses: #10448 - type: Bug Fix - impact: High - -- relnote: | - Fixed spurious failovers caused by transient failures on the primary's - HTTP status endpoint. - jira: - addresses: #10445 - type: Bug Fix - impact: High - -- relnote: | - Fixed escaping of backslashes and control characters in PostgreSQL - configuration values. - details: | - Previously, such characters in parameters like `log_line_prefix` could - corrupt the configuration file or be silently stripped at runtime. - jira: - addresses: #10515 - type: Bug Fix - impact: High - -- relnote: | - Fixed `restore_command` construction to shell-quote each argument. - details: | - Values such as a `destinationPath` containing whitespace (for example, - `s3://my bucket/wal`) were word-split by the POSIX shell and passed to the - WAL restore tool as separate arguments. - jira: - addresses: #10518 - type: Bug Fix - impact: High - -- relnote: | - Tightened `recoveryTarget` validation in the admission webhook. - details: | - `targetXID` must now be a non-negative 32-bit integer, and `targetName` - must be shorter than 64 bytes and free of ASCII control characters. - Malformed values are rejected at admission instead of failing later during - PostgreSQL recovery. - jira: - addresses: #10565 - type: Bug Fix - impact: High - -- relnote: | - Fixed snapshot restores failing when leftover `pgsql_tmp*` directories - were present in the data directory. - jira: - addresses: #10447 - type: Bug Fix - impact: High - -- relnote: | - Fixed a deadlock occurring when PVC storage size and resource requests - are changed simultaneously. - jira: - addresses: #10427 - type: Bug Fix - impact: High diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/meta.yml b/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/meta.yml deleted file mode 100644 index 7ea8d477ad7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rel_notes/src/meta.yml +++ /dev/null @@ -1,340 +0,0 @@ -# yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/develop/tools/automation/generators/relgen/meta-schema.json -product: EDB CloudNativePG Cluster -shortname: "" -title: EDB CloudNativePG Cluster release notes -description: Release notes for EDB CloudNativePG Cluster -intro: | - The EDB Postgres for Kubernetes documentation describes the major version of EDB Postgres for Kubernetes, including minor releases and patches. The release notes provide information on what is new in each release. For new functionality introduced in a minor or patch release, the content also indicates the release that introduced the feature. -outro: | - !!! Info Versions prior to 1.0.0 - EDB Postgres for Kubernetes was made generally available on February 4, 2021. - Earlier versions were made available to selected customers prior to the GA release. -frontmatter: - redirects: - - ../release_notes -columns: -- 0: - label: "Version" - key: version-link -- 1: - label: Release date - key: shortdate -- 2: - label: Upstream merges - key: $upstream-merge -precursor: -- date: 04 Mar 2025 - version: 1.25.1 - upstream-merge: Upstream [1.25.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) -- date: 23 Dec 2024 - version: 1.25.0 - upstream-merge: Upstream [1.25.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.25/) -- date: 04 Mar 2025 - version: 1.24.3 - upstream-merge: Upstream [1.24.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) -- date: 23 Dec 2024 - version: 1.24.2 - upstream-merge: Upstream [1.24.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) -- date: 18 Oct 2024 - version: 1.24.1 - upstream-merge: Upstream [1.24.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) -- date: 26 Aug 2024 - version: 1.24.0 - upstream-merge: Upstream [1.24.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.24/) -- date: 23 Dec 2024 - version: 1.23.6 - upstream-merge: Upstream [1.23.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) -- date: 18 Oct 2024 - version: 1.23.5 - upstream-merge: Upstream [1.23.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) -- date: 26 Aug 2024 - version: 1.23.4 - upstream-merge: Upstream [1.23.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) -- date: 01 Aug 2024 - version: 1.23.3 - upstream-merge: Upstream [1.23.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) -- date: 13 Jun 2024 - version: 1.23.2 - upstream-merge: Upstream [1.23.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) -- date: 29 Apr 2024 - version: 1.23.1 - upstream-merge: Upstream [1.23.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) -- date: 24 Apr 2024 - version: 1.23.0 - upstream-merge: Upstream [1.23.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.23/) -- date: 04 Mar 2025 - version: 1.22.9 - upstream-merge: None -- date: 23 Dec 2024 - version: 1.22.8 - upstream-merge: None -- date: 18 Oct 2024 - version: 1.22.7 - upstream-merge: None -- date: 26 Aug 2024 - version: 1.22.6 - upstream-merge: Upstream [1.22.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) -- date: 01 Aug 2024 - version: 1.22.5 - upstream-merge: Upstream [1.22.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) -- date: 13 Jun 2024 - version: 1.22.4 - upstream-merge: Upstream [1.22.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) -- date: 24 Apr 2024 - version: 1.22.3 - upstream-merge: Upstream [1.22.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) -- date: 22 Mar 2024 - version: 1.22.2 - upstream-merge: Upstream [1.22.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) -- date: 02 Feb 2024 - version: 1.22.1 - upstream-merge: Upstream [1.22.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) -- date: 22 Dec 2023 - version: 1.22.0 - upstream-merge: Upstream [1.22.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.22/) -- date: 13 Jun 2024 - version: 1.21.6 - upstream-merge: Upstream [1.21.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) -- date: 24 Apr 2024 - version: 1.21.5 - upstream-merge: Upstream [1.21.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) -- date: 22 Mar 2024 - version: 1.21.4 - upstream-merge: Upstream [1.21.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) -- date: 02 Feb 2024 - version: 1.21.3 - upstream-merge: Upstream [1.21.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) -- date: 22 Dec 2023 - version: 1.21.2 - upstream-merge: Upstream [1.21.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) -- date: 08 Nov 2023 - version: 1.21.1 - upstream-merge: Upstream [1.21.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) -- date: 18 Oct 2023 - version: 1.21.0 - upstream-merge: Upstream [1.21.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.21/) -- date: 02 Feb 2024 - version: 1.20.6 - upstream-merge: Upstream [1.20.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) -- date: 22 Dec 2023 - version: 1.20.5 - upstream-merge: Upstream [1.20.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) -- date: 08 Nov 2023 - version: 1.20.4 - upstream-merge: Upstream [1.20.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) -- date: 18 Oct 2023 - version: 1.20.3 - upstream-merge: Upstream [1.20.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) -- date: 27 Jul 2023 - version: 1.20.2 - upstream-merge: Upstream [1.20.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) -- date: 13 Jun 2023 - version: 1.20.1 - upstream-merge: Upstream [1.20.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) -- date: 27 Apr 2023 - version: 1.20.0 - upstream-merge: Upstream [1.20.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.20/) -- date: 08 Nov 2023 - version: 1.19.6 - upstream-merge: Upstream [1.19.6](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) -- date: 18 Oct 2023 - version: 1.19.5 - upstream-merge: Upstream [1.19.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) -- date: 27 Jul 2023 - version: 1.19.4 - upstream-merge: Upstream [1.19.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) -- date: 13 Jun 2023 - version: 1.19.3 - upstream-merge: Upstream [1.19.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) -- date: 27 Apr 2023 - version: 1.19.2 - upstream-merge: Upstream [1.19.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) -- date: 20 Mar 2023 - version: 1.19.1 - upstream-merge: Upstream [1.19.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) -- date: 14 Feb 2023 - version: 1.19.0 - upstream-merge: Upstream [1.19.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.19/) -- date: 13 Jun 2024 - version: 1.18.13 - upstream-merge: None -- date: 24 Apr 2024 - version: 1.18.12 - upstream-merge: None -- date: 22 Mar 2024 - version: 1.18.11 - upstream-merge: None -- date: 02 Feb 2024 - version: 1.18.10 - upstream-merge: None -- date: 22 Dec 2023 - version: 1.18.9 - upstream-merge: None -- date: 08 Nov 2023 - version: 1.18.8 - upstream-merge: None -- date: 18 Oct 2023 - version: 1.18.7 - upstream-merge: None -- date: 27 Jul 2023 - version: 1.18.6 - upstream-merge: None -- date: 13 Jun 2023 - version: 1.18.5 - upstream-merge: Upstream [1.18.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) -- date: 27 Apr 2023 - version: 1.18.4 - upstream-merge: Upstream [1.18.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) -- date: 20 Mar 2023 - version: 1.18.3 - upstream-merge: Upstream [1.18.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) -- date: 14 Feb 2023 - version: 1.18.2 - upstream-merge: Upstream [1.18.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) -- date: 21 Dec 2022 - version: 1.18.1 - upstream-merge: Upstream [1.18.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) -- date: 14 Nov 2022 - version: 1.18.0 - upstream-merge: Upstream [1.18.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.18/) -- date: 20 Mar 2023 - version: 1.17.5 - upstream-merge: Upstream [1.17.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) -- date: 14 Feb 2023 - version: 1.17.4 - upstream-merge: Upstream [1.17.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) -- date: 21 Dec 2022 - version: 1.17.3 - upstream-merge: Upstream [1.17.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) -- date: 14 Nov 2022 - version: 1.17.2 - upstream-merge: Upstream [1.17.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) -- date: 07 Oct 2022 - version: 1.17.1 - upstream-merge: Upstream [1.17.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) -- date: 06 Sep 2022 - version: 1.17.0 - upstream-merge: Upstream [1.17.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.17/) -- date: 21 Dec 2022 - version: 1.16.5 - upstream-merge: Upstream [1.16.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) -- date: 14 Nov 2022 - version: 1.16.4 - upstream-merge: Upstream [1.16.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) -- date: 07 Oct 2022 - version: 1.16.3 - upstream-merge: Upstream [1.16.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) -- date: 06 Sep 2022 - version: 1.16.2 - upstream-merge: Upstream [1.16.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) -- date: 12 Aug 2022 - version: 1.16.1 - upstream-merge: Upstream [1.16.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16/) -- date: 07 Jul 2022 - version: 1.16.0 - upstream-merge: Upstream [1.16.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.16) -- date: 07 Oct 2022 - version: 1.15.5 - upstream-merge: Upstream [1.15.5](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) -- date: 06 Sep 2022 - version: 1.15.4 - upstream-merge: Upstream [1.15.4](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) -- date: 12 Aug 2022 - version: 1.15.3 - upstream-merge: Upstream [1.15.3](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) -- date: 07 Jul 2022 - version: 1.15.2 - upstream-merge: Upstream [1.15.2](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) -- date: 27 May 2022 - version: 1.15.1 - upstream-merge: Upstream [1.15.1](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) -- date: 21 Apr 2022 - version: 1.15.0 - upstream-merge: Upstream [1.15.0](https://cloudnative-pg.io/docs/devel/release_notes/old/v1.15) -- date: 25 Mar 2022 - version: 1.14.0 - upstream-merge: NA -- date: 17 Feb 2022 - version: 1.13.0 - upstream-merge: NA -- date: 11 Jan 2022 - version: 1.12.0 - upstream-merge: NA -- date: 15 Dec 2021 - version: 1.11.0 - upstream-merge: NA -- date: 11 Nov 2021 - version: 1.10.0 - upstream-merge: NA -- date: 15 Oct 2021 - version: 1.9.2 - upstream-merge: NA -- date: 30 Sep 2021 - version: 1.9.1 - upstream-merge: NA -- date: 28 Sep 2021 - version: 1.9.0 - upstream-merge: NA -- date: 13 Sep 2021 - version: 1.8.0 - upstream-merge: NA -- date: 11 Aug 2021 - version: 1.7.1 - upstream-merge: NA -- date: 28 Jul 2021 - version: 1.7.0 - upstream-merge: NA -- date: 12 Jul 2021 - version: 1.6.0 - upstream-merge: NA -- date: 11 Jun 2021 - version: 1.5.1 - upstream-merge: NA -- date: 17 Jun 2021 - version: 1.5.0 - upstream-merge: NA -- date: 18 May 2021 - version: 1.4.0 - upstream-merge: NA -- date: 23 Apr 2021 - version: 1.3.0 - upstream-merge: NA -- date: 06 Apr 2021 - version: 1.2.1 - upstream-merge: NA -- date: 31 Mar 2021 - version: 1.2.0 - upstream-merge: NA -- date: 03 Mar 2021 - version: 1.1.0 - upstream-merge: NA -- date: 04 Feb 2021 - version: "1.0.0" - upstream-merge: NA -- date: 29 Jan 2021 - version: "0.8.0" - upstream-merge: NA -- date: 31 Dec 2020 - version: "0.7.0" - upstream-merge: NA -- date: 04 Dec 2020 - version: "0.6.0" - upstream-merge: NA -- date: 20 Nov 2020 - version: "0.5.0" - upstream-merge: NA -- date: 05 Nov 2020 - version: "0.4.0" - upstream-merge: NA -- date: 25 Sep 2020 - version: "0.3.0" - upstream-merge: NA -- date: 11 Aug 2020 - version: "0.2.0" - upstream-merge: NA -- date: 03 Apr 2020 - version: "0.1.0" - upstream-merge: NA -- date: 05 Mar 2020 - version: "0.0.1" - upstream-merge: NA diff --git a/product_docs/docs/postgres_for_kubernetes/preview/replica_cluster.mdx b/product_docs/docs/postgres_for_kubernetes/preview/replica_cluster.mdx deleted file mode 100644 index a3120c143af..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/replica_cluster.mdx +++ /dev/null @@ -1,639 +0,0 @@ ---- -title: 'Replica clusters' -originalFilePath: 'src/replica_cluster.md' ---- - - - -A replica cluster is a {{name.ln}} `Cluster` resource designed to -replicate data from another PostgreSQL instance, ideally also managed by -{{name.ln}}. - -Typically, a replica cluster is deployed in a different Kubernetes cluster in -another region. These clusters can be configured to perform cascading -replication and can rely on object stores for data replication from the source, -as detailed further down. - -There are primarily two use cases for replica clusters: - -1. **Disaster Recovery and High Availability**: Enhance disaster recovery and, - to some extent, high availability of a {{name.ln}} cluster across different - Kubernetes clusters, typically located in different regions. In {{name.ln}} - terms, this is known as a ["Distributed Topology"](replica_cluster.md#distributed-topology). - -2. **Read-Only Workloads**: Create standalone replicas of a PostgreSQL cluster - for purposes such as reporting or Online Analytical Processing (OLAP). These - replicas are primarily for read-only workloads. In {{name.ln}} terms, this - is referred to as a ["Standalone Replica Cluster"](replica_cluster.md#standalone-replica-clusters). - -For example, the diagram below — taken from the ["Architecture" section](architecture.md#deployments-across-kubernetes-clusters) -— illustrates a distributed PostgreSQL topology spanning two Kubernetes -clusters, with a symmetric replica cluster primarily serving disaster recovery -purposes. - -![An example of multi-cluster deployment with a primary and a replica cluster](./images/multi-cluster.png) - -## Basic Concepts - -{{name.ln}} builds on the PostgreSQL replication framework, allowing you to -create and synchronize a PostgreSQL cluster from an existing source cluster -using the replica cluster feature — described in this section. The source can -be a primary cluster or another replica cluster (cascading replication). - -### About PostgreSQL Roles - -A replica cluster operates in continuous recovery mode, meaning no changes to -the database, including the catalog and global objects like roles or databases, -are permitted. These changes are deferred until the `Cluster` transitions to -primary. During this phase, global objects such as roles remain as defined in -the source cluster. {{name.ln}} applies any local redefinitions once the -cluster is promoted. - -If you are not planning to promote the cluster (e.g., for read-only workloads) -or if you intend to detach completely from the source cluster -once the replica cluster is promoted, you don't need to take any action. -This is normally the case of the ["Standalone Replica Cluster"](replica_cluster.md#standalone-replica-clusters). - -If you are planning to promote the cluster at some point, {{name.ln}} will -manage the following roles and passwords when transitioning from replica -cluster to primary: - -- the application user -- the superuser (if you are using it) -- any role defined using the [declarative interface](declarative_role_management.md) - -If your intention is to seamlessly ensure that the above roles and passwords -don't change, you need to define the necessary secrets for the above in each -`Cluster`. -This is normally the case of the ["Distributed Topology"](replica_cluster.md#distributed-topology). - -### Bootstrapping a Replica Cluster - -The first step is to bootstrap the replica cluster using one of the following -methods: - -- **Streaming replication** via `pg_basebackup` -- **Recovery from a volume snapshot** -- **Recovery from a Barman Cloud backup** in an object store - -For detailed instructions on cloning a PostgreSQL server using `pg_basebackup` -(streaming) or recovery (volume snapshot or object store), refer to the -["Bootstrap" section](bootstrap.md#bootstrap-from-another-cluster). - -### Configuring Replication - -Once the base backup for the replica cluster is available, you need to define -how changes will be replicated from the origin using PostgreSQL continuous -recovery. There are three main options: - -1. **Streaming Replication**: Set up streaming replication between the replica - cluster and the source. This method requires configuring network connections - and implementing appropriate administrative and security measures to ensure - seamless data transfer. -2. **WAL Archive**: Use the WAL (Write-Ahead Logging) archive stored in an - object store. WAL files are regularly transferred from the source cluster to - the object store, from where a CNPG-I plugin like [Barman Cloud](https://cloudnative-pg.io/plugin-barman-cloud/) - retrieves them for the replica cluster via the `restore_command`. -3. **Hybrid Approach**: Combine both streaming replication and WAL archive - methods. PostgreSQL can manage and switch between these two approaches as - needed to ensure data consistency and availability. - -### Defining an External Cluster - -When configuring the external cluster, you have the following options: - -- **`plugin` section**: - - Enables bootstrapping the replica cluster using a [CNPG-I](https://github.com/cloudnative-pg/cnpg-i) - plugin that support the - [`restore_job`](https://github.com/cloudnative-pg/cnpg-i/blob/main/docs/protocol.md#restore_job-proto) - and the [`wal`](https://github.com/cloudnative-pg/cnpg-i/blob/main/docs/protocol.md#wal-proto) protocols. - - {{name.ln}} supports the [Barman Cloud Plugin](https://cloudnative-pg.io/plugin-barman-cloud/docs/usage/#restoring-a-cluster) - to allow bootstrapping the replica cluster from an object store. - -- **`connectionParameters` section**: - - Enables bootstrapping the replica cluster via streaming replication using - the `pg_basebackup` section. - - {{name.ln}} automatically sets the `primary_conninfo` option in the - designated primary instance, initiating a WAL receiver process to connect - to the source cluster and receive data. - -You still have access to the **`barmanObjectStore` section**, although deprecated: - -- Enables use of the WAL archive, with {{name.ln}} automatically setting - the `restore_command` in the designated primary instance. -- Allows bootstrapping the replica cluster from an object store using the - `recovery` section if volume snapshots are not feasible. - -### Backup and Symmetric Architectures - -The replica cluster can perform backups to a reserved object store from the -designated primary, supporting symmetric architectures in a distributed -environment. This architectural choice is crucial as it ensures the cluster is -prepared for promotion during a controlled data center switchover or a failover -following an unexpected event. - -### Distributed Architecture Flexibility - -You have the flexibility to design your preferred distributed architecture for -a PostgreSQL database, choosing from: - -- **Private Cloud**: Spanning multiple Kubernetes clusters in different data - centers. -- **Public Cloud**: Spanning multiple Kubernetes clusters in different regions. -- **Hybrid Cloud**: Combining private and public clouds. -- **Multi-Cloud**: Spanning multiple Kubernetes clusters across different - regions and Cloud Service Providers. - -## Setting Up a Replica Cluster - -To set up a replica cluster from a source cluster, follow these steps to create -a cluster YAML file and configure it accordingly: - -1. **Define External Clusters**: - - In the `externalClusters` section, specify the replica cluster. - - For a distributed PostgreSQL topology aimed at disaster recovery (DR) and - high availability (HA), this section should be defined for every - PostgreSQL cluster in the distributed database. - -2. **Bootstrap the Replica Cluster**: - - **Streaming Bootstrap**: Use the `pg_basebackup` section for bootstrapping - via streaming replication. - - **Snapshot/Object Store Bootstrap**: Use the `recovery` section to - bootstrap from a volume snapshot or an object store. - -3. **Continuous Recovery Strategy**: Define this in the `.spec.replica` stanza: - - **Distributed Topology**: Configure using the `primary`, `source`, and - `self` fields along with the distributed topology defined in - `externalClusters`. This allows {{name.ln}} to declaratively control the - demotion of a primary cluster and the subsequent promotion of a replica cluster - using a promotion token. - - **Standalone Replica Cluster**: Enable continuous recovery using the - `enabled` option and set the `source` field to point to an - `externalClusters` name. This configuration is suitable for creating replicas - primarily intended for read-only workloads. - -Both the Distributed Topology and the Standalone Replica Cluster strategies for -continuous recovery are thoroughly explained below. - -## Distributed Topology - -### Planning for a Distributed PostgreSQL Database - -As Dwight Eisenhower famously said, "Planning is everything", and this holds -true for designing PostgreSQL architectures in Kubernetes. - -First, conceptualize your distributed topology on paper, and then translate it -into a {{name.ln}} API configuration. This configuration primarily involves: - -- The `externalClusters` section, which must be included in every `Cluster` - definition within your distributed PostgreSQL setup. -- The `.spec.replica` stanza, specifically the `primary`, `source`, and - (optionally) `self` fields. - -For example, suppose you want to deploy a PostgreSQL cluster distributed across -two Kubernetes clusters located in Southern Europe and Central Europe. - -In this scenario, assume you have {{name.ln}} installed in the Southern -Europe Kubernetes cluster, with a PostgreSQL `Cluster` named `cluster-eu-south` -acting as the primary. This cluster has continuous backup configured with a -local object store. This object store is also accessible by the PostgreSQL -`Cluster` named `cluster-eu-central`, installed in the Central European -Kubernetes cluster. Initially, `cluster-eu-central` functions as a replica -cluster. Following a symmetric approach, it also has a local object store for -continuous backup, which needs to be read by `cluster-eu-south`. - -In this example, recovery is performed solely through WAL shipping, without any -streaming replication between the two clusters. However, you can configure the -setup to use streaming replication alone or adopt a hybrid approach—streaming -replication with WAL shipping as a fallback—as described in the -[“Configuring replication”](replica_cluster.md#defining-an-external-cluster) -section. - -Here’s how you would configure the `externalClusters` section for both -`Cluster` resources, relying on Barman Cloud Plugin for the object store: - -```yaml -# Distributed topology configuration -externalClusters: - - name: cluster-eu-south - plugin: - name: barman-cloud.cloudnative-pg.io - parameters: - barmanObjectName: cluster-eu-south - serverName: cluster-eu-south - - name: cluster-eu-central - plugin: - name: barman-cloud.cloudnative-pg.io - parameters: - barmanObjectName: cluster-eu-central - serverName: cluster-eu-central -``` - -The `.spec.replica` stanza for the `cluster-eu-south` PostgreSQL primary -`Cluster` should be configured as follows: - -```yaml -replica: - primary: cluster-eu-south - source: cluster-eu-central -``` - -Meanwhile, the `.spec.replica` stanza for the `cluster-eu-central` PostgreSQL -replica `Cluster` should be configured as: - -```yaml -replica: - primary: cluster-eu-south - source: cluster-eu-south -``` - -In this configuration, when the `primary` field matches the name of the -`Cluster` resource (or `.spec.replica.self` if a different one is used), the -current cluster is considered the primary in the distributed topology. -Otherwise, it is set as a replica from the `source` (in this case, using the -Barman object store). - -This setup allows you to efficiently manage a distributed PostgreSQL -architecture across multiple Kubernetes clusters, ensuring both high -availability and disaster recovery through controlled switchover of a primary -PostgreSQL cluster using declarative configuration. - -Controlled switchover in a distributed topology is a two-step process -involving: - -- Demotion of a primary cluster to a replica cluster -- Promotion of a replica cluster to a primary cluster - -These processes are described in the next sections. - -!!!info Important -Before you proceed, ensure you review the ["About PostgreSQL Roles" section](#about-postgresql-roles) -above and use identical role definitions, including secrets, in all -`Cluster` objects participating in the distributed topology. -!!! - -### Demoting a Primary to a Replica Cluster - -{{name.ln}} provides the functionality to demote a primary cluster to a -replica cluster. This action is typically planned when transitioning the -primary role from one data center to another. The process involves demoting the -current primary cluster (e.g., `cluster-eu-south`) to a replica cluster and -subsequently promoting the designated replica cluster (e.g., -`cluster-eu-central`) to primary when fully synchronized. - -Provided you have defined an external cluster in the current primary `Cluster` -resource that points to the replica cluster that's been selected to become the -new primary, all you need to do is change the `primary` field as follows: - -```yaml -replica: - primary: cluster-eu-central - source: cluster-eu-central -``` - -When the primary PostgreSQL cluster is demoted, write operations are no -longer possible. {{name.ln}} then: - -1. Archives the WAL file containing the shutdown checkpoint as a `.partial` - file in the WAL archive. - -2. Generates a `demotionToken` in the status, a base64-encoded JSON structure - containing relevant information from `pg_controldata` such as the system - identifier, the timestamp, timeline ID, REDO location, and REDO WAL file of the - latest checkpoint. - -The first step is necessary to demote/promote using solely the WAL archive to -feed the continuous recovery process (without streaming replication). - -The second step, generation of the `.status.demotionToken`, will ensure a -smooth demotion/promotion process, without any data loss and without rebuilding -the former primary. - -At this stage, the former primary has transitioned to a replica cluster, -awaiting WAL data from the new global primary: `cluster-eu-central`. - -To proceed with promoting the other cluster, you need to retrieve the -`demotionToken` from `cluster-eu-south` using the following command: - -```sh -kubectl get cluster cluster-eu-south \ - -o jsonpath='{.status.demotionToken}' -``` - -You can obtain the `demotionToken` using the `cnp` plugin by checking the -cluster's status. The token is listed under the `Demotion token` section. - -!!!note -The `demotionToken` obtained from `cluster-eu-south` will serve as the -`promotionToken` for `cluster-eu-central`. -!!! - -You can verify the role change using the `cnp` plugin, checking the status of -the cluster: - -```shell -kubectl cnp status cluster-eu-south -``` - -### Promoting a Replica to a Primary Cluster - -To promote a PostgreSQL replica cluster (e.g., `cluster-eu-central`) to a -primary cluster and make the designated primary an actual primary instance, -you need to perform the following steps simultaneously: - -1. Set the `.spec.replica.primary` to the name of the current replica cluster - to be promoted (e.g., `cluster-eu-central`). -2. Set the `.spec.replica.promotionToken` with the value obtained from the - former primary cluster (refer to ["Demoting a Primary to a Replica Cluster"](replica_cluster.md#demoting-a-primary-to-a-replica-cluster)). - -The updated `replica` section in `cluster-eu-central`'s spec should look like -this: - -```yaml -replica: - primary: cluster-eu-central - promotionToken: - source: cluster-eu-south -``` - -!!!warning -It is crucial to apply the changes to the `primary` and `promotionToken` -fields simultaneously. If the promotion token is omitted, a failover will be -triggered, necessitating a rebuild of the former primary. -!!! - -After making these adjustments, {{name.ln}} will initiate the promotion of -the replica cluster to a primary cluster. Initially, {{name.ln}} will wait -for the designated primary cluster to replicate all Write-Ahead Logging (WAL) -information up to the specified Log Sequence Number (LSN) contained in the -token. Once this target is achieved, the promotion process will commence. The -new primary cluster will switch timelines, archive the history file and new -WAL, thereby unblocking the replication process in the `cluster-eu-south` -cluster, which will then operate as a replica. - -To verify the role change, use the `cnp` plugin to check the status of the -cluster: - -```shell -kubectl cnp status cluster-eu-central -``` - -This command will provide you with the current status of `cluster-eu-central`, -confirming its promotion to primary. - -By following these steps, you ensure a smooth and controlled promotion process, -minimizing disruption and maintaining data integrity across your PostgreSQL -clusters. - -## Standalone Replica Clusters - -!!!info Important -Standalone Replica Clusters were previously known as Replica Clusters -before the introduction of the Distributed Topology strategy in {{name.ln}} -1.24. -!!! - -In {{name.ln}}, a Standalone Replica Cluster is a PostgreSQL cluster in -continuous recovery with the following configurations: - -- `.spec.replica.enabled` set to `true` -- A physical replication source defined via the `.spec.replica.source` field, - pointing to an `externalClusters` name - -When `.spec.replica.enabled` is set to `false`, the replica cluster exits -continuous recovery mode and becomes a primary cluster, completely detached -from the original source. - -!!!warning -Disabling replication is an **irreversible** operation. Once replication is -disabled and the designated primary is promoted to primary, the replica cluster -and the source cluster become two independent clusters definitively. -!!! - -!!!info Important -Standalone replica clusters are suitable for several use cases, primarily -involving read-only workloads. If you are planning to setup a disaster -recovery solution, look into "Distributed Topology" above. -!!! - -### Main Differences with Distributed Topology - -Although Standalone Replica Clusters can be used for disaster recovery -purposes, they differ from the "Distributed Topology" strategy in several key -ways: - -- **Lack of Distributed Database Concept**: Standalone Replica Clusters do not - support the concept of a distributed database, whether in simple forms (two - clusters) or more complex configurations (e.g., three clusters in a circular - topology). -- **No Global Primary Cluster**: There is no notion of a global primary cluster - in Standalone Replica Clusters. -- **No Controlled Switchover**: A Standalone Replica Cluster can only be - promoted to primary. The former primary cluster must be re-cloned, as - controlled switchover is not possible. - -Failover is identical in both strategies, requiring the former primary to be -re-cloned if it ever comes back up. - -### Example of Standalone Replica Cluster using `pg_basebackup` - -This **first example** defines a standalone replica cluster using streaming -replication in both bootstrap and continuous recovery. The replica cluster -connects to the source cluster using TLS authentication. - -You can check the [sample YAML](../samples/cluster-example-replica-streaming.yaml) -in the `samples/` subdirectory. - -Note the `bootstrap` and `replica` sections pointing to the source cluster. - -```yaml - bootstrap: - pg_basebackup: - source: cluster-example - - replica: - enabled: true - source: cluster-example -``` - -The previous configuration assumes that the application database and its owning -user are set to the default, `app`. If the PostgreSQL cluster being restored -uses different names, you must specify them as documented in [Configure the application database](bootstrap.md#configure-the-application-database). -You should also consider copying over the application user secret from -the original cluster and keep it synchronized with the source. -See ["About PostgreSQL Roles"](#about-postgresql-roles) for more details. - -In the `externalClusters` section, remember to use the right namespace for the -host in the `connectionParameters` sub-section. -The `-replication` and `-ca` secrets should have been copied over if necessary, -in case the replica cluster is in a separate namespace. - -```yaml - externalClusters: - - name: - connectionParameters: - host: -rw..svc - user: streaming_replica - sslmode: verify-full - dbname: postgres - sslKey: - name: -replication - key: tls.key - sslCert: - name: -replication - key: tls.crt - sslRootCert: - name: -ca - key: ca.crt -``` - -### Example of Standalone Replica Cluster from an object store - -The **second example** defines a replica cluster that bootstraps from an object -store using the `recovery` section and continuous recovery using both streaming -replication and the given object store. For streaming replication, the replica -cluster connects to the source cluster using basic authentication. - -You can check the [sample YAML](../samples/cluster-example-replica-from-backup-simple.yaml) -for it in the `samples/` subdirectory. - -Note the `bootstrap` and `replica` sections pointing to the source cluster. - -```yaml - bootstrap: - recovery: - source: cluster-example - - replica: - enabled: true - source: cluster-example -``` - -The previous configuration assumes that the application database and its owning -user are set to the default, `app`. If the PostgreSQL cluster being restored -uses different names, you must specify them as documented in [Configure the application database](recovery.md#configure-the-application-database). -You should also consider copying over the application user secret from -the original cluster and keep it synchronized with the source. -See ["About PostgreSQL Roles"](#about-postgresql-roles) for more details. - -In the `externalClusters` section, take care to use the right namespace in the -`endpointURL` and the `connectionParameters.host`. -And do ensure that the necessary secrets have been copied if necessary, and that -a backup of the source cluster has been created already. - -```yaml - externalClusters: - - name: - # Example with Barman Cloud Plugin - plugin: - name: barman-cloud.cloudnative-pg.io - parameters: - barmanObjectName: - serverName: - … - connectionParameters: - host: -rw.default.svc - user: postgres - dbname: postgres - password: - name: -superuser - key: password -``` - -!!!note -To use streaming replication between the source cluster and the replica -cluster, we need to make sure there is network connectivity between the two -clusters, and that all the necessary secrets which hold passwords or -certificates are properly created in advance. -!!! - -### Example using a Volume Snapshot - -If you use volume snapshots and your storage class provides -snapshots cross-cluster availability, you can leverage that to -bootstrap a replica cluster through a volume snapshot of the -source cluster. - -The **third example** defines a replica cluster that bootstraps -from a volume snapshot using the `recovery` section. It uses -streaming replication (via basic authentication) and the object -store to fetch the WAL files. - -You can check the [sample YAML](../samples/cluster-example-replica-from-volume-snapshot.yaml) -for it in the `samples/` subdirectory. - -The example assumes that the application database and its owning -user are set to the default, `app`. If the PostgreSQL cluster being restored -uses different names, you must specify them as documented in [Configure the -application database](recovery.md#configure-the-application-database). -You should also consider copying over the application user secret from -the original cluster and keep it synchronized with the source. -See ["About PostgreSQL Roles"](#about-postgresql-roles) for more details. - -## Delayed replicas - -{{name.ln}} supports the creation of **delayed replicas** through the -[`.spec.replica.minApplyDelay` option](pg4k.v1.md#replicaclusterconfiguration), -leveraging PostgreSQL's -[`recovery_min_apply_delay`](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-RECOVERY-MIN-APPLY-DELAY). - -Delayed replicas are designed to intentionally lag behind the primary database -by a specified amount of time. This delay is configurable using the -`.spec.replica.minApplyDelay` option, which maps to the underlying -`recovery_min_apply_delay` parameter in PostgreSQL. - -The primary objective of delayed replicas is to mitigate the impact of -unintended SQL statement executions on the primary database. This is especially -useful in scenarios where operations such as `UPDATE` or `DELETE` are performed -without a proper `WHERE` clause. - -To configure a delay in a replica cluster, adjust the -`.spec.replica.minApplyDelay` option. This parameter determines how much time -the replicas will lag behind the primary. For example: - -```yaml - # ... - replica: - enabled: true - source: cluster-example - # Enforce a delay of 8 hours - minApplyDelay: '8h' - # ... -``` - -The above example helps safeguard against accidental data modifications by -providing a buffer period of 8 hours to detect and correct issues before they -propagate to the replicas. - -Monitor and adjust the delay as needed based on your recovery time objectives -and the potential impact of unintended primary database operations. - -The main use cases of delayed replicas can be summarized into: - -1. mitigating human errors: reduce the risk of data corruption or loss - resulting from unintentional SQL operations on the primary database - -2. recovery time optimization: facilitate quicker recovery from unintended - changes by having a delayed replica that allows you to identify and rectify - issues before changes are applied to other replicas. - -3. enhanced data protection: safeguard critical data by introducing a time - buffer that provides an opportunity to intervene and prevent the propagation of - undesirable changes. - -!!!warning -The `minApplyDelay` option of delayed replicas cannot be used in -conjunction with `promotionToken`. -!!! - -By integrating delayed replicas into your replication strategy, you can enhance -the resilience and data protection capabilities of your PostgreSQL environment. -Adjust the delay duration based on your specific needs and the criticality of -your data. - -!!!info Important -Always measure your goals. Depending on your environment, it might be more -efficient to rely on volume snapshot-based recovery for faster outcomes. -Evaluate and choose the approach that best aligns with your unique requirements -and infrastructure. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/replication.mdx b/product_docs/docs/postgres_for_kubernetes/preview/replication.mdx deleted file mode 100644 index 9a6acc772e3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/replication.mdx +++ /dev/null @@ -1,872 +0,0 @@ ---- -title: 'Replication' -originalFilePath: 'src/replication.md' ---- - - - -Physical replication is one of the strengths of PostgreSQL and one of the -reasons why some of the largest organizations in the world have chosen it for -the management of their data in business continuity contexts. Primarily used to -achieve high availability, physical replication also allows scale-out of -read-only workloads and offloading of some work from the primary. - -!!!info Important -This section is about replication within the same `Cluster` resource -managed in the same Kubernetes cluster. For information about how to -replicate with another Postgres `Cluster` resource, even across different -Kubernetes clusters, please refer to the -["Replica clusters"](replica_cluster.md) section. -!!! - -## Application-level replication - -Having contributed throughout the years to the replication feature in -PostgreSQL, we have decided to build high availability in {{name.ln}} on top -of the native physical replication technology, and integrate it directly in the -Kubernetes API. - -In Kubernetes terms, this is referred to as **application-level replication**, -in contrast with *storage-level replication*. - -## A very mature technology - -PostgreSQL has a very robust and mature native framework for replicating data -from the primary instance to one or more replicas, built around the concept of -transactional changes continuously stored in the WAL (Write Ahead Log). - -Started as the evolution of crash recovery and point in time recovery -technologies, physical replication was first introduced in PostgreSQL 8.2 -(2006) through WAL shipping from the primary to a warm standby in continuous -recovery. - -PostgreSQL 9.0 (2010) introduced WAL streaming and read-only replicas through -*hot standby*. In 2011, PostgreSQL 9.1 brought synchronous replication at the -transaction level, supporting [RPO](before_you_start.md#postgresql-terminology)=0 clusters. Cascading -replication was added in PostgreSQL 9.2 (2012). The foundations for -[logical replication](logical_replication.md) were established in PostgreSQL -9.4 (2014), and version 10 (2017) introduced native support for the -publisher/subscriber pattern to replicate data from an origin to a destination. The -table below summarizes these milestones. - -| Version | Year | Feature | -| :-----: | :--: | --------------------------------------------------------------------- | -| 8.2 | 2006 | Warm Standby with WAL shipping | -| 9.0 | 2010 | Hot Standby and physical streaming replication | -| 9.1 | 2011 | Synchronous replication (priority-based) | -| 9.2 | 2012 | Cascading replication | -| 9.4 | 2014 | Foundations of logical replication | -| 10 | 2017 | Logical publisher/subscriber and quorum-based synchronous replication | - -This table highlights key PostgreSQL replication features and their respective -versions. - -## Streaming replication support - -At the moment, {{name.ln}} natively and transparently manages physical -streaming replicas within a cluster in a declarative way, based on the number of -provided `instances` in the `spec`: - -``` -replicas = instances - 1 (where instances > 0) -``` - -Immediately after the initialization of a cluster, the operator creates a user -called `streaming_replica` as follows: - -```sql -CREATE USER streaming_replica WITH REPLICATION; --- NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB NOBYPASSRLS -``` - -Out of the box, the operator automatically sets up streaming replication within -the cluster over an encrypted channel and enforces TLS client certificate -authentication for the `streaming_replica` user - as highlighted by the -following excerpt taken from `pg_hba.conf`: - -``` -# Require client certificate authentication for the streaming_replica user -hostssl postgres streaming_replica all cert map=cnp_streaming_replica -hostssl replication streaming_replica all cert map=cnp_streaming_replica -``` - -!!!note Certificates -For details on how {{name.ln}} manages certificates, please refer -to the ["Certificates" section](certificates.md#client-streaming_replica-certificate) -in the documentation. -!!! - -If configured, the operator manages replication slots for all the replicas in the -HA cluster, ensuring that WAL files required by each standby are retained on -the primary's storage, even after a failover or switchover. - -!!!note Replication slots for High Availability -For details on how {{name.ln}} automatically manages replication slots for the -High Availability replicas, please refer to the -["Replication slots for High Availability" section](#replication-slots-for-high-availability) -below. -!!! - -### Continuous backup integration - -In case continuous backup is configured in the cluster, {{name.ln}} -transparently configures replicas to take advantage of `restore_command` when in -continuous recovery. As a result, PostgreSQL can use the WAL archive as a -fallback option whenever pulling WALs via streaming replication fails. - -## Synchronous Replication - -{{name.ln}} supports both -[quorum-based and priority-based synchronous replication for PostgreSQL](https://www.postgresql.org/docs/current/warm-standby.html#SYNCHRONOUS-REPLICATION). - -!!!warning -By default, synchronous replication pauses write operations if the required -number of standby nodes for WAL replication during transaction commits is -unavailable. This behavior prioritizes data durability and aligns with -PostgreSQL DBA best practices. However, if self-healing is a higher priority -than strict data durability in your setup, this setting can be adjusted. For -details on managing this behavior, refer to the [Data Durability and Synchronous Replication](#data-durability-and-synchronous-replication) -section. -!!! - -!!!info Important -The [*failover quorum* feature](failover.md#failover-quorum-quorum-based-failover) -can be used alongside synchronous replication to improve data durability -and safety during failover events. -!!! - -Direct configuration of the `synchronous_standby_names` option is not -permitted. However, {{name.ln}} automatically populates this option with the -names of local pods, while also allowing customization to extend synchronous -replication beyond the `Cluster` resource. -This can be achieved through the -[`.spec.postgresql.synchronous` stanza](pg4k.v1.md#synchronousreplicaconfiguration). - -Synchronous replication is disabled by default (the `synchronous` stanza is not -defined). When defined, two options are mandatory: - -- `method`: either `any` (quorum) or `first` (priority) -- `number`: the number of synchronous standby servers that transactions must - wait for responses from - -### Quorum-based Synchronous Replication - -In PostgreSQL, quorum-based synchronous replication ensures that transaction -commits wait until their WAL records are replicated to a specified number of -standbys. To enable this, set the `method` to `any`. - -This replication method is the most common setup for a {{name.ln}} cluster. - -#### Example - -The example below, based on a typical `cluster-example` configuration with -three instances, sets up quorum-based synchronous replication with at least one -instance: - -```yaml -postgresql: - synchronous: - method: any - number: 1 -``` - -With this configuration, {{name.ln}} automatically sets the content of -`synchronous_standby_names` as follows: - -```console -ANY 1 (cluster-example-2, cluster-example-3, cluster-example-1) -``` - -#### Migrating from Deprecated Synchronous Replication Implementation - -This section outlines how to migrate from the deprecated quorum-based -synchronous replication format to the newer, more robust implementation in -{{name.ln}}. - -Given the following manifest: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: angus -spec: - instances: 3 - minSyncReplicas: 1 - maxSyncReplicas: 1 - - storage: - size: 1Gi -``` - -You can update it to the new format as follows: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: angus -spec: - instances: 3 - - storage: - size: 1Gi - - postgresql: - synchronous: - method: any - number: 1 - dataDurability: required -``` - -To prioritize self-healing over strict data durability, set `dataDurability` -to `preferred` instead. - -### Priority-based Synchronous Replication - -PostgreSQL's priority-based synchronous replication makes transaction commits -wait until their WAL records are replicated to the requested number of -synchronous standbys chosen based on their priorities. Standbys listed earlier -in the `synchronous_standby_names` option are given higher priority and -considered synchronous. If a current synchronous standby disconnects, it is -immediately replaced by the next-highest-priority standby. To use this method, -set `method` to `first`. - -!!!info Important -Currently, this method is most useful when extending -synchronous replication beyond the current cluster using the -`maxStandbyNamesFromCluster`, `standbyNamesPre`, and `standbyNamesPost` -options explained below. -!!! - -### Controlling `synchronous_standby_names` Content - -By default, {{name.ln}} populates `synchronous_standby_names` with the names -of local pods in a `Cluster` resource, ensuring synchronous replication within -the PostgreSQL cluster. You can customize the content of -`synchronous_standby_names` based on your requirements and replication method -(quorum or priority) using the following optional parameters in the -`.spec.postgresql.synchronous` stanza: - -- `maxStandbyNamesFromCluster`: the maximum number of pod names from the local - `Cluster` object that can be automatically included in the - `synchronous_standby_names` option in PostgreSQL. -- `standbyNamesPre`: a list of standby names (specifically `application_name`) - to be prepended to the list of local pod names automatically listed by the - operator. -- `standbyNamesPost`: a list of standby names (specifically `application_name`) - to be appended to the list of local pod names automatically listed by the - operator. - -!!!warning -You are responsible for ensuring the correct names in `standbyNamesPre` and -`standbyNamesPost`. {{name.ln}} expects that you manage any standby with -an `application_name` listed here, ensuring their high availability. -Incorrect entries can jeopardize your PostgreSQL database uptime. -!!! - -#### Examples - -Here are some examples, all based on a `cluster-example` with three instances: - -If you set: - -```yaml -postgresql: - synchronous: - method: any - number: 1 - maxStandbyNamesFromCluster: 1 - standbyNamesPre: - - angus -``` - -The content of `synchronous_standby_names` will be: - -```console -ANY 1 (angus, cluster-example-2) -``` - -If you set: - -```yaml -postgresql: - synchronous: - method: any - number: 1 - maxStandbyNamesFromCluster: 0 - standbyNamesPre: - - angus - - malcolm -``` - -The content of `synchronous_standby_names` will be: - -```console -ANY 1 (angus, malcolm) -``` - -If you set: - -```yaml -postgresql: - synchronous: - method: first - number: 2 - maxStandbyNamesFromCluster: 1 - standbyNamesPre: - - angus - standbyNamesPost: - - malcolm -``` - -The `synchronous_standby_names` option will look like: - -```console -FIRST 2 (angus, cluster-example-2, malcolm) -``` - -### Data Durability and Synchronous Replication - -The `dataDurability` option in the `.spec.postgresql.synchronous` stanza -controls the trade-off between data safety and availability for synchronous -replication. It can be set to `required` or `preferred`, with the default being -`required` if not specified. - -!!!info Important -`preferred` can only be used when `standbyNamesPre` and `standbyNamesPost` -are unset. -!!! - -#### Required Data Durability - -When `dataDurability` is set to `required`, PostgreSQL only considers -transactions committed once WAL (Write-Ahead Log) records have been replicated -to the specified number of synchronous standbys. This setting prioritizes data -safety over availability, meaning write operations will pause if the required -number of synchronous standbys is unavailable. This ensures zero data loss -(RPO=0) but may reduce database availability during network disruptions or -standby failures. - -Synchronous standbys are selected in this priority order: - -1. Healthy instances -2. Unhealthy instances -3. Primary - -The list is then truncated based on `maxStandbyNamesFromCluster` if this value -is set, prioritizing healthy instances and ensuring `synchronous_standby_names` -is populated. - -##### Example - -Consider the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: foo -spec: - instances: 3 - postgresql: - synchronous: - method: any - number: 1 - dataDurability: required -``` - -1. Initial state. The content of `synchronous_standby_names` is: - - ``` - ANY 1 ("foo-2","foo-3","foo-1") - ``` - -2. `foo-2` becomes unavailable. It gets pushed back in priority: - - ``` - ANY 1 ("foo-3","foo-2","foo-1") - ``` - -3. `foo-3` also becomes unavailable. The list contains no healthy standbys: - - ``` - ANY 1 ("foo-2","foo-3","foo-1") - ``` - - At this point no write operations will be allowed until at least one of the - standbys is available again. - -4. When the standbys are available again, `synchronous_standby_names` will - be back to the initial state. - -#### Preferred Data Durability - -When `dataDurability` is set to `preferred`, the required number of synchronous -instances adjusts based on the number of available standbys. PostgreSQL will -attempt to replicate WAL records to the designated number of synchronous -standbys, but write operations will continue even if fewer than the requested -number of standbys are available. - -!!!info Important -Make sure you have a clear understanding of what *ready/available* means -for a replica and set your expectations accordingly. By default, a replica is -considered ready when it has successfully connected to the source at least -once. However, {{name.ln}} allows you to configure startup and readiness -probes for replicas based on maximum lag. For more details, please refer to -the ["Postgres instance manager" section](instance_manager.md). -!!! - -This setting balances data safety with availability, enabling applications to -continue writing during temporary standby unavailability—hence, it’s also known -as *self-healing mode*. - -!!!warning -This mode may result in data loss if all standbys become unavailable. -!!! - -With `preferred` data durability, **only healthy replicas** are included in -`synchronous_standby_names`. - -##### Example - -Consider the following example. For demonstration, we’ll use a cluster named -`bar` with 5 instances and 2 synchronous standbys: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: bar -spec: - instances: 5 - postgresql: - synchronous: - method: any - number: 2 - dataDurability: preferred -``` - -1. Initial state. The content of `synchronous_standby_names` is: - - ``` - ANY 2 ("bar-2","bar-3", "bar-4", "bar-5") - ``` - -2. `bar-2` and `bar-3` become unavailable. They are removed from the list: - - ``` - ANY 2 ("bar-4", "bar-5") - ``` - -3. `bar-4` also becomes unavailable. It gets removed from the list. Since the - number of available standbys is less than the requested number, the requested - amount gets reduced: - - ``` - ANY 1 ("bar-5") - ``` - -4. `bar-5` also becomes unavailable. `synchronous_standby_names` becomes empty, - disabling synchronous replication completely. Write operations will continue, - but with the risk of potential data loss in case of a primary failure. - -5. When the replicas are back, `synchronous_standby_names` will be back to - the initial state. - -## Synchronous Replication (Deprecated) - -!!!warning -Prior to {{name.ln}} 1.24, only the quorum-based synchronous replication -implementation was supported. Although this method is now deprecated, it -will not be removed anytime soon. -The new method prioritizes data durability over self-healing and offers more -robust features, including priority-based synchronous replication and full -control over the `synchronous_standby_names` option. -It is recommended to gradually migrate to the new configuration method for -synchronous replication, as explained in the previous paragraph. -!!! - -!!!info Important -The deprecated method and the new method are mutually exclusive. -!!! - -{{name.ln}} supports the configuration of **quorum-based synchronous -streaming replication** via two configuration options called `minSyncReplicas` -and `maxSyncReplicas`, which are the minimum and the maximum number of expected -synchronous standby replicas available at any time. -For self-healing purposes, the operator always compares these two values with -the number of available replicas to determine the quorum. - -!!!info Important -By default, synchronous replication selects among all the available -replicas indistinctively. You can limit on which nodes your synchronous -replicas can be scheduled, by working on node labels through the -`syncReplicaElectionConstraint` option as described in the next section. -!!! - -Synchronous replication is disabled by default (`minSyncReplicas` and -`maxSyncReplicas` are not defined). -In case both `minSyncReplicas` and `maxSyncReplicas` are set, {{name.ln}} -automatically updates the `synchronous_standby_names` option in -PostgreSQL to the following value: - -``` -ANY q (pod1, pod2, ...) -``` - -Where: - -- `q` is an integer automatically calculated by the operator to be: - `1 ≤ minSyncReplicas ≤ q ≤ maxSyncReplicas ≤ readyReplicas` -- `pod1, pod2, ...` is the list of all PostgreSQL pods in the cluster - -!!!warning -To provide self-healing capabilities, the operator can ignore -`minSyncReplicas` if such value is higher than the currently available -number of replicas. Synchronous replication is automatically disabled -when `readyReplicas` is `0`. -!!! - -As stated in the -[PostgreSQL documentation](https://www.postgresql.org/docs/current/warm-standby.html#SYNCHRONOUS-REPLICATION), -the *method `ANY` specifies a quorum-based synchronous replication and makes -transaction commits wait until their WAL records are replicated to at least the -requested number of synchronous standbys in the list*. - -!!!info Important -Even though the operator chooses self-healing over enforcement of -synchronous replication settings, our recommendation is to plan for -synchronous replication only in clusters with 3+ instances or, -more generally, when `maxSyncReplicas < (instances - 1)`. -!!! - -### Select nodes for synchronous replication - -{{name.ln}} enables you to select which PostgreSQL instances are eligible to -participate in a quorum-based synchronous replication set through anti-affinity -rules based on the node labels where the PVC holding the PGDATA and the -Postgres pod are. - -!!!note Scheduling -For more information on the general pod affinity and anti-affinity rules, -please check the ["Scheduling" section](scheduling.md). -!!! - -!!!warning -The `.spec.postgresql.syncReplicaElectionConstraint` option only applies to the -legacy implementation of synchronous replication -(see ["Synchronous Replication (Deprecated)"](replication.md#synchronous-replication-deprecated)). -!!! - -As an example use-case for this feature: in a cluster with a single sync -replica, we would be able to ensure the sync replica will be in a different -availability zone from the primary instance, usually identified by -the `topology.kubernetes.io/zone` -[label on a node](https://kubernetes.io/docs/reference/labels-annotations-taints/#topologykubernetesiozone). -This would increase the robustness of the cluster in case of an outage in a -single availability zone, especially in terms of recovery point objective -([RPO](before_you_start.md#postgresql-terminology)). - -The idea of anti-affinity is to ensure that sync replicas that participate in -the quorum are chosen from pods running on nodes that have different values for -the selected labels (in this case, the availability zone label) then the node -where the primary is currently in execution. If no node matches such criteria, -the replicas are eligible for synchronous replication. - -!!!info Important -The self-healing enforcement still applies while defining additional -constraints for synchronous replica election -(see ["Synchronous replication"](replication.md#synchronous-replication)). -!!! - -The example below shows how this can be done through the -`syncReplicaElectionConstraint` section within `.spec.postgresql`. -`nodeLabelsAntiAffinity` allows you to specify those node labels that need to be -evaluated to make sure that synchronous replication will be dynamically -configured by the operator between the current primary and the replicas which -are located on nodes having a value of the availability zone label different -from that of the node where the primary is: - -```yaml -spec: - instances: 3 - postgresql: - syncReplicaElectionConstraint: - enabled: true - nodeLabelsAntiAffinity: - - topology.kubernetes.io/zone -``` - -As you can imagine, the availability zone is just an example, but you could -customize this behavior based on other labels that describe the node, such -as storage, CPU, or memory. - -## Replication slots - -[Replication slots](https://www.postgresql.org/docs/current/warm-standby.html#STREAMING-REPLICATION-SLOTS) -are a native PostgreSQL feature introduced in 9.4 that provides an automated way -to ensure that the primary does not remove WAL segments until all the attached -streaming replication clients have received them, and that the primary does not -remove rows which could cause a recovery conflict even when the standby is ( -temporarily) disconnected. - -A replication slot exists solely on the instance that created it, and PostgreSQL -does not replicate it on the standby servers. As a result, after a failover or a -switchover, the new primary does not contain the replication slot from the old -primary. This can create problems for the streaming replication clients that -were connected to the old primary and have lost their slot. - -{{name.ln}} provides a turn-key solution to synchronize the content of -physical replication slots from the primary to each standby, addressing two use -cases: - -- the replication slots automatically created for the High Availability of the - Postgres cluster ( - see ["Replication slots for High Availability" below](#replication-slots-for-high-availability) - for details) -- [user-defined replication slots](#user-defined-replication-slots) created on - the primary - -### Replication slots for High Availability - -{{name.ln}} fills this gap by introducing the concept of cluster-managed -replication slots, starting with high availability clusters. This feature -automatically manages physical replication slots for each hot standby replica in -the High Availability cluster, both in the primary and the standby. - -In {{name.ln}}, we use the terms: - -- **Primary HA slot**: a physical replication slot whose lifecycle is entirely - managed by the current primary of the cluster and whose purpose is to map to a - specific standby in streaming replication. Such a slot lives on the primary - only. -- **Standby HA slot**: a physical replication slot for a standby whose lifecycle - is entirely managed by another standby in the cluster, based on the content of - the `pg_replication_slots` view in the primary, and updated at regular - intervals using `pg_replication_slot_advance()`. - -This feature is enabled by default and can be disabled via configuration. For -details, please refer to the -["replicationSlots" section in the API reference](pg4k.v1.md#replicationslotsconfiguration). -Here follows a brief description of the main options: - -`.spec.replicationSlots.highAvailability.enabled` -: if `true`, the feature is enabled (`true` is the default) - -`.spec.replicationSlots.highAvailability.slotPrefix` -: the prefix that identifies replication slots managed by the operator for this -feature (default: `_cnp_`) - -`.spec.replicationSlots.updateInterval` -: how often the standby synchronizes the position of the local copy of the -replication slots with the position on the current primary, expressed in -seconds (default: 30) - -Although it is not recommended, if you desire a different behavior, you can -customize the above options. - -For example, the following manifest will create a cluster with replication -slots disabled. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - # Disable replication slots for HA in the cluster - replicationSlots: - highAvailability: - enabled: false - - storage: - size: 1Gi -``` - -### User-Defined Replication slots - -Although {{name.ln}} doesn't support a way to declaratively define physical -replication slots, you can still [create your own slots via SQL](https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-REPLICATION). - -!!!note Information -At the moment, we don't have any plans to manage replication slots -in a declarative way, but it might change depending on the feedback -we receive from users. The reason is that replication slots exist -for a specific purpose and each should be managed by a specific application -the oversees the entire lifecycle of the slot on the primary. -!!! - -{{name.ln}} can manage the synchronization of any user managed physical -replication slots between the primary and standbys, similarly to what it does -for the HA replication slots explained above (the only difference is that you -need to create the replication slot). - -This feature is enabled by default (meaning that any replication slot is -synchronized), but you can disable it or further customize its behavior (for -example by excluding some slots using regular expressions) through the -`synchronizeReplicas` stanza. For example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - replicationSlots: - synchronizeReplicas: - enabled: true - excludePatterns: - - "^foo" -``` - -For details, please refer to the -["replicationSlots" section in the API reference](pg4k.v1.md#replicationslotsconfiguration). -Here follows a brief description of the main options: - -`.spec.replicationSlots.synchronizeReplicas.enabled` -: When true or not specified, every user-defined replication slot on the - primary is synchronized on each standby. If changed to false, the operator will - remove any replication slot previously created by itself on each standby. - -`.spec.replicationSlots.synchronizeReplicas.excludePatterns` -: A list of regular expression patterns to match the names of user-defined - replication slots to be excluded from synchronization. This can be useful to - exclude specific slots based on naming conventions. - -!!!warning -Users utilizing this feature should carefully monitor user-defined replication -slots to ensure they align with their operational requirements and do not -interfere with the failover process. -!!! - -### Synchronization frequency - -You can also control the frequency with which a standby queries the -`pg_replication_slots` view on the primary, and updates its local copy of -the replication slots, like in this example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - # Reduce the frequency of standby HA slots updates to once every 5 minutes - replicationSlots: - updateInterval: 300 - - storage: - size: 1Gi -``` - -### Logical Decoding Slot Synchronization - -{{name.ln}} can synchronize logical decoding (replication) slots across all -nodes in a high-availability cluster, ensuring seamless continuation of logical -replication after a failover or switchover. This feature is disabled by -default, and enabling it requires two steps. - -The first step is to enable logical decoding slot synchronization: - -```yaml - # ... - replicationSlots: - highAvailability: - synchronizeLogicalDecoding: true -``` - -The second step involves configuring PostgreSQL parameters: the required -configuration depends on your PostgreSQL version, as explained below. - -When enabled, the operator automatically manages logical decoding slot states -during failover and switchover, preventing slot invalidation and avoiding data -loss for logical replication clients. - -#### Behavior on PostgreSQL 17 and later - -For PostgreSQL 17 and newer, {{name.ln}} transparently manages the -[`synchronized_standby_slots` parameter](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-SYNCHRONIZED-STANDBY-SLOTS). - -You must enable both `sync_replication_slots` and `hot_standby_feedback` in -your PostgreSQL configuration: - -```yaml -# ... -postgresql: - parameters: - # ... - hot_standby_feedback: 'on' - sync_replication_slots: 'on' -``` - -Additionally, you must create the logical replication `Subscription` with the -`failover` option enabled, for example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Subscription -# ... -spec: -# ... - parameters: - failover: 'true' -# ... -``` - -When configured, logical WAL sender processes send decoded changes to plugins -only after the specified replication slots confirm receiving and flushing the -relevant WAL, ensuring that: - -- logical replication slots do not consume changes until they are safely - received by the replicas of the publisher, and -- logical replication clients can seamlessly reconnect to a promoted standby - without missing data after failover. - -For more details on logical replication slot synchronization, see the -PostgreSQL documentation on [Logical Replication Failover](https://www.postgresql.org/docs/current/logical-replication-failover.html). - -#### Behavior on PostgreSQL 16 and earlier - -For PostgreSQL 16 and older versions, {{name.ln}} uses the -[`pg_failover_slots` extension](https://github.com/EnterpriseDB/pg_failover_slots) -to maintain synchronization of logical replication slots across failovers. - -### Capping the WAL size retained for replication slots - -When replication slots is enabled, you might end up running out of disk space -due to PostgreSQL trying to retain WAL files requested by a replication slot. -This might happen due to a standby that is (temporarily?) down, or lagging, or -simply an orphan replication slot. - -Starting with PostgreSQL 13, you can take advantage of the -[`max_slot_wal_keep_size`](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-SLOT-WAL-KEEP-SIZE) -configuration option controlling the maximum size of WAL files that replication -slots are allowed to retain in the `pg_wal` directory at checkpoint time. By -default, in PostgreSQL `max_slot_wal_keep_size` is set to `-1`, meaning that -replication slots may retain an unlimited amount of WAL files. As a result, our -recommendation is to explicitly set `max_slot_wal_keep_size` -when replication slots support is enabled. For example: - -```ini - # ... - postgresql: - parameters: - max_slot_wal_keep_size: "10GB" - # ... -``` - -### Monitoring replication slots - -Replication slots must be carefully monitored in your infrastructure. By default, -we provide the `pg_replication_slots` metric in our Prometheus exporter with -key information such as the name of the slot, the type, whether it is active, -the lag from the primary. - -!!!note Monitoring -Please refer to the ["Monitoring" section](monitoring.md) for details on -how to monitor a {{name.ln}} deployment. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/resource_management.mdx b/product_docs/docs/postgres_for_kubernetes/preview/resource_management.mdx deleted file mode 100644 index afa3cf0c6fd..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/resource_management.mdx +++ /dev/null @@ -1,189 +0,0 @@ ---- -title: 'Resource management' -originalFilePath: 'src/resource_management.md' ---- - - - -In a typical Kubernetes cluster, pods run with unlimited resources. By default, -they might be allowed to use as much CPU and RAM as needed. - -{{name.ln}} allows administrators to control and manage resource usage by the pods of the cluster, -through the `resources` section of the manifest, with two knobs: - -- `requests`: initial requirement -- `limits`: maximum usage, in case of dynamic increase of resource needs - -For example, you can request an initial amount of RAM of 32MiB (scalable to 128MiB) and 50m of CPU (scalable to 100m) -as follows: - -```yaml - resources: - requests: - memory: "32Mi" - cpu: "50m" - limits: - memory: "128Mi" - cpu: "100m" -``` - -Memory requests and limits are associated with containers, but it is useful to think of a pod as having a memory request -and limit. The pod's memory request is the sum of the memory requests for all the containers in the pod. - -Pod scheduling is based on requests and not on limits. A pod is scheduled to run on a Node only if the Node has enough -available memory to satisfy the pod's memory request. - -For each resource, we divide containers into 3 Quality of Service (QoS) classes, in decreasing order of priority: - -- *Guaranteed* -- *Burstable* -- *Best-Effort* - -For more details, please refer to the ["Configure Quality of Service for Pods"](https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/#qos-classes) -section in the Kubernetes documentation. - -For a PostgreSQL workload it is recommended to set a "Guaranteed" QoS. - -!!!info -When the quality of service is set to "Guaranteed", {{name.ln}} sets the -`PG_OOM_ADJUST_VALUE` for the `postmaster` process to `0`, in line with the -[PostgreSQL documentation](https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT). -This allows the `postmaster` to retain its low Out-Of-Memory (OOM) score of -`-997`, while its child processes run with an OOM score adjustment of `0`. As a -result, if the OOM killer is triggered, it will terminate the child processes -before the `postmaster`. This behavior helps keep the PostgreSQL instance -alive for as long as possible and enables a clean shutdown procedure in the -event of an eviction. -!!! - -To avoid resources related issues in Kubernetes, we can refer to the best practices for "out of resource" handling -while creating a cluster: - -- Specify your required values for memory and CPU in the resources section of the manifest file. - This way, you can avoid the `OOM Killed` and `CPU throttle` or any other - resource-related issues on running instances. -- For your cluster's pods to get assigned to the "Guaranteed" QoS class, you - must set limits and requests - for both memory and CPU to the same value. -- Specify your required PostgreSQL memory parameters consistently with the pod resources (as you would do - in a VM or physical machine scenario - see below). -- Set up database server pods on a dedicated node using nodeSelector. - See the "nodeSelector" and "tolerations" fields of the - [“affinityconfiguration"](pg4k.v1.md#affinityconfiguration) resource on the API reference page. - -You can refer to the following example manifest: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-resources -spec: - - instances: 3 - - postgresql: - parameters: - shared_buffers: "256MB" - - resources: - requests: - memory: "1024Mi" - cpu: 1 - limits: - memory: "1024Mi" - cpu: 1 - - storage: - size: 1Gi -``` - -In the above example, we have specified `shared_buffers` parameter with a value of `256MB` - i.e., how much memory is -dedicated to the PostgreSQL server for caching data (the default value for this parameter is `128MB` in case -it's not defined). - -A reasonable starting value for `shared_buffers` is 25% of the memory in your system. -For example: if your `shared_buffers` is 256 MB, then the recommended value for your container memory size is 1 GB, -which means that within a pod all the containers will have a total of 1 GB memory that Kubernetes will always preserve, -enabling our containers to work as expected. -For more details, please refer to the ["Resource Consumption"](https://www.postgresql.org/docs/current/runtime-config-resource.html) -section in the PostgreSQL documentation. - -!!!note Managing Compute Resources for Containers -For more details on resource management, please refer to the -["Managing Compute Resources for Containers"](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/) -page from the Kubernetes documentation. -!!! - -## Integration with the Vertical Pod Autoscaler (VPA) - -The `Cluster` CRD exposes the `scale` subresource together with the label -selector for its instance pods. This makes a `Cluster` a valid `targetRef` for the -[Vertical Pod Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler) -(VPA), so VPA can observe the instance pods and emit CPU and memory -recommendations for them. - -We recommend running VPA in **recommendation-only** mode -(`updatePolicy.updateMode: Off`). In this mode VPA only reports its -recommendations, which an operator can then apply to `spec.resources` of the -`Cluster` through a normal manifest update; {{name.ln}} performs the rolling -update of the instances using its usual switchover-aware procedure. VPA -produces a recommendation per container: use the one for the `postgres` -container, since that is what `spec.resources` configures. - -Example targeting a `Cluster`: - -```yaml -apiVersion: autoscaling.k8s.io/v1 -kind: VerticalPodAutoscaler -metadata: - name: cluster-example-vpa -spec: - targetRef: - apiVersion: postgresql.k8s.enterprisedb.io/v1 - kind: Cluster - name: cluster-example - updatePolicy: - updateMode: "Off" -``` - -!!!warning - -Do not use `updateMode: Auto`, `Recreate`, or `Initial` against a -{{name.ln}}-managed `Cluster`. The operator owns the pod specification and -treats `spec.resources` of the `Cluster` as the source of truth: it does not -adopt the resources VPA writes onto a running pod, so the live pod and the -declared `spec.resources` silently diverge. Any tuning you sized against the -declared resources (for example a `shared_buffers` value the operator -validated against the memory request) no longer matches the pod's actual -limits. VPA also evicts pods through the Kubernetes eviction API, bypassing -the operator's switchover-aware sequencing; the default primary -`PodDisruptionBudget` then blocks eviction of the primary, so VPA stalls -instead of completing. Apply the VPA recommendations to the `Cluster` manifest -manually instead. -!!! - -## Integration with the Horizontal Pod Autoscaler (HPA) - -The `scale` subresource also exposes `spec.instances`, so a -[Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) -(HPA) can technically change the number of instances in a `Cluster`. -In practice this is **not recommended** for a PostgreSQL cluster, for several -reasons. - -Scaling a `Cluster` only adds or removes standby replicas; it never relieves -write load on the primary. The selector exposed through the scale subresource -matches the primary and all replicas, which have opposite workload profiles -(write-heavy primary, read-only replicas), so the per-pod average that HPA -computes from a CPU or memory metric is not a meaningful signal for any of -them. Adding a replica only dilutes that average further without addressing a -hot primary. - -HPA is also unaware of {{name.ln}}' own constraints on `spec.instances`. If -you configure synchronous replicas, a scale-down below `maxSyncReplicas + 1` -instances is rejected by the validating webhook, and HPA keeps retrying a -value it cannot satisfy. -If you nonetheless drive `spec.instances` from an HPA, base it on a custom -metric that actually reflects read replica load, and set `minReplicas` above -the synchronous-replica floor. Review the impact on replication and quorum -carefully first. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/rolling_update.mdx b/product_docs/docs/postgres_for_kubernetes/preview/rolling_update.mdx deleted file mode 100644 index 53e19e73fd4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/rolling_update.mdx +++ /dev/null @@ -1,111 +0,0 @@ ---- -title: 'Rolling updates' -originalFilePath: 'src/rolling_update.md' ---- - - - -The operator allows you to change the PostgreSQL version used in a cluster -while applications continue running against it. - -Rolling upgrades are triggered when: - -- you change the `imageName` attribute in the cluster specification; - -- you change the list of extension images in the `.spec.postgresql.extensions` - stanza of the cluster specification; - -- the [image catalog](image_catalog.md) is updated with a new image for the - major version used by the cluster; - -- a change in the PostgreSQL configuration requires a restart to apply; - -- you change the `Cluster` `.spec.resources` values; - -- the operator is updated, ensuring Pods run the latest instance manager - (unless [in-place updates are enabled](installation_upgrade.md#in-place-updates-of-the-instance-manager)). - -During a rolling upgrade, the operator upgrades all replicas one Pod at a time, -starting from the one with the highest serial. - -The primary is always the last node to be upgraded. - -Rolling updates are configurable and can be either entirely automated -(`unsupervised`) or requiring human intervention (`supervised`). - -The upgrade keeps the {{name.ln}} identity, without re-cloning the -data. Pods will be deleted and created again with the same PVCs and a new -image, if required. - -During the rolling update procedure, each service's endpoint moves to reflect the -cluster's status, so that applications can ignore the node that is being -updated. - -## Automated updates (`unsupervised`) - -When `primaryUpdateStrategy` is set to `unsupervised`, the rolling update -process is managed by Kubernetes and is entirely automated. Once the replicas -have been upgraded, the selected `primaryUpdateMethod` operation will be executed -on the primary. Unsupervised update is the default behavior. - -The `primaryUpdateMethod` option accepts one of the following values: - -- `restart`: if possible, perform an automated restart of the pod where the - primary instance is running. Otherwise, the restart request is ignored and a - switchover issued. This is the default behavior. - -- `switchover`: a switchover operation is automatically performed, setting the - most aligned replica as the new target primary, and shutting down the former - primary pod. - -!!!warning -When `primaryUpdateMethod` is set to `switchover`, you cannot change the -image name and PostgreSQL configuration parameters at the same time. The -operator will reject such updates with a validation error. If you need to -update both the image and the configuration, you must perform these changes -sequentially: update the image first, wait for the rolling update to -complete, then update the configuration (or vice versa). This restriction -exists because configuration changes tied to a new image version could cause -PostgreSQL to fail if applied to pods still running the old image during the -switchover process. -!!! - -There's no one-size-fits-all configuration for the update method, as that -depends on several factors like the actual workload of your database, the -requirements in terms of [RPO](before_you_start.md#postgresql-terminology) and -[RTO](before_you_start.md#postgresql-terminology), whether your PostgreSQL architecture is shared -or shared nothing, and so on. - -Indeed, since PostgreSQL is a primary/standby architecture database management -system, the update process inevitably generates a downtime for your -applications. One important aspect to consider for your context is the time it -takes for your pod to download the new PostgreSQL container image, as that -depends on your Kubernetes cluster settings and specifications. The -`switchover` method makes sure that the promoted instance already runs the -target image version of the container. The `restart` method instead might require -to download the image from the origin registry after the primary pod has been -shut down. It is up to you to determine whether, for your database, it is best -to use `restart` or `switchover` as part of the rolling update procedure. - -## Manual updates (`supervised`) - -When `primaryUpdateStrategy` is set to `supervised`, the rolling update process -is suspended immediately after all replicas have been upgraded. - -This phase can only be completed with either a manual switchover or an in-place -restart. Keep in mind that image upgrades can not be applied with an in-place restart, -so a switchover is required in such cases. - -You can trigger a switchover with: - -```bash -kubectl cnp promote [cluster] [new_primary] -``` - -You can trigger a restart with: - -```bash -kubectl cnp restart [cluster] [current_primary] -``` - -You can find more information in the [`cnp` plugin page](kubectl-plugin.md). diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples.mdx b/product_docs/docs/postgres_for_kubernetes/preview/samples.mdx deleted file mode 100644 index 6b58b94f0cf..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples.mdx +++ /dev/null @@ -1,247 +0,0 @@ ---- -title: 'Examples' -originalFilePath: 'src/samples.md' ---- - - - -The examples show configuration files for setting up -your PostgreSQL cluster. - -!!!info Important -These examples are for demonstration and experimentation -purposes. You can execute them on a personal Kubernetes cluster with Minikube -or Kind, as described in [Quick start](quickstart.md). -!!! - -!!!note Reference -For a list of available options, see [API reference](pg4k.v1.md). -!!! - -## Basics - -**Basic cluster** -: [`cluster-example.yaml`](../samples/cluster-example.yaml) - A basic example of a cluster. - -**EDB Postgres Advanced Server (EPAS) cluster** -: [`cluster-example-epas.yaml`](../samples/cluster-example-epas.yaml) - A basic example of an EPAS cluster. - -**EDB Postgres Extended (PGE) cluster** -: [`cluster-example-pge.yaml`](../samples/cluster-example-pge.yaml) - A basic example of a PGE cluster. - -**Custom cluster** -: [`cluster-example-custom.yaml`](../samples/cluster-example-custom.yaml) - A basic cluster that uses the default storage class and custom parameters for - the `postgresql.conf` and `pg_hba.conf` files. - -**Cluster with dynamic pg_hba address resolution** -: [`cluster-example-pod-selector-refs.yaml`](../samples/cluster-example-pod-selector-refs.yaml) - A cluster that uses `podSelectorRefs` to dynamically resolve pod IPs in - `pg_hba` rules via the `${podselector:NAME}` syntax. - -**Cluster with customized storage class** -: [`cluster-storage-class.yaml`](../samples/cluster-storage-class.yaml): - A basic cluster that uses a specified storage class of `standard`. - -**Cluster with persistent volume claim (PVC) template configured** -: [`cluster-pvc-template.yaml`](../samples/cluster-pvc-template.yaml): - A basic cluster with an explicit persistent volume claim template. - -**Extended configuration example** -: [`cluster-example-full.yaml`](../samples/cluster-example-full.yaml): - A cluster that sets most of the available options. - -**Bootstrap cluster with SQL files** -: [`cluster-example-initdb-sql-refs.yaml`](../samples/cluster-example-initdb-sql-refs.yaml): - A cluster example that executes a set of queries defined in a secret and a - `ConfigMap` right after the database is created. - -**Sample cluster with customized `pg_hba` configuration** -: [`cluster-example-pg-hba.yaml`](../samples/cluster-example-pg-hba.yaml): - A basic cluster that enables the user app to authenticate using certificates. - -**Sample cluster with Secret and ConfigMap mounted using projected volume template** -: [`cluster-example-projected-volume.yaml`](../samples/cluster-example-projected-volume.yaml) - A basic cluster with the existing `Secret` and `ConfigMap` mounted into Postgres - pod using projected volume mount. - -**Cluster with TDE enabled** -: [`cluster-example-tde.yaml`](../samples/cluster-example-tde.yaml) - an EPAS 15 cluster with TDE. Note that you will need access credentials - to download the image used. - -## Security - -**Sample cluster with custom security contexts** -: [`cluster-example-security-context.yaml`](../samples/cluster-example-security-context.yaml) - A cluster demonstrating how to customize both Pod and Container security contexts. - This is useful when working with Pod Security Standards or meeting specific security requirements. - -## Backups - -**Customized storage class and backups** -: *Prerequisites*: Bucket storage must be available. The sample config is for AWS. - Change it to suit your setup. -: [`cluster-storage-class-with-backup.yaml`](../samples/cluster-storage-class-with-backup.yaml) - A cluster with backups configured. - -**Backup** -: *Prerequisites*: [`cluster-storage-class-with-backup.yaml`](../samples/cluster-storage-class-with-backup.yaml) - applied and healthy. -: [`backup-example.yaml`](../samples/backup-example.yaml): - An example of a backup that runs against the previous sample. - -**Simple cluster with backup configured for minio** -: *Prerequisites*: The configuration assumes minio is running and working. - Update `backup.barmanObjectStore` with your minio parameters or your cloud solution. -: [`cluster-example-with-backup.yaml`](../samples/cluster-example-with-backup.yaml) - A basic cluster with backups configured. - -**Simple cluster with backup configured for Scaleway Object Storage** -: *Prerequisites*: The configuration assumes a Scaleway Object Storage bucket exists. - Update `backup.barmanObjectStore` with your Scaleway parameters. -: [`cluster-example-with-backup-scaleway.yaml`](../samples/cluster-example-with-backup-scaleway.yaml) - A basic cluster with backups configured to work with Scaleway Object Storage.. - -## Replica clusters - -**Replica cluster by way of backup from an object store** -: *Prerequisites*: - [`cluster-storage-class-with-backup.yaml`](../samples/cluster-storage-class-with-backup.yaml) - applied and healthy, and a backup - [`cluster-example-trigger-backup.yaml`](../samples/cluster-example-trigger-backup.yaml) - applied and completed. -: [`cluster-example-replica-from-backup-simple.yaml`](../samples/cluster-example-replica-from-backup-simple.yaml): - A replica cluster following a cluster with backup configured. - -**Replica cluster by way of volume snapshot** -: *Prerequisites*: - [`cluster-example-with-volume-snapshot.yaml`](../samples/cluster-example-with-volume-snapshot.yaml) - applied and healthy, and a volume snapshot - [`backup-with-volume-snapshot.yaml`](../samples/backup-with-volume-snapshot.yaml) - applied and completed. -: [`cluster-example-replica-from-volume-snapshot.yaml`](../samples/cluster-example-replica-from-volume-snapshot.yaml): - A replica cluster following a cluster with volume snapshot configured. - -**Replica cluster by way of streaming (pg_basebackup)** -: *Prerequisites*: [`cluster-example.yaml`](../samples/cluster-example.yaml) - applied and healthy. -: [`cluster-example-replica-streaming.yaml`](../samples/cluster-example-replica-streaming.yaml): - A replica cluster following `cluster-example` with streaming replication. - -## PostGIS - -**PostGIS example with image volume extensions** -: [`postgis-example.yaml`](../samples/postgis-example.yaml): - An example of a PostGIS cluster using image volume extensions. See [PostGIS](postgis.md) for details. - -## Managed roles - -**Cluster with declarative role management** -: [`cluster-example-with-roles.yaml`](../samples/cluster-example-with-roles.yaml): - Declares a role with the `managed` stanza. Includes password management with - Kubernetes secrets. - -**Declarative role management with the `DatabaseRole` resource** -: [`role-examples.yaml`](../samples/role-examples.yaml): - Standalone `DatabaseRole` resources targeting an existing cluster, including - password management with a Kubernetes secret. - -## Managed services - -**Cluster with managed services** -: [`cluster-example-managed-services.yaml`](../samples/cluster-example-managed-services.yaml): - Declares a service with the `managed` stanza. Includes default service disabled and new - `rw` service template of `LoadBalancer` type defined. - -## Declarative tablespaces - -**Cluster with declarative tablespaces** -: [`cluster-example-with-tablespaces.yaml`](../samples/cluster-example-with-tablespaces.yaml) - -**Cluster with declarative tablespaces and backup** -: *Prerequisites*: The configuration assumes minio is running and working. - Update `backup.barmanObjectStore` with your minio parameters or your cloud solution. -: [`cluster-example-with-tablespaces-backup.yaml`](../samples/cluster-example-with-tablespaces-backup.yaml) - -**Restored cluster with tablespaces from object store** -: *Prerequisites*: The previous cluster applied and a base backup completed. - Remember to update `bootstrap.recovery.backup.name` with the backup name. -: [`cluster-restore-with-tablespaces.yaml`](../samples/cluster-restore-with-tablespaces.yaml) - -For a list of available options, see [API reference](pg4k.v1.md). - -## Pooler configuration - -**Pooler with custom service config** -: [`pooler-external.yaml`](../samples/pooler-external.yaml) - -## Logical replication via declarative Publication and Subscription objects - -Two test manifests contain everything needed to set up logical replication: - -**Source cluster with a publication** -: [`cluster-example-logical-source.yaml`](../samples/cluster-example-logical-source.yaml) - -Sets up a cluster, `cluster-example` with some tables created in the `app` -database, and, importantly, *adds replication to the app user*. -A publication is created for the cluster on the `app` database: note that the -publication will be reconciled only after the cluster's primary is up and -running. - -**Destination cluster with a subscription** -: *Prerequisites*: The source cluster with publication, defined as above. -: [`cluster-example-logical-destination.yaml`](../samples/cluster-example-logical-destination.yaml) - -Sets up a cluster `cluster-example-dest` with: - -- the source cluster defined in the `externalClusters` stanza. Note that it uses - the `app` role to connect, which assumes the source cluster grants it - `replication` privilege. -- a bootstrap import of microservice type, with `schemaOnly` enabled - -A subscription is created on the destination cluster: note that the subscription -will be reconciled only after the destination cluster's primary is up and -running. - -After both clusters have been reconciled, together with the publication and -subscription objects, you can verify that that tables in the source cluster, -and the data in them, have been replicated in the destination cluster - -In addition, there are some standalone example manifests: - -**A plain Publication targeting All Tables** -: *Prerequisites*: an existing cluster `cluster-example`. -: [`publication-example.yaml`](../samples/publication-example.yaml) - -**A Publication with a constrained publication target** -: *Prerequisites*: an existing cluster `cluster-example`. -: [`publication-example-objects.yaml`](../samples/publication-example-objects.yaml) - -**A plain Subscription** -: Prerequisites: an existing cluster `cluster-example` set up as source, with - a publication `pub-all`. A cluster `cluster-example-dest` set up as a - destination cluster, including the `externalClusters` stanza with - connection parameters to the source cluster, including a role with - replication privilege. -: [`subscription-example.yaml`](../samples/subscription-example.yaml) - -All the above manifests create publications or subscriptions on the `app` -database. The Database CRD offers a convenient way to create databases -declaratively. With it, logical replication could be set up for arbitrary -databases. -Which brings us to the next section. - -## Declarative management of Postgres databases - -**A plain Database** -: *Prerequisites*: an existing cluster `cluster-example`. -: [`database-example.yaml`](../samples/database-example.yaml) - -**A Database with ICU local specifications** -: *Prerequisites*: an existing cluster `cluster-example` running Postgres 16 - or more advanced. -: [`database-example-icu.yaml`](../samples/database-example-icu.yaml) diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/backup-example.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/backup-example.yaml deleted file mode 100644 index ff8d9e5357d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/backup-example.yaml +++ /dev/null @@ -1,7 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Backup -metadata: - name: pg-backup-example -spec: - cluster: - name: pg-backup diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/backup-with-volume-snapshot.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/backup-with-volume-snapshot.yaml deleted file mode 100644 index 371c8f0beba..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/backup-with-volume-snapshot.yaml +++ /dev/null @@ -1,8 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Backup -metadata: - name: backup-with-volume-snapshot -spec: - method: volumeSnapshot - cluster: - name: cluster-example-with-volume-snapshot diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-additional-volumes.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-additional-volumes.yaml deleted file mode 100644 index 61e25e7076a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-additional-volumes.yaml +++ /dev/null @@ -1,25 +0,0 @@ -apiVersion: v1 -kind: PersistentVolumeClaim -metadata: - name: additional-pvc -spec: - accessModes: - - ReadWriteOnce - resources: - requests: - storage: 1Gi - volumeMode: Filesystem ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example - annotations: - k8s.enterprisedb.io/additionalVolumes: | - - claimName: additional-pvc - readOnly: true - mountPath: /additional -spec: - instances: 1 - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-advanced-initdb.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-advanced-initdb.yaml deleted file mode 100644 index a660108a0ba..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-advanced-initdb.yaml +++ /dev/null @@ -1,25 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-advanced-initdb -spec: - instances: 3 - - bootstrap: - initdb: - database: appdb - owner: appuser - postInitSQL: - - create table numbers (i integer) - - insert into numbers (select generate_series(1,10000)) - postInitTemplateSQL: - - create extension intarray - postInitApplicationSQL: - - create table application_numbers (i integer) - - insert into application_numbers (select generate_series(1,10000)) - dataChecksums: true - encoding: 'UTF8' - localeCollate: 'en_AU.UTF-8' - localeCType: 'en_AU.UTF-8' - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-aws-inherit.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-aws-inherit.yaml deleted file mode 100644 index e807fb0a28a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-aws-inherit.yaml +++ /dev/null @@ -1,15 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: pg-backup-aws-inherit -spec: - instances: 3 - storage: - storageClass: standard - size: 1Gi - backup: - barmanObjectStore: - destinationPath: s3://BUCKET_NAME/path/to/folder - s3Credentials: - inheritFromIAMRole: true - retentionPolicy: "30d" diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-azure-inherit.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-azure-inherit.yaml deleted file mode 100644 index 2d311da1e9f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-azure-inherit.yaml +++ /dev/null @@ -1,15 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: pg-backup-azure-inherit -spec: - instances: 3 - storage: - storageClass: standard - size: 1Gi - backup: - barmanObjectStore: - destinationPath: https://AZURE_STORAGE_ACCOUNT.blob.core.windows.net/pg-backup-azure-inherit/ - azureCredentials: - inheritFromAzureAD: true - retentionPolicy: "30d" diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-retention-30d.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-retention-30d.yaml deleted file mode 100644 index ff87944bf3b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-backup-retention-30d.yaml +++ /dev/null @@ -1,32 +0,0 @@ ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: pg-backup-retention-30d -spec: - instances: 3 - - # Example of rolling update strategy: - # - unsupervised: automated update of the primary once all - # replicas have been upgraded (default) - # - supervised: requires manual supervision to perform - # the switchover of the primary - primaryUpdateStrategy: unsupervised - - # Persistent storage configuration - storage: - storageClass: standard - size: 1Gi - - # Backup properties - backup: - barmanObjectStore: - destinationPath: s3://BUCKET_NAME/path/to/folder - s3Credentials: - accessKeyId: - name: aws-creds - key: ACCESS_KEY_ID - secretAccessKey: - name: aws-creds - key: ACCESS_SECRET_KEY - retentionPolicy: "30d" diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-clone-basicauth.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-clone-basicauth.yaml deleted file mode 100644 index dd0734eeadc..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-clone-basicauth.yaml +++ /dev/null @@ -1,29 +0,0 @@ -# IMPORTANT: this configuration requires an appropriate line -# in the host-based access rules allowing replication connections -# to the postgres user. -# -# The following line met the requisites -# - "host replication postgres all md5" -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-clone-basicauth -spec: - instances: 3 - - bootstrap: - pg_basebackup: - source: cluster-example - - storage: - size: 1Gi - - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: postgres - dbname: postgres - password: - name: cluster-example-superuser - key: password \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-clone-tls.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-clone-tls.yaml deleted file mode 100644 index c8c19a26c32..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-clone-tls.yaml +++ /dev/null @@ -1,30 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-clone-tls -spec: - instances: 3 - - bootstrap: - pg_basebackup: - source: cluster-example - - storage: - size: 1Gi - - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: streaming_replica - sslmode: verify-full - dbname: postgres - sslKey: - name: cluster-example-replication - key: tls.key - sslCert: - name: cluster-example-replication - key: tls.crt - sslRootCert: - name: cluster-example-ca - key: ca.crt diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis-restore-cr.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis-restore-cr.yaml deleted file mode 100644 index 3d033ade9dd..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis-restore-cr.yaml +++ /dev/null @@ -1,26 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - instances: 3 - - storage: - size: 1Gi - storageClass: csi-hostpath-sc - walStorage: - size: 1Gi - storageClass: csi-hostpath-sc - - bootstrap: - recovery: - volumeSnapshots: - storage: - name: cluster-example-20231031161103 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - walStorage: - name: cluster-example-20231031161103-wal - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis-restore.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis-restore.yaml deleted file mode 100644 index a9f14f917d1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis-restore.yaml +++ /dev/null @@ -1,43 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - instances: 3 - imageName: registry.dev:5000/postgresql:16 - - storage: - size: 1Gi - storageClass: csi-hostpath-sc - walStorage: - size: 1Gi - storageClass: csi-hostpath-sc - - # Backup properties - # This assumes a local minio setup -# backup: -# barmanObjectStore: -# destinationPath: s3://backups/ -# endpointURL: http://minio:9000 -# s3Credentials: -# accessKeyId: -# name: minio -# key: ACCESS_KEY_ID -# secretAccessKey: -# name: minio -# key: ACCESS_SECRET_KEY -# wal: -# compression: gzip - - bootstrap: - recovery: - volumeSnapshots: - storage: - name: snapshot-0bc6095db42768c7a1fe897494a966f541ef5fb29b2eb8e9399d80bd0a32408a-2023-11-13-7.41.53 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - walStorage: - name: snapshot-a67084ba08097fd8c3e34c6afef8110091da67e5895f0379fd2df5b9f73ff524-2023-11-13-7.41.53 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis.yaml deleted file mode 100644 index 0a5ae32f7d9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-bis.yaml +++ /dev/null @@ -1,29 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - imageName: registry.dev:5000/postgresql:16 - - backup: - volumeSnapshot: - className: csi-hostpath-groupsnapclass - #className: csi-hostpath-snapclass - groupSnapshot: true - - storage: - storageClass: csi-hostpath-sc - size: 1Gi - walStorage: - storageClass: csi-hostpath-sc - size: 1Gi - # tablespaces: - # first: - # storage: - # storageClass: csi-hostpath-sc - # size: 1Gi - # second: - # storage: - # storageClass: csi-hostpath-sc - # size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-catalog.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-catalog.yaml deleted file mode 100644 index 8cd9076b3b8..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-catalog.yaml +++ /dev/null @@ -1,28 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ImageCatalog -metadata: - name: image-catalog-example -spec: - images: - - image: docker.enterprisedb.com/k8s/postgresql:18-standard-ubi9 - major: 18 - - image: docker.enterprisedb.com/k8s/postgresql:17-standard-ubi9 - major: 17 - - image: docker.enterprisedb.com/k8s/postgresql:16-standard-ubi9 - major: 16 - - image: docker.enterprisedb.com/k8s/postgresql:15-standard-ubi9 - major: 15 ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - imageCatalogRef: - apiGroup: postgresql.k8s.enterprisedb.io - kind: ImageCatalog - name: image-catalog-example - major: 15 - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-cert-manager.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-cert-manager.yaml deleted file mode 100644 index 7d9d11a7b46..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-cert-manager.yaml +++ /dev/null @@ -1,120 +0,0 @@ -apiVersion: cert-manager.io/v1 -kind: Issuer -metadata: - name: selfsigned-issuer -spec: - selfSigned: {} ---- -apiVersion: cert-manager.io/v1 -kind: Certificate -metadata: - name: server-ca -spec: - isCA: true - commonName: my-selfsigned-server-ca - secretName: server-ca-key-pair - privateKey: - algorithm: ECDSA - size: 256 - issuerRef: - name: selfsigned-issuer - kind: Issuer - group: cert-manager.io ---- -apiVersion: cert-manager.io/v1 -kind: Issuer -metadata: - name: server-ca-issuer -spec: - ca: - secretName: server-ca-key-pair ---- -apiVersion: v1 -kind: Secret -metadata: - name: my-postgres-server-cert - labels: - k8s.enterprisedb.io/reload: "" ---- -apiVersion: cert-manager.io/v1 -kind: Certificate -metadata: - name: my-postgres-server-cert -spec: - secretName: my-postgres-server-cert - usages: - - server auth - dnsNames: - - cluster-example-lb.internal.mydomain.net - - cluster-example-rw - - cluster-example-rw.default - - cluster-example-rw.default.svc - - cluster-example-r - - cluster-example-r.default - - cluster-example-r.default.svc - - cluster-example-ro - - cluster-example-ro.default - - cluster-example-ro.default.svc - issuerRef: - name: server-ca-issuer - kind: Issuer - group: cert-manager.io ---- -apiVersion: cert-manager.io/v1 -kind: Certificate -metadata: - name: client-ca -spec: - isCA: true - commonName: my-selfsigned-client-ca - secretName: client-ca-key-pair - privateKey: - algorithm: ECDSA - size: 256 - issuerRef: - name: selfsigned-issuer - kind: Issuer - group: cert-manager.io ---- -apiVersion: cert-manager.io/v1 -kind: Issuer -metadata: - name: client-ca-issuer -spec: - ca: - secretName: client-ca-key-pair ---- -apiVersion: v1 -kind: Secret -metadata: - name: my-postgres-client-cert - labels: - k8s.enterprisedb.io/reload: "" ---- -apiVersion: cert-manager.io/v1 -kind: Certificate -metadata: - name: my-postgres-client-cert -spec: - secretName: my-postgres-client-cert - usages: - - client auth - commonName: streaming_replica - issuerRef: - name: client-ca-issuer - kind: Issuer - group: cert-manager.io ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - certificates: - serverTLSSecret: my-postgres-server-cert - serverCASecret: my-postgres-server-cert - clientCASecret: my-postgres-client-cert - replicationTLSSecret: my-postgres-client-cert - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-custom.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-custom.yaml deleted file mode 100644 index 49223affa68..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-custom.yaml +++ /dev/null @@ -1,28 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-custom -spec: - instances: 3 - - # Parameters and pg_hba configuration will be append - # to the default ones to make the cluster work - postgresql: - parameters: - max_worker_processes: "60" - pg_hba: - # To access through TCP/IP you will need to get username - # and password from the secret cluster-example-custom-app - - host all all all md5 - - - # Example of rolling update strategy: - # - unsupervised: automated update of the primary once all - # replicas have been upgraded (default) - # - supervised: requires manual supervision to perform - # the switchover of the primary - primaryUpdateStrategy: unsupervised - - # Require 1Gi of space per instance using default storage class - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-epas.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-epas.yaml deleted file mode 100644 index 322a010e9b9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-epas.yaml +++ /dev/null @@ -1,10 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-advanced-cluster -spec: - instances: 3 - imageName: docker.enterprisedb.com/k8s/edb-postgres-advanced:18-standard-ubi9 - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-external-backup-adapter-cluster.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-external-backup-adapter-cluster.yaml deleted file mode 100644 index eb7fc22e932..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-external-backup-adapter-cluster.yaml +++ /dev/null @@ -1,35 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example - annotations: - "k8s.enterprisedb.io/addons": '["external-backup-adapter-cluster"]' - "k8s.enterprisedb.io/externalBackupAdapterClusterConfig": |- - electedResourcesDecorators: - - key: "test/edb-elected" - metadataType: "label" - value: "true" - excludedResourcesDecorators: - - key: "test/ignore" - metadataType: "label" - value: "true" - backupInstanceDecorators: - - key: "test/hooks" - metadataType: "label" - value: "true" - preBackupHookConfiguration: - container: - key: "test/pre-backup-container" - command: - key: "test/pre-backup-command" - onError: - key: "test/pre-backup-on-error" - postBackupHookConfiguration: - container: - key: "test/post-backup-container" - command: - key: "test/post-backup-command" -spec: - instances: 3 - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-external-backup-adapter.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-external-backup-adapter.yaml deleted file mode 100644 index b13c2bc3977..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-external-backup-adapter.yaml +++ /dev/null @@ -1,10 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example - annotations: - "k8s.enterprisedb.io/addons": '["external-backup-adapter"]' -spec: - instances: 3 - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-full.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-full.yaml deleted file mode 100644 index 60f5fbac53e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-full.yaml +++ /dev/null @@ -1,110 +0,0 @@ -# Example of definition of a test cluster using all the elements available -# in the CRD. Please change values appropriately for your environment. -# Remember that you can take advantage of convention over configuration -# and normally you don't need to use all these definitions. - -apiVersion: v1 -data: - password: VHhWZVE0bk44MlNTaVlIb3N3cU9VUlp2UURhTDRLcE5FbHNDRUVlOWJ3RHhNZDczS2NrSWVYelM1Y1U2TGlDMg== - username: YXBw -kind: Secret -metadata: - name: cluster-example-app-user -type: kubernetes.io/basic-auth ---- -apiVersion: v1 -data: - password: dU4zaTFIaDBiWWJDYzRUeVZBYWNCaG1TemdxdHpxeG1PVmpBbjBRSUNoc0pyU211OVBZMmZ3MnE4RUtLTHBaOQ== - username: cG9zdGdyZXM= -kind: Secret -metadata: - name: cluster-example-superuser -type: kubernetes.io/basic-auth ---- -apiVersion: v1 -kind: Secret -metadata: - name: backup-creds -data: - ACCESS_KEY_ID: a2V5X2lk - ACCESS_SECRET_KEY: c2VjcmV0X2tleQ== ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-full -spec: - description: "Example of cluster" - imageName: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 - # imagePullSecret is only required if the images are located in a private registry - # imagePullSecrets: - # - name: private_registry_access - instances: 3 - startDelay: 300 - stopDelay: 300 - primaryUpdateStrategy: unsupervised - - postgresql: - parameters: - shared_buffers: 256MB - pg_stat_statements.max: '10000' - pg_stat_statements.track: all - auto_explain.log_min_duration: '10s' - pg_hba: - - host all all 10.244.0.0/16 md5 - - bootstrap: - initdb: - database: app - owner: app - secret: - name: cluster-example-app-user - # Alternative bootstrap method: start from a backup - #recovery: - # backup: - # name: backup-example - - enableSuperuserAccess: true - superuserSecret: - name: cluster-example-superuser - - storage: - storageClass: standard - size: 1Gi - - backup: - barmanObjectStore: - destinationPath: s3://cluster-example-full-backup/ - endpointURL: http://custom-endpoint:1234 - s3Credentials: - accessKeyId: - name: backup-creds - key: ACCESS_KEY_ID - secretAccessKey: - name: backup-creds - key: ACCESS_SECRET_KEY - wal: - compression: gzip - encryption: AES256 - data: - compression: gzip - encryption: AES256 - immediateCheckpoint: false - jobs: 2 - retentionPolicy: "30d" - - resources: - requests: - memory: "512Mi" - cpu: "1" - limits: - memory: "1Gi" - cpu: "2" - - affinity: - enablePodAntiAffinity: true - topologyKey: failure-domain.beta.kubernetes.io/zone - - nodeMaintenanceWindow: - inProgress: false - reusePVC: false diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb-icu.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb-icu.yaml deleted file mode 100644 index 9db3edec3d5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb-icu.yaml +++ /dev/null @@ -1,19 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb-icu -spec: - instances: 3 - - bootstrap: - initdb: - encoding: UTF8 - localeCollate: en_US.UTF8 - localeCType: en_US.UTF8 - localeProvider: icu - icuLocale: en-US - # we want to order g and G after A (and before b) - icuRules: '&A < g <<< G' - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb-sql-refs.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb-sql-refs.yaml deleted file mode 100644 index b853658e570..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb-sql-refs.yaml +++ /dev/null @@ -1,47 +0,0 @@ -apiVersion: v1 -kind: ConfigMap -metadata: - name: post-init-sql-configmap -data: - configmap.sql: | - create table configmaps (i integer); - insert into configmaps (select generate_series(1,10000)); ---- -apiVersion: v1 -kind: Secret -metadata: - name: post-init-sql-secret -stringData: - secret.sql: | - create table secrets (i integer); - insert into secrets (select generate_series(1,10000)); ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb -spec: - instances: 3 - - bootstrap: - initdb: - database: appdb - owner: appuser - postInitSQL: - - create table numbers (i integer) - - insert into numbers (select generate_series(1,10000)) - postInitTemplateSQL: - - create extension intarray - postInitApplicationSQL: - - create table application_numbers (i integer) - - insert into application_numbers (select generate_series(1,10000)) - postInitApplicationSQLRefs: - configMapRefs: - - name: post-init-sql-configmap - key: configmap.sql - secretRefs: - - name: post-init-sql-secret - key: secret.sql - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb.yaml deleted file mode 100644 index 76c79bd4d4e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-initdb.yaml +++ /dev/null @@ -1,23 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-initdb -spec: - instances: 3 - - bootstrap: - initdb: - database: appdb - owner: appuser - postInitSQL: - - create table numbers (i integer) - - insert into numbers (select generate_series(1,10000)) - postInitTemplateSQL: - - create extension intarray - postInitApplicationSQL: - - create table application_numbers (i integer) - - insert into application_numbers (select generate_series(1,10000)) - dataChecksums: true - encoding: 'UTF8' - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-logical-destination.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-logical-destination.yaml deleted file mode 100644 index 86879d80e6a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-logical-destination.yaml +++ /dev/null @@ -1,43 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-dest -spec: - instances: 1 - - storage: - size: 1Gi - - bootstrap: - initdb: - import: - type: microservice - schemaOnly: true - databases: - - app - source: - externalCluster: cluster-example - - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: app - dbname: app - password: - name: cluster-example-app - key: password ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Subscription -metadata: - name: cluster-example-dest-sub -spec: - cluster: - name: cluster-example-dest - name: sub - dbname: app - publicationName: pub - externalClusterName: cluster-example - parameters: - failover: 'true' diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-logical-source.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-logical-source.yaml deleted file mode 100644 index 23180b33481..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-logical-source.yaml +++ /dev/null @@ -1,59 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: DatabaseRole -metadata: - name: cluster-example-app -spec: - cluster: - name: cluster-example - name: app - login: true - replication: true ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - - imageName: docker.enterprisedb.com/k8s/postgresql:18-standard-ubi9 - - storage: - size: 1Gi - - bootstrap: - initdb: - postInitApplicationSQL: - - CREATE TABLE numbers (i SERIAL PRIMARY KEY, m INTEGER) - - INSERT INTO numbers (m) (SELECT generate_series(1,10000)) - - ALTER TABLE numbers OWNER TO app - - CREATE TABLE numbers_two (i SERIAL PRIMARY KEY, m INTEGER) - - INSERT INTO numbers_two (m) (SELECT generate_series(1,10000)) - - ALTER TABLE numbers_two OWNER TO app - - CREATE SCHEMA another_schema - - ALTER SCHEMA another_schema OWNER TO app - - CREATE TABLE another_schema.numbers_three (i SERIAL PRIMARY KEY, m INTEGER) - - INSERT INTO another_schema.numbers_three (m) (SELECT generate_series(1,10000)) - - ALTER TABLE another_schema.numbers_three OWNER TO app - - replicationSlots: - highAvailability: - synchronizeLogicalDecoding: true - - postgresql: - parameters: - hot_standby_feedback: 'on' - sync_replication_slots: 'on' - ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Publication -metadata: - name: cluster-example-pub -spec: - name: pub - dbname: app - cluster: - name: cluster-example - target: - allTables: true diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-managed-services.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-managed-services.yaml deleted file mode 100644 index 087a5afd864..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-managed-services.yaml +++ /dev/null @@ -1,24 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-managed-services -spec: - instances: 1 - storage: - size: 1Gi - - managed: - services: - ## disable the default services - disabledDefaultServices: ["ro", "r"] - additional: - - selectorType: rw - serviceTemplate: - metadata: - name: "test-rw" - labels: - test-label: "true" - annotations: - test-annotation: "true" - spec: - type: LoadBalancer diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-monitoring.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-monitoring.yaml deleted file mode 100644 index 8941e5bad74..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-monitoring.yaml +++ /dev/null @@ -1,234 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - - storage: - size: 1Gi - - monitoring: - customQueriesConfigMap: - - name: example-monitoring - key: custom-queries - customQueriesSecret: - - name: example-monitoring-secret - key: pg-database ---- -apiVersion: monitoring.coreos.com/v1 -kind: PodMonitor -metadata: - name: cluster-example -spec: - selector: - matchLabels: - k8s.enterprisedb.io/cluster: cluster-example - podMetricsEndpoints: - - port: metrics ---- -apiVersion: v1 -kind: ConfigMap -metadata: - name: example-monitoring - labels: - k8s.enterprisedb.io/reload: "" -data: - custom-queries: | - pg_stat_user_tables: - target_databases: - - "*" - query: | - SELECT - pg_catalog.current_database() datname, - schemaname, - relname, - seq_scan, - seq_tup_read, - idx_scan, - idx_tup_fetch, - n_tup_ins, - n_tup_upd, - n_tup_del, - n_tup_hot_upd, - n_live_tup, - n_dead_tup, - n_mod_since_analyze, - COALESCE(last_vacuum, '1970-01-01Z') as last_vacuum, - COALESCE(last_autovacuum, '1970-01-01Z') as last_autovacuum, - COALESCE(last_analyze, '1970-01-01Z') as last_analyze, - COALESCE(last_autoanalyze, '1970-01-01Z') as last_autoanalyze, - vacuum_count, - autovacuum_count, - analyze_count, - autoanalyze_count - FROM - pg_catalog.pg_stat_user_tables - metrics: - - datname: - usage: "LABEL" - description: "Name of current database" - - schemaname: - usage: "LABEL" - description: "Name of the schema that this table is in" - - relname: - usage: "LABEL" - description: "Name of this table" - - seq_scan: - usage: "COUNTER" - description: "Number of sequential scans initiated on this table" - - seq_tup_read: - usage: "COUNTER" - description: "Number of live rows fetched by sequential scans" - - idx_scan: - usage: "COUNTER" - description: "Number of index scans initiated on this table" - - idx_tup_fetch: - usage: "COUNTER" - description: "Number of live rows fetched by index scans" - - n_tup_ins: - usage: "COUNTER" - description: "Number of rows inserted" - - n_tup_upd: - usage: "COUNTER" - description: "Number of rows updated" - - n_tup_del: - usage: "COUNTER" - description: "Number of rows deleted" - - n_tup_hot_upd: - usage: "COUNTER" - description: "Number of rows HOT updated (i.e., with no separate index update required)" - - n_live_tup: - usage: "GAUGE" - description: "Estimated number of live rows" - - n_dead_tup: - usage: "GAUGE" - description: "Estimated number of dead rows" - - n_mod_since_analyze: - usage: "GAUGE" - description: "Estimated number of rows changed since last analyze" - - last_vacuum: - usage: "GAUGE" - description: "Last time at which this table was manually vacuumed (not counting VACUUM FULL)" - - last_autovacuum: - usage: "GAUGE" - description: "Last time at which this table was vacuumed by the autovacuum daemon" - - last_analyze: - usage: "GAUGE" - description: "Last time at which this table was manually analyzed" - - last_autoanalyze: - usage: "GAUGE" - description: "Last time at which this table was analyzed by the autovacuum daemon" - - vacuum_count: - usage: "COUNTER" - description: "Number of times this table has been manually vacuumed (not counting VACUUM FULL)" - - autovacuum_count: - usage: "COUNTER" - description: "Number of times this table has been vacuumed by the autovacuum daemon" - - analyze_count: - usage: "COUNTER" - description: "Number of times this table has been manually analyzed" - - autoanalyze_count: - usage: "COUNTER" - description: "Number of times this table has been analyzed by the autovacuum daemon" - - pg_statio_user_tables: - query: "SELECT pg_catalog.current_database() datname, schemaname, relname, heap_blks_read, heap_blks_hit, idx_blks_read, idx_blks_hit, toast_blks_read, toast_blks_hit, tidx_blks_read, tidx_blks_hit FROM pg_catalog.pg_statio_user_tables" - metrics: - - datname: - usage: "LABEL" - description: "Name of current database" - - schemaname: - usage: "LABEL" - description: "Name of the schema that this table is in" - - relname: - usage: "LABEL" - description: "Name of this table" - - heap_blks_read: - usage: "COUNTER" - description: "Number of disk blocks read from this table" - - heap_blks_hit: - usage: "COUNTER" - description: "Number of buffer hits in this table" - - idx_blks_read: - usage: "COUNTER" - description: "Number of disk blocks read from all indexes on this table" - - idx_blks_hit: - usage: "COUNTER" - description: "Number of buffer hits in all indexes on this table" - - toast_blks_read: - usage: "COUNTER" - description: "Number of disk blocks read from this table's TOAST table (if any)" - - toast_blks_hit: - usage: "COUNTER" - description: "Number of buffer hits in this table's TOAST table (if any)" - - tidx_blks_read: - usage: "COUNTER" - description: "Number of disk blocks read from this table's TOAST table indexes (if any)" - - tidx_blks_hit: - usage: "COUNTER" - description: "Number of buffer hits in this table's TOAST table indexes (if any)" - - pg_stat_activity: - query: | - WITH - metrics AS ( - SELECT - application_name, - SUM(EXTRACT(EPOCH FROM (CURRENT_TIMESTAMP - state_change))::bigint)::float AS process_idle_seconds_sum, - COUNT(*) AS process_idle_seconds_count - FROM pg_catalog.pg_stat_activity - WHERE state = 'idle' - GROUP BY application_name - ), - buckets AS ( - SELECT - application_name, - le, - SUM( - CASE WHEN EXTRACT(EPOCH FROM (CURRENT_TIMESTAMP - state_change)) <= le - THEN 1 - ELSE 0 - END - )::bigint AS bucket - FROM - pg_catalog.pg_stat_activity, - UNNEST(ARRAY[1, 2, 5, 15, 30, 60, 90, 120, 300]) AS le - GROUP BY application_name, le - ORDER BY application_name, le - ) - SELECT - application_name, - process_idle_seconds_sum, - process_idle_seconds_count, - ARRAY_AGG(le) AS process_idle_seconds, - ARRAY_AGG(bucket) AS process_idle_seconds_bucket - FROM metrics JOIN buckets USING (application_name) - GROUP BY 1, 2, 3 - metrics: - - application_name: - usage: "LABEL" - description: "Application Name" - - process_idle_seconds: - usage: "HISTOGRAM" - description: "Idle time of server processes" ---- -apiVersion: v1 -kind: Secret -metadata: - name: example-monitoring-secret - labels: - k8s.enterprisedb.io/reload: "" -stringData: - pg-database: | - pg_database: - query: "SELECT pg_database.datname, pg_catalog.pg_database_size(pg_database.datname) as size_bytes FROM pg_catalog.pg_database" - primary: true - cache_seconds: 30 - metrics: - - datname: - usage: "LABEL" - description: "Name of the database" - - size_bytes: - usage: "GAUGE" - description: "Disk space used by the database" diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pg-hba.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pg-hba.yaml deleted file mode 100644 index 253f5bdfc41..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pg-hba.yaml +++ /dev/null @@ -1,12 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - postgresql: - pg_hba: - - hostssl app all all cert - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pge.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pge.yaml deleted file mode 100644 index 5785cc754d9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pge.yaml +++ /dev/null @@ -1,10 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-extended-cluster -spec: - instances: 3 - imageName: docker.enterprisedb.com/k8s/edb-postgres-extended:18-standard-ubi9 - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pod-selector-refs.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pod-selector-refs.yaml deleted file mode 100644 index b9ab3ccb30a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-pod-selector-refs.yaml +++ /dev/null @@ -1,33 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-pod-selector-refs -spec: - instances: 3 - - # Define named pod label selectors for dynamic pg_hba address resolution. - # The operator resolves matching pod IPs and expands ${podselector:NAME} - # references in pg_hba rules into one line per IP with /32 (IPv4) or /128 (IPv6) masks. - podSelectorRefs: - - name: app-pods - selector: - matchLabels: - app: myapp - - name: monitoring - selector: - matchLabels: - role: monitoring - - postgresql: - pg_hba: - # These rules use ${podselector:NAME} syntax to reference podSelectorRefs. - # Each reference is expanded to one line per matching pod IP. - - "hostssl mydb myuser ${podselector:app-pods} scram-sha-256" - - "hostssl postgres monitor ${podselector:monitoring} scram-sha-256" - # Standard rules without expansion are passed through unchanged. - - host all all 10.244.0.0/16 md5 - - primaryUpdateStrategy: unsupervised - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-projected-volume.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-projected-volume.yaml deleted file mode 100644 index 0f0cbf1a07c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-projected-volume.yaml +++ /dev/null @@ -1,43 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-projected-volume -spec: - instances: 3 - projectedVolumeTemplate: - sources: - - secret: - name: sample-secret - items: - - key: tls.crt - path: certificate/tls.crt - - key: tls.key - path: certificate/tls.key - - configMap: - name: sample-configmap - items: - - key: key1 - path: config/key1 - - key: key2 - path: config/key2 - storage: - size: 1Gi - ---- -apiVersion: v1 -data: - tls.crt: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUNQekNDQWVXZ0F3SUJBZ0lRSHVDY2lKcDVkZis0dHZBcDBrTk9rekFLQmdncWhrak9QUVFEQWpCTk1TTXcKSVFZRFZRUUxFeHB3YjNOMFozSmxjM0ZzTFc5d1pYSmhkRzl5TFhONWMzUmxiVEVtTUNRR0ExVUVBeE1kY0c5egpkR2R5WlhOeGJDMXZjR1Z5WVhSdmNpMWpZUzF6WldOeVpYUXdIaGNOTWpJd09USTVNRGMxTVRBNVdoY05Nakl4Ck1qSTRNRGMxTVRBNVdqQk5NVXN3U1FZRFZRUURFMEp3YjNOMFozSmxjM0ZzTFc5d1pYSmhkRzl5TFhkbFltaHYKYjJzdGMyVnlkbWxqWlM1d2IzTjBaM0psYzNGc0xXOXdaWEpoZEc5eUxYTjVjM1JsYlM1emRtTXdXVEFUQmdjcQpoa2pPUFFJQkJnZ3Foa2pPUFFNQkJ3TkNBQVJRd2lhUm0wSmN4TzlBVlE0MVlqVlRqNUhDSVVFblFQOXNZRXFKCmYvNE1mVm53NkdDOThjNDNmQTVuS2UwSnQ5ZEV3QXREYktkdkRoeDlUTmIzdVY0K280R21NSUdqTUE0R0ExVWQKRHdFQi93UUVBd0lEcURBVEJnTlZIU1VFRERBS0JnZ3JCZ0VGQlFjREFUQU1CZ05WSFJNQkFmOEVBakFBTUI4RwpBMVVkSXdRWU1CYUFGQjN6cUVKbWFORENoRDdkWGptSWRlNEhUY0pFTUUwR0ExVWRFUVJHTUVTQ1FuQnZjM1JuCmNtVnpjV3d0YjNCbGNtRjBiM0l0ZDJWaWFHOXZheTF6WlhKMmFXTmxMbkJ2YzNSbmNtVnpjV3d0YjNCbGNtRjAKYjNJdGMzbHpkR1Z0TG5OMll6QUtCZ2dxaGtqT1BRUURBZ05JQURCRkFpQkMwS2M5WWxYelBpL0lhTkRnWHkwawpYTDJpNlZzSHRORTFxN3MzWXh6Mm53SWhBS2IxUW5EVTlqRnNVK0l5a292TitVU1ZpVm5vU2MvZ2RXWkxmMnhoCjZ2WUsKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo= - tls.key: LS0tLS1CRUdJTiBFQyBQUklWQVRFIEtFWS0tLS0tCk1IY0NBUUVFSUtucWxVQjFqU2sxWW5VZzAyb0tGbXlRdDJLUEZwaFc0K1lmQUFmUFdRenVvQW9HQ0NxR1NNNDkKQXdFSG9VUURRZ0FFVU1JbWtadENYTVR2UUZVT05XSTFVNCtSd2lGQkowRC9iR0JLaVgvK0RIMVo4T2hndmZITwpOM3dPWnludENiZlhSTUFMUTJ5bmJ3NGNmVXpXOTdsZVBnPT0KLS0tLS1FTkQgRUMgUFJJVkFURSBLRVktLS0tLQo= -kind: Secret -metadata: - name: sample-secret -type: kubernetes.io/tls ---- -apiVersion: v1 -data: - key1: value1 - key2: value2 - key3: value3 -kind: ConfigMap -metadata: - name: sample-configmap diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-from-backup-simple.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-from-backup-simple.yaml deleted file mode 100644 index 1baebfbde61..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-from-backup-simple.yaml +++ /dev/null @@ -1,30 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-replica-from-backup-simple -spec: - instances: 1 - - bootstrap: - recovery: - source: cluster-example-backup - - replica: - enabled: true - source: cluster-example-backup - - storage: - size: 1Gi - - externalClusters: - - name: cluster-example-backup - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-from-volume-snapshot.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-from-volume-snapshot.yaml deleted file mode 100644 index ca3bc3dc2eb..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-from-volume-snapshot.yaml +++ /dev/null @@ -1,54 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-replica-from-snapshot -spec: - instances: 1 - - storage: - storageClass: csi-hostpath-sc - size: 1Gi - walStorage: - storageClass: csi-hostpath-sc - size: 1Gi - - bootstrap: - recovery: - source: cluster-example-with-volume-snapshot - volumeSnapshots: - storage: - name: cluster-example-with-volume-snapshot-2-1692618163 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - walStorage: - name: cluster-example-with-volume-snapshot-2-wal-1692618163 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - - replica: - enabled: true - source: cluster-example-with-volume-snapshot - - externalClusters: - - name: cluster-example-with-volume-snapshot - - connectionParameters: - host: cluster-example-with-volume-snapshot-rw.default.svc - user: postgres - dbname: postgres - password: - name: cluster-example-with-volume-snapshot-superuser - key: password - - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - maxParallel: 8 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-streaming.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-streaming.yaml deleted file mode 100644 index 63eba35085d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-replica-streaming.yaml +++ /dev/null @@ -1,38 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-replica-example -spec: - instances: 1 - - bootstrap: - pg_basebackup: - source: cluster-example - - replica: - enabled: true - source: cluster-example - - storage: - size: 1Gi - # note the namespace 'default' in the host name `cluster-example-rw.default.svc` - # remember to change accordingly with the namespace of the main cluster - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: streaming_replica - sslmode: verify-full - dbname: postgres - # NOTE: if this cluster is created in a different namespace than the main cluster - # remember to create the `-replication` and `-ca` secrets in the follower namespace - # before creating the follower cluster - sslKey: - name: cluster-example-replication - key: tls.key - sslCert: - name: cluster-example-replication - key: tls.crt - sslRootCert: - name: cluster-example-ca - key: ca.crt diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-secret.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-secret.yaml deleted file mode 100644 index 998c378e42c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-secret.yaml +++ /dev/null @@ -1,38 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-secret -spec: - instances: 3 - - bootstrap: - initdb: - database: app - owner: app - secret: - name: cluster-example-app-user - - enableSuperuserAccess: true - superuserSecret: - name: cluster-example-superuser - - storage: - size: 1Gi ---- -apiVersion: v1 -data: - username: YXBw - password: cGFzc3dvcmQ= -kind: Secret -metadata: - name: cluster-example-app-user -type: kubernetes.io/basic-auth ---- -apiVersion: v1 -data: - username: cG9zdGdyZXM= - password: cGFzc3dvcmQ= -kind: Secret -metadata: - name: cluster-example-superuser -type: kubernetes.io/basic-auth diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-security-context.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-security-context.yaml deleted file mode 100644 index 85e17fba6fe..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-security-context.yaml +++ /dev/null @@ -1,44 +0,0 @@ -# Example of PostgreSQL cluster with custom security contexts -# -# This example demonstrates how to customize both PodSecurityContext and -# Container SecurityContext for a PostgreSQL cluster. This is particularly -# useful when working with Pod Security Standards (PSS) or when you need -# to meet specific security requirements. -# -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-security-context -spec: - instances: 3 - - # Storage configuration - storage: - size: 1Gi - - # Custom PodSecurityContext - # This will be applied to all pods in the cluster and merged with operator defaults. - # Only RunAsUser, RunAsGroup, and SeccompProfile are merged from defaults if not specified. - podSecurityContext: - runAsUser: 26 - runAsGroup: 26 - fsGroup: 26 - runAsNonRoot: true - supplementalGroups: [1000, 2000] - fsGroupChangePolicy: "OnRootMismatch" - - # Custom Container SecurityContext - # This will be applied to all containers in the cluster pods and merged with operator defaults. - # The operator provides secure defaults for all fields, which will be used if not explicitly set. - securityContext: - allowPrivilegeEscalation: false - # Note: capabilities are not merged with operator defaults. - # If specified, they fully replace any defaults. - capabilities: - drop: - - ALL - add: - - NET_BIND_SERVICE - privileged: false - readOnlyRootFilesystem: true - runAsNonRoot: true diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-sync-az.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-sync-az.yaml deleted file mode 100644 index 1d3bd41758d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-sync-az.yaml +++ /dev/null @@ -1,14 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-az -spec: - instances: 3 - minSyncReplicas: 1 - maxSyncReplicas: 1 - postgresql: - syncReplicaElectionConstraint: - enabled: true - nodeLabelsAntiAffinity: [ "az" ] - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-explicit.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-explicit.yaml deleted file mode 100644 index 43681203a5b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-explicit.yaml +++ /dev/null @@ -1,14 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-syncreplicas -spec: - instances: 5 - - postgresql: - synchronous: - method: first - number: 2 - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-legacy.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-legacy.yaml deleted file mode 100644 index b8a883de4a3..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-legacy.yaml +++ /dev/null @@ -1,12 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-syncreplicas -spec: - instances: 5 - - minSyncReplicas: 1 - maxSyncReplicas: 3 - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-quorum.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-quorum.yaml deleted file mode 100644 index 8f1fbef3c42..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-syncreplicas-quorum.yaml +++ /dev/null @@ -1,15 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - - postgresql: - synchronous: - method: any - number: 1 - failoverQuorum: true - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-tde.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-tde.yaml deleted file mode 100644 index 3b6f5f705aa..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-tde.yaml +++ /dev/null @@ -1,26 +0,0 @@ ---- -apiVersion: v1 -kind: Secret -metadata: - name: tde-key -data: - key: bG9zcG9sbGl0b3NkaWNlbnBpb3Bpb3Bpb2N1YW5kb3RpZW5lbmhhbWJyZWN1YW5kb3RpZW5lbmZyaW8= - ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - imageName: docker.enterprisedb.com/k8s/edb-postgres-advanced:18-standard-ubi9 - postgresql: - epas: - tde: - enabled: true - secretKeyRef: - name: tde-key - key: key - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-trigger-backup.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-trigger-backup.yaml deleted file mode 100644 index 5409d234741..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-trigger-backup.yaml +++ /dev/null @@ -1,7 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Backup -metadata: - name: cluster-example-trigger-backup -spec: - cluster: - name: cluster-example-with-backup diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-wal-storage.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-wal-storage.yaml deleted file mode 100644 index eb08e8fa6e2..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-wal-storage.yaml +++ /dev/null @@ -1,10 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - storage: - size: 1Gi - walStorage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-backup-scaleway.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-backup-scaleway.yaml deleted file mode 100644 index b42041ee9c7..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-backup-scaleway.yaml +++ /dev/null @@ -1,23 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: pg-backup-scaleway -spec: - instances: 3 - storage: - storageClass: standard - size: 1Gi - backup: - barmanObjectStore: - destinationPath: "s3:///backups/" # change with your bucket's name. - endpointURL: "https://s3..scw.cloud" # change with your bucket's location/region. - s3Credentials: - accessKeyId: - name: scaleway - key: ACCESS_KEY_ID - secretAccessKey: - name: scaleway - key: ACCESS_SECRET_KEY - region: - name: scaleway - key: ACCESS_REGION diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-backup.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-backup.yaml deleted file mode 100644 index 97c829662c9..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-backup.yaml +++ /dev/null @@ -1,33 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-with-backup -spec: - instances: 3 - primaryUpdateStrategy: unsupervised - - # Persistent storage configuration - storage: - storageClass: csi-hostpath-sc - size: 1Gi - - # Backup properties - # This assumes a local minio setup - backup: - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip - data: - additionalCommandArgs: - - "--min-chunk-size=5MB" - - "--read-timeout=60" - - "-vv" diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-probes.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-probes.yaml deleted file mode 100644 index 450fab88a4c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-probes.yaml +++ /dev/null @@ -1,16 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - - probes: - startup: - type: streaming - maximumLag: 16Mi - failureThreshold: 30 - periodSeconds: 10 - - storage: - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-roles.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-roles.yaml deleted file mode 100644 index b98d18622cd..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-roles.yaml +++ /dev/null @@ -1,40 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-with-roles -spec: - instances: 3 - storage: - size: 1Gi - - managed: - roles: - - name: app - createdb: true - login: true - - name: dante - ensure: present - comment: my database-side comment - login: true - superuser: false - createdb: true - createrole: false - inherit: false - replication: false - bypassrls: false - connectionLimit: 4 - validUntil: "2053-04-12T15:04:05Z" - inRoles: - - pg_monitor - - pg_signal_backend - passwordSecret: - name: cluster-example-dante ---- -apiVersion: v1 -data: - username: ZGFudGU= - password: ZGFudGU= -kind: Secret -metadata: - name: cluster-example-dante -type: kubernetes.io/basic-auth diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-tablespaces-backup.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-tablespaces-backup.yaml deleted file mode 100644 index bcf438a8ec8..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-tablespaces-backup.yaml +++ /dev/null @@ -1,37 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-with-tablespaces -spec: - instances: 3 - - storage: - size: 1Gi - - backup: - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip - - tablespaces: - - name: atablespace - storage: - size: 1Gi - storageClass: standard - - name: another_tablespace - storage: - size: 2Gi - storageClass: standard - - name: tablespacea1 - storage: - size: 2Gi - storageClass: standard diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-tablespaces.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-tablespaces.yaml deleted file mode 100644 index 1d4a25ea159..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-tablespaces.yaml +++ /dev/null @@ -1,25 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-with-tablespaces -spec: - instances: 3 - - storage: - size: 1Gi - - tablespaces: - - name: atablespace - storage: - size: 1Gi - storageClass: standard - temporary: true - - name: another_tablespace - storage: - size: 2Gi - storageClass: standard - temporary: true - - name: tablespacea1 - storage: - size: 2Gi - storageClass: standard diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-volume-snapshot.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-volume-snapshot.yaml deleted file mode 100644 index ef58162a061..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example-with-volume-snapshot.yaml +++ /dev/null @@ -1,32 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example-with-volume-snapshot -spec: - instances: 3 - primaryUpdateStrategy: unsupervised - - # Persistent storage configuration - storage: - storageClass: csi-hostpath-sc - size: 1Gi - walStorage: - storageClass: csi-hostpath-sc - size: 1Gi - - # Backup properties - backup: - volumeSnapshot: - className: csi-hostpath-snapclass - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example.yaml deleted file mode 100644 index a282ddf3587..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-example.yaml +++ /dev/null @@ -1,10 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - - storage: - size: 1Gi - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-expose-service.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-expose-service.yaml deleted file mode 100644 index 201b25e1643..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-expose-service.yaml +++ /dev/null @@ -1,36 +0,0 @@ ---- -apiVersion: v1 -kind: ConfigMap -metadata: - name: tcp-services - namespace: ingress-nginx -data: - 5432: default/cluster-example-rw:5432 - ---- -apiVersion: v1 -kind: Service -metadata: - name: ingress-nginx - namespace: ingress-nginx - labels: - app.kubernetes.io/name: ingress-nginx - app.kubernetes.io/part-of: ingress-nginx -spec: - type: LoadBalancer - ports: - - name: http - port: 80 - targetPort: 80 - protocol: TCP - - name: https - port: 443 - targetPort: 443 - protocol: TCP - - name: postgres - port: 5432 - targetPort: 5432 - protocol: TCP - selector: - app.kubernetes.io/name: ingress-nginx - app.kubernetes.io/part-of: ingress-nginx diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-schema-only-basicauth.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-schema-only-basicauth.yaml deleted file mode 100644 index 932ce7cc56f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-schema-only-basicauth.yaml +++ /dev/null @@ -1,27 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-pgdump -spec: - instances: 3 - - bootstrap: - initdb: - import: - type: microservice - schemaOnly: true - databases: - - app - source: - externalCluster: cluster-example - storage: - size: 1Gi - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: app - dbname: app - password: - name: cluster-example-app - key: password diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-snapshot-basicauth.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-snapshot-basicauth.yaml deleted file mode 100644 index 11878b8a3b5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-snapshot-basicauth.yaml +++ /dev/null @@ -1,30 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-pgdump -spec: - instances: 3 - - bootstrap: - initdb: - import: - type: microservice - databases: - - app - source: - externalCluster: cluster-example - pgDumpExtraOptions: - - '--jobs=2' - pgRestoreExtraOptions: - - '--jobs=2' - storage: - size: 1Gi - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: app - dbname: app - password: - name: cluster-example-app - key: password diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-snapshot-tls.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-snapshot-tls.yaml deleted file mode 100644 index 6c3a63dd13a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-import-snapshot-tls.yaml +++ /dev/null @@ -1,44 +0,0 @@ -# IMPORTANT: this configuration requires an appropriate line -# in the host-based access rules allowing replication connections -# to the app user. -# -# The following line meet the requisites: -# -# pg_hba: -# - hostssl all app all cert - -# You can generate the required TLS certificate with -# -# ./bin/kubectl-cnp certificate cluster-example-app-tls --cnp-cluster cluster-example --cnp-user app -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-pgdump -spec: - instances: 3 - - bootstrap: - initdb: - import: - type: microservice - databases: - - app - source: - externalCluster: cluster-example - storage: - size: 1Gi - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: app - dbname: app - sslKey: - name: cluster-example-app-tls - key: tls.key - sslCert: - name: cluster-example-app-tls - key: tls.crt - sslRootCert: - name: cluster-example-ca - key: ca.crt diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-pvc-template.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-pvc-template.yaml deleted file mode 100644 index 913ebe5ac51..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-pvc-template.yaml +++ /dev/null @@ -1,25 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-pvc-template -spec: - instances: 3 - - # Example of rolling update strategy: - # - unsupervised: automated update of the primary once all - # replicas have been upgraded (default) - # - supervised: requires manual supervision to perform - # the switchover of the primary - primaryUpdateStrategy: unsupervised - - # Persistent storage configuration - storage: - size: 1Gi - pvcTemplate: - accessModes: - - ReadWriteOnce - resources: - requests: - storage: 1Gi - storageClassName: standard - volumeMode: Filesystem diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-async.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-async.yaml deleted file mode 100644 index feaa30fc991..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-async.yaml +++ /dev/null @@ -1,30 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-replica-async -spec: - instances: 3 - - bootstrap: - recovery: - source: postgresql-bkp - - replica: - enabled: true - source: postgresql-bkp - - storage: - size: 1Gi - - externalClusters: - - name: postgresql-bkp - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-basicauth.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-basicauth.yaml deleted file mode 100644 index a44bf799715..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-basicauth.yaml +++ /dev/null @@ -1,33 +0,0 @@ -# IMPORTANT: this configuration requires an appropriate line -# in the host-based access rules allowing replication connections -# to the postgres user. -# -# The following line met the requisites -# - "host replication postgres all md5" -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-replica-basicauth -spec: - instances: 3 - - bootstrap: - pg_basebackup: - source: cluster-example - - replica: - enabled: true - source: cluster-example - - storage: - size: 1Gi - - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: postgres - dbname: postgres - password: - name: cluster-example-superuser - key: password \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-from-backup-other-namespace.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-from-backup-other-namespace.yaml deleted file mode 100644 index bd7c59fad0b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-from-backup-other-namespace.yaml +++ /dev/null @@ -1,37 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-replica-example-backup -spec: - instances: 1 - - bootstrap: - recovery: - source: cluster-example-backup - - replica: - enabled: true - source: cluster-example-backup - - storage: - size: 1Gi - - externalClusters: - - name: cluster-example-backup - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio-service.main:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - connectionParameters: - host: cluster-example-backup-rw.main.svc - user: postgres - dbname: postgres - password: - name: cluster-example-backup-superuser - key: password \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-restore.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-restore.yaml deleted file mode 100644 index 7520d1ba385..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-restore.yaml +++ /dev/null @@ -1,44 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-replica-from-restore -spec: - instances: 3 - - bootstrap: - recovery: - source: postgresql-bkp - - replica: - enabled: true - source: postgresql-bkp - - storage: - size: 1Gi - - externalClusters: - - name: postgresql-bkp - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - connectionParameters: - host: postgresql-bkp-rw.default.svc - user: streaming_replica - sslmode: verify-full - dbname: postgres - sslKey: - name: postgresql-bkp-replication - key: tls.key - sslCert: - name: postgresql-bkp-replication - key: tls.crt - sslRootCert: - name: postgresql-bkp-ca - key: ca.crt diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-tls.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-tls.yaml deleted file mode 100644 index ce5e2654839..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-replica-tls.yaml +++ /dev/null @@ -1,34 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-replica-tls -spec: - instances: 3 - - bootstrap: - pg_basebackup: - source: cluster-example - - replica: - primary: cluster-example - source: cluster-example - - storage: - size: 1Gi - - externalClusters: - - name: cluster-example - connectionParameters: - host: cluster-example-rw.default.svc - user: streaming_replica - sslmode: verify-full - dbname: postgres - sslKey: - name: cluster-example-replication - key: tls.key - sslCert: - name: cluster-example-replication - key: tls.crt - sslRootCert: - name: cluster-example-ca - key: ca.crt diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-external-cluster.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-external-cluster.yaml deleted file mode 100644 index 32f78117a18..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-external-cluster.yaml +++ /dev/null @@ -1,28 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - instances: 3 - - storage: - size: 5Gi - - bootstrap: - recovery: - source: postgresql-bkp - - externalClusters: - - name: postgresql-bkp - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - maxParallel: 8 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-pitr.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-pitr.yaml deleted file mode 100644 index 0fd04c6f1a4..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-pitr.yaml +++ /dev/null @@ -1,17 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore-pitr -spec: - instances: 3 - - storage: - size: 5Gi - - bootstrap: - recovery: - backup: - name: backup-example - - recoveryTarget: - targetTime: "2020-11-26 15:22:00.00000+00" diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot-full.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot-full.yaml deleted file mode 100644 index 72d7d11507e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot-full.yaml +++ /dev/null @@ -1,18 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore-full -spec: - instances: 3 - - storage: - size: 1Gi - storageClass: csi-hostpath-sc - - bootstrap: - recovery: - volumeSnapshots: - storage: - name: cluster-example-2-1695821489 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot-pitr.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot-pitr.yaml deleted file mode 100644 index 67890530b5f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot-pitr.yaml +++ /dev/null @@ -1,40 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore-pitr -spec: - instances: 3 - - storage: - size: 1Gi - storageClass: csi-hostpath-sc - - externalClusters: - - name: origin - - barmanObjectStore: - serverName: cluster-example-with-backup - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - maxParallel: 8 - - bootstrap: - recovery: - source: origin - - recoveryTarget: - targetTime: "2023-08-21 12:00:00.00000+00" - - volumeSnapshots: - storage: - name: cluster-example-with-backup-3-1692618163 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot.yaml deleted file mode 100644 index 4b232d016d1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-snapshot.yaml +++ /dev/null @@ -1,19 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - instances: 3 - - storage: - size: 1Gi - storageClass: csi-hostpath-sc - - bootstrap: - recovery: - volumeSnapshots: - storage: - name: cluster-example-20230930084154 - kind: VolumeSnapshot - apiGroup: snapshot.storage.k8s.io - diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-with-tablespaces.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-with-tablespaces.yaml deleted file mode 100644 index aa486893d6e..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore-with-tablespaces.yaml +++ /dev/null @@ -1,28 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore-with-tablespaces -spec: - instances: 3 - - storage: - size: 1Gi - - bootstrap: - recovery: - backup: - name: cluster-example-with-tablespaces-20231128093940 - - tablespaces: - atablespace: - storage: - size: 1Gi - storageClass: standard - another_tablespace: - storage: - size: 2Gi - storageClass: standard - tablespacea1: - storage: - size: 2Gi - storageClass: standard diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore.yaml deleted file mode 100644 index ae3f0bc74a5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-restore.yaml +++ /dev/null @@ -1,14 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-restore -spec: - instances: 3 - - storage: - size: 5Gi - - bootstrap: - recovery: - backup: - name: backup-example diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-storage-class-with-backup.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-storage-class-with-backup.yaml deleted file mode 100644 index a2d62d06b2f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-storage-class-with-backup.yaml +++ /dev/null @@ -1,32 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: pg-backup -spec: - instances: 3 - - # Example of rolling update strategy: - # - unsupervised: automated update of the primary once all - # replicas have been upgraded (default) - # - supervised: requires manual supervision to perform - # the switchover of the primary - primaryUpdateStrategy: unsupervised - - # Persistent storage configuration - storage: - storageClass: standard - size: 1Gi - - # Backup properties - backup: - barmanObjectStore: - destinationPath: s3://BUCKET_NAME/path/to/folder - s3Credentials: - accessKeyId: - name: aws-creds - key: ACCESS_KEY_ID - secretAccessKey: - name: aws-creds - key: ACCESS_SECRET_KEY - wal: - compression: gzip diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-storage-class.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-storage-class.yaml deleted file mode 100644 index f3e614e39ee..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/cluster-storage-class.yaml +++ /dev/null @@ -1,18 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-storage-class -spec: - instances: 3 - - # Example of rolling update strategy: - # - unsupervised: automated update of the primary once all - # replicas have been upgraded (default) - # - supervised: requires manual supervision to perform - # the switchover of the primary - primaryUpdateStrategy: unsupervised - - # Persistent storage configuration - storage: - storageClass: standard - size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example-fail.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example-fail.yaml deleted file mode 100644 index 44260589b88..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example-fail.yaml +++ /dev/null @@ -1,9 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - name: db-two -spec: - name: two - owner: app-two - cluster: - name: cluster-example diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example-icu.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example-icu.yaml deleted file mode 100644 index f50bbf1639a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example-icu.yaml +++ /dev/null @@ -1,16 +0,0 @@ -# NOTE: this manifest will only work properly if the Postgres version supports -# ICU locales and rules (version 16 and newer) -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - name: db-icu -spec: - name: declarative-icu - owner: app - encoding: UTF8 - localeProvider: icu - icuLocale: en - icuRules: fr - template: template0 - cluster: - name: cluster-example diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example.yaml deleted file mode 100644 index c951ecdce4d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/database-example.yaml +++ /dev/null @@ -1,9 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - name: db-one -spec: - name: one - owner: app - cluster: - name: cluster-example diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-dc-a.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-dc-a.yaml deleted file mode 100644 index 90f66c5c612..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-dc-a.yaml +++ /dev/null @@ -1,71 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-dc-a -spec: - instances: 3 - primaryUpdateStrategy: unsupervised - - storage: - storageClass: csi-hostpath-sc - size: 1Gi - - backup: - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip - - replica: - self: cluster-dc-a - primary: cluster-dc-a - source: cluster-dc-b - - externalClusters: - - name: cluster-dc-a - barmanObjectStore: - serverName: cluster-dc-a - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip - - name: cluster-dc-b - barmanObjectStore: - serverName: cluster-dc-b - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ScheduledBackup -metadata: - name: cluster-dc-a-backup -spec: - schedule: '0 0 0 * * *' - backupOwnerReference: self - cluster: - name: cluster-dc-a - immediate: true \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-dc-b.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-dc-b.yaml deleted file mode 100644 index 4523eaffb87..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-dc-b.yaml +++ /dev/null @@ -1,75 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-dc-b -spec: - instances: 3 - primaryUpdateStrategy: unsupervised - - storage: - storageClass: csi-hostpath-sc - size: 1Gi - - backup: - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip - - bootstrap: - recovery: - source: cluster-dc-a - - replica: - self: cluster-dc-b - primary: cluster-dc-a - source: cluster-dc-a - - externalClusters: - - name: cluster-dc-a - barmanObjectStore: - serverName: cluster-dc-a - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip - - name: cluster-dc-b - barmanObjectStore: - serverName: cluster-dc-b - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ScheduledBackup -metadata: - name: cluster-dc-b-backup -spec: - schedule: '0 0 0 * * *' - backupOwnerReference: self - cluster: - name: cluster-dc-b - immediate: true \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-test.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-test.yaml deleted file mode 100644 index 2ceb8e3776f..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/dc/cluster-test.yaml +++ /dev/null @@ -1,25 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-test -spec: - instances: 3 - primaryUpdateStrategy: unsupervised - - storage: - storageClass: csi-hostpath-sc - size: 1Gi - - backup: - barmanObjectStore: - destinationPath: s3://backups/ - endpointURL: http://minio:9000 - s3Credentials: - accessKeyId: - name: minio - key: ACCESS_KEY_ID - secretAccessKey: - name: minio - key: ACCESS_SECRET_KEY - wal: - compression: gzip diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/k9s/plugins.yml b/product_docs/docs/postgres_for_kubernetes/preview/samples/k9s/plugins.yml deleted file mode 100644 index 13062a3ed55..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/k9s/plugins.yml +++ /dev/null @@ -1,134 +0,0 @@ -# Move/add to $XDG_CONFIG_HOME/k9s/plugins.yaml -# Requires the cnp kubectl plugin. See https://cloudnative-pg.io/docs/devel/kubectl-plugin/ -# -# Cluster actions: -# b Request a new physical backup -# h View hibernate status -# Shift-H Hibernate cluster (this retains the data, but deletes everything else - including the cluster) -# l View cluster logs -# Shift-L View cluster logs pretty -# p Connect to the cluster via psql -# r Reload the cluster -# Shift-R Restart the cluster -# s View cluster status -# Shift-S View cluster status in verbose mode -# -# Namespace actions: -# Shift-H Wake up Hibernated cluster in this namespace (assumes cluster name equals namespace name) - -plugins: - postgresql-operator-backup: - shortCut: b - description: Backup - scopes: - - cluster - command: bash - confirm: true - background: false - args: - - -c - - "kubectl cnp backup $NAME -n $NAMESPACE --context \"$CONTEXT\" 2>&1 | less -R" - postgresql-operator-hibernate-status: - shortCut: h - description: Hibernate status - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp hibernate status $NAME -n $NAMESPACE --context \"$CONTEXT\" 2>&1 | less -R" - postgresql-operator-hibernate: - shortCut: Shift-H - description: Hibernate - confirm: true - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp hibernate on $NAME -n $NAMESPACE --context \"$CONTEXT\" 2>&1 | less -R" - postgresql-operator-hibernate-off: - shortCut: Shift-H - description: Wake up hibernated cluster in this namespace - confirm: true - scopes: - - namespace - command: bash - background: false - args: - - -c - - "kubectl cnp hibernate off $NAME -n $NAME --context \"$CONTEXT\" 2>&1 | less -R" - postgresql-operator-logs: - shortCut: l - description: Logs - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp logs cluster $NAME -f -n $NAMESPACE --context $CONTEXT" - postgresql-operator-logs-pretty: - shortCut: Shift-L - description: Logs pretty - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp logs cluster $NAME -f -n $NAMESPACE --context $CONTEXT | kubectl cnp logs pretty" - postgresql-operator-psql: - shortCut: p - description: PSQL shell - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp psql $NAME -n $NAMESPACE --context $CONTEXT" - postgresql-operator-reload: - shortCut: r - description: Reload - confirm: true - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp reload $NAME -n $NAMESPACE --context \"$CONTEXT\" 2>&1 | less -R" - postgresql-operator-restart: - shortCut: Shift-R - description: Restart - confirm: true - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp restart $NAME -n $NAMESPACE --context \"$CONTEXT\" 2>&1 | less -R" - postgresql-operator-status: - shortCut: s - description: Status - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp status $NAME -n $NAMESPACE --context \"$CONTEXT\" 2>&1 | less -R" - postgresql-operator-status-verbose: - shortCut: Shift-S - description: Status (verbose) - scopes: - - cluster - command: bash - background: false - args: - - -c - - "kubectl cnp status $NAME -n $NAMESPACE --context \"$CONTEXT\" --verbose 2>&1 | less -R" diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/alerts.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/alerts.yaml deleted file mode 100644 index 29fda38f8bf..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/alerts.yaml +++ /dev/null @@ -1,66 +0,0 @@ -groups: -- name: cnp-default.rules - rules: - - alert: LongRunningTransaction - annotations: - description: Pod {{ $labels.pod }} is taking more than 5 minutes (300 seconds) for a query. - summary: A query is taking longer than 5 minutes. - expr: |- - cnp_backends_max_tx_duration_seconds > 300 - for: 1m - labels: - severity: warning - - alert: BackendsWaiting - annotations: - description: Pod {{ $labels.pod }} has been waiting for longer than 5 minutes - summary: If a backend is waiting for longer than 5 minutes - expr: |- - cnp_backends_waiting_total > 300 - for: 1m - labels: - severity: warning - - alert: PGDatabase - annotations: - description: Over 300,000,000 transactions from frozen xid on pod {{ $labels.pod }} - summary: Number of transactions from the frozen XID to the current one - expr: |- - cnp_pg_database_xid_age > 300000000 - for: 1m - labels: - severity: warning - - alert: PGReplication - annotations: - description: Standby is lagging behind by over 300 seconds (5 minutes) - summary: The standby is lagging behind the primary - expr: |- - cnp_pg_replication_lag > 300 - for: 1m - labels: - severity: warning - - alert: LastFailedArchiveTime - annotations: - description: Archiving failed for {{ $labels.pod }} - summary: Checks the last time archiving failed. Will be < 0 when it has not failed. - expr: |- - (cnp_pg_stat_archiver_last_failed_time - cnp_pg_stat_archiver_last_archived_time) > 1 - for: 1m - labels: - severity: warning - - alert: DatabaseDeadlockConflicts - annotations: - description: There are over 10 deadlock conflicts in {{ $labels.pod }} - summary: Checks the number of database conflicts - expr: |- - cnp_pg_stat_database_deadlocks > 10 - for: 1m - labels: - severity: warning - - alert: ReplicaFailingReplication - annotations: - description: Replica {{ $labels.pod }} is failing to replicate - summary: Checks if the replica is failing to replicate - expr: |- - cnp_pg_replication_in_recovery > cnp_pg_replication_is_wal_receiver_up - for: 1m - labels: - severity: warning diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/kube-stack-config.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/kube-stack-config.yaml deleted file mode 100644 index af912026681..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/kube-stack-config.yaml +++ /dev/null @@ -1,78 +0,0 @@ -# -# Copyright © contributors to CloudNativePG, established as -# CloudNativePG a Series of LF Projects, LLC. -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. -# -# SPDX-License-Identifier: Apache-2.0 -# - -# -- here you can pass the whole values directly to the kube-prometheus-stack chart -enabled: true -kubeControllerManager: - enabled: false -nodeExporter: - enabled: false -defaultRules: - create: true - rules: - alertmanager: false - etcd: false - configReloaders: false - general: false - k8s: true - kubeApiserver: false - kubeApiserverAvailability: false - kubeApiserverSlos: false - kubelet: true - kubeProxy: false - kubePrometheusGeneral: false - kubePrometheusNodeRecording: false - kubernetesApps: false - kubernetesResources: false - kubernetesStorage: false - kubernetesSystem: false - kubeScheduler: false - kubeStateMetrics: false - network: false - node: true - nodeExporterAlerting: false - nodeExporterRecording: true - prometheus: false - prometheusOperator: false - -#nodeSelector: - #workload: monitor -prometheus: - prometheusSpec: - podMonitorSelectorNilUsesHelmValues: false - ruleSelectorNilUsesHelmValues: false - serviceMonitorSelectorNilUsesHelmValues: false - probeSelectorNilUsesHelmValues: false - #nodeSelector: - #workload: monitor -grafana: - enabled: true - # -- the grafana admin password - adminPassword: prom-operator - defaultDashboardsEnabled: false - sidecar: - dashboards: - enabled: true - #nodeSelector: - #workload: monitor -alertmanager: - enabled: true - #alertManagerSpec: - #nodeSelector: - #workload: monitor diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/podmonitor.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/podmonitor.yaml deleted file mode 100644 index bf6e1df96ff..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/podmonitor.yaml +++ /dev/null @@ -1,10 +0,0 @@ -apiVersion: monitoring.coreos.com/v1 -kind: PodMonitor -metadata: - name: postgresql-operator-controller-manager -spec: - selector: - matchLabels: - app.kubernetes.io/name: cloud-native-postgresql - podMetricsEndpoints: - - port: metrics diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/prometheusrule.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/prometheusrule.yaml deleted file mode 100644 index b8bd31055ba..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/monitoring/prometheusrule.yaml +++ /dev/null @@ -1,71 +0,0 @@ -apiVersion: monitoring.coreos.com/v1 -kind: PrometheusRule -metadata: - name: postgresql-operator-default-alerts -spec: - groups: - - name: cnp-default.rules - rules: - - alert: LongRunningTransaction - annotations: - description: Pod {{ $labels.pod }} is taking more than 5 minutes (300 seconds) for a query. - summary: A query is taking longer than 5 minutes. - expr: |- - cnp_backends_max_tx_duration_seconds > 300 - for: 1m - labels: - severity: warning - - alert: BackendsWaiting - annotations: - description: Pod {{ $labels.pod }} has been waiting for longer than 5 minutes - summary: If a backend is waiting for longer than 5 minutes - expr: |- - cnp_backends_waiting_total > 300 - for: 1m - labels: - severity: warning - - alert: PGDatabaseXidAge - annotations: - description: Over 300,000,000 transactions from frozen xid on pod {{ $labels.pod }} - summary: Number of transactions from the frozen XID to the current one - expr: |- - cnp_pg_database_xid_age > 300000000 - for: 1m - labels: - severity: warning - - alert: PGReplication - annotations: - description: Standby is lagging behind by over 300 seconds (5 minutes) - summary: The standby is lagging behind the primary - expr: |- - cnp_pg_replication_lag > 300 - for: 1m - labels: - severity: warning - - alert: LastFailedArchiveTime - annotations: - description: Archiving failed for {{ $labels.pod }} - summary: Checks the last time archiving failed. Will be < 0 when it has not failed. - expr: |- - (cnp_pg_stat_archiver_last_failed_time - cnp_pg_stat_archiver_last_archived_time) > 1 - for: 1m - labels: - severity: warning - - alert: DatabaseDeadlockConflicts - annotations: - description: There are over 10 deadlock conflicts in {{ $labels.pod }} - summary: Checks the number of database conflicts - expr: |- - cnp_pg_stat_database_deadlocks > 10 - for: 1m - labels: - severity: warning - - alert: ReplicaFailingReplication - annotations: - description: Replica {{ $labels.pod }} is failing to replicate - summary: Checks if the replica is failing to replicate - expr: |- - cnp_pg_replication_in_recovery > cnp_pg_replication_is_wal_receiver_up - for: 1m - labels: - severity: warning diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/networkpolicy-example.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/networkpolicy-example.yaml deleted file mode 100644 index a291ad3dd7b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/networkpolicy-example.yaml +++ /dev/null @@ -1,23 +0,0 @@ -# This network policy allows ingress from the CNP operator -# installed in namespace postgresql-operator-system into the pods corresponding -# to a cluster named cluster-example -# NOTE: in OpenShift the default namespace for the operator is openshift-operators -apiVersion: networking.k8s.io/v1 -kind: NetworkPolicy -metadata: - name: allow-operator -spec: - podSelector: - matchLabels: - cnpg.io/cluster: cluster-example # The label value must be the cluster name - ingress: - - from: - - namespaceSelector: - matchLabels: - kubernetes.io/metadata.name: postgresql-operator-system # Or on OpenShift: openshift-operators - podSelector: - matchLabels: - app.kubernetes.io/name: cloud-native-postgresql # Matches the Operator pod - ports: - - port: 8000 - - port: 5432 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-basic-auth.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-basic-auth.yaml deleted file mode 100644 index 7fa97608d17..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-basic-auth.yaml +++ /dev/null @@ -1,15 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-example-rw -spec: - cluster: - name: cluster-example - - instances: 1 - type: rw - pgbouncer: - poolMode: session - authQuerySecret: - name: cluster-example-superuser - authQuery: SELECT usename, passwd FROM pg_catalog.pg_shadow WHERE usename=$1 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-deployment-strategy.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-deployment-strategy.yaml deleted file mode 100644 index 3f86f1ba3a1..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-deployment-strategy.yaml +++ /dev/null @@ -1,19 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-deployment-strategy -spec: - cluster: - name: cluster-example - - instances: 1 - type: rw - - deploymentStrategy: - type: RollingUpdate - rollingUpdate: - maxSurge: 0 - maxUnavailable: 10% - - pgbouncer: - poolMode: session diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-external.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-external.yaml deleted file mode 100644 index 9bf16d51ec5..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-external.yaml +++ /dev/null @@ -1,20 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-example-rw -spec: - cluster: - name: cluster-example - instances: 3 - type: rw - serviceTemplate: - metadata: - labels: - app: pooler - spec: - type: LoadBalancer - pgbouncer: - poolMode: session - parameters: - max_client_conn: "1000" - default_pool_size: "10" diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-tls.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-tls.yaml deleted file mode 100644 index f11fd830723..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/pooler-tls.yaml +++ /dev/null @@ -1,14 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-example-rw -spec: - cluster: - name: cluster-example - - instances: 1 - type: rw - pgbouncer: - poolMode: session - parameters: - server_tls_protocols: tlsv1.3 diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/postgis-example.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/postgis-example.yaml deleted file mode 100644 index 21ce41aec04..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/postgis-example.yaml +++ /dev/null @@ -1,38 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgis-example -spec: - imageName: docker.enterprisedb.com/k8s/postgresql:18.4-minimal-ubi9 - instances: 1 - - storage: - size: 1Gi - - postgresql: - extensions: - - name: postgis - image: - reference: ghcr.io/cloudnative-pg/postgis-extension:3.6.1-18-trixie - ld_library_path: - - system ---- -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Database -metadata: - name: postgis-example-app -spec: - name: app - owner: app - cluster: - name: postgis-example - extensions: - - name: postgis - version: '3.6.1' - - name: postgis_raster - - name: postgis_sfcgal - - name: fuzzystrmatch - - name: address_standardizer - - name: address_standardizer_data_us - - name: postgis_tiger_geocoder - - name: postgis_topology diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/publication-example-objects.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/publication-example-objects.yaml deleted file mode 100644 index 4e47ecb73ed..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/publication-example-objects.yaml +++ /dev/null @@ -1,16 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Publication -metadata: - name: publication-example-objects -spec: - cluster: - name: cluster-example - name: pub-objects - dbname: app - target: - objects: - - tablesInSchema: public - - table: - schema: another_schema - name: numbers_three - only: true diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/publication-example.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/publication-example.yaml deleted file mode 100644 index 40eca1acdea..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/publication-example.yaml +++ /dev/null @@ -1,11 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Publication -metadata: - name: publication-example -spec: - cluster: - name: cluster-example - name: pub-all - dbname: app - target: - allTables: true diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/scheduled-backup-example.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/scheduled-backup-example.yaml deleted file mode 100644 index b360276ab4a..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/scheduled-backup-example.yaml +++ /dev/null @@ -1,9 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: ScheduledBackup -metadata: - name: backup-example -spec: - schedule: "0 0 0 * * *" - backupOwnerReference: self - cluster: - name: pg-backup diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/subscription-example.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/subscription-example.yaml deleted file mode 100644 index 500b8717a52..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/subscription-example.yaml +++ /dev/null @@ -1,11 +0,0 @@ -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Subscription -metadata: - name: subscription-sample -spec: - name: sub - dbname: app - publicationName: pub-all - cluster: - name: cluster-example-dest - externalClusterName: cluster-example diff --git a/product_docs/docs/postgres_for_kubernetes/preview/samples/subscription.yaml b/product_docs/docs/postgres_for_kubernetes/preview/samples/subscription.yaml deleted file mode 100644 index 20ff6874ee6..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/samples/subscription.yaml +++ /dev/null @@ -1,10 +0,0 @@ -apiVersion: operators.coreos.com/v1alpha1 -kind: Subscription -metadata: - name: cloud-native-postgresql - namespace: openshift-operators -spec: - channel: stable - name: cloud-native-postgresql - source: certified-operators - sourceNamespace: openshift-marketplace diff --git a/product_docs/docs/postgres_for_kubernetes/preview/scheduling.mdx b/product_docs/docs/postgres_for_kubernetes/preview/scheduling.mdx deleted file mode 100644 index c746900f66d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/scheduling.mdx +++ /dev/null @@ -1,213 +0,0 @@ ---- -title: 'Scheduling' -originalFilePath: 'src/scheduling.md' ---- - - - -Scheduling, in Kubernetes, is the process responsible for placing a new pod on -the best node possible, based on several criteria. - -!!!note Kubernetes documentation -Please refer to the -[Kubernetes documentation](https://kubernetes.io/docs/concepts/scheduling-eviction/) -for more information on scheduling, including all the available policies. On -this page we assume you are familiar with concepts like affinity, -anti-affinity, node selectors, and so on. -!!! - -You can control how the {{name.ln}} cluster's instances should be -scheduled through the [`affinity`](pg4k.v1.md#affinityconfiguration) -section in the definition of the cluster, which supports: - -- pod affinity/anti-affinity -- node selectors -- tolerations - -## Pod Affinity and Anti-Affinity - -Kubernetes provides mechanisms to control where pods are scheduled using -*affinity* and *anti-affinity* rules. These rules allow you to specify whether -a pod should be scheduled on particular nodes (*affinity*) or avoided on -specific nodes (*anti-affinity*) based on the workloads already running there. -This capability is technically referred to as **inter-pod -affinity/anti-affinity**. - -By default, {{name.ln}} configures cluster instances to preferably be -scheduled on different nodes, while `pgBouncer` instances might still run on -the same nodes. - -For example, given the following `Cluster` specification: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - imageName: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 - - affinity: - enablePodAntiAffinity: true # Default value - topologyKey: kubernetes.io/hostname # Default value - podAntiAffinityType: preferred # Default value - - storage: - size: 1Gi -``` - -The `affinity` configuration applied in the instance pods will be: - -```yaml -affinity: - podAntiAffinity: - preferredDuringSchedulingIgnoredDuringExecution: - - podAffinityTerm: - labelSelector: - matchExpressions: - - key: k8s.enterprisedb.io/cluster - operator: In - values: - - cluster-example - - key: k8s.enterprisedb.io/podRole - operator: In - values: - - instance - topologyKey: kubernetes.io/hostname - weight: 100 -``` - -With this setup, Kubernetes will *prefer* to schedule a 3-node PostgreSQL -cluster across three different nodes, assuming sufficient resources are -available. - -### Requiring Pod Anti-Affinity - -You can modify the default behavior by adjusting the settings mentioned above. - -For example, setting `podAntiAffinityType` to `required` will enforce -`requiredDuringSchedulingIgnoredDuringExecution` instead of -`preferredDuringSchedulingIgnoredDuringExecution`. - -However, be aware that this strict requirement may cause pods to remain pending -if resources are insufficient—this is particularly relevant when using [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler) -for automated horizontal scaling in a Kubernetes cluster. - -!!!note Inter-pod Affinity and Anti-Affinity -For more details, refer to the [Kubernetes documentation](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity). -!!! - -### Topology Considerations - -In cloud environments, you might consider using `topology.kubernetes.io/zone` -as the `topologyKey` to ensure pods are distributed across different -availability zones rather than just nodes. For more options, see -[Well-Known Labels, Annotations, and Taints](https://kubernetes.io/docs/reference/labels-annotations-taints/). - -### Disabling Anti-Affinity Policies - -If needed, you can disable the operator-generated anti-affinity policies by -setting `enablePodAntiAffinity` to `false`. - -### Fine-Grained Control with Custom Rules - -For scenarios requiring more precise control, you can specify custom pod -affinity or anti-affinity rules using the `additionalPodAffinity` and -`additionalPodAntiAffinity` configuration attributes. These custom rules will -be added to those generated by the operator, if enabled, or used directly if -the operator-generated rules are disabled. - -!!!note -When using `additionalPodAntiAffinity` or `additionalPodAffinity`, you must -provide the full `podAntiAffinity` or `podAffinity` structure expected by the -Pod specification. The following YAML example demonstrates how to configure -only one instance of PostgreSQL per worker node, regardless of which PostgreSQL -cluster it belongs to: -!!! - -```yaml - additionalPodAntiAffinity: - requiredDuringSchedulingIgnoredDuringExecution: - - labelSelector: - matchExpressions: - - key: postgresql - operator: Exists - values: [] - topologyKey: "kubernetes.io/hostname" -``` - -## Node selection through `nodeSelector` - -Kubernetes allows `nodeSelector` to provide a list of labels (defined as -key-value pairs) to select the nodes on which a pod can run. Specifically, -the node must have each indicated key-value pair as labels for the -pod to be scheduled and run. - -Similarly, {{name.ln}} consents you to define a `nodeSelector` in the -`affinity` section, so that you can request a PostgreSQL cluster to run only -on nodes that have those labels. - -## Tolerations - -Kubernetes allows you to specify (through `taints`) whether a node should repel -all pods not explicitly tolerating (through `tolerations`) their `taints`. - -So, by setting a proper set of `tolerations` for a workload matching a specific -node's `taints`, Kubernetes scheduler will now take into consideration the -tainted node, while deciding on which node to schedule the workload. -Tolerations can be configured for all the pods of a Cluster through the -`.spec.affinity.tolerations` section, which accepts the usual Kubernetes syntax -for tolerations. - -!!!note Taints and Tolerations -More information on taints and tolerations can be found in the -[Kubernetes documentation](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/). -!!! - -## Isolating PostgreSQL workloads - -!!!info Important -Before proceeding, please ensure you have read the -["Architecture"](architecture.md) section of the documentation. -!!! - -While you can deploy PostgreSQL on Kubernetes in various ways, we recommend -following these essential principles for production environments: - -- **Exploit Availability Zones:** If possible, take advantage of availability - zones (AZs) within the same Kubernetes cluster by distributing PostgreSQL - instances across different AZs. -- **Dedicate Worker Nodes:** Allocate specific worker nodes for PostgreSQL - workloads through the `node-role.kubernetes.io/postgres` label and taint, - as detailed in the [Reserving Nodes for PostgreSQL Workloads](architecture.md#reserving-nodes-for-postgresql-workloads) - section. -- **Avoid Node Overlap:** Ensure that no instances from the same PostgreSQL - cluster are running on the same node. - -As explained in greater detail in the previous sections, {{name.ln}} -provides the flexibility to configure pod anti-affinity, node selectors, and -tolerations. - -Below is a sample configuration to ensure that a PostgreSQL `Cluster` is -deployed on `postgres` nodes, with its instances distributed across different -nodes: - -```yaml - # - affinity: - enablePodAntiAffinity: true - topologyKey: kubernetes.io/hostname - podAntiAffinityType: required - nodeSelector: - node-role.kubernetes.io/postgres: "" - tolerations: - - key: node-role.kubernetes.io/postgres - operator: Exists - effect: NoSchedule - # -``` - -Despite its simplicity, this setup ensures optimal distribution and isolation -of PostgreSQL workloads, leading to enhanced performance and reliability in -your production environment. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/security.mdx b/product_docs/docs/postgres_for_kubernetes/preview/security.mdx deleted file mode 100644 index 139cdfff340..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/security.mdx +++ /dev/null @@ -1,856 +0,0 @@ ---- -title: 'Security' -originalFilePath: 'src/security.md' ---- - -{{name.ln}} is designed to be secure by default, following the "Least Privilege" -principle across all layers of the stack. This document outlines our security -governance, supply chain integrity, and the technical controls analyzed at three -distinct layers: Code, Container, and Cluster. - -!!! Warning - The information contained in this page must not exonerate you from - performing regular InfoSec duties on your Kubernetes cluster. Please - familiarize yourself with the ["Overview of Cloud Native Security"](https://kubernetes.io/docs/concepts/security/overview/) - page from the Kubernetes documentation. - -!!! Seealso "About the 4C's Security Model" - Please refer to ["The 4C’s Security Model in Kubernetes"](https://www.enterprisedb.com/blog/4cs-security-model-kubernetes) - blog article to get a better understanding and context of the approach EDB - has taken with security in {{name.ln}}. - -## Code - -{{name.ln}}' source code undergoes systematic static analysis, including -checks for security vulnerabilities, using the popular open-source linter for -Go, [GolangCI-Lint](https://github.com/golangci/golangci-lint), directly -integrated into the CI/CD pipeline. GolangCI-Lint can run multiple linters on -the same source code. - -The following tools are used to identify security issues: - -- **[Golang Security Checker](https://github.com/securego/gosec) (`gosec`):** A - linter that scans the abstract syntax tree of the source code against a set - of rules designed to detect known vulnerabilities, threats, and weaknesses, - such as hard-coded credentials, integer overflows, and SQL injections. - GolangCI-Lint runs `gosec` as part of its suite. - -- **[govulncheck](https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck):** This - tool runs in the CI/CD pipeline and reports known vulnerabilities affecting - Go code or the compiler. If the operator is built with a version of the Go - compiler containing a known vulnerability, `govulncheck` will detect it. - -- **[CodeQL](https://codeql.github.com/):** Provided by GitHub, this tool scans - for security issues and blocks any pull request with detected - vulnerabilities. CodeQL is configured to review only Go code, excluding other - languages in the repository such as Python or Bash. - -- **[Snyk](https://snyk.io/):** Conducts nightly code scans in a scheduled job - and generates weekly reports highlighting any new findings related to code - security and licensing issues. - -The {{name.ln}} repository has the *"Private vulnerability reporting"* option -enabled in the [Security section](https://github.com/cloudnative-pg/cloudnative-pg/security). -This feature allows users to safely report security issues that require careful -handling before being publicly disclosed. If you discover any security bug, -please use this medium to report it. - -!!! Important - A failure in the static code analysis phase of the CI/CD pipeline will - block the entire delivery process of {{name.ln}}. Every commit must pass all - the linters defined by GolangCI-Lint. - -## Container - -Operator images for {{name.ln}} are built and [published](./private_edb_registries.mdx) as part of our release process. -See [Release Notes](rel_notes/) for information on the latest available operator versions. - -Operand images are built and published monthly for each supported PostgreSQL version -(including [EDB Postgres Extended](/pge/latest/) and [EDB Postgres Advanced](/epas/latest/)). - -Images undergo scanning with the following tools: - -- **[Dockle](https://github.com/goodwithtech/dockle):** Ensures best practices - in the container build process. -- **[Black Duck](https://www.blackduck.com/):** Checks for vulnerabilities in Open Source - components, validates license consistency. - -!!! Important -All operand images are automatically rebuilt monthly by our pipelines to incorporate the latest security updates at both the base image and package levels, providing **patch-level updates** for the container images distributed to EDB download sites. -!!! - -!!! Warning -Running outdated images can expose your environment to security risks and performance issues. We highly recommend that you update to the latest image version and keep your images up to date. This will ensure that you take advantage of the latest updates and patches available. -!!! - -### Guidelines and Frameworks for Container Security - -The following guidelines and frameworks have been considered for ensuring -container-level security: - -- **["Container Image Creation and Deployment Guide"](https://dl.dod.cyber.mil/wp-content/uploads/devsecops/pdf/DevSecOps_Enterprise_Container_Image_Creation_and_Deployment_Guide_2.6-Public-Release.pdf):** - Developed by the Defense Information Systems Agency (DISA) of the United States - Department of Defense (DoD). -- **["CIS Benchmark for Docker"](https://www.cisecurity.org/benchmark/docker/):** - Developed by the Center for Internet Security (CIS). - -!!! Seealso "About Container-Level Security" - For more information on the approach that EDB has taken regarding security - at the container level in {{name.ln}}, please refer to the blog article - ["Security and Containers in {{name.ln}}"](https://www.enterprisedb.com/blog/security-and-containers-cloud-native-postgresql). - -## Cluster - -Security at the cluster level takes into account all Kubernetes components that -form both the control plane and the nodes, as well as the applications that run in -the cluster (PostgreSQL included). We start by defining the trust model and the -security boundaries that frame the rest of this section. - -### Trust Model and Security Boundaries - -{{name.ln}} follows a clear separation of responsibilities between the -operator and the Kubernetes platform for enforcing security policies. The -subsections below describe who is trusted to influence the PostgreSQL Pods, -where the enforcement boundary actually lies, how the operator confines the -resources it manages, and how access to all of this is governed by RBAC. - -#### Trusted Cluster Resource Writers - -Any user with create or update permissions on the `Cluster` custom resource is -trusted to define the full specification of the PostgreSQL Pods that the -operator manages. This includes security-sensitive fields such as -`spec.securityContext`, `spec.podSecurityContext`, and -`spec.serviceAccountName`. The operator applies these settings as instructed. -When a Cluster writer does not override them, the operator applies a hardened -default Pod and container security context (see -[Pod and Container Security Contexts](#pod-and-container-security-contexts)). - -This is consistent with how all Kubernetes operators work: the operator acts as -a privileged agent that translates high-level intent into low-level Kubernetes -resources. Granting someone write access to a Cluster resource is equivalent -to granting them control over the resulting Pods, Services, PVCs, and other -managed resources. - -The same principle applies to [CNPG-I plugins](cnpg_i.md). A plugin hooks into -the Pod lifecycle and can modify any field of the Pod specification before the -Pod is created. Installing a plugin is therefore an explicit trust decision -made by the cluster administrator, on par with granting write access to a -Cluster resource. - -#### Kubernetes Admission Control - -The operator creates Pods through the standard Kubernetes API, meaning every -Pod goes through the full admission control chain configured on the cluster. -This includes -[Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/) -(PSA), the built-in Kubernetes mechanism that enforces -[Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/) -at the namespace level, as well as any third-party policy engine in use. If a -namespace enforces the PSA `restricted` or `baseline` profile, the Kubernetes -API server rejects any Pod that violates the policy, including Pods created by -the operator. - -Because the trusted Cluster writers described above can set any Pod field, this -admission control chain (not the operator) is the boundary that enforces Pod -security policies in your environment. - -#### Namespace Isolation - -The operator confines all managed resources to the namespace of their parent -Cluster. Instance Pods are always created in the same namespace as their -Cluster, set explicitly and deterministically rather than inferred from any -other relationship. Because Kubernetes owner references are confined to a -single namespace, the operator also cannot establish ownership of resources in -any other namespace. - -#### RBAC on Custom Resources - -Access to {{name.ln}} custom resources is governed by standard Kubernetes -RBAC. Since write access to a Cluster resource implies control over the -resulting Pods, annotations like `k8s.enterprisedb.io/podPatch` (which applies a -user-supplied patch to the managed Pods), `k8s.enterprisedb.io/validation`, and -`k8s.enterprisedb.io/reconciliationLoop` are subject to the same RBAC rules as the -Cluster resource itself. - -In particular, setting `k8s.enterprisedb.io/validation` to `disabled` bypasses the -operator's own validating admission webhook for that Cluster, including the -syntactic and applicability checks performed on `k8s.enterprisedb.io/podPatch`. -{{name.ln}}' webhook validation is therefore advisory: it can be turned off -by the same actor who can write the Cluster, so it is not a security boundary. -Kubernetes admission control still applies to the resulting Pods regardless of -this annotation. - -The same reasoning applies to the `DatabaseRole` resource: its specification -allows `superuser: true` and membership of any existing role through -`inRoles`, including the `postgres` role itself. Write access to -`DatabaseRole` objects in a namespace is therefore equivalent to superuser -access on the PostgreSQL clusters in that namespace, and deserves the same -care as write access to the `Cluster` resource. - -The RBAC discussed here governs access to {{name.ln}}' own custom resources. -The next section covers the complementary side: the RBAC that the operator -itself relies on to manage Kubernetes resources on your behalf. - - -### Role Based Access Control (RBAC) - -This section covers the operator's *own* RBAC (the service account and roles it -uses to manage Kubernetes resources on your behalf), as opposed to the user -access to custom resources discussed in -[RBAC on Custom Resources](#rbac-on-custom-resources) above. - -The operator interacts with the Kubernetes API server using a dedicated service -account named `postgresql-operator-manager`. This service account is typically installed in -the operator namespace, commonly `postgresql-operator-system`. However, the namespace may vary -based on the deployment method (see the subsection below). - -In the same namespace, there is a binding between the `postgresql-operator-manager` service -account and a role. The specific name and type of this role (either `Role` or -`ClusterRole`) also depend on the deployment method. This role defines the -necessary permissions required by the operator to function correctly. To learn -more about these roles, you can use the `kubectl describe clusterrole` or -`kubectl describe role` commands, depending on the deployment method. -For OpenShift specificities on this matter, please consult the -["Red Hat OpenShift" section](openshift.md#predefined-rbac-objects), in particular -["Pre-defined RBAC objects" section](openshift.md#predefined-rbac-objects). - -!!! Important - The above permissions are exclusively reserved for the operator's service - account to interact with the Kubernetes API server. They are not directly - accessible by the users of the operator that interact only with `Cluster`, - `Pooler`, `Backup`, `ScheduledBackup`, `Database`, `Publication`, - `Subscription`, `ImageCatalog` and `ClusterImageCatalog` resources. - -Below we provide some examples and, most importantly, the reasons why -{{name.ln}} requires full or partial management of standard Kubernetes -namespaced or non-namespaced resources. - -`configmaps` -: The operator needs to create and manage default config maps for - the Prometheus exporter monitoring metrics. - -`deployments` -: The operator needs to manage a PgBouncer connection pooler - using a standard Kubernetes `Deployment` resource. - -`jobs` -: The operator needs to handle jobs to manage different `Cluster`'s phases. - -`persistentvolumeclaims` -: The volume where the `PGDATA` resides is the - central element of a PostgreSQL `Cluster` resource; the operator needs - to interact with the selected storage class to dynamically provision - the requested volumes, based on the defined scheduling policies. - -`pods` -: The operator needs to manage `Cluster`'s instances. - -`secrets` -: Unless you provide certificates and passwords to your `Cluster` - objects, the operator adopts the "convention over configuration" paradigm by - self-provisioning random generated passwords and TLS certificates, and by - storing them in secrets. - -`serviceaccounts` -: The operator needs to create a service account that - enables the instance manager (which is the *PID 1* process of the container - that controls the PostgreSQL server) to safely communicate with the - Kubernetes API server to coordinate actions and continuously provide - a reliable status of the `Cluster`. - -`services` -: The operator needs to control network access to the PostgreSQL cluster - (or the connection pooler) from applications, and properly manage - failover/switchover operations in an automated way (by assigning, for example, - the correct end-point of a service to the proper primary PostgreSQL instance). - -`validatingwebhookconfigurations` and `mutatingwebhookconfigurations` -: The operator injects its self-signed webhook CA into both webhook - configurations, which are needed to validate and mutate all the resources it - manages. For more details, please see the - [Kubernetes documentation](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/). - -`volumesnapshots` -: The operator needs to generate `VolumeSnapshots` objects in order to take - backups of a PostgreSQL server. VolumeSnapshots are read too in order to - validate them before starting the restore process. - -`nodes` -: The operator needs to get the labels for Affinity and AntiAffinity so it can - decide in which nodes a pod can be scheduled. This is useful, for example, to - prevent the replicas from being scheduled in the same node - especially - important if nodes are in different availability zones. This - permission is also used to determine whether a node is scheduled, preventing - the creation of pods on unscheduled nodes, or triggering a switchover if - the primary lives in an unscheduled node. - - -#### Deployments and `ClusterRole` Resources - -As mentioned above, each deployment method may have variations in the namespace -location of the service account, as well as the names and types of role -bindings and respective roles. - -##### Via Kubernetes Manifest - -When installing {{name.ln}} using the Kubernetes manifest, permissions are -set to `ClusterRoleBinding` by default. You can inspect the permissions -required by the operator by running: - -```sh -kubectl describe clusterrole postgresql-operator-manager -``` - -##### Via OLM - -From a security perspective, the Operator Lifecycle Manager (OLM) provides a -more flexible deployment method. It allows you to configure the operator to -watch either all namespaces or specific namespaces, enabling more granular -permission management. - -!!!Info - OLM allows you to deploy the operator in its own namespace and configure it - to watch specific namespaces used for {{name.ln}} clusters. This setup helps - to contain permissions and restrict access more effectively. - -#### Why Are ClusterRole Permissions Needed? - -The operator currently requires `ClusterRole` permissions to read `nodes` and -`ClusterImageCatalog` objects. All other permissions can be namespace-scoped (i.e., `Role`) or -cluster-wide (i.e., `ClusterRole`). - -If you remove the `ClusterRoles` permissions, -the operator will crash unless you explicitly set the experimental `--no-cluster-roles=true` -command-line argument by editing the operator's `Deployment` definition. -Note that enabling this flag will disable the operator's ability -to work with `ClusterImageCatalog` objects and respond to changes in `Node` status. -This also affects Pooler resources: any Pooler referencing a `ClusterImageCatalog` -for its PgBouncer image will not react to catalog updates. - -Even with these permissions, if someone gains access to the `ServiceAccount`, -they will only have `get`, `list`, and `watch` permissions, which are limited -to viewing resources. However, if an unauthorized user gains access to the -`ServiceAccount`, it indicates a more significant security issue. - -Therefore, it's crucial to prevent users from accessing the operator's -`ServiceAccount` and any other `ServiceAccount` with elevated permissions. - -### Calls to the API server made by the instance manager - -The instance manager, which is the entry point of the operand container, needs -to make some calls to the Kubernetes API server to ensure that the status of -some resources is correctly updated and to access the config maps and secrets -that are associated with that Postgres cluster. Such calls are performed through -a dedicated `ServiceAccount` created by the operator that shares the same -PostgreSQL `Cluster` resource name. - -!!! Important - The operand can only access a specific and limited subset of resources - through the API server. A service account is the - [recommended way to access the API server from within a Pod](https://kubernetes.io/docs/tasks/run-application/access-api-from-pod/). -#### Using a shared ServiceAccount - -By default, {{name.ln}} creates a dedicated `ServiceAccount` for each cluster, -named after the cluster itself. However, in cloud environments using IAM roles -(such as AWS IRSA, GCP Workload Identity, or Azure Workload Identity), each -cluster creating its own `ServiceAccount` requires individual IAM configuration -for every new cluster, making it difficult to scale when managing multiple -clusters. - -{{name.ln}} allows multiple clusters to share a single `ServiceAccount` by -specifying the `serviceAccountName` field in the cluster specification. This -enables one-time IAM configuration that works across all clusters using that -`ServiceAccount`. - -!!!important -When using a shared `ServiceAccount`, you are responsible for creating and -managing the `ServiceAccount` yourself. The operator will validate that the -specified `ServiceAccount` exists but will not create or modify it. -!!! - -Here's an example of using a shared `ServiceAccount`: - -```yaml -# Create the shared ServiceAccount once -apiVersion: v1 -kind: ServiceAccount -metadata: - name: postgres-cloud-sa - annotations: - # AWS IRSA annotation - eks.amazonaws.com/role-arn: arn:aws:iam:us-east-1:123456789012:role/PostgresRole ---- -# Reference it from multiple clusters -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-prod -spec: - serviceAccountName: postgres-cloud-sa - instances: 3 - storage: - size: 100Gi -``` - -!!!note -The `serviceAccountName` field is mutually exclusive with -`serviceAccountTemplate`. You can either let the operator manage the -`ServiceAccount` (optionally customizing it with `serviceAccountTemplate`) -or reference an existing one with `serviceAccountName`, but not both. -!!! - -!!!warning -The `serviceAccountName` field is immutable once set. If you need to change -the `ServiceAccount`, you must recreate the cluster. -!!! - -!!!note -When multiple clusters share a `ServiceAccount`, the operator creates -a separate `Role` and `RoleBinding` for each cluster. The shared -`ServiceAccount` accumulates the Kubernetes RBAC permissions of all -clusters using it. Each `Role` is narrowly scoped to the specific -cluster's resources, so this does not constitute a privilege escalation. -!!! - -#### Using a shared ServiceAccount with Poolers - -The same shared `ServiceAccount` feature is available for `Pooler` resources. -When deploying PgBouncer poolers in cloud environments with IAM integration, -you can specify the `serviceAccountName` field in the Pooler spec to reference -an existing `ServiceAccount` instead of having the operator create one per pooler. - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Pooler -metadata: - name: pooler-prod -spec: - cluster: - name: cluster-prod - serviceAccountName: pgbouncer-cloud-sa - instances: 3 - pgbouncer: - poolMode: session -``` - -!!!warning -As with clusters, the `serviceAccountName` field on poolers is immutable -once set. If you need to change the `ServiceAccount`, you must recreate -the pooler. -!!! - -For transparency, the permissions associated with the service account are defined in the -[roles.go](https://github.com/cloudnative-pg/cloudnative-pg/blob/main/pkg/specs/roles.go) -file. For example, to retrieve the permissions of a generic `mypg` cluster in the -`myns` namespace, you can type the following command: - -```bash -kubectl get role -n myns mypg -o yaml -``` - -Then verify that the role is bound to the service account: - -```bash -kubectl get rolebinding -n myns mypg -o yaml -``` - -!!! Important - Remember that **roles are limited to a given namespace**. - -Below we provide a quick summary of the permissions associated with the service -account for generic Kubernetes resources. - -`configmaps` -: The instance manager can only read config maps that are related to the same - cluster, such as custom monitoring queries - -`secrets` -: The instance manager can only read secrets that are related to the same - cluster, namely: streaming replication user, application user, super user, - LDAP authentication user, client CA, server CA, server certificate, backup - credentials, custom monitoring queries - -`events` -: The instance manager can create an event for the cluster, informing the - API server about a particular aspect of the PostgreSQL instance lifecycle - -Here instead, we provide the same summary for resources specific to -{{name.ln}}. - -`clusters` -: The instance manager requires read-only permissions, namely `get`, `list` and - `watch`, just for its own `Cluster` resource - -`clusters/status` -: The instance manager requires to `update` and `patch` the status of just its - own `Cluster` resource - -`backups` -: The instance manager requires `get` and `list` permissions to read any - `Backup` resource in the namespace. Additionally, it requires the `delete` - permission to clean up the Kubernetes cluster by removing the `Backup` objects - that do not have a counterpart in the object store - typically because of - retention policies - -`backups/status` -: The instance manager requires to `update` and `patch` the status of any - `Backup` resource in the namespace - -### Pod and Container Security Contexts - -A [Security Context](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) -defines privilege and access control settings for a pod or container. - -{{name.ln}} does not require *privileged* mode for container execution. -The PostgreSQL containers run as the `postgres` system user. No component -whatsoever requires running as `root`. - -Likewise, Volume access does not require *privileged* mode nor `root` -privileges. Proper permissions must be assigned by the Kubernetes platform -and/or administrators. The PostgreSQL containers run with a read-only root -filesystem (i.e. no writable layer). - -The operator manages the setting of security contexts for all pods and -containers of a PostgreSQL cluster. The [Seccomp Profile](https://kubernetes.io/docs/tutorials/security/seccomp/) -to be used for the PostgreSQL containers can be configured with the -`spec.seccompProfile` section of the `Cluster` resource. If this section is left -blank, the containers will use a seccompProfile `Type` of `RuntimeDefault`, that -is, the container runtime default. - -The security context of PostgreSQL containers using the default `seccompProfile` -will look like this: - -``` -securityContext: - allowPrivilegeEscalation: false - capabilities: - drop: - - ALL - privileged: false - readOnlyRootFilesystem: true - runAsNonRoot: true - seccompProfile: - type: RuntimeDefault -``` - -#### Customizing Security Contexts - -{{name.ln}} provides fine-grained control over security contexts for both -pods and containers through the `spec.podSecurityContext` and -`spec.securityContext` fields respectively. - -!!! info Important - Changing security contexts can significantly affect the security posture - of your PostgreSQL clusters and may prevent pods from starting or - operating correctly. Before making changes, review which fields you will - override and how they merge with the operator defaults, test changes - in a non-production environment, and apply the minimal, well-documented - modifications necessary. - - -**Pod Security Context** (`spec.podSecurityContext`): -This allows you to override the default `PodSecurityContext` applied to all -PostgreSQL cluster pods. When specified, it will merge with the operator's -default settings, with your values taking precedence for explicitly set fields. - -Example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - podSecurityContext: - runAsUser: 26 - runAsGroup: 26 - fsGroup: 26 - supplementalGroups: [2000, 3000] - fsGroupChangePolicy: "OnRootMismatch" -``` - -**Container Security Context** (`spec.securityContext`): -This allows you to override the default `SecurityContext` applied to all -containers within the PostgreSQL cluster pods. Like `podSecurityContext`, it -merges with the operator's defaults. - -Example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example -spec: - instances: 3 - securityContext: - allowPrivilegeEscalation: false - # Note: capabilities are not merged with operator defaults. - # If specified, they fully replace any defaults. - capabilities: - drop: - - ALL - add: - - NET_BIND_SERVICE - readOnlyRootFilesystem: true - runAsNonRoot: true -``` - -!!! info Important - For any fields you don't explicitly set, the operator will apply its - secure defaults. This ensures that even partial configurations maintain - security best practices. - - -!!! note - These fields are particularly useful when working with the - [Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/) - `restricted` profile, which has strict requirements for pod and container - security contexts. As described in - [Kubernetes Admission Control](#kubernetes-admission-control), it is this - admission chain (not the operator) that enforces such profiles on the - resulting Pods. - - -#### Security Context Constraints - -When running in an environment that is utilizing -[Security Context Constraints (SCC)](https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html) -the operator does not explicitly set the security context of the PostgreSQL -cluster pods, but rather allows the pods to inherit the restricted Security -Context Constraints that are already defined. - -On Red Hat OpenShift, Cloud Native PostgreSQL runs in `restricted` security context constraint, -the most restrictive one. The goal is to limit the execution of a pod to a namespace allocated UID -and SELinux context. - -!!! Seealso "Security Context Constraints in OpenShift" - For further information on Security Context Constraints (SCC) in - OpenShift, please refer to the - ["Managing SCC in OpenShift"](https://www.openshift.com/blog/managing-sccs-in-openshift) - article. - -!!! Warning "Security Context Constraints and namespaces" - As stated by [Openshift documentation](https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html#role-based-access-to-ssc_configuring-internal-oauth) - SCCs are not applied in the default namespaces (`default`, `kube-system`, - `kube-public`, `openshift-node`, `openshift-infra`, `openshift`) and those - should not be used to run pods. CNP clusters deployed in those namespaces - will be unable to start due to missing SCCs. - -### Restricting Pod access using AppArmor - -You can assign an -[AppArmor](https://kubernetes.io/docs/tutorials/security/apparmor/) profile to -the `postgres`, `initdb`, `join`, `full-recovery` and `bootstrap-controller` containers inside every `Cluster` pod through the -`container.apparmor.security.beta.kubernetes.io` annotation. -For example: - -```yaml -kind: Cluster -metadata: - name: cluster-apparmor - annotations: - container.apparmor.security.beta.kubernetes.io/postgres: runtime/default - container.apparmor.security.beta.kubernetes.io/initdb: runtime/default - container.apparmor.security.beta.kubernetes.io/join: runtime/default -``` - -!!! Warning - Using this kind of annotations can result in your cluster to stop working. - If this is the case, the annotation can be safely removed from the `Cluster`. - -The AppArmor configuration must be at Kubernetes node level, meaning that the -underlying operating system must have this option enable and properly -configured. - -In case this is not the situation, and the annotations were added at the -`Cluster` creation time, pods will not be created. On the other hand, if you -add the annotations after the `Cluster` was created the pods in the cluster will -be unable to start and you will get an error like this: - -``` -metadata.annotations[container.apparmor.security.beta.kubernetes.io/postgres]: Forbidden: may not add AppArmor annotations] -``` - -In such cases, please refer to your Kubernetes administrators and ask for the proper AppArmor profile to use. - -!!! Warning "AppArmor and OpenShift" - AppArmor is currently available only on Debian distributions like Ubuntu, - hence this is not (and will not be) available in OpenShift - -### Network Policies - -The pods created by the `Cluster` resource can be controlled by Kubernetes -[network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) -to enable/disable inbound and outbound network access at IP and TCP level. -You can find more information in the [networking document](networking.md). - -!!! Important - The operator needs to communicate to each instance on TCP port 8000 - to get information about the status of the PostgreSQL server. Please - make sure you keep this in mind in case you add any network policy, - and refer to the "Exposed Ports" section below for a list of ports used by - {{name.ln}} for finer control. - -Network policies are beyond the scope of this document. -Please refer to the ["Network policies"](https://kubernetes.io/docs/concepts/services-networking/network-policies/) -section of the Kubernetes documentation for further information. - -#### Exposed Ports - -{{name.ln}} exposes ports at operator, instance manager and operand -levels, as listed in the table below: - -| System | Port number | Exposing | Name | TLS | Authentication | -|:-----------------|:------------|:--------------------|:-----------------|:---------|:---------------| -| operator | 9443 | webhook server | `webhook-server` | Yes | Yes | -| operator | 8080 | metrics | `metrics` | No | No | -| instance manager | 9187 | metrics | `metrics` | Optional | No | -| instance manager | 8000 | status | `status` | Yes | Partial (1) | -| operand | 5432 | PostgreSQL instance | `postgresql` | Optional | Yes | - -(1) Status, health, and probe endpoints are unauthenticated. Sensitive -endpoints (backup, `pg_controldata`, partial WAL archive, and instance-manager -upgrade) require the operator's client certificate, as described in -[Operator-to-instance authentication](#operator-to-instance-authentication) -below. - -#### Operator-to-instance authentication - -The operator generates a self-signed ECDSA client certificate in memory at -startup and publishes its SHA-256 public-key fingerprint in the cluster's -`.status.operatorCertificateFingerprint`. The instance manager pins that -fingerprint and rejects any call to its sensitive endpoints (backup, -`pg_controldata`, partial WAL archive, and instance-manager upgrade) that does -not present a matching certificate. Status, health, and probe endpoints remain -unauthenticated. - -The certificate is never written to disk and is regenerated on every operator -restart, so trust derives from fingerprint pinning rather than CA validation. - -This protection has a hard requirement: the status port **must** be served over -TLS, which has been the default since v1.24. A client certificate can only be -presented over a TLS connection, so the protected endpoints are reachable by the -operator only when the status port uses TLS. - -!!!warning -If the status port is not served over TLS, the instance manager cannot -authenticate the operator and **permanently** rejects every call to its -protected endpoints (backup, `pg_controldata`, partial WAL archive, and -instance-manager upgrade) with `401 Unauthorized`. This is not a transient -condition and will not resolve on its own. It can affect instances created by an -operator older than v1.24 (whose status port serves plain HTTP) once their -instance manager is upgraded to a version that enforces this authentication: such -instances must be rolled out so their Pods are recreated with a TLS-enabled status -port. Newly created instances always enable TLS on the status port and are -unaffected. -!!! - -### PostgreSQL - -The current implementation of {{name.ln}} automatically creates -passwords and `.pgpass` files for the database owner and, only -if requested by setting `enableSuperuserAccess` to `true`, for the -`postgres` superuser. - -!!! Warning - `enableSuperuserAccess` is set to `false` by default to improve the - security-by-default posture of the operator, fostering a microservice approach - where changes to PostgreSQL are performed in a declarative way through the - `spec` of the `Cluster` resource, while providing developers with full powers - inside the database through the database owner user. - -As far as password encryption is concerned, {{name.ln}} follows -the default behavior of PostgreSQL: starting from PostgreSQL 14, -`password_encryption` is by default set to `scram-sha-256`, while on earlier -versions it is set to `md5`. - -!!! Important - Please refer to the ["Password authentication"](https://www.postgresql.org/docs/current/auth-password.html) - section in the PostgreSQL documentation for details. - -!!! Note - The operator supports toggling the `enableSuperuserAccess` option. When you - disable it on a running cluster, the operator will ignore the content of the secret, - remove it (if previously generated by the operator) and set the password of the - `postgres` user to `NULL` (de facto disabling remote access through password authentication). - -!!! info Important - PostgreSQL may include cleartext role passwords in its logs for some role - operations, as mentioned in the [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-createrole.html). - {{name.ln}} ensures that `postgres` logging (both statement logging and - error statement logging) is temporarily suppressed for CREATE/ALTER ROLE - operations with passwords, thus preventing any password leakage. - -See the ["Secrets" section in the "Connecting from an application" page](applications.md#secrets) for more information. - -You can use those files to configure application access to the database. - -By default, every replica is automatically configured to connect in **physical -async streaming replication** with the current primary instance, with a special -user called `streaming_replica`. The connection between nodes is **encrypted** -and authentication is via **TLS client certificates** (please refer to the -["Client TLS/SSL Connections"](ssl_connections.md) page -for details). By default, the operator requires TLS v1.3 connections. - -Currently, the operator allows administrators to add `pg_hba.conf` lines directly in the manifest -as part of the `pg_hba` section of the `postgresql` configuration. The lines defined in the -manifest are added to a default `pg_hba.conf`. - -For further detail on how `pg_hba.conf` is managed by the operator, see the -["PostgreSQL Configuration" page](postgresql_conf.md#the-pg_hba-section) of the documentation. - -The administrator can also customize the content of the `pg_ident.conf` file that by default -only maps the local postgres user to the postgres user in the database. - -For further detail on how `pg_ident.conf` is managed by the operator, see the -["PostgreSQL Configuration" page](postgresql_conf.md#the-pg_ident-section) of the documentation. - -!!! Important - Examples assume that the Kubernetes cluster runs in a private and secure network. - -#### Schema resolution and `search_path` hardening - -A user with privileges on a database can plant objects (functions, -operators, tables, or types) in a writable schema such as `public` and -change the database- or role-level `search_path` (for example with -`ALTER DATABASE ... SET search_path` or `ALTER ROLE ... SET -search_path`). A privileged session that later connects to that database -inherits the tenant-controlled `search_path`, so an unqualified -reference in one of its queries could resolve to the planted object -instead of the intended one. This is a privilege-escalation vector -analogous to -[CWE-426 (Untrusted Search Path)](https://cwe.mitre.org/data/definitions/426.html), -and the same class of issue as the well-known -[CVE-2018-1058](https://www.postgresql.org/support/security/CVE-2018-1058/). - -To prevent this, {{name.ln}} pins the `search_path` on every -connection it opens to PostgreSQL to a fixed value of -`pg_catalog, public, pg_temp`, regardless of any `search_path` -configured on the database or the connecting role: - -- `pg_catalog` is searched first, so a built-in object always takes - precedence over a same-named object planted in another schema; -- `pg_temp` (the session-private temporary schema) is searched last - rather than first, so it cannot shadow relations or data types. - -In addition, the `SECURITY DEFINER` lookup function used by the -PgBouncer integration is created with its own pinned `search_path`, and -the monitoring queries run inside a transaction whose `search_path` is -pinned as described in the ["Monitoring" page](monitoring.md). - -!!!note -User-authored SQL — `postInitSQL`/`postInitApplicationSQL`/`postInitTemplateSQL` -during bootstrap, and the post-import queries of a logical import — runs -with the standard `"$user", public` resolution so that it keeps behaving -as it would in a plain PostgreSQL session. Schema-qualify object -references in those scripts if you need them to be independent of the -`search_path`. -!!! - -### Storage - -{{name.ln}} delegates encryption at rest to the underlying storage class. For -data protection in production environments, we highly recommend that you choose -a storage class that supports encryption at rest. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/service_management.mdx b/product_docs/docs/postgres_for_kubernetes/preview/service_management.mdx deleted file mode 100644 index 852e8e95b7b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/service_management.mdx +++ /dev/null @@ -1,143 +0,0 @@ ---- -title: 'Service management' -originalFilePath: 'src/service_management.md' ---- - - - -A PostgreSQL cluster should only be accessed via standard Kubernetes network -services directly managed by {{name.ln}}. For more details, refer to the -["Service" page of the Kubernetes Documentation](https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies). - -{{name.ln}} defines three types of services for each `Cluster` resource: - -- `rw`: Points to the primary instance of the cluster (read/write). -- `ro`: Points to the replicas, where available (read-only). -- `r`: Points to any PostgreSQL instance in the cluster (read). - -By default, {{name.ln}} creates all the above services for a `Cluster` -resource, with the following conventions: - -- The name of the service follows this format: `-`. -- All services are of type `ClusterIP`. - -!!!info Important -Default service names are reserved for {{name.ln}} usage. -!!! - -While this setup covers most use cases for accessing PostgreSQL within the same -Kubernetes cluster, {{name.ln}} offers flexibility to: - -- Disable the creation of the `ro` and/or `r` default services. -- Define your own services using the standard `Service` API provided by - Kubernetes. - -You can mix these two options. - -A common scenario arises when using {{name.ln}} in database-as-a-service -(DBaaS) contexts, where access to the database from outside the Kubernetes -cluster is required. In such cases, you can create your own service of type -`LoadBalancer`, if available in your Kubernetes environment. - -## Disabling Default Services - -You can disable any or all of the `ro` and `r` default services through the -[`managed.services.disabledDefaultServices` option](pg4k.v1.md#managedservices). - -!!!info Important -The `rw` service is essential and cannot be disabled because {{name.ln}} -relies on it to ensure PostgreSQL replication. -!!! - -For example, if you want to remove both the `ro` (read-only) and `r` (read) -services, you can use this configuration: - -```yaml -# -managed: - services: - disabledDefaultServices: ["ro", "r"] -``` - -## Adding Your Own Services - -!!!info Important -When defining your own services, you cannot use any of the default reserved -service names that follow the convention `-`. It is -your responsibility to pick a unique name for the service in the Kubernetes -namespace. -!!! - -You can define a list of additional services through the -[`managed.services.additional` stanza](pg4k.v1.md#managedservice) -by specifying the service type (e.g., `rw`) in the `selectorType` field -and optionally the `updateStrategy`. - -The `serviceTemplate` field gives you access to the standard Kubernetes API for -the network `Service` resource, allowing you to define both the `metadata` and -the `spec` sections as you like. - -You must provide a `name` to the service and avoid defining the `selector` -field, as it is managed by the operator. - -!!!warning -Service templates give you unlimited possibilities in terms of configuring -network access to your PostgreSQL database. This translates into greater -responsibility on your end to ensure that services work as expected. -{{name.ln}} has no control over the service configuration, except honoring -the selector. -!!! - -The `updateStrategy` field allows you to control how the operator -updates a service definition. By default, the operator uses the `patch` -strategy, applying changes directly to the service. -Alternatively, the `replace` strategy deletes the existing service and -recreates it from the template. - -!!!warning -The `replace` strategy will cause a service disruption with every -change. However, it may be necessary for modifying certain -parameters that can only be set during service creation. -!!! - -For example, if you want to have a single `LoadBalancer` service for your -PostgreSQL database primary, you can use the following excerpt: - -```yaml -# -managed: - services: - additional: - - selectorType: rw - serviceTemplate: - metadata: - name: "mydb-lb" - labels: - test-label: "true" - annotations: - test-annotation: "true" - spec: - type: LoadBalancer -``` - -The above example also shows how to set metadata such as annotations and labels -for the created service. - -### About Exposing Postgres Services - -There are primarily three use cases for exposing your PostgreSQL service -outside your Kubernetes cluster: - -- Temporarily, for testing. -- Permanently, for **DBaaS purposes**. -- Prolonged period/permanently, for **legacy applications** that cannot be - easily or sustainably containerized and need to reside in a virtual machine - or physical machine outside Kubernetes. This use case is very similar to DBaaS. - -Be aware that allowing access to a database from the public network could -expose your database to potential attacks from malicious users. - -!!!warning -Ensure you secure your database before granting external access, or make -sure your Kubernetes cluster is only reachable from a private network. -!!! diff --git a/product_docs/docs/postgres_for_kubernetes/preview/ssl_connections.mdx b/product_docs/docs/postgres_for_kubernetes/preview/ssl_connections.mdx deleted file mode 100644 index e569bff942b..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/ssl_connections.mdx +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: 'Client TLS/SSL connections' -originalFilePath: 'src/ssl_connections.md' ---- - - - -!!!note Certificates -See [Certificates](certificates.md) -for more details on how {{name.ln}} supports TLS certificates. -!!! - -The {{name.ln}} operator was designed to work with TLS/SSL for both -encryption in transit and authentication on the server and client sides. -Clusters created using the CNP operator come with a certification authority -(CA) to create and sign TLS client certificates. Using the cnp plugin for -kubectl, you can issue a new TLS client certificate for authenticating a user -instead of using passwords. - -These instructions for authenticating using TLS/SSL certificates assume you -installed a cluster using the -[cluster-example-pg-hba.yaml](../samples/cluster-example-pg-hba.yaml) manifest. -According to the convention-over-configuration paradigm, that file creates an -`app` database that's owned by a user called app. (You can change this -convention by way of the `initdb` configuration in the `bootstrap` section.) - -## Issuing a new certificate - -!!!note About CNP plugin for kubectl -See the [Certificates in the {{name.ln}} plugin](kubectl-plugin.md#certificates) -content for details on how to use the plugin for kubectl. -!!! - -You can create a certificate for the app user in the `cluster-example` -PostgreSQL cluster as follows: - -```shell -kubectl cnp certificate cluster-app \ - --cnp-cluster cluster-example \ - --cnp-user app -``` - -You can now verify the certificate: - -```shell -kubectl get secret cluster-app \ - -o jsonpath="{.data['tls\.crt']}" \ - | base64 -d | openssl x509 -text -noout \ - | head -n 11 -``` - -Output: - -```console - -Certificate: - Data: - Version: 3 (0x2) - Serial Number: - 5d:e1:72:8a:39:9f:ce:51:19:9d:21:ff:1e:4b:24:5d - Signature Algorithm: ecdsa-with-SHA256 - Issuer: OU = default, CN = cluster-example - Validity - Not Before: Mar 22 10:22:14 2021 GMT - Not After : Mar 22 10:22:14 2022 GMT - Subject: CN = app -``` - -As you can see, TLS client certificates by default are created with 90 days of -validity, and with a simple CN that corresponds to the username in PostgreSQL. -You can specify the validity and threshold values using the -`EXPIRE_CHECK_THRESHOLD` and `CERTIFICATE_DURATION` parameters. This is -necessary to leverage the `cert` authentication method for `hostssl` entries in -`pg_hba.conf`. - -## Testing the connection via a TLS certificate - -Next, test this client certificate by configuring a demo client application -that connects to your {{name.ln}} cluster. - -The following manifest, called `cert-test.yaml`, creates a demo pod with a test -application in the same namespace where your database cluster is running: - -```yaml -apiVersion: apps/v1 -kind: Deployment -metadata: - name: cert-test -spec: - replicas: 1 - selector: - matchLabels: - app: webtest - template: - metadata: - labels: - app: webtest - spec: - containers: - - image: ghcr.io/cloudnative-pg/webtest:1.7.0 - name: cert-test - volumeMounts: - - name: secret-volume-root-ca - mountPath: /etc/secrets/ca - - name: secret-volume-app - mountPath: /etc/secrets/app - ports: - - containerPort: 8080 - env: - - name: DATABASE_URL - value: > - sslkey=/etc/secrets/app/tls.key - sslcert=/etc/secrets/app/tls.crt - sslrootcert=/etc/secrets/ca/ca.crt - host=cluster-example-rw.default.svc - dbname=app - user=app - sslmode=verify-full - - name: SQL_QUERY - value: SELECT 1 - readinessProbe: - httpGet: - port: 8080 - path: /tx - volumes: - - name: secret-volume-root-ca - secret: - secretName: cluster-example-ca - defaultMode: 0600 - - name: secret-volume-app - secret: - secretName: cluster-app - defaultMode: 0600 -``` - -This pod mounts secrets managed by the {{name.ln}} operator, including: - -- `sslcert` – The TLS client public certificate. -- `sslkey` – The TLS client certificate private key. -- `sslrootcert` – The TLS CA certificate that signed the certificate on - the server to use to verify the identity of the instances. - -They're used to create the default resources that psql (and other libpq-based -applications, like pgbench) requires to establish a TLS-encrypted connection to -the Postgres database. - -By default, psql searches for certificates in the `~/.postgresql` directory of -the current user, but you can use the `sslkey`, `sslcert`, and `sslrootcert` -options to point libpq to the actual location of the cryptographic material. -The content of these files is gathered from the secrets that were previously -created by using the cnp plugin for kubectl. - -Deploy the application: - -```shell -kubectl create -f cert-test.yaml -``` - -Then use the created pod as the PostgreSQL client to validate the SSL -connection and authentication using the TLS certificates you just created. - -A readiness probe was configured to ensure that the application is ready when -the database server can be reached. - -You can verify that the connection works. To do so, execute an interactive -`bash` inside the pod's container to run psql using the necessary options. The -PostgreSQL server is exposed through the read-write Kubernetes service. Point -the psql command to connect to this service: - -```shell -kubectl exec -it cert-test -- bash -c "psql -'sslkey=/etc/secrets/app/tls.key sslcert=/etc/secrets/app/tls.crt -sslrootcert=/etc/secrets/ca/ca.crt host=cluster-example-rw.default.svc dbname=app -user=app sslmode=verify-full' -c 'select version();'" -``` - -Output: - -```console - version --------------------------------------------------------------------------------------- ------------------- -PostgreSQL 18.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat -8.3.1-5), 64-bit -(1 row) -``` - -## About TLS protocol versions - -By default, the operator sets both [`ssl_min_protocol_version`](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-SSL-MIN-PROTOCOL-VERSION) -and [`ssl_max_protocol_version`](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-SSL-MAX-PROTOCOL-VERSION) -to `TLSv1.3`. - -This assumes that the PostgreSQL operand images include an OpenSSL library that -supports the `TLSv1.3` version. If not, or if your client applications need a -lower version number, you need to manually configure it in the PostgreSQL -configuration as any other Postgres GUC. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/storage.mdx b/product_docs/docs/postgres_for_kubernetes/preview/storage.mdx deleted file mode 100644 index 1b365d3ad3d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/storage.mdx +++ /dev/null @@ -1,488 +0,0 @@ ---- -title: 'Storage' -originalFilePath: 'src/storage.md' ---- - - - -Storage is the most critical component in a database workload. -Storage must always be available, scale, perform well, -and guarantee consistency and durability. The same expectations and -requirements that apply to traditional environments, such as virtual machines -and bare metal, are also valid in container contexts managed by Kubernetes. - -!!!info Important -When it comes to dynamically provisioned storage, -Kubernetes has its own specifics. These include *storage classes*, *persistent -volumes*, and *Persistent Volume Claims (PVCs)*. You need to own these -concepts, on top of all the valuable knowledge you've built over -the years in terms of storage for database workloads on VMs and -physical servers. -!!! - -There are two primary methods of access to storage: - -- **Network** – Either directly or indirectly. (Think of an NFS volume locally - mounted on a host running Kubernetes.) -- **Local** – Directly attached to the node where a pod is running. This also - includes directly attached disks on bare metal installations of Kubernetes. - -Network storage, which is the most common usage pattern in Kubernetes, -presents the same issues of throughput and latency that you can -experience in a traditional environment. These issues can be accentuated in -a shared environment, where I/O contention with several applications -increases the variability of performance results. - -Local storage enables shared-nothing architectures, which is more suitable -for high transactional and very large database (VLDB) workloads, as it -guarantees higher and more predictable performance. - -!!!warning -Before you deploy a PostgreSQL cluster with {{name.ln}}, -ensure that the storage you're using is recommended for database -workloads. We recommend clearly setting performance expectations by -first benchmarking the storage using tools such as [fio](https://fio.readthedocs.io/en/latest/fio_doc.html) -and then the database using [pgbench](https://www.postgresql.org/docs/current/pgbench.html). -!!! - -!!!info -{{name.ln}} doesn't use `StatefulSet` for managing data persistence. -Rather, it manages PVCs directly. If you want -to know more, see -[Custom pod controller](controller.md). -!!! - -## Backup and recovery - -Since {{name.ln}} supports volume snapshots for both backup and recovery, -we recommend that you also consider this aspect when you choose your storage -solution, especially if you manage very large databases. - -!!!info Important -See the Kubernetes documentation for a list of all -the supported [container storage interface (CSI) drivers](https://kubernetes-csi.github.io/docs/drivers.html) -that provide snapshot capabilities. -!!! - -## Benchmarking {{name.ln}} - -Before deploying the database in production, we recommend that you benchmark -{{name.ln}} in a controlled Kubernetes environment. Follow the guidelines in -[Benchmarking](benchmarking.md). - -Briefly, we recommend operating at two levels: - -- Measuring the performance of the underlying storage using fio, with relevant - metrics for database workloads such as throughput for sequential reads, sequential - writes, random reads, and random writes -- Measuring the performance of the database using pgbench, the default benchmarking tool - distributed with PostgreSQL - -!!!info Important -You must measure both the storage and database performance before putting -the database into production. These results are extremely valuable not just in -the planning phase (for example, capacity planning). They are also valuable in -the production lifecycle, particularly in emergency situations when you don't -have time to run this kind of test. Databases change and evolve over time, and -so does the distribution of data, potentially affecting performance. Knowing -the theoretical maximum throughput of sequential reads or writes is extremely -useful in those situations. This is true especially in shared-nothing contexts, -where results don't vary due to the influence of external workloads. - -Know your system: benchmark it. -!!! - -## Encryption at rest - -Encryption at rest is possible with {{name.ln}}. The operator delegates that -to the underlying storage class. See the storage class for -information about this important security feature. - -## Persistent Volume Claim (PVC) - -The operator creates a PVC for each PostgreSQL instance, with the goal of -storing the `PGDATA`. It then mounts it into each pod. - -Additionally, it supports creating clusters with: - -- A separate PVC on which to store PostgreSQL WAL, as explained in - [Volume for WAL](#volume-for-wal) -- Additional separate volumes reserved for PostgreSQL tablespaces, as explained - in [Tablespaces](tablespaces.md) - -In {{name.ln}}, the volumes attached to a single PostgreSQL instance are -defined as a *PVC group*. - -## Configuration via a storage class - -!!!info Important -{{name.ln}} was designed to work interchangeably with all storage classes. -As usual, we recommend properly benchmarking the storage class in a -controlled environment before deploying to production. -!!! - -The easiest way to configure the storage for a PostgreSQL class is to request -storage of a certain size, like in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-storage-class -spec: - instances: 3 - storage: - size: 1Gi -``` - -Using the previous configuration, the generated PVCs are satisfied by the -default storage class. If the target Kubernetes cluster has no default storage -class, or even if you need your PVCs to be satisfied by a known storage class, -you can set it into the custom resource: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-storage-class -spec: - instances: 3 - storage: - storageClass: standard - size: 1Gi -``` - -## Configuration via a PVC template - -To further customize the generated PVCs, you can provide a PVC template inside the custom resource, -like in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-pvc-template -spec: - instances: 3 - - storage: - pvcTemplate: - accessModes: - - ReadWriteOnce - resources: - requests: - storage: 1Gi - storageClassName: standard - volumeMode: Filesystem -``` - -## Volume for WAL - -By default, PostgreSQL stores all its data in the so-called `PGDATA` (a -directory). One of the core directories inside `PGDATA` is `pg_wal`, which -contains the log of transactional changes that occurred in the database, in the -form of segment files. (`pg_wal` is historically known as `pg_xlog` in -PostgreSQL.) - -!!!info -Normally, each segment is 16MB in size, but you can configure the size -using the `walSegmentSize` option. This option is applied at cluster -initialization time, as described in -[Bootstrap an empty cluster](bootstrap.md#bootstrap-an-empty-cluster-initdb). -!!! - -In most cases, having `pg_wal` on the same volume where `PGDATA` -resides is fine. However, having WALs stored in a separate -volume has a few benefits: - -- **I/O performance** – By storing WAL files on different storage from `PGDATA`, - PostgreSQL can exploit parallel I/O for WAL operations (normally - sequential writes) and for data files (tables and indexes for example), thus - improving vertical scalability. - -- **More reliability** – By reserving dedicated disk space to WAL files, you - can be sure that exhausting space on the `PGDATA` volume - never interferes with WAL writing. This behavior ensures that your PostgreSQL primary - is correctly shut down. - -- **Finer control** – You can define the amount of space dedicated to both - `PGDATA` and `pg_wal`, fine tune [WAL - configuration](https://www.postgresql.org/docs/current/wal-configuration.html) - and checkpoints, and even use a different storage class for cost optimization. - -- **Better I/O monitoring** – You can constantly monitor the load and disk usage - on both `PGDATA` and `pg_wal`. You can also set alerts that notify you in case, - for example, `PGDATA` requires resizing. - -!!!note Write-Ahead Log (WAL) -See [Reliability and the Write-Ahead Log](https://www.postgresql.org/docs/current/wal.html) -in the PostgreSQL documentation for more information. -!!! - -You can add a separate volume for WAL using the `.spec.walStorage` option. -It follows the same rules described for the `storage` field and provisions a -dedicated PVC. For example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: separate-pgwal-volume -spec: - instances: 3 - storage: - size: 1Gi - walStorage: - size: 1Gi -``` - -!!!info Important -Removing `walStorage` isn't supported. Once added, a separate volume for -WALs can't be removed from an existing Postgres cluster. -!!! - -## Volumes for tablespaces - -{{name.ln}} supports declarative tablespaces. You can add one or more -volumes, each dedicated to a single PostgreSQL tablespace. -See [Tablespaces](tablespaces.md) for details. - -## Volume expansion - -Kubernetes exposes an API allowing [expanding PVCs](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims) -that's enabled by default. However, it needs to be supported by the underlying `StorageClass`. - -To check if a certain `StorageClass` supports volume expansion, you can read the `allowVolumeExpansion` -field for your storage class: - -``` -$ kubectl get storageclass -o jsonpath='{$.allowVolumeExpansion}' premium-storage -true -``` - -### Using the volume expansion Kubernetes feature - -Given the storage class supports volume expansion, you can change the size -requirement of the `Cluster`, and the operator applies the change to every PVC. - -If the `StorageClass` supports [online volume resizing](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#resizing-an-in-use-persistentvolumeclaim), -the change is immediately applied to the pods. If the underlying storage class -doesn't support that, you must delete the pod to trigger the resize. - -The best way to proceed is to delete one pod at a time, starting from replicas -and waiting for each pod to be back up. - -### Re-creating storage - -If the storage class doesn't support volume expansion, you can still regenerate -your cluster on different PVCs. Allocate new PVCs with increased storage and -then move the database there. This operation is feasible only when the cluster -contains more than one node. - -While you do that, you need to prevent the operator from changing the existing -PVC by disabling the `resizeInUseVolumes` flag, like in the following example: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: postgresql-pvc-template -spec: - instances: 3 - - storage: - storageClass: standard - size: 1Gi - resizeInUseVolumes: False -``` - -To move the entire cluster to a different storage area, you need to re-create -all the PVCs and all the pods. Suppose you have a cluster with three replicas, -like in the following example: - -``` -$ kubectl get pods -NAME READY STATUS RESTARTS AGE -cluster-example-1 1/1 Running 0 2m37s -cluster-example-2 1/1 Running 0 2m22s -cluster-example-3 1/1 Running 0 2m10s -``` - -To re-create the cluster using different PVCs, you can edit the cluster -definition to disable `resizeInUseVolumes`. Then re-create every instance in a -different PVC. - -For example, re-create the storage for `cluster-example-3`: - -``` -$ kubectl delete pvc/cluster-example-3 pod/cluster-example-3 -``` - -!!!info Important -If you created a dedicated WAL volume, both PVCs must be deleted during -this process. The same procedure applies if you want to regenerate the WAL -volume PVC. You can do this by also disabling `resizeInUseVolumes` for the -`.spec.walStorage` section. -!!! - -For example, if a PVC dedicated to WAL storage is present: - -``` -$ kubectl delete pvc/cluster-example-3 pvc/cluster-example-3-wal pod/cluster-example-3 -``` - -Having done that, the operator orchestrates creating another replica with a -resized PVC: - -``` -$ kubectl get pods -NAME READY STATUS RESTARTS AGE -cluster-example-1 1/1 Running 0 5m58s -cluster-example-2 1/1 Running 0 5m43s -cluster-example-3-join-v2 0/1 Completed 0 17s -cluster-example-3 1/1 Running 0 10s -``` - -## Volume reduction - -Kubernetes does not provide an API to shrink a PVC, and {{name.ln}}' -validating webhook rejects any attempt to decrease `.spec.storage.size`, -`.spec.walStorage.size` or any tablespace storage size in `.spec.tablespaces`. -You can still reduce the storage of a cluster, but only by recreating -each instance with a smaller volume, as described below. - -!!!warning - -{{name.ln}} does not support automated volume shrinking, as it is a -delicate operation that can lead to data loss if performed incorrectly. For -the time being, it can only be achieved manually, through the supervised -procedure described below. -This procedure requires you to temporarily disable the validating webhook. -While validation is disabled, the operator accepts spec changes that would -normally be rejected, including unsafe or destructive ones. Proceed with -caution and at your own risk, and re-enable validation as soon as possible. - -Before you start, make sure the cluster's current data, WAL, and any tablespace -data comfortably fit within the new, smaller sizes. If they don't, the instances -recreated on smaller volumes can fail to rejoin or quickly run out of space. -!!! - -To reduce the size of the persistent volumes: - -1. Disable the validating webhook by setting the `k8s.enterprisedb.io/validation: disabled` - annotation on the `Cluster`, set `.spec.storage.size` (and, if present, - `.spec.walStorage.size` or tablespace storage size in `.spec.tablespaces`) - to the new, smaller value, and increase `.spec.instances` by 1 to provide a - spare instance during the rollout. - -2. Re-enable validation by removing the `k8s.enterprisedb.io/validation` annotation (or - setting it to `enabled`). The new, smaller size is now stored in the spec - and is applied to every instance the operator recreates from this point on. - Existing instances keep their current volumes; for each one, the operator - logs an informational `cannot decrease storage requirement` message until - that instance is recreated. This is expected and harmless. - -3. Destroy one standby that still has a volume of the old size. The operator - provisions a replacement instance — reusing the name of the one you - destroyed, since instance serials are recycled — on the new, smaller volume: - - ```sh - kubectl-cnp destroy CLUSTER INSTANCE - ``` - -4. Wait for the operator to create the replacement instance and for it to - become healthy. - -5. Repeat steps 3 and 4 for every remaining standby that still has an - old-size volume. - -6. Promote one of the newly created standbys so that the current primary — - which still has an old-size volume — is demoted to a standby: - - ```sh - kubectl-cnp promote CLUSTER INSTANCE - ``` - -7. Destroy the former primary (now a standby with an old-size volume) so the - operator provisions its replacement on the new, smaller volume, and wait - until all instances are healthy. - -8. Decrease `.spec.instances` back to its original value. - -## Static provisioning of persistent volumes - -{{name.ln}} was designed to work with dynamic volume provisioning. This -capability allows storage volumes to be created on demand when requested by -users by way of storage classes and PVC templates. -See [Re-creating storage](#re-creating-storage). - -However, in some cases, Kubernetes administrators prefer to manually create -storage volumes and then create the related `PersistentVolume` objects for -their representation inside the Kubernetes cluster. This is also known as -*pre-provisioning* of volumes. - -!!!info Important -We recommend that you avoid pre-provisioning volumes, as it has an effect -on the high availability and self-healing capabilities of the operator. It -breaks the fully declarative model on which {{name.ln}} was built. -!!! - -To use a pre-provisioned volume in {{name.ln}}: - -1. Manually create the volume outside Kubernetes. -2. Create the `PersistentVolume` object to match this volume using the - correct parameters as required by the actual CSI driver (that is, `volumeHandle`, - `fsType`, `storageClassName`, and so on). -3. Create the Postgres `Cluster` using, for each storage section, a coherent - [`pvcTemplate`](storage.md#configuration-via-a-pvc-template) - section that can help Kubernetes match the `PersistentVolume` - and enable {{name.ln}} to create the needed `PersistentVolumeClaim`. - -!!!warning -With static provisioning, it's your responsibility to ensure that Postgres -pods can be correctly scheduled by Kubernetes where a pre-provisioned volume -exists. (The scheduling configuration is based on the affinity rules of your -cluster.) Make sure you check for any pods stuck in `Pending` after you deploy -the cluster. If the condition persists, investigate why it's happening. -!!! - -## Block storage considerations (Ceph/Longhorn) - -Most block storage solutions in Kubernetes, such as Longhorn and Ceph, -recommend having multiple replicas of a volume to enhance resiliency. This -approach works well for workloads that lack built-in resiliency. - -However, {{name.ln}} integrates this resiliency directly into the Postgres -`Cluster` through the number of instances and the persistent volumes attached -to them, as explained in ["Synchronizing the state"](architecture.md#synchronizing-the-state). - -As a result, defining additional replicas at the storage level can lead to -write amplification, unnecessarily increasing disk I/O and space usage. - -For {{name.ln}} usage, consider reducing the number of replicas at the block storage -level to one, while ensuring that no single point of failure (SPoF) exists at -the storage level for the entire `Cluster` resource. This typically means -ensuring that a single storage host—and ultimately, a physical disk—does not -host blocks from different instances of the same `Cluster`, in alignment with -the broader *shared-nothing architecture* principle. - -In Longhorn, you can mitigate this risk by enabling strict-local data locality -when creating a custom storage class. Detailed instructions for creating a -volume with strict-local data locality are available [here](https://longhorn.io/docs/1.7.0/high-availability/data-locality/). -This setting ensures that a pod’s data volume resides on the same node as the -pod itself. - -Additionally, your Postgres `Cluster` should have [pod anti-affinity rules](scheduling.md#isolating-postgresql-workloads) -in place to ensure that the operator deploys pods across different nodes, -allowing Longhorn to place the data volumes on the corresponding hosts. If -needed, you can manually relocate volumes in Longhorn by temporarily setting -the volume replica count to 2, reducing it afterward, and then removing the old -replica. If a host becomes corrupted, you can use the [`cnp` plugin to destroy](kubectl-plugin.md#destroy) -the affected instance. {{name.ln}} will then recreate the instance on another -host and replicate the data. - -In Ceph, this can be configured through CRUSH rules. The documentation for -configuring CRUSH rules is available -[here](https://rook.io/docs/rook/latest-release/CRDs/Cluster/external-cluster/topology-for-external-mode/?h=topology). -These rules aim to ensure one volume per pod per node. You can also relocate -volumes by importing them into a different pool. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/tablespaces.mdx b/product_docs/docs/postgres_for_kubernetes/preview/tablespaces.mdx deleted file mode 100644 index db2f4488626..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/tablespaces.mdx +++ /dev/null @@ -1,370 +0,0 @@ ---- -title: 'Tablespaces' -originalFilePath: 'src/tablespaces.md' ---- - - - -A tablespace is a robust and widely embraced feature in database -management systems. It offers a powerful means to enhance the vertical -scalability of a database by decoupling the physical and logical modeling of -data. Essentially, it serves as a technique for physical database modeling, -enabling the efficient distribution of I/O operations across multiple volumes -on distinct storage. It thereby optimizes performance through parallel on-disk -read/write operations. - -In the context of the database industry, tablespaces play a strategic role, -particularly when paired with table partitioning, a logical database modeling -technique. They prove instrumental in managing large-scale databases and are -also used for tasks such as separating tables from indexes or executing -temporary operations. - -Tablespaces in PostgreSQL have been playing a pivotal role since 2005 (version -8.0), while declarative partitioning was introduced in 2017 (version 10). -Consequently, tablespaces are seamlessly integrated into all supported releases -of PostgreSQL. Quoting from the -[PostgreSQL documentation on tablespaces](https://www.postgresql.org/docs/current/manage-ag-tablespaces.html): - -> By using tablespaces, an administrator can control the disk layout of a -> PostgreSQL installation. This is useful in at least two ways. -> -> - First, if the partition or volume on which the cluster was initialized runs -> out of space and cannot be extended, a tablespace can be created on a -> different partition and used until the system can be reconfigured. -> - Second, tablespaces allow an administrator to use knowledge of the usage -> pattern of database objects to optimize performance. - -## Declarative tablespaces - -{{name.ln}} provides support for PostgreSQL tablespaces through *declarative -tablespaces*, operating at two distinct levels: - -- Kubernetes, managing persistent volume claims, identically to how PGDATA and - WAL volumes are handled -- PostgreSQL, managing the `TABLESPACE` global objects in the PostgreSQL - instance - -Being a part of the Kubernetes ecosystem, {{name.ln}}' declarative -tablespaces are implemented by leveraging persistent volume claims (and persistent -volumes). Each tablespace defined in the cluster is housed in its own -persistent volume. {{name.ln}} takes care of generating the PVCs. It mounts -the required volumes in the instance pods in normalized locations and ensures -replicas are ready to support tablespaces before activating them in the -primary. - -You can set up tablespaces when creating the cluster or add them later, -provided the storage is available when requested. Currently, you can't -remove them. However, this limitation will be addressed in a future minor or patch version -of {{name.ln}}. - -## Using declarative tablespaces - -Using declarative tablespaces is straightforward. You can find a full example in -[`cluster-example-with-tablespaces.yaml`](../samples/cluster-example-with-tablespaces.yaml). - -To use them, use the new `tablespaces` stanza on a new or existing `Cluster` resource: - -```yaml -spec: - instances: 3 - - # ... - - tablespaces: - - name: tbs1 - storage: - size: 1Gi - - name: tbs2 - storage: - size: 2Gi - - name: tbs3 - storage: - size: 2Gi -``` - -Each tablespace has its own storage section where you can configure the size and the -storage class of the generated PVC. The administrator can thus -plan to use different storage classes for different kinds of workloads, as -explained in [Storage classes and tablespaces](#storage-classes-and-tablespaces). - -{{name.ln}} creates the persistent volume claims for each instance -in the high-availability Postgres cluster. It mounts them in each pod when they -have been provisioned. Then, it ensures that the `tbs1`, `tbs2`, and `tbs3` -tablespaces are created on the primary PostgreSQL instance using the `CREATE -TABLESPACE` command. This process is quick, and you see this reflected in -Postgres: - -```txt -app=# SELECT oid, spcname FROM pg_tablespace; - oid | spcname --------+-------------------- - 1663 | pg_default - 1664 | pg_global - 16387 | tbs1 - 16388 | tbs2 - 16389 | tbs3 -(5 rows) -``` - -You can start using them right away: - -```txt -app=# CREATE TABLE fibonacci(num INTEGER) TABLESPACE tbs1; -CREATE TABLE -``` - -The cluster status has a section for tablespaces: - -```yaml -status: - - <- snipped -> - tablespacesStatus: - - name: atablespace - state: reconciled - - name: another_tablespace - state: reconciled - - name: tablespacea1 - state: reconciled -``` - -## Storage classes and tablespaces - -You can use different storage classes for your tablespaces, just as you can for PGDATA and -WAL volumes. This is a convenient way of optimizing your resources, -balancing performance and costs of your storage based on data access usage and -expectations. - -This example helps to explain the feature: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: yardbirds -spec: - instances: 3 - - storage: - size: 10Gi - walStorage: - size: 10Gi - tablespaces: - - name: current - storage: - size: 100Gi - storageClass: fastest - - name: this_year - storage: - size: 500Gi - storageClass: balanced -``` - -The `yardbirds` cluster example requests 4 persistent volume claims using -3 different storage classes: - -- Default storage class – Used by the `PGDATA` and WAL volumes. -- `fastest` – Used by the `current` tablespace to store the most active and - demanding set of data in the database. -- `balanced` – Used by the `this_year` tablespace to store older partitions of - data that are rarely accessed by users and where performance expectations - aren't the highest. - -You can then take advantage of horizontal table partitioning and create -the current month's table (for example, facts for December 2023) in the `current` -tablespace: - -```sql -CREATE TABLE facts_202312 PARTITION OF facts - FOR VALUES FROM ('2023-12-01') TO ('2024-01-01') - TABLESPACE current; -``` - -!!!info Important -This example assumes you're familiar with -[PostgreSQL declarative partitioning](https://www.postgresql.org/docs/current/ddl-partitioning.html). -!!! - -## Tablespace ownership - -By default, unless otherwise specified, tablespaces are owned by the `app` -application user, as defined in `.spec.bootstrap.initdb.owner`. See -[Bootstrap a new cluster](bootstrap.md#bootstrap-an-empty-cluster-initdb) for -details. -This default behavior works in most microservice database use cases. - -You can set the owner of a tablespace in the `owner` stanza, for example -the `postgres` user, like in the following excerpt: - -```yaml - # ... - tablespaces: - - name: clapton - owner: - name: postgres - storage: - size: 1Gi -``` - -!!!info Important -If you change the ownership of a tablespace, make sure that you're using -an existing role. Otherwise, the status of the cluster reports the -issue and stops reconciling tablespaces until fixed. It's your responsibility -to monitor the status and the log and to promptly intervene by fixing the issue. -!!! - -If you define a tablespace with an owner that doesn't exist, {{name.ln}} can't -create the tablespace and reflects this in the cluster status: - -```yaml -spec: - instances: 3 - - # ... - - tablespaces: - - name: tbs1 - storage: - size: 1Gi - - name: tbs2 - storage: - size: 2Gi - - name: tbs3 - owner: - name: badhombre - storage: - size: 2Gi - status: - - <- snipped -> - tablespacesStatus: - - name: tbs1 - status: reconciled - - name: tbs2 - status: reconciled - - error: 'while creating tablespace tbs3: ERROR: role "badhombre" does - not exist (SQLSTATE 42704)' - name: tbs3 - status: pending -``` - -## Backup and recovery - -{{name.ln}} handles backup of tablespaces (and the relative -tablespace map) both on object stores and volume snapshots. - -!!!warning -By default, backups are taken from replica nodes. A backup taken immediately -after creating tablespaces in a cluster can result in an -incomplete view of the tablespaces from the replica and thus an incomplete -backup. The lag will be resolved in a maximum of 5 minutes, with the next -reconciliation. -!!! - -!!!warning -When you add or remove a tablespace in an existing cluster, recovery -from WAL will fail until you take a new base backup. -!!! - -Once a cluster with tablespaces has a base backup, you can restore a -new cluster from it. When it comes to the recovery side, it's your -responsibility to ensure that the `Cluster` definition of the recovered -database contains the exact list of tablespaces. - -## Replica clusters - -Replica clusters must have the same tablespace definition as their origin. -The reason is that tablespace management commands like `CREATE TABLESPACE` -are WAL logged and are replayed by any physical replication client (streaming or by way of WAL shipping). - -It's your responsibility to ensure that replica clusters have the same list of -tablespaces, with the same name. Storage class and size might vary. - -For example: - -```yaml -spec: - - # ... - bootstrap: - recovery: - # ... your selected recovery method - - tablespaces: - - name: tbs1 - storage: - size: 1Gi - - name: tbs2 - storage: - size: 2Gi - - name: tbs3 - storage: - size: 2Gi -``` - -## Temporary tablespaces - -PostgreSQL allows you to define one or more temporary tablespaces to create -temporary objects (temporary tables and indexes on temporary tables) when a -`CREATE` command doesn't explicitly specify a tablespace, and to create temporary -files for purposes such as sorting large data sets. When no temporary -tablespace is specified, PostgreSQL uses the default tablespace of a database, which is -currently the main `PGDATA` volume. - -When you specify more than one temporary tablespace, PostgreSQL randomly picks -one the first time a temporary object needs to be created in a transaction. -Then it sequentially iterates through the list. - -Temporary tablespaces also work like regular tablespaces with regard to backups. - -{{name.ln}} provides the `.spec.tablespaces[*].temporary` option to -determine whether to add a tablespace to the `temp_tablespaces` -PostgreSQL parameter and thus become eligible to store temporary data that -doesn't have an explicit tablespace assignment. - -```yaml -spec: - [...] - tablespaces: - - name: atablespace - storage: - size: 1Gi - temporary: true -``` - -They can be created at initialization time or added later, requiring a -rolling update. The `temporary: true/false` option adds or removes the -tablespace name to or from the list of tablespaces in the `temp_tablespaces` -option. This change doesn't require a restart of PostgreSQL. - -Although temporary tablespaces can also work as regular tablespaces (meaning -that users can also host regular data on them while using them for -temporary operations), we recommend that you don't mix the two workloads. - -See the [PostgreSQL documentation on `temp_tablespaces`](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-TEMP-TABLESPACES) -for details. - -## kubectl plugin support - -The [kubectl status](kubectl-plugin.md#status) plugin includes a section -dedicated to tablespaces that offers a convenient overview, including -tablespace status, owner, temporary flag, and any errors: - -```yaml -[...] - -Tablespaces status -Tablespace Owner Status Temporary Error ----------- ----- ------ --------- ----- -atablespace app reconciled true -another_tablespace app reconciled true -tablespacea1 app reconciled false - -Instances status -[...] -``` - -## Limitations - -Currently, you can't remove tablespaces from an existing {{name.ln}} -cluster. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/tde.mdx b/product_docs/docs/postgres_for_kubernetes/preview/tde.mdx deleted file mode 100644 index 583840b1d0d..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/tde.mdx +++ /dev/null @@ -1,300 +0,0 @@ ---- -title: 'Transparent Data Encryption (TDE)' -originalFilePath: 'src/tde.md' ---- - -!!!info Important -TDE is available *only* for operands that support it: -EPAS and PG Extended, versions 15 and newer. -!!! - -Transparent Data Encryption, or TDE, is a technology used by several database -vendors to **encrypt data at rest**, i.e. database files on disk. -TDE does not however encrypt data in use. - -TDE is included in EDB Postgres Advanced Server and EDB Postgres Extended -Server from version 15, and is supported by the {{name.ln}} -operator. - -!!!info Important -Before you proceed, please take some time to familiarize with the -[TDE feature in the EPAS documentation](/tde/latest/). -!!! - -With TDE activated, both WAL files and files for tables will be encrypted. -Data encryption/decryption is entirely transparent to the user, as it is -managed by the database without requiring any application changes or updated -client drivers. - -!!!note -In the code samples shown below, the `epas` sub-section of `postgresql` in -the YAML manifests is used to activate TDE. The `epas` section can be used -to enable TDE for PG Extended images as well as for EPAS images. -!!! - -{{name.ln}} provides 3 ways to use TDE: - -- using a secret containing the passphrase -- using a secret containing a custom passphrase command -- using a pair of secrets containing custom wrap/unwrap commands - -## Passphrase secret - -The basic approach is to store the passphrase in a Kubernetes secret. Such a -passphrase will be used to encrypt the EPAS binary key. - -!!!note EPAS documentation -Please refer to [the EPAS documentation](/tde/latest/secure_key/) -for details on the EPAS encryption key. -!!! - -Activating TDE on the operator is simple. In the `epas` section of the manifest, -use the `tde` stanza to enable TDE, and set the Kubernetes secret that -will hold the TDE encryption key. - -For example: - -```yaml - […] - postgresql: - epas: - tde: - enabled: true - secretKeyRef: - name: tde-key - key: key -``` - -You can find an example in [`cluster-example-tde.yaml`](../samples/cluster-example-tde.yaml). - -!!!note -This file also contains the definition of the secret to hold the encryption -key. Look at the following section for an example on how to create a secret -for this purpose. -!!! - -The key stored in the secret will be used as the pass-phrase to invoke -`openssl` to wrap/unwrap the EPAS encryption key. - -### How to create the secret containing the passphrase - -First choose the passphrase. While it is recommended to use a randomly -generated passphrase, in this example we will use `PostgresRocks` as -passphrase, and rely on `kubectl` to generate for us the secret definition: - -```shell -kubectl create secret generic -o yaml tde-key \ - --from-literal=key=PostgresRocks -``` - -This should return something like this: - -```yaml -apiVersion: v1 -data: - key: UG9zdGdyZXNSb2Nrcw== -kind: Secret -metadata: - creationTimestamp: "YYYY-MM-DDTHH:MM:SSZ" - name: tde-key - namespace: default - resourceVersion: .... - uid: .... -type: Opaque -``` - -Remember to run `kubectl apply` or remove the `-o yaml` option to the `create` -command above to actually create the secret in the cluster. - -## Custom passphrase command - -Instead of the `secretKeyRef` in the cluster manifest snippet above, it is -possible to specify a `passphraseCommand` stored in a secret. The passphrase -command can be run to generate a passphrase to be used with `openssl`. - -```yaml - […] - postgresql: - epas: - tde: - enabled: true - passphraseCommand: - name: tde-passphrase - key: command -``` - -The passphrase command should write to standard output. -For example, we could simply use `echo my-passphrase`. - -The passphrase generated by the command will be used the same way the -secretKeyRef was used, i.e. as a passphrase argument for `openssl`. - -## Custom wrap/unwrap commands - -It is also possible to specify the wrap and unwrap commands, rather than rely -on the default invocation of `openssl`. -This can be done by creating secrets containing the custom commands, and -declaring those secrets in the `tde` stanza. - -The snippet below shows a cluster with TDE enabled using custom commands. - -```yaml - […] - postgresql: - epas: - tde: - enabled: true - wrapCommand: - name: tde-wrap-command - key: command - unwrapCommand: - name: tde-unwrap-command - key: command -``` - -The custom commands need to obey the following conventions: - -1. The custom wrap command should accept input from standard input, which EPAS - will use to feed it the binary key. It should write to a file via an explicit - argument (not shell redirections). Moreover, the file argument - should be given the string "%p", which is a placeholder EPAS will use to - pass the file path of the new, wrapped encryption key file. - -2. The custom unwrap command should write to standard output. It should have - an explicit file path argument for input (not shell redirections). - Again, the file argument should be given the string "%p", which is the - placeholder EPAS will fill in with the wrapped encryption key file path. - -For example: - -- wrap command: `openssl enc -aes-128-cbc -pass pass:temp-pass -e -out %p` -- unwrap command: `openssl enc -aes-128-cbc -pass pass:temp-pass -d -in %p` - -## Example using HashiCorp Vault - -The following example shows how to use HashiCorp Vault to store the encryption -key and use it to activate TDE. The `vault` CLI is used to interact with Vault -and is included by default in the EDB Postgres Advanced Server (EPAS) image. - -First, wherever you have vault running you must enable the Transit secrets -engine and create a key: - -```shell -vault secrets enable transit -vault write -f transit/keys/pg-tde -``` - -Then, create a secret containing the custom wrap/unwrap commands. The wrap -and unwrap commands will 'wrap' a binary that is in the EPAS image. The -binary will interact with the vault API to encrypt/decrypt the EPAS encryption. - -The binary needs 5 flags: `--file`, `--host`, `--secret`, `--key` and `--vault-endpoint`. The -`--host` flag is in the format of `http://vault-host:vault-port` and needs to be -provided to reach the Vault. The server`--secret` flag is the name of the Kubernetes -secret that contains the vault token and the `--key` flag is the key in that secret -pointing the vault token. The `--vault-endpoint` flag is the name of the key that -was created inside vault; in the example above it is `pg-tde`. - -If running the Vault operator in Kubernetes the root token can be obtained from the -following two commands: - -```shell -kubectl exec vault-0 -- vault operator init -key-shares=1 -key-threshold=1 -format=json > cluster-keys.json -cat cluster-keys.json | jq -r ".root_token" -``` - -```shell -kubectl create secret generic -o yaml vault-token \ - --from-literal=wrap="/bin/vault wrap --file %p --host http://vault:8200 --secret vault-token --key token --vault-endpoint pg-tde" \ - --from-literal=unwrap="/bin/vault unwrap --file %p --host http://vault:8200 --secret vault-token --key token --vault-endpoint pg-tde" \ - --from-literal=token="hvs.whatever" -``` - -You can now create a Cluster that is referencing the secrets: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: hashicorp-vault-tde -spec: - instances: 3 - storage: - size: 1Gi - postgresql: - epas: - tde: - enabled: true - wrapCommand: - name: vault-token - key: wrap - unwrapCommand: - name: vault-token - key: unwrap -``` - -### Enable TLS - -The binary needs 6 flags: `--file`, `--host`, `--secret`, `--key`, `--vault-endpoint` and `--enable-tls`. -The `--host` flag is in the format of `http://vault-host:vault-port` and needs to be -provided to reach the Vault. The server`--secret` flag is the name of the Kubernetes -secret that contains the vault token and the `--key` flag is the key in that secret -pointing the vault token. The `--vault-endpoint` flag is the name of the key that -was created inside vault; in the example above it is `pg-tde`. -To enable TLS, `--enable-tls` must be set to `true`. - -```shell -kubectl create secret generic -o yaml vault-token \ - --from-literal=wrap="/bin/vault wrap --file %p --host http://vault:8200 --secret vault-token --key token --vault-endpoint pg-tde --enable-tls true" \ - --from-literal=unwrap="/bin/vault unwrap --file %p --host http://vault:8200 --secret vault-token --key token --vault-endpoint pg-tde --enable-tls true" \ - --from-literal=token="hvs.whatever" -``` - -Then, specify the environment variables in a secret or configMap. - -```shell -kubectl create secret generic -o yaml env-var-secret \ ---from-literal=VAULT_CACERT="/projected/certificate/vault-ca.pem" \ -``` - -Reference the secret in the Cluster spec `envFrom` section, -so that the binary can use the environment variables, as they will be injected in the pods. -If one or more environment variables refers to files, rely on the `projectedVolumeTemplate` -to mount custom files, and on secrets or configmaps for their contents. -Following the example, the values of the `tls-vault-secret` key `ca` -is mounted as file into the path `/projected/certificate/vault-ca.pem`. - -```shell -kubectl create secret generic -o yaml tls-vault-secret --from-file=ca=vault-ca.crt -``` - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: hashicorp-vault-tde -spec: - envFrom: - - secretRef: - name: env-var-secret - projectedVolumeTemplate: - sources: - - secret: - name: tls-vault-secret - items: - - key: ca - path: certificate/vault-ca.pem - instances: 3 - storage: - size: 1Gi - postgresql: - epas: - tde: - enabled: true - wrapCommand: - name: vault-token - key: wrap - unwrapCommand: - name: vault-token - key: unwrap -``` diff --git a/product_docs/docs/postgres_for_kubernetes/preview/troubleshooting.mdx b/product_docs/docs/postgres_for_kubernetes/preview/troubleshooting.mdx deleted file mode 100644 index f1368e32c73..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/troubleshooting.mdx +++ /dev/null @@ -1,913 +0,0 @@ ---- -title: 'Troubleshooting' -originalFilePath: 'src/troubleshooting.md' ---- - - - -In this page, you can find some basic information on how to troubleshoot -{{name.ln}} in your Kubernetes cluster deployment. - -!!!tip Hint -As a Kubernetes administrator, you should have the -[`kubectl` Cheat Sheet](https://kubernetes.io/docs/reference/kubectl/cheatsheet/) page -bookmarked! -!!! - -## Before you start - -### Kubernetes environment - -What can make a difference in a troubleshooting activity is to provide -clear information about the underlying Kubernetes system. - -Make sure you know: - -- the Kubernetes distribution and version you are using -- the specifications of the nodes where PostgreSQL is running -- as much as you can about the actual [storage](storage.md), including storage - class and benchmarks you have done before going into production. -- which relevant Kubernetes applications you are using in your cluster (i.e. - Prometheus, Grafana, Istio, Certmanager, ...) -- the situation of continuous backup, in particular if it's in place and working - correctly: in case it is not, make sure you take an [emergency backup](#emergency-backup) - before performing any potential disrupting operation - -### Useful utilities - -On top of the mandatory `kubectl` utility, for troubleshooting, we recommend the -following plugins/utilities to be available in your system: - -- [`cnp` plugin](kubectl-plugin.md) for `kubectl` -- [`jq`](https://stedolan.github.io/jq/), a lightweight and flexible command-line JSON processor -- [`grep`](https://www.gnu.org/software/grep/), searches one or more input files - for lines containing a match to a specified pattern. It is already available in most \*nix distros. - If you are on Windows OS, you can use [`findstr`](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/findstr) as an alternative to `grep` or directly use [`wsl`](https://docs.microsoft.com/en-us/windows/wsl/) - and install your preferred \*nix distro and use the tools mentioned above. - -## First steps - -To quickly get an overview of the cluster or installation, the `kubectl` plugin -is the primary tool to use: - -1. the [status subcommand](kubectl-plugin.md#status) provides an overview of a - cluster -2. the [report subcommand](kubectl-plugin.md#report) provides the manifests - for clusters and the operator deployment. It can also include logs using - the `--logs` option. - The report generated via the plugin will include the full cluster manifest. - -The plugin can be installed on air-gapped systems via packages. -Please refer to the [plugin document](kubectl-plugin.md) for complete instructions. - -## Are there backups? - -After getting the cluster manifest with the plugin, you should verify if backups -are set up and working. - -Before proceeding with troubleshooting operations, it may be advisable -to perform an emergency backup depending on your findings regarding backups. -Refer to the following section for instructions. - -It is **extremely risky** to operate a production database without keeping -regular backups. - -## Emergency backup - -In some emergency situations, you might need to take an emergency logical -backup of the main `app` database. - -!!!info Important -The instructions you find below must be executed only in emergency situations -and the temporary backup files kept under the data protection policies -that are effective in your organization. The dump file is indeed stored -in the client machine that runs the `kubectl` command, so make sure that -all protections are in place and you have enough space to store the -backup file. -!!! - -The following example shows how to take a logical backup of the `app` database -in the `cluster-example` Postgres cluster, from the `cluster-example-1` pod: - -```sh -kubectl exec cluster-example-1 -c postgres \ - -- pg_dump -Fc -d app > app.dump -``` - -!!!note -You can easily adapt the above command to backup your cluster, by providing -the names of the objects you have used in your environment. -!!! - -The above command issues a `pg_dump` command in custom format, which is the most -versatile way to take [logical backups in PostgreSQL](https://www.postgresql.org/docs/current/app-pgdump.html). - -The next step is to restore the database. We assume that you are operating -on a new PostgreSQL cluster that's been just initialized (so the `app` database -is empty). - -The following example shows how to restore the above logical backup in the -`app` database of the `new-cluster-example` Postgres cluster, by connecting to -the primary (`new-cluster-example-1` pod): - -```sh -kubectl exec -i new-cluster-example-1 -c postgres \ - -- pg_restore --no-owner --role=app -d app --verbose < app.dump -``` - -!!!info Important -The example in this section assumes that you have no other global objects -(databases and roles) to dump and restore, as per our recommendation. In case -you have multiple roles, make sure you have taken a backup using `pg_dumpall -g` -and you manually restore them in the new cluster. In case you have multiple -databases, you need to repeat the above operation one database at a time, making -sure you assign the right ownership. If you are not familiar with PostgreSQL, -we advise that you do these critical operations under the guidance of -a professional support company. -!!! - -The above steps might be integrated into the `cnp` plugin at some stage in the future. - -## Logs - -All resources created and managed by {{name.ln}} log to standard output in -accordance with Kubernetes conventions, using [JSON format](logging.md). - -While logs are typically processed at the infrastructure level and include -those from {{name.ln}}, accessing logs directly from the command line -interface is critical during troubleshooting. You have three primary options -for doing so: - -- Use the `kubectl logs` command to retrieve logs from a specific resource, and - apply `jq` for better readability. -- Use the [`kubectl cnp logs` command](kubectl-plugin.md#logs) for - {{name.ln}}-specific logging. -- Leverage specialized open-source tools like - [stern](https://github.com/stern/stern), which can aggregate logs from - multiple resources (e.g., all pods in a PostgreSQL cluster by selecting the - `k8s.enterprisedb.io/clusterName` label), filter log entries, customize output formats, - and more. - -!!!note -The following sections provide examples of how to retrieve logs for various -resources when troubleshooting {{name.ln}}. -!!! - -## Operator information - -By default, the {{name.ln}} operator is installed in the -`postgresql-operator-system` namespace in Kubernetes as a `Deployment` -(see the ["Details about the deployment" section](installation_upgrade.md#details-about-the-deployment) -for details). - -You can get a list of the operator pods by running: - -```shell -kubectl get pods -n postgresql-operator-system -``` - -!!!note -Under normal circumstances, you should have one pod where the operator is -running, identified by a name starting with `postgresql-operator-controller-manager-`. -In case you have set up your operator for high availability, you should have more entries. -Those pods are managed by a deployment named `postgresql-operator-controller-manager`. -!!! - -Collect the relevant information about the operator that is running in pod -`` with: - -```shell -kubectl describe pod -n postgresql-operator-system -``` - -Then get the logs from the same pod by running: - -```shell -kubectl logs -n postgresql-operator-system -``` - -### Gather more information about the operator - -Get logs from all pods in {{name.ln}} operator Deployment -(in case you have a multi operator deployment) by running: - -```shell -kubectl logs -n postgresql-operator-system \ - deployment/postgresql-operator-controller-manager --all-containers=true -``` - -!!!tip -You can add `-f` flag to above command to follow logs in real time. -!!! - -Save logs to a JSON file by running: - -```shell -kubectl logs -n postgresql-operator-system \ - deployment/postgresql-operator-controller-manager --all-containers=true | \ - jq -r . > cnp_logs.json -``` - -Get {{name.ln}} operator version by using `kubectl-cnp` plugin: - -```shell -kubectl-cnp status -``` - -Output: - -```shell -Cluster in healthy state -Name: cluster-example -Namespace: default -System ID: 7044925089871458324 -PostgreSQL Image: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 -Primary instance: cluster-example-1 -Instances: 3 -Ready instances: 3 -Current Write LSN: 0/5000000 (Timeline: 1 - WAL File: 000000010000000000000004) - -Continuous Backup status -Not configured - -Streaming Replication status -Name Sent LSN Write LSN Flush LSN Replay LSN Write Lag Flush Lag Replay Lag State Sync State Sync Priority ----- -------- --------- --------- ---------- --------- --------- ---------- ----- ---------- ------------- -cluster-example-2 0/5000000 0/5000000 0/5000000 0/5000000 00:00:00 00:00:00 00:00:00 streaming async 0 -cluster-example-3 0/5000000 0/5000000 0/5000000 0/5000000 00:00:00.10033 00:00:00.10033 00:00:00.10033 streaming async 0 - -Instances status -Name Database Size Current LSN Replication role Status QoS Manager Version ----- ------------- ----------- ---------------- ------ --- --------------- -cluster-example-1 33 MB 0/5000000 Primary OK BestEffort 1.12.0 -cluster-example-2 33 MB 0/5000000 Standby (async) OK BestEffort 1.12.0 -cluster-example-3 33 MB 0/5000060 Standby (async) OK BestEffort 1.12.0 -``` - -## Cluster information - -You can check the status of the `` cluster in the `NAMESPACE` -namespace with: - -```shell -kubectl get cluster -n -``` - -Output: - -```shell -NAME AGE INSTANCES READY STATUS PRIMARY - 10d4h3m 3 3 Cluster in healthy state -1 -``` - -The above example reports a healthy PostgreSQL cluster of 3 instances, all in -*ready* state, and with `-1` being the primary. - -In case of unhealthy conditions, you can discover more by getting the manifest -of the `Cluster` resource: - -```shell -kubectl get cluster -o yaml -n -``` - -Another important command to gather is the `status` one, as provided by the -`cnp` plugin: - -```shell -kubectl cnp status -n -``` - -!!!tip -You can print more information by adding the `--verbose` option. -!!! - -Get EDB PostgreSQL Advanced Server (EPAS) / PostgreSQL container image version: - -```shell -kubectl describe cluster -n | grep "Image Name" -``` - -Output: - -```shell - Image Name: docker.enterprisedb.com/k8s/postgresql:18.4-standard-ubi9 -``` - -!!!note -Also you can use `kubectl-cnp status -n ` -to get the same information. -!!! - -## Pod information - -You can retrieve the list of instances that belong to a given PostgreSQL -cluster with: - -```shell -# using labels available from CNP 1.12.0 -kubectl get pod -l k8s.enterprisedb.io/cluster= -L role -n -# using legacy labels -kubectl get pod -l postgresql= -L role -n -``` - -Output: - -```shell -NAME READY STATUS RESTARTS AGE ROLE --1 1/1 Running 0 10d4h5m primary --2 1/1 Running 0 10d4h4m replica --3 1/1 Running 0 10d4h4m replica -``` - -You can check if/how a pod is failing by running: - -```shell -kubectl get pod -n -o yaml - -``` - -You can get all the logs for a given PostgreSQL instance with: - -```shell -kubectl logs -n - -``` - -If you want to limit the search to the PostgreSQL process only, you can run: - -```shell -kubectl logs -n - | \ - jq 'select(.logger=="postgres") | .record.message' -``` - -The following example also adds the timestamp: - -```shell -kubectl logs -n - | \ - jq -r 'select(.logger=="postgres") | [.ts, .record.message] | @csv' -``` - -If the timestamp is displayed in Unix Epoch time, you can convert it to a user-friendly format: - -```shell -kubectl logs -n - | \ - jq -r 'select(.logger=="postgres") | [(.ts|strflocaltime("%Y-%m-%dT%H:%M:%S %Z")), .record.message] | @csv' -``` - -### Gather and filter extra information about PostgreSQL pods - -Check logs from a specific pod that has crashed: - -```shell -kubectl logs -n --previous - -``` - -Get FATAL errors from a specific PostgreSQL pod: - -```shell -kubectl logs -n - | \ - jq -r '.record | select(.error_severity == "FATAL")' -``` - -Output: - -```json -{ - "log_time": "2021-11-08 14:07:44.520 UTC", - "user_name": "streaming_replica", - "process_id": "68", - "connection_from": "10.244.0.10:60616", - "session_id": "61892f30.44", - "session_line_num": "1", - "command_tag": "startup", - "session_start_time": "2021-11-08 14:07:44 UTC", - "virtual_transaction_id": "3/75", - "transaction_id": "0", - "error_severity": "FATAL", - "sql_state_code": "28000", - "message": "role \"streaming_replica\" does not exist", - "backend_type": "walsender" -} -``` - -Filter PostgreSQL DB error messages in logs for a specific pod: - -```shell -kubectl logs -n - | jq -r '.err | select(. != null)' -``` - -Output: - -```shell -dial unix /controller/run/.s.PGSQL.5432: connect: no such file or directory -``` - -Get messages matching `err` word from a specific pod: - -```shell -kubectl logs -n - | jq -r '.msg' | grep "err" -``` - -Output: - -```shell -2021-11-08 14:07:39.610 UTC [15] LOG: ending log output to stderr -``` - -Get all logs from PostgreSQL process from a specific pod: - -```shell -kubectl logs -n - | \ - jq -r '. | select(.logger == "postgres") | select(.msg != "record") | .msg' -``` - -Output: - -```shell -2021-11-08 14:07:52.591 UTC [16] LOG: redirecting log output to logging collector process -2021-11-08 14:07:52.591 UTC [16] HINT: Future log output will appear in directory "/controller/log". -2021-11-08 14:07:52.591 UTC [16] LOG: ending log output to stderr -2021-11-08 14:07:52.591 UTC [16] HINT: Future log output will go to log destination "csvlog". -``` - -Get pod logs filtered by fields with values and join them separated by `|` running: - -```shell -kubectl logs -n - | \ - jq -r '[.level, .ts, .logger, .msg] | join(" | ")' -``` - -Output: - -```shell -info | 1636380469.5728037 | wal-archive | Backup not configured, skip WAL archiving -info | 1636383566.0664876 | postgres | record -``` - -## Backup information - -You can list the backups that have been created for a named cluster with: - -```shell -kubectl get backup -l k8s.enterprisedb.io/cluster= -``` - -## Storage information - -Sometimes is useful to double-check the StorageClass used by the cluster to have -some more context during investigations or troubleshooting, like this: - -```shell -STORAGECLASS=$(kubectl get pvc -o jsonpath='{.spec.storageClassName}') -kubectl get storageclasses $STORAGECLASS -o yaml -``` - -We are taking the StorageClass from one of the cluster pod here since often -clusters are created using the default StorageClass. - -## Node information - -Kubernetes nodes is where ultimately PostgreSQL pods will be running. It's -strategically important to know as much as we can about them. - -You can get the list of nodes in your Kubernetes cluster with: - -```shell -# look at the worker nodes and their status -kubectl get nodes -o wide -``` - -Additionally, you can gather the list of nodes where the pods of a given -cluster are running with: - -```shell -kubectl get pod -l k8s.enterprisedb.io/cluster= \ - -L role -n -o wide -``` - -The latter is important to understand where your pods are distributed - very -useful if you are using [affinity/anti-affinity rules and/or tolerations](scheduling.md). - -## Conditions - -Like many native kubernetes -objects [like here](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions), -Cluster exposes `status.conditions` as well. This allows one to 'wait' for a particular -event to occur instead of relying on the overall cluster health state. Available conditions as of now are: - -- LastBackupSucceeded -- ContinuousArchiving -- Ready - -`LastBackupSucceeded` is reporting the status of the latest backup. If set to `True` the -last backup has been taken correctly, it is set to `False` otherwise. - -`ContinuousArchiving` is reporting the status of the WAL archiving. If set to `True` the -last WAL archival process has been terminated correctly, it is set to `False` otherwise. - -`Ready` is `True` when the cluster has the number of instances specified by the user -and the primary instance is ready. This condition can be used in scripts to wait for -the cluster to be created. - -### How to wait for a particular condition - -- Backup: - -```bash -$ kubectl wait --for=condition=LastBackupSucceeded cluster/ -n -``` - -- ContinuousArchiving: - -```bash -$ kubectl wait --for=condition=ContinuousArchiving cluster/ -n -``` - -- Ready (Cluster is ready or not): - -```bash -$ kubectl wait --for=condition=Ready cluster/ -n -``` - -Below is a snippet of a `cluster.status` that contains a failing condition. - -```bash -$ kubectl get cluster/ -o yaml -. -. -. - status: - conditions: - - message: 'unexpected failure invoking barman-cloud-wal-archive: exit status - 2' - reason: ContinuousArchivingFailing - status: "False" - type: ContinuousArchiving - - - message: exit status 2 - reason: LastBackupFailed - status: "False" - type: LastBackupSucceeded - - - message: Cluster Is Not Ready - reason: ClusterIsNotReady - status: "False" - type: Ready - - -``` - -## Networking - -{{name.ln}} requires basic networking and connectivity in place. -You can find more information in the [networking](networking.md) section. - -If installing {{name.ln}} in an existing environment, there might be -network policies in place, or other network configuration made specifically -for the cluster, which could have an impact on the required connectivity -between the operator and the cluster pods and/or the between the pods. - -You can look for existing network policies with the following command: - -```sh -kubectl get networkpolicies -``` - -There might be several network policies set up by the Kubernetes network -administrator. - -```sh -$ kubectl get networkpolicies -NAME POD-SELECTOR AGE -allow-prometheus k8s.enterprisedb.io/cluster=cluster-example 47m -default-deny-ingress 57m -``` - -## PostgreSQL core dumps - -Although rare, PostgreSQL can sometimes crash and generate a core dump -in the `PGDATA` folder. When that happens, normally it is a bug in PostgreSQL -(and most likely it has already been solved - this is why it is important -to always run the latest minor version of PostgreSQL). - -{{name.ln}} allows you to control what to include in the core dump through -the `k8s.enterprisedb.io/coredumpFilter` annotation. - -!!!info -Please refer to ["Labels and annotations"](labels_annotations.md) -for more details on the standard annotations that {{name.ln}} provides. -!!! - -By default, the `k8s.enterprisedb.io/coredumpFilter` is set to `0x31` in order to -exclude shared memory segments from the dump, as this is the safest -approach in most cases. - -!!!info -Please refer to -["Core dump filtering settings" section of "The `/proc` Filesystem" page of the Linux Kernel documentation](https://docs.kernel.org/filesystems/proc.html#proc-pid-coredump-filter-core-dump-filtering-settings). -for more details on how to set the bitmask that controls the core dump filter. -!!! - -!!!info Important -Beware that this setting only takes effect during Pod startup and that changing -the annotation doesn't trigger an automated rollout of the instances. -!!! - -Although you might not personally be involved in inspecting core dumps, -you might be asked to provide them so that a Postgres expert can look -into them. First, verify that you have a core dump in the `PGDATA` -directory with the following command (please run it against the -correct pod where the Postgres instance is running): - -```sh -kubectl exec -ti POD -c postgres \ - -- find /var/lib/postgresql/data/pgdata -name 'core.*' -``` - -Under normal circumstances, this should return an empty set. Suppose, for -example, that we have a core dump file: - -``` -/var/lib/postgresql/data/pgdata/core.14177 -``` - -Once you have verified the space on disk is sufficient, you can collect the -core dump on your machine through `kubectl cp` as follows: - -```sh -kubectl cp POD:/var/lib/postgresql/data/pgdata/core.14177 core.14177 -``` - -You now have the file. Make sure you free the space on the server by -removing the core dumps. - -## Visualizing and Analyzing Profiling Data - -{{name.ln}} integrates with [pprof](https://github.com/google/pprof) to -collect and analyze profiling data at two levels: - -- **Operator level** – enable by adding the `--pprof-server=true` option to the - operator deployment (see [Operator configuration](operator_conf.md#profiling-tools)). -- **Postgres cluster level** – enable by adding the - `alpha.k8s.enterprisedb.io/enableInstancePprof` annotation to a `Cluster` resource - (described below). - -When the `alpha.k8s.enterprisedb.io/enableInstancePprof` annotation is set to `"true"`, -each instance pod exposes a Go pprof HTTP server provided by the instance -manager. - -- The server listens on `0.0.0.0:6060` inside the pod. -- A container port named `pprof` (`6060/TCP`) is automatically added to the pod - spec. - -You can disable pprof at any time by either removing the annotation or setting -it to `"false"`. The operator will roll out changes automatically to remove the -pprof port and flag. - -!!!info Important -The pprof server only serves plain HTTP on port `6060`. -!!! - -### Example - -Enable pprof on a cluster by adding the annotation: - -```yaml -apiVersion: postgresql.k8s.enterprisedb.io/v1 -kind: Cluster -metadata: - name: cluster-example - annotations: - alpha.k8s.enterprisedb.io/enableInstancePprof: "true" -spec: - instances: 3 - # ... -``` - -Changing this annotation updates the instance pod spec (adds port `6060` and -the corresponding flag) and triggers a rolling update. - -!!!warning -The example below uses `kubectl port-forward` for local testing only. -This is **not** the intended way to expose the feature in production. -Treat pprof as a sensitive debugging interface and never expose it publicly. -If you must access it remotely, secure it with proper network policies and access controls. -!!! - -Use port-forwarding to access the pprof endpoints: - -```bash -kubectl port-forward -n pod/ 6060 -curl -sS http://localhost:6060/debug/pprof/ -go tool pprof http://localhost:6060/debug/pprof/profile?seconds=30 -``` - -You can also access pprof using the browser at . - -### Troubleshooting - -First, verify that the cluster has the `alpha.k8s.enterprisedb.io/enableInstancePprof: -"true"` annotation set. - -Next, check that the instance manager command includes the `--pprof-server` -flag and that port `6060/TCP` is exposed. You can do this by running: - -```bash -kubectl -n describe pod -``` - -Then review the **Command** and **Ports** sections in the output. - -Finally, if you are not using port-forwarding, make sure that your -NetworkPolicies allow access to port `6060/TCP`. - -## Some known issues - -### Storage is full - -In case the storage is full, the PostgreSQL pods will not be able to write new -data, or, in case of the disk containing the WAL segments being full, PostgreSQL -will shut down. - -If you see messages in the logs about the disk being full, you should increase -the size of the affected PVC. You can do this by editing the PVC and changing -the `spec.resources.requests.storage` field. After that, you should also update -the Cluster resource with the new size to apply the same change to all the pods. -Please look at the ["Volume expansion" section](storage.md#volume-expansion) in the documentation. - -If the space for WAL segments is exhausted, the pod will be crash-looping and -the cluster status will report `Not enough disk space`. Increasing the size in -the PVC and then in the Cluster resource will solve the issue. See also -the ["Disk Full Failure" section](instance_manager.md#disk-full-failure) - -### Pods are stuck in `Pending` state - -In case a Cluster's instance is stuck in the `Pending` phase, you should check -the pod's `Events` section to get an idea of the reasons behind this: - -```shell -kubectl describe pod -n -``` - -Some of the possible causes for this are: - -- No nodes are matching the `nodeSelector` -- Tolerations are not correctly configured to match the nodes' taints -- No nodes are available at all: this could also be related to - `cluster-autoscaler` hitting some limits, or having some temporary issues - -In this case, it could also be useful to check events in the namespace: - -```shell -kubectl get events -n -# list events in chronological order -kubectl get events -n --sort-by=.metadata.creationTimestamp -``` - -### Replicas out of sync when no backup is configured - -Sometimes replicas might be switched off for a bit of time due to maintenance -reasons (think of when a Kubernetes nodes is drained). In case your cluster -does not have backup configured, when replicas come back up, they might -require a WAL file that is not present anymore on the primary (having been -already recycled according to the WAL management policies as mentioned in -["The `postgresql` section"](postgresql_conf.md#the-postgresql-section)), and -fall out of synchronization. - -Similarly, when `pg_rewind` might require a WAL file that is not present -anymore in the former primary, reporting `pg_rewind: error: could not open file`. - -In these cases, pods cannot become ready anymore, and you are required to delete -the PVC and let the operator rebuild the replica. - -If you rely on dynamically provisioned Persistent Volumes, and you are confident -in deleting the PV itself, you can do so with: - -```shell -PODNAME= -VOLNAME=$(kubectl get pv -o json | \ - jq -r '.items[]|select(.spec.claimRef.name=='\"$PODNAME\"')|.metadata.name') - -kubectl delete pod/$PODNAME pvc/$PODNAME pvc/$PODNAME-wal pv/$VOLNAME -``` - -### Cluster stuck in `Creating new replica` - -Cluster is stuck in "Creating a new replica", while pod logs don't show -relevant problems. -This has been found to be related to the next issue -[on connectivity](#networking-is-impaired-by-installed-network-policies). -Networking issues are reflected in the status column as follows: - -```text -Instance Status Extraction Error: HTTP communication issue -``` - -### Networking is impaired by installed Network Policies - -As pointed out in the [networking section](#networking), local network policies -could prevent some of the required connectivity. - -A tell-tale sign that connectivity is impaired is the presence in the operator -logs of messages like: - -```text -"Cannot extract Pod status", […snipped…] "Get \"http://:8000/pg/status\": dial tcp :8000: i/o timeout" -``` - -You should list the network policies, and look for any policies restricting -connectivity. - -```sh -$ kubectl get networkpolicies -NAME POD-SELECTOR AGE -allow-prometheus k8s.enterprisedb.io/cluster=cluster-example 47m -default-deny-ingress 57m -``` - -For example, in the listing above, `default-deny-ingress` seems a likely culprit. -You can drill into it: - -```sh -$ kubectl get networkpolicies default-deny-ingress -o yaml -<…snipped…> -spec: - podSelector: {} - policyTypes: - - Ingress -``` - -In the [networking page](networking.md) you can find a network policy file -that you can customize to create a `NetworkPolicy` explicitly allowing the -operator to connect cross-namespace to cluster pods. - -### Error while bootstrapping the data directory - -If your Cluster's initialization job crashes with a "Bus error (core dumped) -child process exited with exit code 135", you likely need to fix the Cluster -hugepages settings. - -The reason is the incomplete support of hugepages in the cgroup v1 that should -be fixed in v2. For more information, check the PostgreSQL [BUG #17757: Not -honoring huge_pages setting during initdb causes DB crash in -Kubernetes](https://www.postgresql.org/message-id/17757-dbdfc1f1c954a6db%40postgresql.org). - -To check whether hugepages are enabled, run `grep HugePages /proc/meminfo` on -the Kubernetes node and check if hugepages are present, their size, and how many -are free. - -If the hugepages are present, you need to configure how much hugepages memory -every PostgreSQL pod should have available. - -For example: - -```yaml - postgresql: - parameters: - shared_buffers: "128MB" - - resources: - requests: - memory: "512Mi" - limits: - hugepages-2Mi: "512Mi" -``` - -Please remember that you must have enough hugepages memory available to schedule -every Pod in the Cluster (in the example above, at least 512MiB per Pod must be -free). - -### Bootstrap job hangs in running status - -If your Cluster's initialization job hangs while in `Running` status with the -message: -"error while waiting for the API server to be reachable", you probably have -a network issue preventing communication with the Kubernetes API server. -Initialization jobs (like most of jobs) need to access the Kubernetes -API. Please check your networking. - -Another possible cause is when you have sidecar injection configured. Sidecars -such as Istio may make the network temporarily unavailable during startup. If -you have sidecar injection enabled, retry with injection disabled. - -### Replicas take over two minutes to reconnect after a failover - -When the primary instance fails, the operator promotes the most advanced standby -to the primary role. Other standby instances then attempt to reconnect to the -`-rw` service for replication. However, during this reconnection process, -`kube-proxy` may not have updated its routing information yet. As a result, the -initial `SYN` packet sent by the standby instances might fail to reach its -intended destination. - -If the network is configured to silently drop packets instead of rejecting them, -standby instances will not receive a response and will retry the connection -after an exponential backoff period. On Linux systems, the default value for the -`tcp_syn_retries` kernel parameter is 6, meaning the system will attempt to -establish the connection for approximately 127 seconds before giving up. This -prolonged retry period can significantly delay the reconnection process. -For more details, consult the -[tcp_syn_retries documentation](https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt). - -You can work around this issue by setting `STANDBY_TCP_USER_TIMEOUT` in the -[operator configuration](operator_conf.md#available-options). This will cause -the standby instances to close the TCP connection if the initial `SYN` packet -is not acknowledged within the specified timeout, allowing them to retry the -connection more quickly. diff --git a/product_docs/docs/postgres_for_kubernetes/preview/use_cases.mdx b/product_docs/docs/postgres_for_kubernetes/preview/use_cases.mdx deleted file mode 100644 index 185bd6d9d1c..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/use_cases.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: 'Use cases' -originalFilePath: 'src/use_cases.md' ---- - - - -{{name.ln}} has been designed to work with applications -that reside in the same Kubernetes cluster, for a full cloud native -experience. - -However, it might happen that, while the database can be hosted -inside a Kubernetes cluster, applications cannot be containerized -at the same time and need to run in a *traditional environment* such -as a VM. - -## Case 1: Applications inside Kubernetes - -In a typical situation, the application and the database run in the same -namespace inside a Kubernetes cluster. - -![Application and Database inside Kubernetes](./images/apps-in-k8s.png) - -The application, normally stateless, is managed as a standard `Deployment`, -with multiple replicas spread over different Kubernetes node, and internally -exposed through a `ClusterIP` service. - -The service is exposed externally to the end user through an `Ingress` and the -provider's load balancer facility, via HTTPS. - -The application uses the backend PostgreSQL database to keep track of the state -in a reliable and persistent way. The application refers to the read-write -service exposed by the `Cluster` resource defined by {{name.ln}}, -which points to the current primary instance, through a TLS connection. The -`Cluster` resource embeds the logic of single primary and multiple standby -architecture, hiding the complexity of managing a high availability cluster in -Postgres. - -![Close-up view of application and database inside Kubernetes](./images/architecture-in-k8s.png) - -## Case 2: Applications outside Kubernetes - -Another possible use case is to manage your PostgreSQL database inside -Kubernetes, while having your applications outside of it (for example in a -virtualized environment). In this case, PostgreSQL is represented by an IP -address (or host name) and a TCP port, corresponding to the defined Ingress -resource in Kubernetes (normally a `LoadBalancer` service type as explained -in the ["Service Management"](service_management.md) page). - -The application can still benefit from a TLS connection to PostgreSQL. - -![Application outside Kubernetes](./images/apps-outside-k8s.png) diff --git a/product_docs/docs/postgres_for_kubernetes/preview/wal_archiving.mdx b/product_docs/docs/postgres_for_kubernetes/preview/wal_archiving.mdx deleted file mode 100644 index b152a133d73..00000000000 --- a/product_docs/docs/postgres_for_kubernetes/preview/wal_archiving.mdx +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: 'WAL archiving' -originalFilePath: 'src/wal_archiving.md' ---- - - - -Write-Ahead Log (WAL) archiving in {{name.ln}} is the process of continuously -shipping WAL files to a designated object store from the PostgreSQL primary. -These archives are essential for enabling Point-In-Time Recovery (PITR) and are -a foundational component for both object store and volume snapshot-based backup -strategies. - -## Plugin-Based Architecture - -{{name.ln}} supports WAL archiving through a **plugin-based mechanism**, -defined via the [`spec.pluginConfiguration`](pg4k.v1.md#clusterspec) -section of the `Cluster` resource. - -Only **one plugin at a time** can be responsible for WAL archiving. This is -configured by setting the `isWALArchiver` field to `true` within the plugin -configuration. - -## Supported Plugins - -Currently, the **Barman Cloud Plugin** is the only officially supported WAL -archiving plugin maintained by the {{name.ln}} Community. -For full documentation, configuration options, and best practices, see the -[Barman Cloud Plugin documentation](https://cloudnative-pg.io/plugin-barman-cloud/docs/intro/). - -## Deprecation Notice: Native Barman Cloud - -{{name.ln}} still supports WAL archiving natively through the -`.spec.backup.barmanObjectStore` field. While still functional, **this -interface is deprecated** and will be removed in a future release. - -!!!info Important -All new deployments are strongly encouraged to adopt the plugin-based -architecture, which offers a more flexible and maintainable approach. -!!! - -If you are currently using the native `.spec.backup.barmanObjectStore` -approach, refer to the official guide for a smooth transition: -[Migrating from Built-in {{name.ln}} Backup](https://cloudnative-pg.io/plugin-barman-cloud/docs/migration/). - -## About the archive timeout - -By default, {{name.ln}} sets `archive_timeout` to `5min`, ensuring -that WAL files, even in case of low workloads, are closed and archived -at least every 5 minutes, providing a deterministic time-based value for -your Recovery Point Objective ([RPO](before_you_start.md#postgresql-terminology)). - -Even though you change the value of the -[`archive_timeout` setting in the PostgreSQL configuration](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-ARCHIVE-TIMEOUT), -our experience suggests that the default value set by the operator is suitable -for most use cases. diff --git a/scripts/source/process-cnp-docs.sh b/scripts/source/process-cnp-docs.sh index 8e8f10709af..c66019213d2 100755 --- a/scripts/source/process-cnp-docs.sh +++ b/scripts/source/process-cnp-docs.sh @@ -73,7 +73,7 @@ function do_import { node "$DESTINATION_CHECKOUT/scripts/source/update-yaml.mjs" "$api_ref_index" \ navTitle="API Reference" \ pdfExclude=null \ - navigation=[`ls "$api_ref_dir" | grep ^v | sed -e 's/\.mdx$//' | sort -V -r | paste -sd "," - `] + navigation=[`ls "$api_ref_dir" | grep ^v | sed -e 's/\.mdx$//' | sed '/-/!{s/$/_/}' | sort -V -r | sed 's/_$//' | paste -sd "," - `] fi node "$DESTINATION_CHECKOUT/scripts/source/update-yaml.mjs" "$current_api_ref" \ originalFilePath=null @@ -89,22 +89,26 @@ cd $SOURCE_CHECKOUT git fetch --tags +# trick to make semantic version sorting work with "-rcX" versions, which are not strictly semver-compliant. +# We append an underscore to all tags that do not contain a hyphen, sort them, and then remove the underscore again. +# h/t: https://stackoverflow.com/questions/40390957/how-to-sort-semantic-versions-in-bash/40391207#40391207 + if [ -z $3 ] then - LATEST_TAG=`git tag | sort -V -r | head -n 1` + LATEST_TAG=`git tag | sed '/-/!{s/$/_/}' | sort -V -r | sed 's/_$//' | head -n 1` else LATEST_TAG="$3" fi CURRENT_TAG=`git describe --exact-match --tags || echo "$LATEST_TAG-next"` -CURRENT_TAG_INDEX=`git tag | sort -V -r | grep -nx $CURRENT_TAG | cut -d : -f 1 || echo 0` -PREVIOUS_TAGS=`git tag | sort -V -r | head -n $(($CURRENT_TAG_INDEX+30)) | tail -n 30` +CURRENT_TAG_INDEX=`git tag | sed '/-/!{s/$/_/}' | sort -V -r | sed 's/_$//' | grep -nx $CURRENT_TAG | cut -d : -f 1 || echo 0` +PREVIOUS_TAGS=`git tag | sed '/-/!{s/$/_/}' | sort -V -r | sed 's/_$//' | head -n $(($CURRENT_TAG_INDEX+30)) | tail -n 30` cd $DESTINATION_CHECKOUT git fetch --tags -PREVIOUS_DOCS_TAGS=`git for-each-ref --format='%(refname:short)' refs/tags/product/pg4k | sort -V -r | cut -d / -f 3` -PREVIOUS_TAG=`comm -12 <(echo "$PREVIOUS_DOCS_TAGS" | sort) <(echo "$PREVIOUS_TAGS" | sort) | sort -V -r | head -n 1` +PREVIOUS_DOCS_TAGS=`git for-each-ref --format='%(refname:short)' refs/tags/product/pg4k | sed '/-/!{s/$/_/}' | sort -V -r | sed 's/_$//' | cut -d / -f 3` +PREVIOUS_TAG=`comm -12 <(echo "$PREVIOUS_DOCS_TAGS" | sort) <(echo "$PREVIOUS_TAGS" | sort) | sed '/-/!{s/$/_/}' | sort -V -r | sed 's/_$//' | head -n 1` PREVIOUS_COMMIT=`git rev-list -n 1 product/pg4k/$PREVIOUS_TAG || git rev-list -n 1 HEAD` PREVIOUS_COMMIT_DESC=`git rev-list --format=oneline -n 1 $PREVIOUS_COMMIT`