Skip to content

Commit 0a9a4a8

Browse files
committed
scope registry to one or more apps
1 parent 89accc5 commit 0a9a4a8

File tree

1 file changed

+45
-5
lines changed

1 file changed

+45
-5
lines changed

docs/vendor/packaging-private-images.md

Lines changed: 45 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Connect to an External Registry
1+
# Add and Manage External Registries
22

33
This topic describes how to add credentials for an external private registry using the Replicated Vendor Portal or Replicated CLI. Adding an external registry allows you to grant proxy access to private images using the Replicated proxy registry. For more information, see [About the Replicated Proxy Registry](private-images-about).
44

@@ -37,6 +37,8 @@ To add an external registry using the Vendor Portal:
3737

3838
1. In the **Provider** drop-down, select your registry provider.
3939

40+
1. For **Registry Name**, optionally add a unique name for the registry. This can be useful if you intend to add multiple registries or duplicate any of your registries.
41+
4042
1. Complete the fields in the dialog, depending on the provider that you chose:
4143

4244
:::note
@@ -201,9 +203,17 @@ To add an external registry using the Vendor Portal:
201203
</tr>
202204
</table>
203205

204-
1. For **Image name & tag**, enter the image name and image tag and click **Test** to confirm that the Vendor Portal can access the image. For example, `api:v1.0.1` or `my-app/api:v1.01`.
206+
1. For **App Access**, select one of these options:
207+
* **All Apps**: Make the registry available to all applications in your Vendor Portal team. This means that all customers have pull-through access to the images in this registry with their valid license.
208+
* **Specific apps**: Make this registry available only to the applications that you specify. When the registry is scoped to specific applications, only customers with a valid license for the specified applications have pull-through access to the images in the registry.
205209

206-
1. Click **Link registry**.
210+
1. Click **Test** and provide your image name and tag (for example, `api:v1.0.1` or `my-app/api:v1.01`.). Click **Test** to confirm that the Vendor Portal can access the image.
211+
212+
:::note
213+
This tests credential validity only. Replicated strongly recommends that you still test your application end-to-end in a development environment.
214+
:::
215+
216+
1. Click **Save**.
207217

208218
### Using the CLI
209219

@@ -249,6 +259,36 @@ For example:
249259
replicated registry test index.docker.io --image my-company/my-image:v1.2.3
250260
```
251261

252-
## Related Topic
262+
## Scope a Registry to Specific Applications
263+
264+
You can scope each external registry to one or more applications in your Vendor Portal team.
265+
266+
When the registry is scoped to specific applications, only customers with a valid license for the specified applications have pull-through access to the images in the registry. Additionally, when you add new applications to your team, those applications do not automatically get access to the registry.
267+
268+
To scope a registry to specific applications:
269+
270+
1. In the **Vendor Portal**, go to **Images** and click **Edit** next to the target registry.
271+
272+
1. For **App Access**, select one of these options:
273+
* **All Apps**: Make the registry available to all applications in your Vendor Portal team. This means that all customers have pull-through access to the images in this registry with their valid license.
274+
* **Specific apps**: Make this registry available only to the applications that you specify.
275+
276+
1. Click **Save**.
277+
278+
## Duplicate a Registry
279+
280+
You can duplicate an existing registry. This can be useful when you want to add an external registry with the same credentials, but make the registry available to a different application in your Vendor Portal team.
281+
282+
To duplicate an existing external registry:
283+
284+
1. In the Vendor Portal, go to **Images** and click **Edit** next to the registry that you want to duplicate.
285+
286+
1. Click **Duplicate**.
287+
288+
The fields are automatically populated with the credentials and provider from the duplicated registry.
289+
290+
1. For **Registry Name**, provide a name for the registry.
291+
292+
1. For **App access**, specify the application or applications that have access to the images in this registry.
253293

254-
[Tutorial: Using ECR for Private Images](tutorial-ecr-private-images)
294+
1. Click **Save**.

0 commit comments

Comments
 (0)