Skip to content

Commit

Permalink
docs: backport limitation (#4065)
Browse files Browse the repository at this point in the history
Co-authored-by: Lenny Chen <[email protected]>
  • Loading branch information
lennessyy and lennessyy authored Sep 24, 2024
1 parent ee7d212 commit 285b415
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,11 @@ stylus:
You can point the Edge Installer to a non-default registry to load content from another source. Use the
`registryCredentials` parameter object to specify the registry configurations.

If you are using an external registry and want to use content bundles when deploying your Edge cluster, you must also
enable the local Harbor registry. For more information, refer to
[Build Content Bundles](../edgeforge-workflow/build-content-bundle.md) and
[Enable Local Harbor Registry](../networking/local-registry.md).

| Parameter | Description |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `domain` | The domain of the registry. You can use an IP address plus the port or a domain name. |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,15 @@ Creating a content bundle provides several benefits that may address common use
- Organizations that want better control over the software used by their Edge hosts can use content bundles to ensure
that only approved software is consumed.

## Limitation

- You cannot use content bundles with an external registry if you do not enable the local Harbor registry on your Edge
host. If you specify a external registry without enabling the local Harbor registry, the images will be downloaded
from the external registry even if you provide a content bundle, and deployment will fail if the necessary images
cannot be located in the external registry. For more information, refer to
[Installer Reference](../edge-configuration/installer-reference.md#external-registry) and
[Enable Local Harbor Registry](../networking/local-registry.md).

## Prerequisites

- Linux Machine (Physical or VM) with an AMD64 architecture.
Expand Down

0 comments on commit 285b415

Please sign in to comment.