Samuel Vijaykumar M

I would suggest you follow these steps - Build you own redis image, with RedisJSON(`.so`) compiled to a know location - Use your custom Image by passing to the CRD...

@ese in fact in the next release of the redis... ``` # Command renaming (DEPRECATED). # # ------------------------------------------------------------------------ # WARNING: avoid using this option if possible. Instead use ACLs to...

@ese I am starting to work on this feature, here is excerpt.... 1. `redisops-admin` will the admin user with `-@all +@admin` with privileges 2. Defaults to nopass but if the...

@ese do let me know how you feel about this?

@dmamolina your thoughts too.

@szelenka if we are still supporting the 5.x of redis, then this change #430 will definitely not work. But we are taking a call that we will only support north...

So the approach i am going to take is that... ``` auth: redisOpsAdmin: kungfoo secretPath: foopass ``` - if we do not set the `redisOpsAdmin` it will default to `default`...

But a more elaborate plan for ACL would be to have something likes this... ``` auth - name: user1 password: valueFrom: ... acl: valueFrom: ... - name: user2 ... ```...

@szelenka please check if the change i taking is in the right direction

``` auth: admin: name: admin1 passwords: - valueFrom(or value) - acl: users: - name: foo passwords: - valueFrom(or value) - acl: "+@all -@dangerous" ... ... ```