Page MenuHomePhabricator

Deploy redis-commander tool for debugging
Closed, ResolvedPublic3 Estimated Story Points

Description

In order to debug customer-related issues as well as data points like breaking news, we need to deploy r`edis-commander` in order to have easy access to our redis cluster.

To do

  • Deploy redis-commander service, following similar IaC and mechanism as that of kafka-ui
  • Configure access to redis-commander tool via ssh port forwarding, similar to what we have for kafka-ui
  • Test in dev and release to prod

QA / Acceptance criteria

  • Able to access redis cluster and query username, breaking-news from dev and prod env

Details

Other Assignee
Alex.lep.sp

Event Timeline

It was tested in Dev, but there is a problem with connecting to it from the desktop. Alex thinks we need a firewall change to allow dynamic addresses. Alex will investigate later today

Alex updated the bastion script to use make and fix the port number.

The problem is that the RedisCommander config doesn't point to a valid Redis server. It could be an issue with the REDIS_HOST config string. Needs more investigation

We use TLS encryption to connect to Redis. How RedisCommander connects to Redis doesn't allow TLS in the REDIS_HOSTS environment variable. However, we can use a connections.json file inside the RedisCommander docker container.

I need to change it to us Redis commander's connections.json file. I need to investigate if the connections file is secure because we'd need to store passwords in the file.