$ tar xvf <file>
The opm
CLI tool is provided by the Operator Framework for use with the Operator Bundle Format. This tool allows you to create and maintain catalogs of Operators from a list of bundles, called an index, that are similar to software repositories. The result is a container image, called an index image, which can be stored in a container registry and then installed on a cluster.
An index contains a database of pointers to Operator manifest content that can be queried through an included API that is served when the container image is run. On OKD, Operator Lifecycle Manager (OLM) can use the index image as a catalog by referencing it in a CatalogSource
object, which polls the image at regular intervals to enable frequent updates to installed Operators on the cluster.
See Operator Framework packaging formats for more information about the Bundle Format.
To create a bundle image using the Operator SDK, see Working with bundle images.
You can install the opm
CLI tool on your Linux, macOS, or Windows workstation.
For Linux, you must provide the following packages. RHEL 8 meets these requirements:
podman
version 1.9.3+ (version 2.0+ recommended)
glibc
version 2.28+
Navigate to the OpenShift mirror site and download the latest version of the tarball that matches your operating system.
Unpack the archive.
For Linux or macOS:
$ tar xvf <file>
For Windows, unzip the archive with a ZIP program.
Place the file anywhere in your PATH
.
For Linux or macOS:
Check your PATH
:
$ echo $PATH
Move the file. For example:
$ sudo mv ./opm /usr/local/bin/
For Windows:
Check your PATH
:
C:\> path
Move the file:
C:\> move opm.exe <directory>
After you install the opm
CLI, verify that it is available:
$ opm version
Version: version.Version{OpmVersion:"v1.14.3-29-ge82c4649", GitCommit:"e82c4649b208cd0b08dbd5b88da55450f97b3a2d", BuildDate:"2021-02-13T02:20:52Z", GoOs:"linux", GoArch:"amd64"}
See Managing custom catalogs for opm
procedures including creating, updating, and pruning index images.