ContextQMD
Back to Redis

Index

content/operate/kubernetes/networking/_index.md

latest3.1 KB
Original Source

Configure 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.

Database connectivity

Connect applications to your Redis Enterprise databases:

  • [Database connectivity]({{< relref "/operate/kubernetes/networking/database-connectivity" >}}) - Comprehensive guide to in-cluster and external database access, service discovery, and credentials management.

External routing methods

Choose the appropriate method for your environment to enable external access:

  • [Ingress routing]({{< relref "/operate/kubernetes/networking/ingress" >}}) - Use NGINX or HAProxy ingress controllers with ingress API resources
  • [Istio ingress routing]({{< relref "/operate/kubernetes/networking/istio-ingress" >}}) - Use Istio service mesh with Gateway and VirtualService API resources
  • [OpenShift routes]({{< relref "/operate/kubernetes/networking/routes" >}}) - Use OpenShift-specific route resources for external traffic

Automatic ingress configuration

For Active-Active databases, configure automatic ingress creation:

  • [REC external routing]({{< relref "/operate/kubernetes/networking/ingressorroutespec" >}}) - Use ingressOrRouteSpec field in RedisEnterpriseCluster (REC) for automatic ingress creation

ingressOrRouteSpec for Active-Active databases

Versions 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]({{< relref "/operate/kubernetes/networking/ingressorroutespec" >}}) for more details.

This 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.

OSS Cluster API support

[OSS Cluster API]({{< relref "/operate/kubernetes/networking/cluster-aware-clients" >}}) is supported for both internal and external clients:

  • Internal clients running on pods within the same Kubernetes cluster can connect directly to Redis Enterprise pods using pod IPs.
  • 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.

See [Enable cluster-aware clients (OSS Cluster API)]({{< relref "/operate/kubernetes/networking/cluster-aware-clients" >}}) for configuration details.

REC domain name

The RedisEnterpriseCluster does not support custom domain names. Domain names for the REC are in the following format: <rec-name>.<namespace>.svc.cluster.local.