mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
118 lines
3.6 KiB
Plaintext
118 lines
3.6 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * observability/logging/cluster-logging-deploying.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="cluster-logging-deploy-cli_{context}"]
|
|
= Installing the {clo} by using the CLI
|
|
|
|
You can use the {oc-first} to install the {clo}.
|
|
|
|
.Prerequisites
|
|
|
|
ifdef::openshift-origin[]
|
|
* Ensure that you have downloaded the {cluster-manager-url-pull} as shown in _Obtaining the installation program_ in the installation documentation for your platform.
|
|
+
|
|
If you have the pull secret, add the `redhat-operators` catalog to the OperatorHub custom resource (CR) as shown in *Configuring {product-title} to use Red Hat Operators*.
|
|
endif::[]
|
|
|
|
* You have administrator permissions.
|
|
* You have installed the {oc-first}.
|
|
|
|
.Procedure
|
|
|
|
. Create a `Namespace` object as a YAML file:
|
|
+
|
|
.Example `Namespace` object
|
|
[source,yaml]
|
|
----
|
|
apiVersion: v1
|
|
kind: Namespace
|
|
metadata:
|
|
name: <name> <1>
|
|
annotations:
|
|
openshift.io/node-selector: ""
|
|
labels:
|
|
openshift.io/cluster-monitoring: "true"
|
|
----
|
|
<1> You must specify `openshift-logging` as the name of the namespace for logging versions 5.7 and earlier versions. For logging 5.8 and later versions, you can use any name.
|
|
|
|
. Apply the `Namespace` object by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc apply -f <filename>.yaml
|
|
----
|
|
|
|
. Create an `OperatorGroup` object as a YAML file:
|
|
+
|
|
.Example `OperatorGroup` object
|
|
[source,yaml]
|
|
----
|
|
apiVersion: operators.coreos.com/v1
|
|
kind: OperatorGroup
|
|
metadata:
|
|
name: cluster-logging
|
|
namespace: openshift-logging <1>
|
|
spec:
|
|
targetNamespaces: [ ] <2>
|
|
----
|
|
<1> Ensure that the `namespace` field is set to `openshift-logging`.
|
|
<2> For logging versions 5.7 and earlier, set `targetNamespaces` to `openshift-logging`. For logging versions 5.8 and later, the default installation mode is all namespaces on the cluster, or specify a list of namespaces separated by a comma.
|
|
|
|
. Apply the `OperatorGroup` object by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc apply -f <filename>.yaml
|
|
----
|
|
|
|
. Create a `Subscription` object to subscribe the namespace to the {clo}:
|
|
+
|
|
.Example `Subscription` object
|
|
[source,yaml]
|
|
----
|
|
apiVersion: operators.coreos.com/v1alpha1
|
|
kind: Subscription
|
|
metadata:
|
|
name: cluster-logging
|
|
namespace: openshift-logging <1>
|
|
spec:
|
|
channel: stable <2>
|
|
name: cluster-logging
|
|
source: redhat-operators <3>
|
|
sourceNamespace: openshift-marketplace
|
|
----
|
|
<1> You must specify the `openshift-logging` namespace for logging versions 5.7 and older. For logging 5.8 and later versions, you can use any namespace.
|
|
<2> Specify `stable` or `stable-x.y` as the channel.
|
|
<3> Specify `redhat-operators`. If your {product-title} cluster is installed on a restricted network, also known as a disconnected cluster, specify the name of the `CatalogSource` object you created when you configured the Operator Lifecycle Manager (OLM).
|
|
|
|
. Apply the subscription by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc apply -f <filename>.yaml
|
|
----
|
|
+
|
|
The {clo} is installed to the `openshift-logging` namespace.
|
|
|
|
.Verification
|
|
|
|
. Run the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get csv -n <namespace>
|
|
----
|
|
|
|
. Observe the output and confirm that the {clo} exists in the namespace:
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAMESPACE NAME DISPLAY VERSION REPLACES PHASE
|
|
...
|
|
openshift-logging clusterlogging.5.8.0-202007012112.p0 OpenShift Logging 5.8.0-202007012112.p0 Succeeded
|
|
...
|
|
----
|