You can install Red Hat OpenShift distributed tracing on OpenShift Container Platform in either of two ways:
You can install Red Hat OpenShift distributed tracing as part of Red Hat OpenShift Service Mesh. Distributed tracing is included by default in the Service Mesh installation. To install Red Hat OpenShift distributed tracing as part of a service mesh, follow the Red Hat Service Mesh Installation instructions. You must install Red Hat OpenShift distributed tracing in the same namespace as your service mesh, that is, the ServiceMeshControlPlane
and the Red Hat OpenShift distributed tracing resources must be in the same namespace.
If you do not want to install a service mesh, you can use the Red Hat OpenShift distributed tracing Operators to install distributed tracing by itself. To install Red Hat OpenShift distributed tracing without a service mesh, use the following instructions.
Before you can install Red Hat OpenShift distributed tracing, 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.10 overview.
Install OpenShift Container Platform 4.10.
Install the version of the OpenShift CLI (oc
) that matches your OpenShift Container Platform version and add it to your path.
An account with the cluster-admin
role.
The steps for installing Red Hat OpenShift distributed tracing are as follows:
Review the documentation and determine your deployment strategy.
If your deployment strategy requires persistent storage, install the OpenShift Elasticsearch Operator via the OperatorHub.
Install the Red Hat OpenShift distributed tracing platform Operator via the OperatorHub.
Modify the custom resource YAML file to support your deployment strategy.
Deploy one or more instances of Red Hat OpenShift distributed tracing platform to your OpenShift Container Platform environment.
The default Red Hat OpenShift distributed tracing platform deployment uses in-memory storage because it is designed to be installed quickly for those evaluating Red Hat OpenShift distributed tracing, giving demonstrations, or using Red Hat OpenShift distributed tracing platform in a test environment. If you plan to use Red Hat OpenShift distributed tracing platform in production, you must install and configure a persistent storage option, in this case, Elasticsearch.
You have access to the OpenShift Container Platform web console.
You have access to the cluster as a user with the cluster-admin
role. If you use Red Hat OpenShift Dedicated, you must have an account with the dedicated-admin
role.
Do not install Community versions of the Operators. Community Operators are not supported. |
If you have already installed the OpenShift Elasticsearch Operator as part of OpenShift Logging, you do not need to install the OpenShift Elasticsearch Operator again. The Red Hat OpenShift distributed tracing platform Operator creates the Elasticsearch instance using the installed OpenShift Elasticsearch Operator. |
Log in to the OpenShift Container Platform web console as a user with the cluster-admin
role. If you use Red Hat OpenShift Dedicated, you must have an account with the dedicated-admin
role.
Navigate to Operators → OperatorHub.
Type Elasticsearch into the filter box to locate the OpenShift Elasticsearch Operator.
Click the OpenShift Elasticsearch Operator provided by Red Hat to display information about the Operator.
Click Install.
On the Install Operator page, select the stable Update Channel. This automatically updates your Operator as new versions are released.
Accept the default All namespaces on the cluster (default). This installs the Operator in the default openshift-operators-redhat
project and makes the Operator available to all projects in the cluster.
The Elasticsearch installation requires the openshift-operators-redhat namespace for the OpenShift Elasticsearch Operator. The other Red Hat OpenShift distributed tracing Operators are installed in the |
Accept the default Automatic approval strategy. By accepting the default, when a new version of this Operator is available, 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, 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 Install.
On the Installed Operators page, select the openshift-operators-redhat
project. Wait until you see that the OpenShift Elasticsearch Operator shows a status of "InstallSucceeded" before continuing.
To install Red Hat OpenShift distributed tracing platform, you use the OperatorHub to install the Red Hat OpenShift distributed tracing platform Operator.
By default, the Operator is installed in the openshift-operators
project.
You have access to the OpenShift Container Platform web console.
You have access to the cluster as a user with the cluster-admin
role. If you use Red Hat OpenShift Dedicated, you must have an account with the dedicated-admin
role.
If you require persistent storage, you must also install the OpenShift Elasticsearch Operator before installing the Red Hat OpenShift distributed tracing platform 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. If you use Red Hat OpenShift Dedicated, you must have an account with the dedicated-admin
role.
Navigate to Operators → OperatorHub.
Type distributed tracing platform into the filter to locate the Red Hat OpenShift distributed tracing platform Operator.
Click the Red Hat OpenShift distributed tracing platform Operator provided by Red Hat to display information about the Operator.
Click Install.
On the Install Operator page, select the stable Update Channel. This automatically updates your Operator as new versions are released.
Accept the default 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.
Accept the default Automatic approval strategy. By accepting the default, when a new version of this Operator is available, 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, 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 Install.
Navigate to Operators → Installed Operators.
On the Installed Operators page, select the openshift-operators
project. Wait until you see that the Red Hat OpenShift distributed tracing platform Operator shows a status of "Succeeded" before continuing.
The Red Hat OpenShift distributed tracing data collection Operator is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope. |
To install Red Hat OpenShift distributed tracing data collection, you use the OperatorHub to install the Red Hat OpenShift distributed tracing data collection Operator.
By default, the Operator is installed in the openshift-operators
project.
You have access to the OpenShift Container Platform web console.
You have access to the cluster as a user with the cluster-admin
role. If you use Red Hat OpenShift Dedicated, you must have an account with the dedicated-admin
role.
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. If you use Red Hat OpenShift Dedicated, you must have an account with the dedicated-admin
role.
Navigate to Operators → OperatorHub.
Type distributed tracing data collection into the filter to locate the Red Hat OpenShift distributed tracing data collection Operator.
Click the Red Hat OpenShift distributed tracing data collection Operator provided by Red Hat to display information about the Operator.
Click Install.
On the Install Operator page, accept the default stable Update channel. This automatically updates your Operator as new versions are released.
Accept the default 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.
Accept the default Automatic approval strategy. By accepting the default, when a new version of this Operator is available, 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, 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 Install.
Navigate to Operators → Installed Operators.
On the Installed Operators page, select the openshift-operators
project. Wait until you see that the Red Hat OpenShift distributed tracing data collection Operator shows a status of "Succeeded" before continuing.