Change Details

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` **QA / Acceptance criteria** - Able to access redis cluster and query username, breaking-news from dev and prod env

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** [x] Deploy redis-commander service, following similar IaC and mechanism as that of `kafka-ui` [x] 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

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** [x] Deploy redis-commander service, following similar IaC and mechanism as that of `kafka-ui` [x] 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