I’m unable to connect to Redis from my Tyk deployment. I’m deploying Tyk in a GKE cluster in GCP. On the same network in GCP Memorystore, I have created a Redis instance with 2 read replicas.
I see the following repeated logs showing the Redis connection is not working (I enabled debug logs to see if it would have anything extra useful):
time="May 06 02:30:11" level=error msg="Redis health check failed" error="storage: Redis is either down or was not configured" liveness-check=true prefix=main
time="May 06 02:30:11" level=debug msg="No Primary instance found, assuming control" prefix=host-check-mgr
time="May 06 02:30:11" level=warning msg="Reconnecting storage: Redis is either down or was not configured" prefix=pub-sub
I set redis.enableCluster = false. And redis.addrs = [xxx.xx.xxx.x:6378]. I have in transit encryption enabled for the Redis instance and then redis.useSSL set to true.
I’m migrating my Tyk deployment from AWS to GCP. Previously, I had enableCluster=true and I had the redis.addrs = [clustercfg.xxx.xxx.usw2.cache.amazonaws.com:6379] and it worked great.
I can curl the read endpoint of my Redis instance from my pod, so I don’t feel it is a networking issue. I read some GCP docs and Tyk community forums but didn’t have any luck switching configurations or much else, hoping someone here might have an idea what could be wrong. Thanks!