Merge branch 'update-registry-docs-ga' into 'master'

container registry: update documentation for GA

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/160805



Merged-by: Marcel Amirault <mamirault@gitlab.com>
Approved-by: Marcel Amirault <mamirault@gitlab.com>
Co-authored-by: Hayley Swimelar <hswimelar@gitlab.com>

doc/administration/packages/container_registry.md

@@ -12,7 +12,7 @@ DETAILS:
 
 NOTE:
 The [next-generation container registry](container_registry_metadata_database.md)
-is now available for upgrade and testing on self-managed instances as a beta feature.
+is now available for upgrade on self-managed instances.
 This upgraded registry supports online garbage collection, and has significant performance
 and reliability improvements.
 
@@ -1093,7 +1093,6 @@ end
 DETAILS:
 **Tier:** Free, Premium, Ultimate
 **Offering:** Self-managed
-**Status:** Beta
 
 The metadata database enables many new registry features, including
 online garbage collection, and increases the efficiency of many registry operations.
@@ -1290,16 +1289,10 @@ blobs start being deleted is anything permanent done.
 ### Continuous Zero-Downtime Garbage Collection
 
 DETAILS:
-**Status:** Beta
 
 You can run garbage collection in the background without the need to schedule it or require read-only mode,
 if you migrate to the [metadata database](container_registry_metadata_database.md).
 
-NOTE:
-If you would like to try this [beta feature](../../policy/experiment-beta-support.md#beta),
-you should review the [known limitations](container_registry_metadata_database.md#known-limitations). If you have any feedback,
-you can let us know in the [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/423459).
-
 ## Configure GitLab and Registry to run on separate nodes (Linux package installations)
 
 By default, package assumes that both services are running on the same node.

doc/administration/packages/container_registry_metadata_database.md

@@ -9,16 +9,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 DETAILS:
 **Tier:** Free, Premium, Ultimate
 **Offering:** Self-managed
-**Status:** Beta
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/423459) in GitLab 16.4 as a [beta feature](../../policy/experiment-beta-support.md) for self-managed GitLab instances.
 
-WARNING:
-The metadata database is a [beta feature](../../policy/experiment-beta-support.md#beta).
-Carefully review the documentation before enabling the registry database in production!
-If you encounter a problem with either the import or operation of the
-registry, please add a comment in the [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/423459).
-
 The metadata database enables many new registry features, including
 online garbage collection, and increases the efficiency of many registry operations.
 The work on the self-managed release of the registry metadata database feature
@@ -53,7 +46,7 @@ for the status of features related to the container registry database.
 
 Prerequisites:
 
-- GitLab 16.7 or later.
+- GitLab 17.3 or later.
 - PostgreSQL database version 12 or later. It must be accessible from the registry node.
 
 Follow the instructions that match your situation: