Re-evaluate forked Redis / Redis HA charts
Summary
We forked Redis in the past for reasons as documented in our architectural decisions document. Since then, Bitnami has taken over stable/redis, and integrated HA.
Previous reasoning
Populate the password directly into the
redis.conf
instead of via Environment
This is addressed by usePassword
and usePasswordFile
Make use of pre-existing Kubernetes secrets instead of creating new ones from properties.
This is now available via existingSecret
property.
Benefits of using upstream
- Remove
redis
andredis-ha
forks - No undocumented behavior when redis & redis-ha charts are both enabled somehow
- Reduced load on our team for maintenance
- Now a
StatefulSet
, being more resilient
Downsides
Edited by Jason Plum