diff --git a/modules/jaeger-deploy-default.adoc b/modules/jaeger-deploy-default.adoc index 6ed9382019..efb4d4519a 100644 --- a/modules/jaeger-deploy-default.adoc +++ b/modules/jaeger-deploy-default.adoc @@ -20,6 +20,11 @@ In-memory storage is not persistent, which means that if the Jaeger pod shuts do * Review the instructions for how to customize the Jaeger installation. * An account with the `cluster-admin` role. +[NOTE] +==== +Jaeger streaming is currently unsupported on IBM Z. +==== + .Procedure . Log in to the {product-title} web console as a user with the `cluster-admin` role. diff --git a/modules/jaeger-deploy-streaming.adoc b/modules/jaeger-deploy-streaming.adoc index d45b8e11db..852284d732 100644 --- a/modules/jaeger-deploy-streaming.adoc +++ b/modules/jaeger-deploy-streaming.adoc @@ -21,6 +21,11 @@ The streaming strategy requires an additional Red Hat subscription for AMQ Strea * Review the instructions for how to customize the Jaeger installation. * An account with the `cluster-admin` role. +[NOTE] +==== +Jaeger streaming is currently unsupported on IBM Z. +==== + .Procedure . Log in to the {product-title} web console as a user with the `cluster-admin` role. @@ -138,3 +143,4 @@ jaeger-streaming-kafka-0 2/2 Runnin jaeger-streaming-query-65bf5bb854-ncnc7 3/3 Running 0 80s jaeger-streaming-zookeeper-0 2/2 Running 0 3m39s ---- + diff --git a/modules/jaeger-rn-known-issues.adoc b/modules/jaeger-rn-known-issues.adoc index 8e39646b1f..c9435a0b56 100644 --- a/modules/jaeger-rn-known-issues.adoc +++ b/modules/jaeger-rn-known-issues.adoc @@ -19,8 +19,11 @@ These limitations exist in Jaeger: * Apache Spark is not supported. +* Jaeger streaming via AMQ/Kafka is unsupported on IBM Z and IBM Power Systems. + These are the known issues in Jaeger: * link:https://issues.redhat.com/browse/TRACING-1166[TRACING-1166] It is not currently possible to use the Jaeger streaming strategy within a disconnected environment. When a Kafka cluster is being provisioned, it results in a error: `Failed to pull image registry.redhat.io/amq7/amq-streams-kafka-24-rhel7@sha256:f9ceca004f1b7dccb3b82d9a8027961f9fe4104e0ed69752c0bdd8078b4a1076`. * link:https://issues.redhat.com/browse/TRACING-809[TRACING-809] Jaeger Ingester is incompatible with Kafka 2.3. When there are two or more instances of the Jaeger Ingester and enough traffic it will continuously generate rebalancing messages in the logs. This is due to a regression in Kafka 2.3 that was fixed in Kafka 2.3.1. For more information, see https://github.com/jaegertracing/jaeger/issues/1819[Jaegertracing-1819]. + diff --git a/modules/ossm-rn-known-issues.adoc b/modules/ossm-rn-known-issues.adoc index 89d76ba816..a32c69e4f3 100644 --- a/modules/ossm-rn-known-issues.adoc +++ b/modules/ossm-rn-known-issues.adoc @@ -21,6 +21,8 @@ These limitations exist in {ProductName}: * The first time you access related services such as Jaeger and Grafana, from the Kiali console, you must accept the certificate and re-authenticate using your {product-title} login credentials. This happens due to an issue with how the framework displays embedded pages in the console. +* WebAssembly is unsupported on IBM Z and IBM Power Systems. + [id="ossm-rn-known-issues-ossm_{context}"] == {ProductShortName} known issues diff --git a/modules/ossm-supported-configurations.adoc b/modules/ossm-supported-configurations.adoc index 9847a51926..4fa2ecc8d3 100644 --- a/modules/ossm-supported-configurations.adoc +++ b/modules/ossm-supported-configurations.adoc @@ -17,7 +17,9 @@ OpenShift Online and OpenShift Dedicated are not supported for {ProductName}. ==== * The deployment must be contained to a single {product-title} cluster that is not federated. -* This release of {ProductName} is only available on {product-title} x86_64. +* This release of {ProductName} is only available on {product-title} x86_64, IBM Z, and IBM Power Systems. +** IBM Z is only supported on {product-title} 4.6 and later. +** IBM Power Systems is only supported on {product-title} 4.6 and later. * This release only supports configurations where all {ProductShortName} components are contained in the OpenShift cluster in which it operates. It does not support management of microservices that reside outside of the cluster, or in a multi-cluster scenario. * This release only supports configurations that do not integrate external services such as virtual machines. diff --git a/service_mesh/v2x/preparing-ossm-installation.adoc b/service_mesh/v2x/preparing-ossm-installation.adoc index 1680d2f3d2..63e9ac9396 100644 --- a/service_mesh/v2x/preparing-ossm-installation.adoc +++ b/service_mesh/v2x/preparing-ossm-installation.adoc @@ -15,6 +15,8 @@ Before you can install {ProductName}, review the installation activities, ensure ** xref:../../installing/installing_aws/installing-aws-user-infra.adoc#installing-aws-user-infra[Install {product-title} {product-version} on user-provisioned AWS] ** xref:../../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[Install {product-title} {product-version} on bare metal] ** xref:../../installing/installing_vsphere/installing-vsphere.adoc#installing-vsphere[Install {product-title} {product-version} on vSphere] +** xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[Install {product-title} 4.6 on IBM Z and LinuxONE] +** xref:../../installing/installing_ibm_power/installing-ibm-power.adoc#installing-ibm-power[Install {product-title} 4.6 on IBM Power Systems] + [NOTE] ==== diff --git a/service_mesh/v2x/servicemesh-release-notes.adoc b/service_mesh/v2x/servicemesh-release-notes.adoc index 0cd95d071a..09f57da454 100644 --- a/service_mesh/v2x/servicemesh-release-notes.adoc +++ b/service_mesh/v2x/servicemesh-release-notes.adoc @@ -44,3 +44,5 @@ include::modules/jaeger-rn-known-issues.adoc[leveloffset=+2] include::modules/ossm-rn-fixed-issues.adoc[leveloffset=+1] include::modules/jaeger-rn-fixed-issues.adoc[leveloffset=+2] + +