[Test] : e2e Fix Flakes in Redis Cluster Test

.gitignore

@@ -25,4 +25,5 @@ testbin/*
 *~
 .vscode
 
-docs/build
+docs/build
+kubeconfig

tests/_config/kuttl-test.yaml

@@ -4,5 +4,7 @@ startKIND: false
 kindConfig: "./kind-config.yaml"
 parallel: 1
 timeout: 300
+testDirs:
+- tests/e2e/v1beta2/setup
 suppress : 
   - events

tests/e2e/v1beta2/setup/00-install.yaml → tests/e2e/v1beta2/setup/redis-cluster/00-install.yaml

@@ -4,4 +4,5 @@ apply :
   - cluster.yaml
 assert :
   - ready-cluster.yaml
-  - ready-cluster-sts.yaml
+  - ready-cluster-sts.yaml
+  - ready-pvc.yaml

tests/e2e/v1beta2/setup/ready-cluster.yaml → tests/e2e/v1beta2/setup/redis-cluster/ready-cluster.yaml

@@ -3,5 +3,5 @@ kind: RedisCluster
 metadata:
   name: redis-cluster-v1beta2
 status:
-  # readyFollowerReplicas: 3
+  readyFollowerReplicas: 3
   readyLeaderReplicas: 3

tests/e2e/v1beta2/setup/redis-cluster/ready-pvc.yaml

@@ -0,0 +1,181 @@
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: node-conf-redis-cluster-v1beta2-leader-0
+  labels:
+    app: redis-cluster-v1beta2-leader
+    redis_setup_type: cluster
+    role: leader
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: node-conf-redis-cluster-v1beta2-leader-1
+  labels:
+    app: redis-cluster-v1beta2-leader
+    redis_setup_type: cluster
+    role: leader
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: node-conf-redis-cluster-v1beta2-leader-2
+  labels:
+    app: redis-cluster-v1beta2-leader
+    redis_setup_type: cluster
+    role: leader
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: node-conf-redis-cluster-v1beta2-follower-0
+  labels:
+    app: redis-cluster-v1beta2-follower
+    redis_setup_type: cluster
+    role: follower
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: node-conf-redis-cluster-v1beta2-follower-1
+  labels:
+    app: redis-cluster-v1beta2-follower
+    redis_setup_type: cluster
+    role: follower
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: node-conf-redis-cluster-v1beta2-follower-2
+  labels:
+    app: redis-cluster-v1beta2-follower
+    redis_setup_type: cluster
+    role: follower
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+
+---
+
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: redis-cluster-v1beta2-leader-redis-cluster-v1beta2-leader-0
+  labels:
+    app: redis-cluster-v1beta2-leader
+    redis_setup_type: cluster
+    role: leader
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: redis-cluster-v1beta2-leader-redis-cluster-v1beta2-leader-1
+  labels:
+    app: redis-cluster-v1beta2-leader
+    redis_setup_type: cluster
+    role: leader
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: redis-cluster-v1beta2-leader-redis-cluster-v1beta2-leader-2
+  labels:
+    app: redis-cluster-v1beta2-leader
+    redis_setup_type: cluster
+    role: leader
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: redis-cluster-v1beta2-follower-redis-cluster-v1beta2-follower-0
+  labels:
+    app: redis-cluster-v1beta2-follower
+    redis_setup_type: cluster
+    role: follower
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: redis-cluster-v1beta2-follower-redis-cluster-v1beta2-follower-1
+  labels:
+    app: redis-cluster-v1beta2-follower
+    redis_setup_type: cluster
+    role: follower
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: redis-cluster-v1beta2-follower-redis-cluster-v1beta2-follower-2
+  labels:
+    app: redis-cluster-v1beta2-follower
+    redis_setup_type: cluster
+    role: follower
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound

tests/readme.md

@@ -20,7 +20,7 @@ Ensure you have the following tools installed:
 Create a 3-node kind cluster using the provided configuration:
 
 ```bash
-kind create cluster --config /redis-operator/tests/_config/kind-config.yaml
+kind create cluster --config tests/_config/kind-config.yaml
 ```
 
 ### 2. Install the Redis Operator
@@ -35,6 +35,14 @@ Please refer to the repository's README for detailed instructions on installing
 
 Execute the kuttl test using the following command:
 
+To run all default tests ( _config/kuttl-test.yaml is the default config file )
+
+```bash
+kubectl kuttl test --config tests/_config/kuttl-test.yaml
+```
+
+To run a test at specified path
+
 ```bash
-kubectl kuttl test redis-operator/tests/e2e/v1beta2 --config /redis-operator/tests/_config/kuttl-test.yaml --timeout 600
+kubectl kuttl test tests/e2e/v1beta2 --config tests/_config/kuttl-test.yaml --timeout 600
 ```