Helm Support #226
Description
I wrote a helm chart to help manage Send in Kubernetes. I have 2 pods, 1 with the send container and 1 with a redis container. Now I see there's been some more activity and issues in this repo where others are using it, I was thinking maybe it could make sense to make a PR with my helm chart in a way that the community could use it. I also wanted to make sure Tim as the maintainer was ok with adding helm support to the repo.
There are some concerns I have with the current Redis setup: Whenever I delete my underlying nodes and restart redis, the send pod has trouble reading the redis connection and writes out errors and doesn't try to do anything to rebuild the connection. The UI shows links as expired. I was thinking about moving the Redis to Elasticache to see if more stability on the Redis connection could help make the uptime better with less errors. If there was a helm chart in this repo, would it be preferred that there's a redis statefulset or read a passed in a reference to where it can be found, like elasticache?
There's probably a deeper change to be made to check the redis connection on a health check or do something to reinitialize the connection if the code detects its unhealthy, but that might be a separate change.