Docs for bringing your own Redis instance for the rate limiter

[artberger]

Version

master

Describe the requested changes

Example steps for how to use your own redis instance

• Install from scratch
• Upgrade from using the default redis to using your own existing instance
• Different Helm fields if you need to do different things like clustered redis

Benefits include they might have their own HA capabilities with their own instance.

Link to any relevant existing docs

• In Edge, we mention DynamoDB, but it's not a full example: https://docs.solo.io/gloo-edge/latest/guides/security/rate_limiting/enterprise/#dynamodb-backed-rate-limit-service
• Helm reference page has some redis fields, but again not a full example: https://docs.solo.io/gloo-edge/latest/reference/helm_chart_values/enterprise_helm_chart_values/
• In Mesh, somewhat related to this architecture page: https://docs.solo.io/gloo-mesh-enterprise/latest/policies/rate-limit/#architecture
• Can try it out in the AWS account, ElastiCache Redis cluster. Guide to set up Edge in EKS: https://www.solo.io/blog/from-zero-to-gloo-edge-in-15-minutes-eks-edition/

Browser Information

No response

Additional Context

Follow up to:

• https://github.com/solo-io/gloo/issues/6577
• https://github.com/solo-io/gloo-mesh-enterprise/issues/2291#issuecomment-1063425690

[nfuden]

It might be worth it to mention what it takes in general as there are similar considerations in other services such as extauth