From 854dff3f3bacdcb83d23983bcfcd41b7622c174c Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Thu, 25 Apr 2024 11:27:00 -0400 Subject: [PATCH 1/2] Edits to pg4k PR5482 --- .../1/known_issues.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx index f15f968f9a9..95d06248b97 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx @@ -14,15 +14,15 @@ This version of EDB Postgres Distributed for Kubernetes **doesn't support** migr ## Connectivity with PgBouncer -EDB Postgres Distributed for Kubernetes does not support using [PgBouncer](/pgbouncer/latest/) to pool client connection requests. -This applies to both the open-source and EDB versions of PgBouncer. +EDB Postgres Distributed for Kubernetes **doesn't support** using [PgBouncer](/pgbouncer/latest/) to pool client connection requests. +This limitation applies to both the open-source and EDB versions of PgBouncer. ## Backup operations -To configure an EDB Postgres Distributed for Kubernetes environment, you must apply a `PGDGroup` YAML object to each Kubernetes cluster, -which then creates all necessary services for the implementation of a distributed architecture. +To configure an EDB Postgres Distributed for Kubernetes environment, you must apply a `PGDGroup` YAML object to each Kubernetes cluster. Applying this object +creates all necessary services for implementing a distributed architecture. -If you have added a `spec.backup` section to this `PGDGroup` object with the goal of setting up a backup configuration, +If you added a `spec.backup` section to this `PGDGroup` object with the goal of setting up a backup configuration, the backup will fail unless you also set the `spec.backup.cron.schedule` value. Error output example: @@ -58,5 +58,5 @@ spec: All issues and limitations known for the EDB Postgres Distributed version that you include in your deployment also affect your EDB Postgres Distributed for Kubernetes instance. -For example, if the EDB Postgres Distributed version you are using is 5.x, your EDB Postgres Distributed for Kubernetes +For example, if the EDB Postgres Distributed version you're using is 5.x, your EDB Postgres Distributed for Kubernetes instance will be affected by these [5.x known issues](/pgd/latest/known_issues/) and [5.x limitations](/pgd/latest/limitations/). From f7a1d9708dd53efab661448a38910642d1cbd559 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Tue, 30 Apr 2024 10:37:42 +0200 Subject: [PATCH 2/2] No contraction for RN product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx --- .../docs/postgres_distributed_for_kubernetes/1/known_issues.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx b/product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx index 95d06248b97..85ab048583e 100644 --- a/product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx +++ b/product_docs/docs/postgres_distributed_for_kubernetes/1/known_issues.mdx @@ -14,7 +14,7 @@ This version of EDB Postgres Distributed for Kubernetes **doesn't support** migr ## Connectivity with PgBouncer -EDB Postgres Distributed for Kubernetes **doesn't support** using [PgBouncer](/pgbouncer/latest/) to pool client connection requests. +EDB Postgres Distributed for Kubernetes **does not support** using [PgBouncer](/pgbouncer/latest/) to pool client connection requests. This limitation applies to both the open-source and EDB versions of PgBouncer. ## Backup operations