kas does not work when using separate redis instances
KAS configuration fails due to it not being able to correctly identify the redis to use when the system is configured to use separate instances.
In our HA setup, we are using separate redis databases for different purposes. Unless we set the "default" redis instance as well, KAS configures itself to use the local unix socket (which is very obviously wrong).
This appears to be caused by RedisHelper only knowing how to read from the common "shared" redis config, eg: gitlab_rails['redis_host']
, which is normally absent in configurations with multiple redis servers. This limitation is not documented anywhere.
Workaround is to set the common rails redis config to a single instance for the kas recipe to reference.
Related to gitlab-environment-toolkit#626 (closed)