diff --git a/modules/ossm-upgrade-known-issues.adoc b/modules/ossm-upgrade-known-issues.adoc
index 034edbfcc1df..c6bbc0a99891 100644
--- a/modules/ossm-upgrade-known-issues.adoc
+++ b/modules/ossm-upgrade-known-issues.adoc
@@ -7,6 +7,8 @@
 
 Known issues that may affect your upgrade include:
 
+* When upgrading an Operator, custom configurations for Jaeger or Kiali might be reverted. Before upgrading an Operator, note any custom configuration settings for the Jaeger or Kiali objects in the {SMProductShortName} production deployment so that you can recreate them.
+
 * {SMProductName} does not support the use of `EnvoyFilter` configuration except where explicitly documented. This is due to tight coupling with the underlying Envoy APIs, meaning that backward compatibility cannot be maintained. If you are using Envoy Filters, and the configuration generated by Istio has changed due to the lastest version of Envoy introduced by upgrading your `ServiceMeshControlPlane`, that has the potential to break any `EnvoyFilter` you may have implemented.
 
 * https://issues.redhat.com/browse/OSSM-1505[OSSM-1505] `ServiceMeshExtension` does not work with {product-title} version 4.11. Because `ServiceMeshExtension` has been deprecated in {SMProductName} 2.2, this known issue will not be fixed and you must migrate your extensions to `WasmPluging`