Skip to content

Commit

Permalink
OSSMDOC-326 Note about Jaeger damoneset support.
Browse files Browse the repository at this point in the history
  • Loading branch information
JStickler committed Jun 10, 2021
1 parent 757a7fa commit 424e60c
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 0 deletions.
2 changes: 2 additions & 0 deletions modules/jaeger-deployment-best-practices.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,6 @@ This module included in the following assemblies:

* If you have a multitenant implementation and tenants are separated by namespaces, deploy a Jaeger instance to each tenant namespace.

** Jaeger agent as a sidecar is the only supported configuration. Jaeger as a daemonset is not supported for multitenant installations or OpenShift Dedicated.

* If you are installing Jaeger as part of Red Hat OpenShift Service Mesh, Jaeger resources must be installed in the same namespace as the `ServiceMeshControlPlane` resource.
5 changes: 5 additions & 0 deletions modules/ossm-supported-configurations.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,11 @@ For additional information about {ProductName} lifecycle and supported configura

* The Kiali observability console is only supported on the two most recent releases of the Chrome, Edge, Firefox, or Safari browsers.

[id="ossm-supported-configurations-jaeger_{context}"]
== Supported configurations for Distributed Tracing

* Jaeger agent as a sidecar is the only supported configuration for Jaeger. Jaeger as a daemonset is not supported for multitenant installations or OpenShift Dedicated.

[id="ossm-supported-configurations-adapters_{context}"]
== Supported Mixer adapters

Expand Down

0 comments on commit 424e60c

Please sign in to comment.