Kyma

Appearance

Redis Cluster ​

WARNING

This is a beta feature available only per request for SAP-internal teams.

Use the Cloud Manager module to provision a Redis cluster. With the Cloud Manager module, you can provision a cloud provider-managed Redis cluster in cluster mode within your cluster network.

NOTE

Using the Cloud Manager module and enabling Redis, introduces additional costs. For more information, see Calculation with the Cloud Manager Module.

Cloud Providers ​

When you create a Redis cluster in SAP BTP, Kyma runtime, you depend on the cloud provider of your Kyma cluster. The cloud provider in use determines the exact implementation.

The Cloud Manager module supports the Redis cluster feature of the following cloud providers:

You can configure Cloud Manager's Redis clusters using a dedicated Redis cluster custom resource (CR) corresponding with the cloud provider for your Kyma cluster, namely AwsRedisCluster CR, GcpRedisCluster CR, or AzureRedisCluster CR. For more information, see Redis Resources.

Tiers ​

Depending on the cloud provider, you can choose between several tiers. Cloud Manager offers a dedicated subset of machine types available at the cloud providers.

Prerequisites ​

  • For Amazon Web Service and Microsoft Azure, an IpRange CR must exist in the Kyma cluster. IpRange defines network address space reserved for your cloud provider's Redis resources. If you don't create the IpRange CR manually, Cloud Manager creates a default IpRange CR with the default address space and Classless Inter-Domain Routing(CIDR) selected. For more information, see IpRange Custom Resoucre.
  • For Google Cloud, a GcpSubnet CR must exist in the Kyma cluster. GcpSubnet specifies the VPC Network Subnet. Once needed, the resource is automatically created with the hardcoded CIDR. For most use cases, this automatic allocation is sufficient. For more information, see GcpSubnet Custom Resource.

Lifecycle ​

AwsRedisCluster, GcpRedisCluster, and AzureRedisCluster are namespace-level CRs. When you create any of the Redis cluster resources, the following resources are also created automatically:

  • IpRange CR / GcpSubnet
    • IpRange and GcpSubnet are cluster-level CRs.
    • Only one IpRange CR or GcpSubnet CR can exist per cluster.
    • If you don't want the default IpRange or GcpSubnet to be used, create one manually.
  • Secret CR
    • The Secret is a namespace-level CR.
    • The Secret's name is the same as the name of the respective Redis cluster CR.
    • The Secret holds values and information used to access the Redis cluster.