Should we file an issue? And what would you suggest the workaround be? Should we spin up a non-managed redis instance until this is resolved?
11 months ago
Quickest solution would be spinning up a non-managed redis instance. We'll be able to push a fix for this in the next release.Or reverting to Fleet 3.13.0Or you can build binaries/Docker containers yourself after I merge the fix.