diff --git a/doc/source/usertasks/kubernetes/delete-image-tags-in-the-docker-registry-8e2e91d42294.rst b/doc/source/usertasks/kubernetes/delete-image-tags-in-the-docker-registry-8e2e91d42294.rst
new file mode 100644
index 000000000..93b14dc18
--- /dev/null
+++ b/doc/source/usertasks/kubernetes/delete-image-tags-in-the-docker-registry-8e2e91d42294.rst
@@ -0,0 +1,29 @@
+.. _delete-image-tags-in-the-docker-registry-8e2e91d42294:
+
+========================================
+Delete Image Tags in the Docker Registry
+========================================
+
+When deleting image tags in the registry.local docker registry, you should be
+aware that the deletion of an **<image-name><tag-name>** will delete all tags
+under the specified <image-name> that have the same 'digest' as the specified
+<image-name:tag-name>.
+
+The docker registry API v2 does not support deleting specific tags.
+See, `https://github.com/distribution/distribution/issues/1566 <https://github.com/distribution/distribution/issues/1566>`_ .
+
+For example:
+
+jsmith/sampleimage-test:v1.0
+jsmith/sampleimage-test:v1.1
+jsmith/sampleimage-production:v1.0
+
+If the above three image tags share the same digest in registry.local, then, if
+'jsmith/sampleimage-test:v1.1' is deleted, then **ALL** other tags under
+'jsmith/sampleimage-test' that have the **SAME** digest
+(as jsmith/sampleimage-test:v1.1) are deleted. That is, both
+'jsmith/sampleimage-test:v1.0' and 'jsmith/sampleimage-test:v1.1' will be
+deleted, while 'jsmith/sampleimage-production:v1.0' with the same digest
+but different <image-name> will not be deleted.
+
+
diff --git a/doc/source/usertasks/kubernetes/index.rst b/doc/source/usertasks/kubernetes/index.rst
index 907e9d968..7507593c4 100644
--- a/doc/source/usertasks/kubernetes/index.rst
+++ b/doc/source/usertasks/kubernetes/index.rst
@@ -67,6 +67,8 @@ Local Docker registry
 
    kubernetes-user-tutorials-authentication-and-authorization
    using-an-image-from-the-local-docker-registry-in-a-container-spec
+   delete-image-tags-in-the-docker-registry-8e2e91d42294
+
 
 ---------------------------
 NodePort usage restrictions