Skip to content

Commit 63e0843

Browse files
committed
add link to image registry doc from kurl page
1 parent 2921e9b commit 63e0843

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

docs/enterprise/image-registry-kurl.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ To keep the registry from running out of storage, images that are no longer used
1111

1212
For more information about the kURL Registry add-on, see [Registry Add-On](https://kurl.sh/docs/add-ons/registry) in the kURL documentation.
1313

14+
:::note
15+
Users can also optionally configure their own private registry for kURL installations in the Admin Console. For more information, see [Configuring Local Image Registries](/enterprise/image-registry-settings).
16+
:::
17+
1418
## Trigger Garbage Collection
1519

1620
Every time the application instance is upgraded, image garbage collection automatically deletes images that are no longer used.

docs/enterprise/image-registry-settings.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ import ImageRegistrySettings from "../partials/image-registry/_image-registry-se
44

55
This topic describes how to configure private registry settings in the Replicated KOTS Admin Console.
66

7+
The information in this topic applies to existing cluster installations with KOTS and installations with Replicated kURL.
8+
79
## Overview
810

911
Using a private registry lets you create a custom image pipeline. Any proprietary configurations that you make to the application are shared only with the groups that you allow access, such as your team or organization. You also have control over the storage location, logging messages, load balancing requests, and other configuration options.

0 commit comments

Comments
 (0)