Skip to main content
Redis is an in-memory data structure store used for caching and improving performance across the application. It can either run inside the Kubernetes cluster as an additional workload, or outside the cluster. You can also use a fully managed solution for PostgreSQL. Compatible and tested Redis versions are later than 5 and earlier than 7.

​
Redis Variables

KeyTypeDefaultDescription
redis.enabledBooltrueSet to false if using external redis and modify the below variables.
redis.hoststringInternal Redis Deployment NameRedis Host Name
redis.auth.passwordstring"redis"Redis Password
redis.master.persistence.enabledbooltruePersistence can be disabled completely, if you want your data to only exist while the server is running.
redis.nameOverridestring"live-agent-redis"Override the deployment name, if internal Redis is enabled.
redis.sentinelMasterNamestring""A Redis sentinel master name is required when using sentinel.
redis.sentinelsstring""Redis Sentinel can be used by passing a list of sentinel hosts and ports. For example: sentinel_host1:port1, sentinel_host2:port2

​
Internal Setup

It is a good practice to change the redis.auth.password in the values.yaml file. To do this, you can change the value, or comment, on the line password: redis before installing the Helm chart, which will autogenerate a password.

​
External Setup

  1. Go to the values.yaml file and scroll down to the redis field. Change the enabled value to false.
  2. Type the user credentials, and uncomment the properties host and port, assigning them the correct values.
  3. Define a password to access the external Redis instance:
    • A. A secret is created by default. Edit the password inside the Redis secret. The secret name is composed of the release name + redis.
    • B. (Recommended) Define an existing secret. Create the secret and set the values inside the values.yaml file. The keys are redis.existingSecret and redis.existingSecretPasswordKey.
⌘I