Skip to content

K8s: add istio wildcard limitation #2327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 3, 2025
Merged

K8s: add istio wildcard limitation #2327

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions content/operate/kubernetes/networking/istio-ingress.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
2 changes: 2 additions & 0 deletions content/operate/kubernetes/release-notes/7-22-0-releases/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)**
Expand Down