Skip to content

Commit

Permalink
Change order
Browse files Browse the repository at this point in the history
  • Loading branch information
mmitoraj committed Jan 10, 2025
1 parent 08694c2 commit ad3eaf5
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/user/00-40-redis.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,6 @@

The Cloud Manager module allows you to provision a cloud provider-managed Redis instance within your cluster network.

### Tiers

When you provision a Redis instance, you can choose between the Standard and Premium Tier.

* Standard Tier offers one instance.
* Premium Tier offers high availability with automatic failover by provisioning an additional read replica of your instance.

### Cloud Providers

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.
Expand All @@ -23,6 +16,13 @@ Cloud Manager module supports the Redis feature of three cloud providers:

You can configure Cloud Manager's Redis instances using a dedicated Redis instance custom resource corresponding with the cloud provider for your Kyma cluster, namely AwsRedisInstance CR, GcpRedisInstance CR, or AzureRedisInstance CR.

### Tiers

When you provision a Redis instance, you can choose between the 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.

## Prerequisites

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](./resources/04-10-iprange.md).
Expand Down

0 comments on commit ad3eaf5

Please sign in to comment.