mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
71 lines
1.8 KiB
Plaintext
71 lines
1.8 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * hardware_enablement/psap-special-resource-operator.adoc
|
|
|
|
:_content-type: PROCEDURE
|
|
[id="installing-the-special-resource-operator-using-cli_{context}"]
|
|
= Installing the Special Resource Operator by using the CLI
|
|
|
|
As a cluster administrator, you can install the Special Resource Operator (SRO) by using the OpenShift CLI.
|
|
|
|
.Prerequisites
|
|
|
|
* You have a running {product-title} cluster.
|
|
* You installed the OpenShift CLI (`oc`).
|
|
* You are logged into the OpenShift CLI as a user with `cluster-admin` privileges.
|
|
|
|
.Procedure
|
|
|
|
. Install the SRO in the `openshift-operators` namespace:
|
|
|
|
.. Create the following `Subscription` CR and save the YAML in the `sro-sub.yaml` file:
|
|
+
|
|
.Example Subscription CR
|
|
[source,yaml]
|
|
----
|
|
apiVersion: operators.coreos.com/v1alpha1
|
|
kind: Subscription
|
|
metadata:
|
|
name: openshift-special-resource-operator
|
|
namespace: openshift-operators
|
|
spec:
|
|
channel: "stable"
|
|
installPlanApproval: Automatic
|
|
name: openshift-special-resource-operator
|
|
source: redhat-operators
|
|
sourceNamespace: openshift-marketplace
|
|
----
|
|
|
|
.. Create the subscription object by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc create -f sro-sub.yaml
|
|
----
|
|
|
|
.. Switch to the `openshift-operators` project:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc project openshift-operators
|
|
----
|
|
|
|
.Verification
|
|
|
|
* To verify that the Operator deployment is successful, run:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get pods
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME READY STATUS RESTARTS AGE
|
|
nfd-controller-manager-7f4c5f5778-4lvvk 2/2 Running 0 89s
|
|
special-resource-controller-manager-6dbf7d4f6f-9kl8h 2/2 Running 0 81s
|
|
----
|
|
+
|
|
A successful deployment shows a `Running` status.
|