You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We found many users wanting to use opstree's redis operator to run the RedisTimeseries, RedisJSON, RedisSearch, RedisBloom, etc.
I'd like to understand who would prefer the base image to be exchanged by the redis-stack-server image, which includes all these features - AND - that these modules could be loaded with the operator's config optionally. Also, it should allow to pass arguments to the loading of the modules. This in contrast of using the slim redis images without the additional modules.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We found many users wanting to use opstree's redis operator to run the RedisTimeseries, RedisJSON, RedisSearch, RedisBloom, etc.
I'd like to understand who would prefer the base image to be exchanged by the redis-stack-server image, which includes all these features - AND - that these modules could be loaded with the operator's config optionally. Also, it should allow to pass arguments to the loading of the modules. This in contrast of using the slim redis images without the additional modules.
FYI: The license is not an obstacle. See the RSAL
20 votes ·
Beta Was this translation helpful? Give feedback.
All reactions