Hello, we currently have GoodData.CN 3.21 on AWS pointing to an Elasticache redis cluster configured in the helm chart as follows:

service:
  redis:
    clusterMode: true
    hosts:
      - "AWS_REDIS_HOST_NAME"

Can we remove these redis settings and remove redis from our AWS account? Will GoodData.CN continue to function or is there still a dependency on redis? We'd like to get rid of redis to save costs. Thanks 🙏

Hi Pete, once again 🙂 I just wanted to let you know that our team are going to look into this issue for you and will get back to you as soon as possible with more details.

Hi Pete, I will ask internally about redis dependecies in CN application. However may I ask you if you already use FlexQuery for chaching https://support.gooddata.com/hc/en-us/articles/21948942400659-GoodData-CN-3-0-0?

Hi Jan, I believe we do (or we don't explicitly disable it). Is there a particular helm chart variable I should look at?

If you are using flexQuery you should see running

quiver-xtab

and

quiver-cache

pods in gooddata CN namespace. There was a helm chart option

deployQuiver: false

that would prevent deploying FlexQuery caching in older versions but I think it was removed

Yes, we have those pods running.

right, thanks for confirmation

@Jan Kos is there an update on whether we can decommission redis?

Hi Pete, redis is still required as it is still used across multiple microservices. However you can spin up cheaper deployment - instead of using aws-managed redis (elasticache), you can run redis in k8s cluster or on a small VM. Or you can rely on redis subchart which can be deployed by gooddata-cn helm chart.

Thanks, Jan. Would setting "deployRedisHA: true" be the only thing we need to set up a working redis instance in the cluster so we can deprovision our Elasticache cluster (currently this variable is set to false because we're using Elasticache)?

Hi Pete, yes

deployRedisHA: true

should be enough. Of course we recommend such changes test first in dev / testing environment.