From 7290ee2a56dcad6cdd8e84f76bedc3adb85b290d Mon Sep 17 00:00:00 2001
From: Michael Ryan Peter <mipeter@redhat.com>
Date: Mon, 27 Mar 2023 17:46:20 -0400
Subject: [PATCH] OSDOCS-1929 [RN] Discovering Operators from the CLI

---
 release_notes/ocp-4-13-release-notes.adoc | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

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