diff --git a/content/operate/kubernetes/networking/istio-ingress.md b/content/operate/kubernetes/networking/istio-ingress.md
index 129fbf3e75..a71836c1bd 100644
--- a/content/operate/kubernetes/networking/istio-ingress.md
+++ b/content/operate/kubernetes/networking/istio-ingress.md
@@ -17,6 +17,10 @@ Istio can also understand Ingress resources, but using that mechanism takes away
 
 To configure Istio to work with the Redis Kubernetes operator, we will use two custom resources: a `Gateway` and a `VirtualService`. Then you'll be able to establish external access to your database.
 
+{{< note >}}
+When using Istio ingress for Redis on Kubernetes, avoid partial wildcard hostnames in your REC configuration. Use only valid FQDNs or leftmost wildcards for Istio compatibility and stable external routing. For more information, see [Istio Ingress Fails for Redis on Kubernetes with Partial Wildcard Hostnames](https://support.redislabs.com/hc/en-us/articles/30446436267666-Istio-Ingress-Fails-for-Redis-on-Kubernetes-with-Partial-Wildcard-Hostnames).
+{{< /note >}}
+
 ## Install and configure Istio for Redis Enterprise
 
 1. [Download](https://istio.io/latest/docs/setup/getting-started/) and [install](https://istio.io/latest/docs/setup/getting-started/) Istio (see instructions from Istio's [Getting Started](https://istio.io/latest/docs/setup/getting-started/) guide).
@@ -78,8 +82,6 @@ To configure Istio to work with the Redis Kubernetes operator, we will use two c
           mode: PASSTHROUGH
     ```
 
-
-
 1. Apply the `Gateway` custom resource file to create the Ingress gateway.
 
     ```sh
@@ -132,7 +134,6 @@ To configure Istio to work with the Redis Kubernetes operator, we will use two c
 
     - Replace `.istio.k8s.my.example.com` with the domain that matches your DNS record.
     - The gateway's metadata name must be similar to the gateway's spec name (`redis-gateway` in this example).
-   
 1. Apply `VirtualService` custom resource file to create the virtual service.
 
     ```sh
diff --git a/content/operate/kubernetes/release-notes/7-22-0-releases/_index.md b/content/operate/kubernetes/release-notes/7-22-0-releases/_index.md
index 9708c5a1bd..5a3ebd9b9a 100644
--- a/content/operate/kubernetes/release-notes/7-22-0-releases/_index.md
+++ b/content/operate/kubernetes/release-notes/7-22-0-releases/_index.md
@@ -26,6 +26,8 @@ Redis Enterprise for Kubernetes 7.22.0 includes bug fixes, enhancements, and sup
 
 - **PVC expansion is not supported when using Redis on Flash (Auto Tiering) (RED-165770)** Do not enable `enablePersistentVolumeResize` if your REC uses `redisOnFlashSpec` as this will result in conflicts.
 
+- **Istio ingress does not support partial wildcard hostnames** When using Istio ingress for Redis on Kubernetes, avoid partial wildcard hostnames in your REC configuration. Use only valid FQDNs or leftmost wildcards for Istio compatibility and stable external routing. For more information, see [Istio Ingress Fails for Redis on Kubernetes with Partial Wildcard Hostnames](https://support.redislabs.com/hc/en-us/articles/30446436267666-Istio-Ingress-Fails-for-Redis-on-Kubernetes-with-Partial-Wildcard-Hostnames).
+
 - **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.
 
 - **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)**