From 1f6f8d8a62f4077da52eec4d24cc7195eb6f9425 Mon Sep 17 00:00:00 2001 From: leo-jin-edb Date: Wed, 19 Nov 2025 16:24:15 -0500 Subject: [PATCH 01/11] update --- .../hybrid-manager/system/synced-images.mdx | 116 ++++++++++++++++++ .../hybrid-manager/system/what-to-expect.mdx | 2 + 2 files changed, 118 insertions(+) create mode 100644 product_docs/docs/edb-postgres-ai/preview/hybrid-manager/system/synced-images.mdx diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/system/synced-images.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/system/synced-images.mdx new file mode 100644 index 0000000000..60b4df4786 --- /dev/null +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/system/synced-images.mdx @@ -0,0 +1,116 @@ +# Sync EDB Postgres AI Platform container images into a customer owned registry + +The software stack of our EDB PGAI is pushed into EDB Cloudsmith registry to provide artifacts that our customers will be able to use. + +A requirement to use our stack will be that customers hosts their own secure and approved internal registry (in case of EKS as a platform to run PGAI that can be an ECR in the same AWS account, or can be another kind of supported container registry) and knowing the EDB PGAI version that we want to install, we can take all the artifacts from Cloudsmith and sync them internally into the local registry before installing or upgrading the software stack with the helm chart. + +The sync process needs to preserve the container images SHA256 to ensure images security and immutability across different environments. You can do the sync using `edbctl`, the CLI to manage PGAI resources, or by running a tool like [skopeo](https://github.com/containers/skopeo), that you can install referring to [their official docs](https://github.com/containers/skopeo/blob/main/install.md). + +!!! note + If the local registry is AWS ECR, since we want all the EDB repositories to stay under a single namespace (see related AWS docs [here](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html#repository-concepts)), we would need to create multiple repositories in the registry to allow the image copy to work, because ECR doesn’t support images with multiple slashes in their name to be saved in the same repository. + +## Using `edbctl` - Suggested + +!!! note + `edbctl` is still in development and we don't have yet released binaries, you will need to build it by yourself, see [here](https://github.com/EnterpriseDB/upm-beaconator-cli?tab=readme-ov-file#build-and-run-locally). + +```bash +# building binary +$ make build + +# Configure the EDB PGAI release to be taken +export EDBPGAI_RELEASE= +# Configure the EDB Cloudsmith access token +export CS_EDB_TOKEN= +# Configure the EDB Cloudsmith registry source +export EDB_SOURCE_REGISTRY=pgai-platform +# Run the sync-to-local-registry command +build/edbctl image sync-to-local-registry \ + --destination-registry-uri "" \ + --version "${EDBPGAI_RELEASE}" \ + --source-registry-username "${EDB_SOURCE_REGISTRY}" \ + --source-registry-password "${CS_EDB_TOKEN}" \ + --destination-registry-username "" \ + --destination-registry-password "" +``` + +!!! note + Starting with EDB PGAI version 1.3.0, syncing the EDB PGAI Operator image to your local registry is a required step. + +```bash +# Sync the EDB PGAI Operator Image to the destination registry: +build/edbctl operator sync-to-local-registry \ + --destination-registry-uri "" \ + --version "${EDBPGAI_RELEASE}" \ + --source-registry-username "${EDB_SOURCE_REGISTRY}" \ + --source-registry-password "${CS_EDB_TOKEN}" \ + --destination-registry-username "" \ + --destination-registry-password "" +``` + +When you run the above command `edbctl image sync-to-local-registry` with a that is AWS ECR, the CLI will ask a confirmation before proceed with they sync process and will provide a code snippet with a list of AWS CLI commands that can be used to pre-create all the repositories that ECR requires to successfully complete the sync process. + +## Using `skopeo` + +Every EDB PGAI release provides an artifact that contains the list of all the container images that are required to install/upgrade the software stack, and can be used to run a sync process to copy over all these container images from the EDB Cloudsmith registry to an internal one. + +The following snippet can run on Bash on Linux/MacOS/Windows WSL + +```bash +# Configure the EDB PGAI release to be taken +export EDBPGAI_RELEASE= +# Configure the EDB Cloudsmith access token +export CS_EDB_TOKEN= +# Downloading the image list artifact locally +curl -sLO "https://downloads.enterprisedb.com/${CS_EDB_TOKEN}/pgai-platform/raw/names/${EDBPGAI_RELEASE}-images.txt/versions/${EDBPGAI_RELEASE}/images.txt" +# Configure the EDB Cloudsmith registry source +export EDB_SOURCE_REGISTRY=docker.enterprisedb.com/pgai-platform +# Configure the local registry destination +export LOCAL_REGISTRY_URI= +# skopeo login to the source registry, provide credentials as requested +skopeo login docker.enterprisedb.com +# skopeo login to the destination registry, provide credentials as requested +skopeo login +# Parsing the image list and syncing every image +while read -r image; do skopeo --override-os linux copy --multi-arch all docker://$EDB_SOURCE_REGISTRY/${image/:*@/@} docker://$LOCAL_REGISTRY_URI/${image/:*@/@} --retry-times 3; done < images.txt +``` + +!!! note + Starting with EDB PGAI version 1.3.0, syncing the EDB PGAI Operator image to your local registry is a required step. + +```bash +# Sync the EDB PGAI Operator Image to the destination registry: +skopeo --override-os linux copy \ + --multi-arch all \ + docker://${EDB_SOURCE_REGISTRY}/edb-hcp-operator/manager:${EDBPGAI_RELEASE} \ + docker://${LOCAL_REGISTRY_URI}/edb-hcp-operator/manager:${EDBPGAI_RELEASE} \ + --retry-times 3 +``` + +This is a sample run that shows an output result of the previous commands, using AWS ECR as a destination registry: + +```bash +$ export EDBPGAI_RELEASE=v1.0.0-gm-appl +$ export CS_EDB_TOKEN= +$ export AWS_ACCOUNT_ID=123456789012 # sample value, replace with the correct one +$ curl -sLO "https://downloads.enterprisedb.com/${CS_EDB_TOKEN}/pgai-platform/raw/names/${EDBPGAI_RELEASE}-images.txt/versions/${EDBPGAI_RELEASE}/images.txt" +$ wc -l images.txt # shows how many images are in the release +132 images.txt +$ export EDB_SOURCE_REGISTRY=docker.enterprisedb.com/pgai-platform +$ export LOCAL_REGISTRY_URI=${AWS_ACCOUNT_ID}.dkr.ecr.us-east-1.amazonaws.com/edbpgai-test-ecr +$ skopeo login docker.enterprisedb.com +Username: +Password: +Login Succeeded! +$ skopeo login ${AWS_ACCOUNT_ID}.dkr.ecr.us-east-1.amazonaws.com -u AWS -p $(aws ecr get-login-password --region us-east-1) +Login Succeeded! +# WE CAN IGNORE AWS RepositoryAlreadyExistsException WHILE RUNNING aws ecr create-repository +$ while read -r image; do aws ecr create-repository --repository-name "${LOCAL_REGISTRY_URI#*/}/${image%%[:@]*}" --no-cli-pager || true; skopeo --override-os linux copy --multi-arch all docker://$EDB_SOURCE_REGISTRY/${image/:*@/@} docker://$LOCAL_REGISTRY_URI/${image/:*@/@} --retry-times 3; done < images.txt +...the sync process will take quite a few minutes to copy the full set of images... +# CHECKING RESULTS OF THE IMAGE SYNC +$ aws ecr describe-repositories --query 'repositories[?starts_with(repositoryName, `edbpgai-test-ecr`)]' --output json | jq '. | length' +93 +$ cat images.txt | awk -F'[:@]' '{print $1}' | sort -u | wc -l +93 +# SINGLE IMAGE AND REPOS ARE MATCHING +``` \ No newline at end of file diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/system/what-to-expect.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/system/what-to-expect.mdx index 35d8c79f49..3aa40dfa9a 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/system/what-to-expect.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/system/what-to-expect.mdx @@ -13,6 +13,7 @@ After your order is confirmed, you'll complete a site readiness survey to guide - Power, rack, and cabling details - Networking and security preferences - Physical access and contact coordination +- Dedicated image registry ### What happens @@ -20,6 +21,7 @@ After your order is confirmed, you'll complete a site readiness survey to guide - EDB and Supermicro teams perform on-site racking, power-up, and validation. - Configuration is completed based on your preferences. - You receive login credentials and URL access to the Hybrid Manager portal. +- You will have a dedicated image registry that syncs with EDB's production registry to pull all required Hybrid Manager artifacts. More details [here](./synced-images.mdx) ## Days 21–28: Deploying your first workloads From 9a76507f6b74001edb3d2944597b2f6c5532f5c3 Mon Sep 17 00:00:00 2001 From: leo-jin-edb Date: Wed, 19 Nov 2025 16:26:36 -0500 Subject: [PATCH 02/11] added to 1.3 --- .../hybrid-manager/system/synced-images.mdx | 116 ++++++++++++++++++ .../hybrid-manager/system/what-to-expect.mdx | 2 + 2 files changed, 118 insertions(+) create mode 100644 product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/system/synced-images.mdx diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/system/synced-images.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/system/synced-images.mdx new file mode 100644 index 0000000000..60b4df4786 --- /dev/null +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/system/synced-images.mdx @@ -0,0 +1,116 @@ +# Sync EDB Postgres AI Platform container images into a customer owned registry + +The software stack of our EDB PGAI is pushed into EDB Cloudsmith registry to provide artifacts that our customers will be able to use. + +A requirement to use our stack will be that customers hosts their own secure and approved internal registry (in case of EKS as a platform to run PGAI that can be an ECR in the same AWS account, or can be another kind of supported container registry) and knowing the EDB PGAI version that we want to install, we can take all the artifacts from Cloudsmith and sync them internally into the local registry before installing or upgrading the software stack with the helm chart. + +The sync process needs to preserve the container images SHA256 to ensure images security and immutability across different environments. You can do the sync using `edbctl`, the CLI to manage PGAI resources, or by running a tool like [skopeo](https://github.com/containers/skopeo), that you can install referring to [their official docs](https://github.com/containers/skopeo/blob/main/install.md). + +!!! note + If the local registry is AWS ECR, since we want all the EDB repositories to stay under a single namespace (see related AWS docs [here](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html#repository-concepts)), we would need to create multiple repositories in the registry to allow the image copy to work, because ECR doesn’t support images with multiple slashes in their name to be saved in the same repository. + +## Using `edbctl` - Suggested + +!!! note + `edbctl` is still in development and we don't have yet released binaries, you will need to build it by yourself, see [here](https://github.com/EnterpriseDB/upm-beaconator-cli?tab=readme-ov-file#build-and-run-locally). + +```bash +# building binary +$ make build + +# Configure the EDB PGAI release to be taken +export EDBPGAI_RELEASE= +# Configure the EDB Cloudsmith access token +export CS_EDB_TOKEN= +# Configure the EDB Cloudsmith registry source +export EDB_SOURCE_REGISTRY=pgai-platform +# Run the sync-to-local-registry command +build/edbctl image sync-to-local-registry \ + --destination-registry-uri "" \ + --version "${EDBPGAI_RELEASE}" \ + --source-registry-username "${EDB_SOURCE_REGISTRY}" \ + --source-registry-password "${CS_EDB_TOKEN}" \ + --destination-registry-username "" \ + --destination-registry-password "" +``` + +!!! note + Starting with EDB PGAI version 1.3.0, syncing the EDB PGAI Operator image to your local registry is a required step. + +```bash +# Sync the EDB PGAI Operator Image to the destination registry: +build/edbctl operator sync-to-local-registry \ + --destination-registry-uri "" \ + --version "${EDBPGAI_RELEASE}" \ + --source-registry-username "${EDB_SOURCE_REGISTRY}" \ + --source-registry-password "${CS_EDB_TOKEN}" \ + --destination-registry-username "" \ + --destination-registry-password "" +``` + +When you run the above command `edbctl image sync-to-local-registry` with a that is AWS ECR, the CLI will ask a confirmation before proceed with they sync process and will provide a code snippet with a list of AWS CLI commands that can be used to pre-create all the repositories that ECR requires to successfully complete the sync process. + +## Using `skopeo` + +Every EDB PGAI release provides an artifact that contains the list of all the container images that are required to install/upgrade the software stack, and can be used to run a sync process to copy over all these container images from the EDB Cloudsmith registry to an internal one. + +The following snippet can run on Bash on Linux/MacOS/Windows WSL + +```bash +# Configure the EDB PGAI release to be taken +export EDBPGAI_RELEASE= +# Configure the EDB Cloudsmith access token +export CS_EDB_TOKEN= +# Downloading the image list artifact locally +curl -sLO "https://downloads.enterprisedb.com/${CS_EDB_TOKEN}/pgai-platform/raw/names/${EDBPGAI_RELEASE}-images.txt/versions/${EDBPGAI_RELEASE}/images.txt" +# Configure the EDB Cloudsmith registry source +export EDB_SOURCE_REGISTRY=docker.enterprisedb.com/pgai-platform +# Configure the local registry destination +export LOCAL_REGISTRY_URI= +# skopeo login to the source registry, provide credentials as requested +skopeo login docker.enterprisedb.com +# skopeo login to the destination registry, provide credentials as requested +skopeo login +# Parsing the image list and syncing every image +while read -r image; do skopeo --override-os linux copy --multi-arch all docker://$EDB_SOURCE_REGISTRY/${image/:*@/@} docker://$LOCAL_REGISTRY_URI/${image/:*@/@} --retry-times 3; done < images.txt +``` + +!!! note + Starting with EDB PGAI version 1.3.0, syncing the EDB PGAI Operator image to your local registry is a required step. + +```bash +# Sync the EDB PGAI Operator Image to the destination registry: +skopeo --override-os linux copy \ + --multi-arch all \ + docker://${EDB_SOURCE_REGISTRY}/edb-hcp-operator/manager:${EDBPGAI_RELEASE} \ + docker://${LOCAL_REGISTRY_URI}/edb-hcp-operator/manager:${EDBPGAI_RELEASE} \ + --retry-times 3 +``` + +This is a sample run that shows an output result of the previous commands, using AWS ECR as a destination registry: + +```bash +$ export EDBPGAI_RELEASE=v1.0.0-gm-appl +$ export CS_EDB_TOKEN= +$ export AWS_ACCOUNT_ID=123456789012 # sample value, replace with the correct one +$ curl -sLO "https://downloads.enterprisedb.com/${CS_EDB_TOKEN}/pgai-platform/raw/names/${EDBPGAI_RELEASE}-images.txt/versions/${EDBPGAI_RELEASE}/images.txt" +$ wc -l images.txt # shows how many images are in the release +132 images.txt +$ export EDB_SOURCE_REGISTRY=docker.enterprisedb.com/pgai-platform +$ export LOCAL_REGISTRY_URI=${AWS_ACCOUNT_ID}.dkr.ecr.us-east-1.amazonaws.com/edbpgai-test-ecr +$ skopeo login docker.enterprisedb.com +Username: +Password: +Login Succeeded! +$ skopeo login ${AWS_ACCOUNT_ID}.dkr.ecr.us-east-1.amazonaws.com -u AWS -p $(aws ecr get-login-password --region us-east-1) +Login Succeeded! +# WE CAN IGNORE AWS RepositoryAlreadyExistsException WHILE RUNNING aws ecr create-repository +$ while read -r image; do aws ecr create-repository --repository-name "${LOCAL_REGISTRY_URI#*/}/${image%%[:@]*}" --no-cli-pager || true; skopeo --override-os linux copy --multi-arch all docker://$EDB_SOURCE_REGISTRY/${image/:*@/@} docker://$LOCAL_REGISTRY_URI/${image/:*@/@} --retry-times 3; done < images.txt +...the sync process will take quite a few minutes to copy the full set of images... +# CHECKING RESULTS OF THE IMAGE SYNC +$ aws ecr describe-repositories --query 'repositories[?starts_with(repositoryName, `edbpgai-test-ecr`)]' --output json | jq '. | length' +93 +$ cat images.txt | awk -F'[:@]' '{print $1}' | sort -u | wc -l +93 +# SINGLE IMAGE AND REPOS ARE MATCHING +``` \ No newline at end of file diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/system/what-to-expect.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/system/what-to-expect.mdx index 35d8c79f49..3aa40dfa9a 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/system/what-to-expect.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/system/what-to-expect.mdx @@ -13,6 +13,7 @@ After your order is confirmed, you'll complete a site readiness survey to guide - Power, rack, and cabling details - Networking and security preferences - Physical access and contact coordination +- Dedicated image registry ### What happens @@ -20,6 +21,7 @@ After your order is confirmed, you'll complete a site readiness survey to guide - EDB and Supermicro teams perform on-site racking, power-up, and validation. - Configuration is completed based on your preferences. - You receive login credentials and URL access to the Hybrid Manager portal. +- You will have a dedicated image registry that syncs with EDB's production registry to pull all required Hybrid Manager artifacts. More details [here](./synced-images.mdx) ## Days 21–28: Deploying your first workloads From d0616dc7beda4c67a1989337043657afb2e81f53 Mon Sep 17 00:00:00 2001 From: leo-jin-edb Date: Wed, 19 Nov 2025 16:48:45 -0500 Subject: [PATCH 03/11] update --- .../cluster_management/create-clusters/cluster-settings.mdx | 2 ++ .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 2 ++ 2 files changed, 4 insertions(+) diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index 7a65159902..2ae540ab28 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -37,6 +37,8 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl 3. HM supports multiple images of each Postgres database, stored in the image library. Each image is a configuration of the database that includes various extensions. Select the image that you want to use for your cluster. See [Asset library](../../image-management/asset-library.mdx) for more information. Generally, without `-full` at the end of the name, the image has no extensions. With `-full` at the end of the name, the image has all available extensions. +**Note** If you do not have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) + **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. ### Storage diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index 519b1333af..60d361513d 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -20,6 +20,8 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. +**Note** If you do not have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) + 1. Review the upgrade path and confirm by selecting the **Continue** button. 1. The dialogue window now shows the specific package changes to be expected with the upgrade. From 0dbb64cd5adea2448dc6eb45c31087eae904962f Mon Sep 17 00:00:00 2001 From: leo-jin-edb Date: Wed, 19 Nov 2025 17:01:17 -0500 Subject: [PATCH 04/11] update --- .../cluster_management/create-clusters/cluster-settings.mdx | 3 +++ .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 3 +++ .../cluster_management/create-clusters/cluster-settings.mdx | 3 ++- .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 3 ++- 4 files changed, 10 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index 7a65159902..53291f81e5 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -39,6 +39,9 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. +!!! Note + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) + ### Storage You can specify the following storage settings: diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index 519b1333af..612b75460a 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -20,6 +20,9 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. +!!! Note + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) + 1. Review the upgrade path and confirm by selecting the **Continue** button. 1. The dialogue window now shows the specific package changes to be expected with the upgrade. diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index 2ae540ab28..eca39e121b 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -37,7 +37,8 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl 3. HM supports multiple images of each Postgres database, stored in the image library. Each image is a configuration of the database that includes various extensions. Select the image that you want to use for your cluster. See [Asset library](../../image-management/asset-library.mdx) for more information. Generally, without `-full` at the end of the name, the image has no extensions. With `-full` at the end of the name, the image has all available extensions. -**Note** If you do not have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) +!!! Note + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index 60d361513d..612b75460a 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -20,7 +20,8 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. -**Note** If you do not have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) +!!! Note + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) 1. Review the upgrade path and confirm by selecting the **Continue** button. From 10c63b7342d8f48eb349c35104b196b839e95125 Mon Sep 17 00:00:00 2001 From: leo-jin-edb Date: Wed, 19 Nov 2025 17:02:30 -0500 Subject: [PATCH 05/11] update --- .../cluster_management/create-clusters/cluster-settings.mdx | 1 + .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 1 + .../cluster_management/create-clusters/cluster-settings.mdx | 1 + .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 1 + 4 files changed, 4 insertions(+) diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index 53291f81e5..af5efebc9a 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -40,6 +40,7 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. !!! Note + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) ### Storage diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index 612b75460a..b5956a5918 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -21,6 +21,7 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. !!! Note + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) 1. Review the upgrade path and confirm by selecting the **Continue** button. diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index eca39e121b..d0f8efd40c 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -38,6 +38,7 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl 3. HM supports multiple images of each Postgres database, stored in the image library. Each image is a configuration of the database that includes various extensions. Select the image that you want to use for your cluster. See [Asset library](../../image-management/asset-library.mdx) for more information. Generally, without `-full` at the end of the name, the image has no extensions. With `-full` at the end of the name, the image has all available extensions. !!! Note + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index 612b75460a..b5956a5918 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -21,6 +21,7 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. !!! Note + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) 1. Review the upgrade path and confirm by selecting the **Continue** button. From 7929f6896ffc825114e51f371b2bda6efbc1d660 Mon Sep 17 00:00:00 2001 From: leo-jin-edb Date: Wed, 19 Nov 2025 17:03:27 -0500 Subject: [PATCH 06/11] update --- .../cluster_management/create-clusters/cluster-settings.mdx | 1 - .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 1 - .../cluster_management/create-clusters/cluster-settings.mdx | 1 - .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 1 - 4 files changed, 4 deletions(-) diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index af5efebc9a..53291f81e5 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -40,7 +40,6 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) ### Storage diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index b5956a5918..612b75460a 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -21,7 +21,6 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) 1. Review the upgrade path and confirm by selecting the **Continue** button. diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index d0f8efd40c..eca39e121b 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -38,7 +38,6 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl 3. HM supports multiple images of each Postgres database, stored in the image library. Each image is a configuration of the database that includes various extensions. Select the image that you want to use for your cluster. See [Asset library](../../image-management/asset-library.mdx) for more information. Generally, without `-full` at the end of the name, the image has no extensions. With `-full` at the end of the name, the image has all available extensions. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index b5956a5918..612b75460a 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -21,7 +21,6 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) 1. Review the upgrade path and confirm by selecting the **Continue** button. From 8649486e191793d894a87145c4f22118e9bc7373 Mon Sep 17 00:00:00 2001 From: leo-jin-edb <72026186+leo-jin-edb@users.noreply.github.com> Date: Wed, 19 Nov 2025 17:09:28 -0500 Subject: [PATCH 07/11] Fix typos in cluster settings documentation Corrected typos and improved clarity in the note about dedicated registry setup. --- .../cluster_management/create-clusters/cluster-settings.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index eca39e121b..45ed0fe2f0 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -38,7 +38,7 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl 3. HM supports multiple images of each Postgres database, stored in the image library. Each image is a configuration of the database that includes various extensions. Select the image that you want to use for your cluster. See [Asset library](../../image-management/asset-library.mdx) for more information. Generally, without `-full` at the end of the name, the image has no extensions. With `-full` at the end of the name, the image has all available extensions. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version of Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. From 61dd4dd5955ef5c8c028948eada352d26534c4a0 Mon Sep 17 00:00:00 2001 From: leo-jin-edb <72026186+leo-jin-edb@users.noreply.github.com> Date: Wed, 19 Nov 2025 17:10:04 -0500 Subject: [PATCH 08/11] Fix typos in cluster settings documentation Corrected typographical errors in the note about registry setup and compatibility issues. --- .../cluster_management/create-clusters/cluster-settings.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index 45ed0fe2f0..3bce20f9f5 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -38,7 +38,7 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl 3. HM supports multiple images of each Postgres database, stored in the image library. Each image is a configuration of the database that includes various extensions. Select the image that you want to use for your cluster. See [Asset library](../../image-management/asset-library.mdx) for more information. Generally, without `-full` at the end of the name, the image has no extensions. With `-full` at the end of the name, the image has all available extensions. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version of Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version of Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedicated registry as described [here](../../../system/synced-images.mdx) **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. From 63f5260cb81d9e45f55b35ddc027c1d0630e8ebb Mon Sep 17 00:00:00 2001 From: leo-jin-edb <72026186+leo-jin-edb@users.noreply.github.com> Date: Wed, 19 Nov 2025 17:10:32 -0500 Subject: [PATCH 09/11] Update upgrade_major.mdx --- .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index 612b75460a..7bb8771c8b 100644 --- a/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/preview/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -21,7 +21,7 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version of Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedicated registry as described [here](../../../system/synced-images.mdx) 1. Review the upgrade path and confirm by selecting the **Continue** button. From 306c82e4462c76676576c0f44b4bc87a5914ac2c Mon Sep 17 00:00:00 2001 From: leo-jin-edb <72026186+leo-jin-edb@users.noreply.github.com> Date: Wed, 19 Nov 2025 17:11:20 -0500 Subject: [PATCH 10/11] Fix typo and clarify registry setup note --- .../cluster_management/create-clusters/cluster-settings.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx index 53291f81e5..3ba07b326e 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/cluster_management/create-clusters/cluster-settings.mdx @@ -40,7 +40,7 @@ You set these options in the [**Data Groups**](data-groups.mdx) tab for other cl **Instance Size** — Select the number of CPUs and the amount of memory for your cluster. The number of CPUs and the amount of memory you can select depends on available resources in your Kubernetes cluster. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version of Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedicated registry as described [here](../../../system/synced-images.mdx) ### Storage From b6c71f70a7dd524cecc46d58d258468c65a12169 Mon Sep 17 00:00:00 2001 From: leo-jin-edb <72026186+leo-jin-edb@users.noreply.github.com> Date: Wed, 19 Nov 2025 17:11:50 -0500 Subject: [PATCH 11/11] Fix typo and improve clarity in upgrade instructions --- .../using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx index 612b75460a..83d25ca714 100644 --- a/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx +++ b/product_docs/docs/edb-postgres-ai/1.3/hybrid-manager/using_hybrid_manager/upgrading/pg_major/upgrade_major.mdx @@ -21,8 +21,7 @@ Now check the cluster and database metrics and make sure everything is operating 1. Select your preferred new major version image. !!! Note - If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) - + If you **do not** have a dedicated registry setup and is relying directly on EDB production registry, you may run into issues where the system allows you to setup the cluster with operands incompatible with the installed version of Hybrid Manager. In this case, you need to pay attenion to the meta data displayed while selecting an image to ensure it's compatible. . To counter this issue, EDB recommends setting up a customer dedicated registry as described [here](../../../system/synced-images.mdx) 1. Review the upgrade path and confirm by selecting the **Continue** button. 1. The dialogue window now shows the specific package changes to be expected with the upgrade.