1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/op-installing-pipelines-operator-using-the-cli.adoc
2025-10-07 12:26:32 -04:00

43 lines
1.5 KiB
Plaintext

// Module included in the following assemblies:
//
// * openshift_pipelines/installing-pipelines.adoc
:_mod-docs-content-type: PROCEDURE
[id="op-installing-pipelines-operator-using-the-cli_{context}"]
= Installing the {pipelines-shortname} Operator using the CLI
You can install {pipelines-title} Operator from the software catalog using the CLI.
[discrete]
.Procedure
. Create a Subscription object YAML file to subscribe a namespace to the {pipelines-title} Operator,
for example, `sub.yaml`:
+
.Example Subscription
[source,yaml]
----
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: openshift-pipelines-operator
namespace: openshift-operators
spec:
channel: <channel name> <1>
name: openshift-pipelines-operator-rh <2>
source: redhat-operators <3>
sourceNamespace: openshift-marketplace <4>
----
<1> The channel name of the Operator. The `pipelines-<version>` channel is the default channel. For example, the default channel for {pipelines-title} Operator version `1.7` is `pipelines-1.7`. The `latest` channel enables installation of the most recent stable version of the {pipelines-title} Operator.
<2> Name of the Operator to subscribe to.
<3> Name of the CatalogSource that provides the Operator.
<4> Namespace of the CatalogSource. Use `openshift-marketplace` for the default software catalog sources.
. Create the Subscription object:
+
----
$ oc apply -f sub.yaml
----
+
The {pipelines-title} Operator is now installed in the default target namespace `openshift-operators`.