diff --git a/doc/source/admintasks/kubernetes/freeing-space-in-the-local-docker-registry.rst b/doc/source/admintasks/kubernetes/freeing-space-in-the-local-docker-registry.rst
index e29808335..4124f077a 100644
--- a/doc/source/admintasks/kubernetes/freeing-space-in-the-local-docker-registry.rst
+++ b/doc/source/admintasks/kubernetes/freeing-space-in-the-local-docker-registry.rst
@@ -74,6 +74,12 @@ associated space from the file system. To do so, you must also run the
     **image:tags** from the file system and frees the file system spaces
     allocated to deleted/unreferenced images.
 
+    .. note::
+
+        The :command:`registry-garbage-collect` command executes background
+        tasks that may affect access to the docker registry. It is recommended
+        to wait a few minutes before executing other registry related commands.
+
     .. code-block:: none
 
         ~(keystone_admin)]$ system registry-garbage-collect
diff --git a/doc/source/cli_ref/system.rst b/doc/source/cli_ref/system.rst
index 3d17d8317..af884c221 100644
--- a/doc/source/cli_ref/system.rst
+++ b/doc/source/cli_ref/system.rst
@@ -94,6 +94,12 @@ the local Docker registry's file system (`docker-distribution`) becomes full.
     read-only mode. If this occurs, run garbage-collect again to take the
     registry out of read-only mode.
 
+    .. note::
+
+        The :command:`registry-garbage-collect` command executes background
+        tasks that may affect access to the docker registry. It is recommended
+        to wait a few minutes before executing other registry related commands.
+
 ``registry-image-delete``
     Remove the specified Docker image from the local registry.
 
diff --git a/doc/source/system_configuration/kubernetes/check-new-registry-and-reapply-application.rst b/doc/source/system_configuration/kubernetes/check-new-registry-and-reapply-application.rst
index 42aa7855c..3956827ee 100644
--- a/doc/source/system_configuration/kubernetes/check-new-registry-and-reapply-application.rst
+++ b/doc/source/system_configuration/kubernetes/check-new-registry-and-reapply-application.rst
@@ -57,6 +57,12 @@ to controller-1 and perform the same steps.
        # SSH to controller-1 (or the standby controller)
        crictl rmi registry.local:9001/quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0
 
+   .. note::
+
+        The :command:`registry-garbage-collect` command executes background
+        tasks that may affect access to the docker registry. It is recommended
+        to wait a few minutes before executing other registry related commands.
+
 #. To reapply the application run the following command:
 
    .. code-block:: none