The Cloud Manager module allows you to provision a cloud provider-managed Redis instance within your cluster network.
When you create a Redis instance in Kyma, 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 feature of the following cloud providers:
- Amazon Web Services Amazon ElastiCashe for Redis OSS
- Google Cloud Memorystore
- Microsoft Azure Azure Cache for Redis
You can configure Cloud Manager's Redis instances using a dedicated Redis instance custom resource (CR) corresponding with the cloud provider for your Kyma cluster, namely AwsRedisInstance CR, GcpRedisInstance CR, or AzureRedisInstance CR.
When you provision a Redis instance, you can choose between Standard or Premium Tier.
- Standard Tier offers one instance.
- Premium Tier offers high availability with automatic failover by provisioning an additional read replica of your instance.
To instantiate Redis, an IpRange CR must exist in the Kyma cluster. IpRange defines network address space reserved for your cloud provider's NFS 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.
AwsRedisInstance, GcpRedisInstance, and AzureRedisInstance are namespace-level CRs. Once you create any of the Redis resources, the following are also created automatically:
- IpRange CR
- IpRange is a cluster-level CR.
- Only one IpRange CR can exist per cluster.
- If you don't want the default IpRange 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 instance CR.
- The Secret holds values and information used to access the Redis instance.
Using the Cloud Manager module and enabling Redis, introduces additional costs. For more information, see Calculation with the Cloud Manager Module.