​
Why Redis?

As the features and use case of Infisical have grown, the need for a fast and reliable in-memory data storage has become clear. By adding Redis to Infisical, we can now support more complex workflows such as queuing system to run long running asynchronous tasks, cron jobs, and access reliable cache to speed up frequently used resources.

Starting with Infisical version v0.31.0, Redis will be required to fully use Infisical

​
Adding Redis to your self hosted instance of Infisical

To add Redis to your self hosted instance, follow the instructions for the deployment method you used.

  • Kubernetes Helm chart

  • Docker compose

  • Standalone Docker image

In cluster Redis

By default, new versions of the Infisical Helm chart already comes with an in-cluster Redis instance. To deploy a in-cluster Redis instance along with your Infisical instance, update your Infisical chart then redeploy/upgrade your release. This will spin up a Redis instance and automatically configure it with your Infisical backend.

  1. Update Infisical Helm chart
helm repo update
  1. Upgrade Infisical release
helm upgrade <infisical release name> infisical-helm-charts/infisical  --values <path to your values file>

External Redis

If you want to use an external Redis instance, please add a Redis connection URL under the backend environments variables and then upgrade/redeploy your Infisical instance.

  1. Update your helm values file
your-values.yaml
backendEnvironmentVariables:
  REDIS_URL=<your redis connection string>
  1. Upgrade Infisical release
helm upgrade <infisical release name> infisical-helm-charts/infisical  --values <path to your values file>

​
Support

If you have questions or need support, please join our slack channel and one of our teammates will be happy to guide you.