Huh? Tyk doesn’t start Redis for you, you need to set that up yourself, since it has so many ways of being run (dev / prod / master+slave+hot-failover / cluster), Tykwon’t make that architecture decision for you.
That’s the bit when you create the actual cluster. You haven’t installed a cluster in that case, instead, you have a half-installed redis master/slave relationship (maybe). So the cluster flag in tyk.conf will not work since Tyk will try to speak to the redis DB as f it were a cluster, not as if it were a single instance.
If you can’t set up a Redis cluster using the guide, maybe just use a single instance? Or, if you must use a cluster, but don’t want to go through setting one up, maybe use a pre-built docker-based redis cluster, it’s much easier to get started and debug with?