Networking on Docs

Database connectivity

Mon, 01 Jan 0001 00:00:00 +0000

Connecting applications to Redis Enterprise databases in Kubernetes involves understanding service discovery, credentials management, and access patterns. This guide covers the essential connectivity aspects unique to Kubernetes deployments.

Service types and access patterns

When you create a RedisEnterpriseDatabase (REDB), the Redis Enterprise operator automatically creates Kubernetes services to route traffic to your database. Understanding these service types is crucial for proper connectivity.

Configure Ingress for external routing

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

Before creating an Ingress, you'll need:

Use OpenShift routes for external database access

Mon, 01 Jan 0001 00:00:00 +0000

OpenShift routes allow requests to be routed to the database or cluster API from outside the cluster. For more information about routes, see OpenShift documentation.

Prerequisites

Before you can connect to your database from outside the cluster, you'll need the root CA certificate of the DMC Proxy server to validate the server certificate.

Configure Istio for external routing

Mon, 01 Jan 0001 00:00:00 +0000

Redis Enterprise for Kubernetes has the ability to use an Istio Ingress gateway as an alternative to NGINX or HaProxy Ingress controllers.

Istio can also understand Ingress resources, but using that mechanism takes away the advantages and options that the native Istio resources provide. Istio offers its own configuration methods using custom resources.

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.

Establish external routing on the RedisEnterpriseCluster

Mon, 01 Jan 0001 00:00:00 +0000

An Ingress is an API resource that provides a standardized and flexible way to manage external access to services running within a Kubernetes cluster.

Install Ingress controller

Redis Enterprise for Kubernetes supports the Ingress controllers below:

Enable cluster-aware clients (OSS Cluster API)

Mon, 01 Jan 0001 00:00:00 +0000

The OSS Cluster API improves performance by allowing cluster-aware Redis clients to discover database topology and route requests directly. This feature supports cluster-aware clients running on the same Kubernetes cluster (internal) and cluster-aware clients outside the Kubernetes cluster (external).

Note:

Enabling external access for OSS Cluster API creates a separate LoadBalancer service for each Redis Enterprise pod in addition to the LoadBalancer service for the cluster endpoint. LoadBalancers are resources that can significantly increase operational costs; plan your infrastructure budget accordingly.

Prerequisites

RedisEnterpriseCluster (REC) running version 8.0.10-tbd or later.
Proxy policy is set to all-master-shards or all-nodes.
Modules used by the database (if any) are bundled modules.
The database is not an Active-Active database.

Limitations

OSS Cluster databases with external access must be created and managed using the RedisEnterpriseDatabase (REDB) custom resource. You cannot create or configure these databases using the Redis Enterprise REST API directly.

Enable OSS Cluster API

To enable cluster-aware clients, edit the REC and REDB custom resources with the following fields.