Doc update for dedicated registry #7023
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leo-jin-edb
commented
Nov 19, 2025
|
|
||
| !!! 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. <Add a screen shot and detailed explanation>. To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) | ||
|
|
Author
There was a problem hiding this comment.
@dhilipkumars was thinking we add a bit more meat here with screenshots to better explain the scenario?
leo-jin-edb
commented
Nov 19, 2025
|
|
||
| !!! 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. <Add a screen shot and detailed explanation>. To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) | ||
|
|
Author
There was a problem hiding this comment.
@dhilipkumars was thinking we add a bit more meat here with screenshots
leo-jin-edb
commented
Nov 19, 2025
|
|
||
| **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. <Add a screen shot and detailed explanation>. 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. <Add a screen shot and detailed explanation>. To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) |
Author
There was a problem hiding this comment.
@dhilipkumars was thinking we add a bit more meat here with screenshots
leo-jin-edb
commented
Nov 19, 2025
|
|
||
| **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. <Add a screen shot and detailed explanation>. 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. <Add a screen shot and detailed explanation>. To counter this issue, EDB recommends setting up a customer dedidated registry as described [here](../../../system/synced-images.mdx) |
Author
There was a problem hiding this comment.
@dhilipkumars was thinking we add a bit more meat here with screenshots
Corrected typos and improved clarity in the note about dedicated registry setup.
Corrected typographical errors in the note about registry setup and compatibility issues.
| - Power, rack, and cabling details | ||
| - Networking and security preferences | ||
| - Physical access and contact coordination | ||
| - Dedicated image registry |
Contributor
There was a problem hiding this comment.
FYI i dont think this is the right place to add it.
| - 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) |
Contributor
There was a problem hiding this comment.
Same here i dont think this is the right place to add this one too
Contributor
|
Hey @leo-jin-edb ! I have created a docs ticket for someone in our team to help you get this across the finish line. https://enterprisedb.atlassian.net/browse/DOCS-3090 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What Changed?
https://enterprisedb.atlassian.net/browse/DOCS-3090