{
  "id": "networking",
  "title": "Networking",
  "url": "https://redis.io/docs/latest/operate/kubernetes/8.0/networking/",
  "summary": "Configure networking and external access for Redis Enterprise clusters and databases on Kubernetes.",
  "content": "\nConfigure networking and external access for your Redis Enterprise deployment on Kubernetes. By default, Kubernetes doesn't allow external access to your Redis databases. Redis Enterprise for Kubernetes provides several methods to route external traffic to your clusters and databases.\n\n## Database connectivity\n\nConnect applications to your Redis Enterprise databases:\n\n- [Database connectivity](https://redis.io/docs/latest/operate/kubernetes/networking/database-connectivity) - Comprehensive guide to in-cluster and external database access, service discovery, and credentials management.\n\n## External routing methods\n\nChoose the appropriate method for your environment to enable external access:\n\n- [Ingress routing](https://redis.io/docs/latest/operate/kubernetes/networking/ingress) - Use NGINX or HAProxy ingress controllers with `ingress` API resources\n- [Istio ingress routing](https://redis.io/docs/latest/operate/kubernetes/networking/istio-ingress) - Use Istio service mesh with `Gateway` and `VirtualService` API resources\n- [OpenShift routes](https://redis.io/docs/latest/operate/kubernetes/networking/routes) - Use OpenShift-specific route resources for external traffic\n\n## Automatic ingress configuration\n\nFor Active-Active databases, configure automatic ingress creation:\n\n- [REC external routing](https://redis.io/docs/latest/operate/kubernetes/networking/ingressorroutespec) - Use `ingressOrRouteSpec` field in RedisEnterpriseCluster (REC) for automatic ingress creation\n\n## `ingressOrRouteSpec` for Active-Active databases\n\nVersions 6.4.2 or later of Redis Enterprise for Kubernetes include a feature for ingress configuration. The `ingressOrRouteSpec` field is available in the RedisEnterpriseCluster spec to automatically create an Ingress (or route) for the API service and databases (REAADB) on that REC. See [REC external routing](https://redis.io/docs/latest/operate/kubernetes/networking/ingressorroutespec) for more details.\n\nThis feature only supports automatic Ingress creation for Active-Active databases created and managed with the RedisEnterpriseActiveActiveDatabase (REAADB) custom resource. Use with the standard Redis Enterprise database (REDB) is not currently supported.\n\n## OSS Cluster API support\n\n[OSS Cluster API](https://redis.io/docs/latest/operate/kubernetes/networking/cluster-aware-clients) is supported for both internal and external clients:\n\n- **Internal clients** running on pods within the same Kubernetes cluster can connect directly to Redis Enterprise pods using pod IPs.\n- **External clients** outside the Kubernetes cluster can connect through LoadBalancer services when `enableExternalAccess: true` is configured in the database specification. This creates a separate LoadBalancer service for each Redis Enterprise pod. Note that LoadBalancers are resources that can significantly increase operational costs.\n\nSee [Enable cluster-aware clients (OSS Cluster API)](https://redis.io/docs/latest/operate/kubernetes/networking/cluster-aware-clients) for configuration details.\n\n## REC domain name\n\nThe RedisEnterpriseCluster does not support custom domain names. Domain names for the REC are in the following format: `\u003crec-name\u003e.\u003cnamespace\u003e.svc.cluster.local`.\n",
  "tags": ["docs","operate","kubernetes"],
  "last_updated": "2026-06-04T14:49:57+01:00",
  "children": [{"id":"database-connectivity","summary":"Connect applications to Redis Enterprise databases in Kubernetes clusters with in-cluster and external access patterns.","title":"Database connectivity","url":"https://redis.io/docs/latest/operate/kubernetes/8.0/networking/database-connectivity/"},{"id":"ingress","summary":"Configure an ingress controller to access your Redis Enterprise databases from outside the Kubernetes cluster.","title":"Configure Ingress for external routing","url":"https://redis.io/docs/latest/operate/kubernetes/8.0/networking/ingress/"},{"id":"routes","summary":"","title":"Use OpenShift routes for external database access","url":"https://redis.io/docs/latest/operate/kubernetes/8.0/networking/routes/"},{"id":"istio-ingress","summary":"Configure Istio as an ingress controller for access to your Redis Enterprise databases from outside the Kubernetes cluster.","title":"Configure Istio for external routing","url":"https://redis.io/docs/latest/operate/kubernetes/8.0/networking/istio-ingress/"},{"id":"ingressorroutespec","summary":"","title":"Establish external routing on the RedisEnterpriseCluster","url":"https://redis.io/docs/latest/operate/kubernetes/8.0/networking/ingressorroutespec/"},{"id":"cluster-aware-clients","summary":"Improve performance with cluster-aware clients by enabling the OSS Cluster API for your Redis Enterprise for Kubernetes database.","title":"Enable cluster-aware clients (OSS Cluster API)","url":"https://redis.io/docs/latest/operate/kubernetes/8.0/networking/cluster-aware-clients/"}]
}