Unable to configure Redis Sentinel or Redis Cluster with official Helm, standalone Redis works fine about helm HOT 3 OPEN

On 9/06/24 22:14, JesseBot wrote: Sorry for the delay! I edited your description to make it a little easier to read by adding collapsibles and syntax highlighting. If you're trying to use redis cluster vs stand alone, the seeds param you specified should be correct according to [docs.nextcloud.com/server/29](https://docs.nextcloud.com/server/29/developer_manual/how_to/index.html#redis-cluster): <?php $ CONFIG = array ( 'memcache.distributed' => '\OC\Memcache\Redis' , 'memcache.locking' => '\OC\Memcache\Redis' , 'redis.cluster' => array ( 'seeds' => array ( 'redis-cluster-headless:6379' ), 'password' => getenv( 'REDIS_HOST_PASSWORD' ), ), ); I don't use redis cluster, but if I'm understanding correctly, the seed should be the name of the redis service right? - which should be whatever this is: https://github.com/bitnami/charts/blob/1a5338daf534b712823a407b409f7b71b9ddb294/bitnami/redis-cluster/templates/redis-svc.yaml#L9 - which should be whatever your helm release name is for the redis cluster helm chart release, or the fullnameOverride parameter value for that chart. Some minor follow up questions: - Are you doing a fresh install of nextcloud in between testing different redis installations? I ask because I noticed you have persistence enabled in your values.yaml. If not, can you try a fresh install without persistence while also using a fresh install of redis-cluster? - Can you verify the name of the redis service when using bitnami's redis-cluster chart? If others in the community have better information or suggestions here, please feel free to chime in, as I haven't been using redis lately. — Reply to this email directly, [view it on GitHub](#543 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ADUNCRQ2LX47VD6IECOLGD3ZGQTG3AVCNFSM6AAAAABEOZFGGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWGQZDONRVGE). You are receiving this because you authored the thread.Message ID: ***@***.***>