Every time a Redis Enterprise database (REDB), Redis Enterprise Active-Active database (REAADB), or Redis Enterprise cluster (REC) is created, the Redis Enterprise operator, automatically creates a service to allow requests to be routed to that resource.
Redis Enterprise supports three types of services for accessing databases:
For accessing Redis Enterprise clusters (REC), Redis Enterprise supports the following types of services:
By default, the operator creates a
ClusterIP type service, which exposes a cluster-internal IP and can only be accessed from within the K8s cluster. For requests to be routed from outside the K8s cluster, you need an ingress controller (or routes if you are using OpenShift).
- To use NGNX or HAProxy, see Establish external routing with an ingress.
- To use OpenShift routes, see Use OpenShift routes for external database access.
- To use Istio, see Configure Istio for external routing
6.4.2-4 preview feature
The 6.4.2-4 release of Redis Enterprise for Kubernetes includes a public preview feature for ingress configuration. The
ingressOrRouteSpec field is available in the RedisEnterpriseCluster spec which automatically creates an ingress (or route) for the API service and databases (REAADB) on that REC. See Establish external routing on the REC for more details.
The preview release of this feature only supports automatic ingress creation for Active-Active databases with the RedisEnterpriseActiveActiveDatabase (REAADB) custom resource. Use with the standard Redis Enterprise database (REDB) is not supported in the public preview.