k8s api docs 7.22.0-6

content/embeds/k8s/multi-ns_role.md

@@ -8,7 +8,12 @@ metadata:
 rules:
   - apiGroups:
       - app.redislabs.com
-    resources: ["redisenterprisedatabases", "redisenterprisedatabases/status", "redisenterprisedatabases/finalizers"]
+    resources: ["redisenterprisedatabases",
+                "redisenterprisedatabases/status",
+                "redisenterprisedatabases/finalizers",
+                "redisenterpriseactiveactivedatabases",
+                "redisenterpriseactiveactivedatabases/status",
+                "redisenterpriseactiveactivedatabases/finalizers"]
     verbs: ["delete", "get", "list", "patch", "create", "update", "watch"]
   - apiGroups: [""]
     resources: ["secrets"]
@@ -18,7 +23,7 @@ rules:
     verbs: ["get", "list", "watch"]
   - apiGroups: [""]
     resources: ["events"]
-    verbs: ["create"]
+    verbs: ["create", "patch"]
   - apiGroups: [""]
     resources: ["services"]
     verbs: ["get", "list", "update", "patch", "create", "delete", "watch"]

content/embeds/k8s/openshift_rec.md

@@ -26,7 +26,7 @@ spec:
       memory: 4Gi
   redisEnterpriseImageSpec:
     repository: registry.connect.redhat.com/redislabs/redis-enterprise
-    versionTag: 7.8.6-13
+    versionTag: 7.22.0-21
   redisEnterpriseServicesRiggerImageSpec:
     repository: registry.connect.redhat.com/redislabs/services-manager
   bootstrapperImageSpec:

content/embeds/k8s/openshift_role.md

@@ -72,6 +72,18 @@ rules:
       - update
       - list
       - watch
+  - apiGroups:
+      - batch
+    resources:
+      - cronjobs
+    verbs:
+      - create
+      - delete
+      - get
+      - patch
+      - update
+      - list
+      - watch
   - apiGroups:
       - policy
     resources:
@@ -169,7 +181,7 @@ rules:
   - apiGroups:
       - security.openshift.io
     resourceNames:
-      - nonroot
+      - nonroot-v2
     resources:
       - securitycontextconstraints
     verbs:

content/embeds/k8s/openshift_scc.md

@@ -4,15 +4,15 @@ kind: SecurityContextConstraints
 metadata:
   name: redis-enterprise-scc-v2
   annotations:
-    kubernetes.io/description: redis-enterprise-scc-v2 is the minimal SCC needed to run Redis Enterprise nodes on Kubernetes. It provides the same features as restricted-v2 SCC, but allows pods to enable the SYS_RESOURCE capability, which is required by Redis Enterprise nodes to manage file descriptor limits and OOM scores for database shards. Additionally, it requires pods to run as UID/GID 1001, which are the UID/GID used within the Redis Enterprise node containers.
+    kubernetes.io/description: redis-enterprise-scc-v2 is the minimal SCC needed to run Redis Enterprise nodes on Kubernetes with automatic FD limit adjustment enabled. It provides the same features as restricted-v2 SCC, but allows pods to enable the SYS_RESOURCE capability, which is required by Redis Enterprise nodes to manage file descriptor limits and OOM scores for database shards. Additionally, it requires pods to run as UID/GID 1001, which are the UID/GID used within the Redis Enterprise node containers.
 allowedCapabilities:
   - SYS_RESOURCE
 allowHostDirVolumePlugin: false
 allowHostIPC: false
 allowHostNetwork: false
 allowHostPID: false
 allowHostPorts: false
-allowPrivilegeEscalation: false
+allowPrivilegeEscalation: true
 allowPrivilegedContainer: false
 readOnlyRootFilesystem: false
 runAsUser:

content/embeds/k8s/role.md

@@ -72,6 +72,18 @@ rules:
       - update
       - list
       - watch
+  - apiGroups:
+      - batch
+    resources:
+      - cronjobs
+    verbs:
+      - create
+      - delete
+      - get
+      - patch
+      - update
+      - list
+      - watch
   - apiGroups:
       - policy
     resources:

content/operate/kubernetes/reference/redis_enterprise_active_active_database_api.md

@@ -135,6 +135,13 @@ RedisEnterpriseActiveActiveDatabaseSpec defines the desired state of RedisEnterp
           The desired replication endpoint's port number for users who utilize LoadBalancers for sync between AA replicas and need to provide the specific port number that the LoadBalancer listens to.<br/>
         </td>
         <td>false</td>
+      </tr><tr>
+        <td>namespace</td>
+        <td>string</td>
+        <td>
+          Namespace in which the REAADB object will be deployed to within the corresponding participating cluster. The user must ensure that the Redis Enterprise operator is configured to watch this namespace in the corresponding cluster, and the required RBAC configuration is properly set up. See https://redis.io/docs/latest/operate/kubernetes/re-clusters/multi-namespace/ for more information how to set up multiple namespaces. If no namespace is specified, then the REAADB is deployed to the REC's namespace in the corresponding cluster.<br/>
+        </td>
+        <td>false</td>
       </tr></tbody>
 </table>