Closed keyolk closed 2 years ago
I'm not a Redis expert, but the error message "ERR This instance has cluster support disabled" suggests that the Redis cluster itself is configured in a way Envoy doesn't expect.
You may want to start from a minimal setup described in https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/redis.html
/cc @msukalski @henryyyang if they have a better idea.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
Expecting a cm init: all clusters initialized
after starting main dispatch loop
. It aligns with what @rojkov found
So the cluster warm up is the blocker of listener
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
I'm trying to use envoy's redis_proxy with the below config. Testing with docker, it opens admin port only. Am I missing something ?
envoy.yaml I used.
Run docker container.
check socket with the command ss.
Logs from docker container
Thanks