diff --git a/release_notes/ocp-4-13-release-notes.adoc b/release_notes/ocp-4-13-release-notes.adoc
index 8d07ce026233..47b2a37a2678 100644
--- a/release_notes/ocp-4-13-release-notes.adoc
+++ b/release_notes/ocp-4-13-release-notes.adoc
@@ -410,6 +410,26 @@ In {product-title} {product-version}, you can add and configure {lvms-first} thr
 [id="ocp-4-13-olm"]
 === Operator lifecycle
 
+[id=ocp-4-13-olm-discover-operator-versions]
+==== Finding Operator versions by using the OpenShift CLI
+In {product-title} 4.13, you can find which versions and channels of an Operator you can install on your system by running the following OpenShift CLI (`oc`) command:
+
+.Example `oc describe` command syntax
+[source,terminal]
+----
+$ oc describe packagemanifests <operator_name> -n <catalog_namespace>
+----
+
+You can specify the output format of an Operator's version and channel information by running the following command:
+
+.Example `oc get` command syntax
+[source,terminal]
+----
+$ oc get packagemanifests <operator_name> -n <catalog_namespace> -o <output_format>
+----
+
+For more information, see xref:../operators/admin/olm-adding-operators-to-cluster.adoc#olm-installing-specific-version-cli_olm-adding-operators-to-a-cluster[Installing a specific version of an Operator].
+
 [id="ocp-4-13-osdk"]
 === Operator development