You can install Jaeger on OpenShift Container Platform in either of two ways:
You can install Jaeger as part of Red Hat OpenShift Service Mesh. Jaeger is included by default in the Service Mesh installation. To install Jaeger as part of a service mesh, follow the Red Hat Service Mesh Installation instructions.
If you do not want to install a service mesh, you can use the Jaeger Operator to install the Red Hat build of Jaeger by itself. To install Jaeger without a service mesh, use the following instructions.
Before you can install OpenShift Jaeger, review the installation activities, and ensure that you meet the prerequisites:
Possess an active OpenShift Container Platform subscription on your Red Hat account. If you do not have a subscription, contact your sales representative for more information.
Review the OpenShift Container Platform 4.3 overview.
Install OpenShift Container Platform 4.3.
Install the version of the OpenShift Container Platform command line utility (the oc
client tool) that matches your OpenShift Container Platform version and add it to your path.
An account with the cluster-admin
role.
The steps for installing OpenShift Jaeger are as follows:
Review the documentation and determine your deployment strategy.
If your deployment strategy requires persistent storage, install the Elasticsearch Operator via the OperatorHub.
Install the Jaeger Operator via the OperatorHub.
Modify the Jaeger YAML file to support your deployment strategy.
Deploy one or more instances of Jaeger to your OpenShift Container Platform environment.
The default Jaeger deployment uses in-memory storage because it is designed to be installed quickly for those evaluating Jaeger, giving demonstrations, or using Jaeger in a test environment. If you plan to use Jaeger in production, you must install a persistent storage option, in this case, Elasticsearch.
Access to the OpenShift Container Platform web console.
An account with the cluster-admin
role.
Do not install Community versions of the Operators. Community Operators are not supported. |
If you have already installed the Elasticsearch Operator as part of OpenShift cluster logging, you do not need to install the Elasticsearch Operator again. The Jaeger Operator will create the Elasticsearch instance using the installed Elasticsearch Operator. |
Log in to the OpenShift Container Platform web console as a user with the cluster-admin
role.
Navigate to Operators → OperatorHub.
Type Elasticsearch into the filter box to locate the Elasticsearch Operator.
Click the Elasticsearch Operator provided by Red Hat to display information about the Operator.
Click Install.
On the Create Operator Subscription page, select the A specific namespace on the cluster option and then select openshift-operators-redhat from the menu.
Select the Update Channel that matches your OpenShift Container Platform installation. For example, if you are installing on OpenShift Container Platform version 4.5, select the 4.5 update channel.
Select the Automatic Approval Strategy.
The Manual approval strategy requires a user with appropriate credentials to approve the Operator install and subscription process. |
Click Subscribe.
On the Installed Operators page, select the openshift-operators-redhat
project. Wait until you see that the Elasticsearch Operator shows a status of "InstallSucceeded" before continuing.
To install Jaeger you use the OperatorHub to install the Jaeger Operator.
By default the Operator is installed in the openshift-operators
project.
Access to the OpenShift Container Platform web console.
An account with the cluster-admin
role.
If you require persistent storage, you must also install the Elasticsearch Operator before installing the Jaeger Operator.
Do not install Community versions of the Operators. Community Operators are not supported. |
Log in to the OpenShift Container Platform web console as a user with the cluster-admin
role.
Navigate to Operators → OperatorHub.
Type Jaeger into the filter to locate the Jaeger Operator.
Click the Jaeger Operator provided by Red Hat to display information about the Operator.
Click Install.
On the Create Operator Subscription page, select All namespaces on the cluster (default). This installs the Operator in the default openshift-operators
project and makes the Operator available to all projects in the cluster.
Select the stable Update Channel. This will automatically update Jaeger as new versions are released. If you select a maintenance channel, for example, 1.17-stable, you will receive bug fixes and security patches for the length of the support cycle for that version.
Select an Approval Strategy. You can select Automatic or Manual updates. If you choose Automatic updates for an installed Operator, when a new version of that Operator is available, the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without human intervention. If you select Manual updates, when a newer version of an Operator is available, the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to have the Operator updated to the new version.
The Manual approval strategy requires a user with appropriate credentials to approve the Operator install and subscription process. |
Click Subscribe.
On the Subscription Overview page, select the openshift-operators
project. Wait until you see that the Jaeger Operator shows a status of "InstallSucceeded" before continuing.