Skip to content

OSDOCS#1929 [RN] Discovering Operators from the CLI #57837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 27, 2023
Merged

OSDOCS#1929 [RN] Discovering Operators from the CLI #57837

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions release_notes/ocp-4-13-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down