From 10b61d468d4f339b67d5bb24c3df35c36c12ed34 Mon Sep 17 00:00:00 2001 From: Grant Miller Date: Wed, 20 Nov 2024 09:26:25 -0600 Subject: [PATCH] moving private registry proxy to beta --- docs/vendor/using-third-party-registry-proxy.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/vendor/using-third-party-registry-proxy.mdx b/docs/vendor/using-third-party-registry-proxy.mdx index c8c8b06fb5..95ee045021 100644 --- a/docs/vendor/using-third-party-registry-proxy.mdx +++ b/docs/vendor/using-third-party-registry-proxy.mdx @@ -1,4 +1,4 @@ -# Using a Registry Proxy for Helm Air Gap Installations (Alpha) +# Using a Registry Proxy for Helm Air Gap Installations (Beta) This topic describes how to connect the Replicated proxy registry to a Harbor or jFrog Artifactory instance to support pull-through image caching. It also includes information about how to set up replication rules in Harbor for image mirroring. @@ -69,4 +69,4 @@ To configure image mirroring in Harbor: [jFrog Artifactory](https://jfrog.com/help/r/jfrog-artifactory-documentation) supports pull-through caching for Docker registries. -For information about how to configure a pull-through cache with Artifactory, see [Remote Repository](https://jfrog.com/help/r/jfrog-artifactory-documentation/configure-a-remote-repository) in the Artifactory documentation. \ No newline at end of file +For information about how to configure a pull-through cache with Artifactory, see [Remote Repository](https://jfrog.com/help/r/jfrog-artifactory-documentation/configure-a-remote-repository) in the Artifactory documentation.