Configure Spinnaker's Usage of Redis

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker relies on its cache for a few key purposes:

Session data for logins
Bake logs and history
Recording which triggers have already been acted upon when using docker/jenkins triggers
ETC.

Most of these can be configured to your needs, whether it is to make Spinnaker more responsive, or reduce the load on a downstream dependency. Some of these settings apply only to SQL or REDIS depending upon configuration. The below are some examples of adjusting these configurations.

Externalize Redis

Mon, 01 Jan 0001 00:00:00 +0000

One of the easiest ways to improve Spinnaker’s reliability at scale is to use an external Redis. The default redis component isn’t configured to be production-ready. If you have a hosted Redis alternative, or a database team managing a Redis installation, we highly recommend using that.

Configure a Spinnaker-wide Redis

First, determine the URL of your Redis installation. Some examples include:

redis://some.redis.url:6379: Redis running at some.redis.url on port 6379.
redis://admin:passw0rd@some.redis.url:6379: Same as above, but with a username/password pair.

Configure Caching on Spinnaker

Configure Spinnaker's Usage of Redis

Externalize Redis

Configure a Spinnaker-wide Redis