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
What did you expect to see?
A working cluster. This is from the examples...
What did you see instead?
kubectl get po command
$ kubectl get po
NAME READY STATUS RESTARTS AGE
redis-cluster-leader-0 0/1 CrashLoopBackOff 5 (105s ago) 4m52s
kubectl logs redis-cluster-leader-0 command
$ kubectl logs redis-cluster-leader-0
mkdir: can't create directory '/node-conf': Permission denied
Redis is running without password which is not recommended
sed: /node-conf/nodes.conf: No such file or directory
Running without TLS mode
ACL_MODE is not true, skipping ACL file modification
Starting redis service in cluster mode.....
7:C 14 Dec 2024 12:27:01.553 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7:C 14 Dec 2024 12:27:01.553 # Redis version=7.0.12, bits=64, commit=00000000, modified=0, pid=7, just started
7:C 14 Dec 2024 12:27:01.553 # Configuration loaded
7:M 14 Dec 2024 12:27:01.553 * monotonic clock: POSIX clock_gettime
7:M 14 Dec 2024 12:27:01.553 # Can't open /node-conf/nodes.conf in order to acquire a lock: No such file or directory
The RedisCluster is created using the recommanded podSecurityContext yet before even starting we can see that
What version of redis operator are you using?
redis-operator version: quay.io/opstree/redis-operator:v0.15.1
Does this issue reproduce with the latest release?
As far as I know ;)
What operating system and processor architecture are you using (
kubectl version
)?kubectl version
OutputWhat did you do?
kubectl create RedisCluster
commandWhat did you expect to see?
A working cluster. This is from the examples...
What did you see instead?
kubectl get po
commandkubectl logs redis-cluster-leader-0
commandThe RedisCluster is created using the recommanded podSecurityContext yet before even starting we can see that
So the cluster will go nowhere. what am I doing wrong ?
Using an other storageClass doesnt help
The text was updated successfully, but these errors were encountered: