Hi,
We want to deploy tyk components for our client side .
We are using 1.21 version of EKS,AWS RDS postgres instead of Mongo, Elasticache for Redis(AWS Service).
We get the pods loaded into Eks, and manually executing using command line ./tyk (with tyk.conf is located inside the same folder). We are not using any config maps and environment variables.
We are not able to connect to Elasticache for Redis, providing all the host name, connection string correctly.
ERROR cannot set key in pollerCacheKey error=storage: Redis is either down or was not configured
[Nov 22 14:34:29] DEBUG HOST CHECKER: Host list reset
[Nov 22 14:34:29] ERROR pub-sub: Connection to Redis failed, reconnect in 10s error=storage: Redis is either down or was not configured
[Nov 22 14:34:39] ERROR main: Redis health check failed error=storage: Redis is either down or was not configured liveness-check=true
ERROR cannot set key in pollerCacheKey error=storage: Redis is either down or was not configured
[Nov 22 14:34:39] ERROR pub-sub: Connection to Redis failed, reconnect in 10s error=storage: Redis is either down or was not configured
[Nov 22 14:34:49] ERROR main: Redis health check failed error=storage: Redis is either down or was not configured liveness-check=true
[Nov 22 14:34:49] ERROR cannot set key in pollerCacheKey error=storage: Redis is either down or was not configured
[Nov 22 14:34:49] ERROR pub-sub: Connection to Redis failed, reconnect in 10s error=storage: Redis is either down or was not configured
Welcome to the community.
Could you share the logs in debug mode? There should be a log_level field in the tyk config. If it’s not there, then kindly add it.
“log_level”: “debug”
You mentioned you are not using any config maps and environment variables. By default Tyk would try to connect to Redis on localhost:6379. Enabling the debug log would show what Tyk is trying to connect to.
Also is the issue occurring on the gateway, the dashboard or both?
.