K8s: Wisconsin release (#1321)

---------

Co-authored-by: redisdocsapp[bot] <177626021+redisdocsapp[bot]@users.noreply.github.com>
Co-authored-by: Cameron Bates <cameron.bates@redis.com>
Co-authored-by: Cameron Bates <102550101+cmilesb@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: oshri barazani <oshribr@gmail.com>
Co-authored-by: Zvi Cahana <zcahana@users.noreply.github.com>
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com>
Co-authored-by: mich-elle-luna <153109578+mich-elle-luna@users.noreply.github.com>

Author: 9 people

content/embeds/k8s/log_collector_role_all_mode.md

@@ -170,13 +170,6 @@ rules:
   verbs:
   - get
   - list
-- apiGroups:
-  - policy
-  resources:
-  - podsecuritypolicy
-  verbs:
-  - get
-  - list
 - apiGroups:
   - certificates.k8s.io
   resources:

content/embeds/k8s/openshift_rec.md

@@ -6,11 +6,27 @@ metadata:
   labels:
     app: redis-enterprise
 spec:
-  # Add fields here
+  # The number of Redis Enterprise nodes in the clusters.
   nodes: 3
+
+  persistentSpec:
+    # Whether to enable persistent storage for the Redis Enterprise nodes.
+    enabled: true
+
+    # The size of the persistent volume for each Redis Enterprise node.
+    volumeSize: 20Gi
+
+  # The resources allocated to each Redis Enterprise node.
+  redisEnterpriseNodeResources:
+    requests:
+      cpu: 2
+      memory: 4Gi
+    limits:
+      cpu: 2
+      memory: 4Gi
   redisEnterpriseImageSpec:
     repository: registry.connect.redhat.com/redislabs/redis-enterprise
-    versionTag: 7.8.4-66.rhel8-openshift
+    versionTag: 7.8.6-13
   redisEnterpriseServicesRiggerImageSpec:
     repository: registry.connect.redhat.com/redislabs/services-manager
   bootstrapperImageSpec:

content/embeds/k8s/openshift_role.md

@@ -22,18 +22,7 @@ rules:
   - apiGroups:
       - app.redislabs.com
     resources:
-      - redisenterpriseclusters
-      - redisenterpriseclusters/status
-      - redisenterpriseclusters/finalizers
-      - redisenterprisedatabases
-      - redisenterprisedatabases/status
-      - redisenterprisedatabases/finalizers
-      - redisenterpriseremoteclusters
-      - redisenterpriseremoteclusters/status
-      - redisenterpriseremoteclusters/finalizers
-      - redisenterpriseactiveactivedatabases
-      - redisenterpriseactiveactivedatabases/status
-      - redisenterpriseactiveactivedatabases/finalizers
+      - "*"
     verbs:
       - delete
       - get
@@ -93,6 +82,7 @@ rules:
       - get
       - list
       - watch
+      - update
   - apiGroups:
       - ""
     resources:
@@ -138,14 +128,6 @@ rules:
       - create
       - delete
       - watch
-  - apiGroups:
-      - policy
-    resourceNames:
-      - redis-enterprise-psp
-    resources:
-      - podsecuritypolicies
-    verbs:
-      - use
   - apiGroups:
       - networking.k8s.io
     resources:

content/embeds/k8s/reaadb.md

@@ -2,13 +2,14 @@
 apiVersion: app.redislabs.com/v1alpha1
 kind: RedisEnterpriseActiveActiveDatabase
 metadata:
-  name: reaadb-1
+  name: reaadb
   labels:
     app: redis-enterprise
 spec:
   participatingClusters:
     # Participating cluster pointing to RERC named: 'new-york-1'.
     - name: new-york-1
+
     # Participating cluster pointing to RERC named: 'boston-1'.
     - name: boston-1
 ```

content/embeds/k8s/rec.md

@@ -6,6 +6,22 @@ metadata:
   labels:
     app: redis-enterprise
 spec:
-  # Add fields here
+  # The number of Redis Enterprise nodes in the clusters.
   nodes: 3
+
+  persistentSpec:
+    # Whether to enable persistent storage for the Redis Enterprise nodes.
+    enabled: true
+
+    # The size of the persistent volume for each Redis Enterprise node.
+    volumeSize: 20Gi
+
+  # The resources allocated to each Redis Enterprise node.
+  redisEnterpriseNodeResources:
+    requests:
+      cpu: 2
+      memory: 4Gi
+    limits:
+      cpu: 2
+      memory: 4Gi
 ```

content/embeds/k8s/redb.md

@@ -2,7 +2,16 @@
 apiVersion: app.redislabs.com/v1alpha1
 kind: RedisEnterpriseDatabase
 metadata:
-  name: redis-enterprise-database
+  name: redb
   labels:
     app: redis-enterprise
+spec:
+  # Memory size of the database.
+  memorySize: 256MB
+
+  # Number of shards in the database.
+  shardCount: 1
+
+  # Determines whether replication will be enabled for the database.
+  replication: false
 ```

content/embeds/k8s/rerc.md

@@ -2,21 +2,24 @@
 apiVersion: app.redislabs.com/v1alpha1
 kind: RedisEnterpriseRemoteCluster
 metadata:
-  # Your name of the RERC.
   name: new-york-1
   labels:
     app: redis-enterprise
 spec:
-  # The name of the REC that the RERC is pointing at
+  # The name of the REC that the RERC is pointing at.
   recName: rec
-  # The Namespace of the REC that the RERC is pointing at
+
+  # The namespace of the REC that the RERC is pointing at.
   recNamespace: ns1
-  # The URL of the cluster, will be used for the active-active database URL
+
+  # The URL of the cluster, will be used for the active-active database URL.
   apiFqdnUrl: testapi-new-york-1-ns1.redislabs.com
+
   # The database URL suffix, will be used for the active-active
-  # database replication endpoint and replication endpoint SNI
+  # database replication endpoint and replication endpoint SNI.
   dbFqdnSuffix: -example-new-york-1-ns1.redislabs.com
+
   # The name of the secret containing cluster credentials.
-  #  Need to follow format: "redis-enterprise-<RERC name>"'
+  # Needs to be formatted as: "redis-enterprise-<RERC name>"
   secretName: redis-enterprise-new-york-1
 ```

content/embeds/k8s/role.md

@@ -22,18 +22,7 @@ rules:
   - apiGroups:
       - app.redislabs.com
     resources:
-      - redisenterpriseclusters
-      - redisenterpriseclusters/status
-      - redisenterpriseclusters/finalizers
-      - redisenterprisedatabases
-      - redisenterprisedatabases/status
-      - redisenterprisedatabases/finalizers
-      - redisenterpriseremoteclusters
-      - redisenterpriseremoteclusters/status
-      - redisenterpriseremoteclusters/finalizers
-      - redisenterpriseactiveactivedatabases
-      - redisenterpriseactiveactivedatabases/status
-      - redisenterpriseactiveactivedatabases/finalizers
+      - "*"
     verbs:
       - delete
       - get
@@ -93,6 +82,7 @@ rules:
       - get
       - list
       - watch
+      - update
   - apiGroups:
       - ""
     resources:
@@ -138,14 +128,6 @@ rules:
       - create
       - delete
       - watch
-  - apiGroups:
-      - policy
-    resourceNames:
-      - redis-enterprise-psp
-    resources:
-      - podsecuritypolicies
-    verbs:
-      - use
   - apiGroups:
       - networking.k8s.io
     resources:

content/operate/kubernetes/7.8.4/_index.md

@@ -0,0 +1,17 @@
+---
+Title: Redis Enterprise for Kubernetes
+alwaysopen: false
+categories:
+- docs
+- operate
+- kubernetes
+description: The Redis Enterprise operators allows you to use Redis Enterprise for
+  Kubernetes.
+hideListLinks: false
+linkTitle: 7.8.4
+weight: 50
+url: '/operate/kubernetes/7.8.4/'
+---
+
+Kubernetes provides enterprise orchestration of containers and has been widely adopted. Redis Enterprise for Kubernetes provides a simple way to get a Redis Enterprise cluster on Kubernetes and enables more complex deployment scenarios.
+

content/operate/kubernetes/7.8.4/active-active/_index.md

@@ -0,0 +1,99 @@
+---
+Title: Active-Active databases
+alwaysopen: false
+categories:
+- docs
+- operate
+- kubernetes
+description: Content related to Active-Active Redis Enterprise databases for Kubernetes.
+hideListLinks: true
+linkTitle: Active-Active databases
+weight: 40
+url: '/operate/kubernetes/7.8.4/active-active/'
+---
+
+On Kubernetes, Redis Enterprise [Active-Active]({{< relref "/operate/rs/databases/active-active/" >}}) databases provide read and write access to the same dataset from different Kubernetes clusters.
+
+## Active-Active setup methods
+
+There are two methods for creating an Active-Active database with Redis Enterprise for Kubernetes:
+
+- The `RedisEnterpriseActiveActiveDatabase` (REAADB) custom resource is available for versions 6.4.2 and later.
+- The `crdb-cli` method is available for versions 6.4.2 or earlier.
+
+
+We recommend creating new Active-Active databases using the RedisEnterpriseActiveActiveDatabase (REAADB) custom resource. This allows you to manage your Active-Active database with the operator and ensures you have the latest features and functionality.
+
+### Active-Active controller method
+
+Versions 6.4.2-6 or later fully support the Active-Active controller. Some of these features were available as a preview in 6.4.2-4 and 6.4.2-5. Please upgrade to 6.4.2-6 for the full set of general availability features and bug fixes.
+
+This setup method includes the following steps:
+
+1. Gather REC credentials and [prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters.md" >}}).
+2. Create [`RedisEnterpriseRemoteCluster` (RERC)]({{< relref "/operate/kubernetes/active-active/create-reaadb#create-rerc" >}}) resources.
+3. Create [`RedisEnterpriseActiveActiveDatabase` (REAADB)]({{< relref "/operate/kubernetes/active-active/create-reaadb#create-reaadb" >}}) resource.
+
+### `crdb-cli` method
+
+For versions 6.4.2 or earlier, this Active-Active setup method includes the following steps:
+
+1. Install and configure an ingress.
+2. Gather configuration details.
+3. Add the `ActiveActive` field to the REC spec.
+4. Create the database with the `crdb-cli` tool.
+
+## Redis Enterprise Active-Active controller for Kubernetes
+
+{{<note>}}These features are supported for general availability in releases 6.4.2-6 and later.{{</note>}}
+
+[Active-Active]({{< relref "/operate/rs/databases/active-active/" >}}) databases give you read-and-write access to Redis Enterprise clusters (REC) in different Kubernetes clusters or namespaces. Active-Active deployments managed by the Redis Enterprise operator require two additional custom resources: Redis Enterprise Active-Active database (REAADB) and Redis Enterprise remote cluster (RERC).
+
+To create an Active-Active Redis Enterprise deployment for Kubernetes with these new features, first [prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters.md" >}}) then [create an Active-Active database]({{< relref "/operate/kubernetes/active-active/create-reaadb.md" >}}).
+
+### Preview versions
+
+If you are using a preview version of these features (operator version 6.4.2-4 or 6.4.2-5), you'll need to enable the Active-Active controller with the following steps. You need to do this only once per cluster. We recommend using the fully supported 6.4.2-6 version.
+
+1. Download the custom resource definitions (CRDs) for the most recent release (6.4.2-4) from [redis-enterprise-k8s-docs Github](https://github.com/RedisLabs/redis-enterprise-k8s-docs/tree/master/crds).
+
+1. Apply the new CRDs for the Redis Enterprise Active-Active database (REAADB) and Redis Enterprise remote cluster (RERC) to install those controllers.
+
+    ```sh
+    kubectl apply -f crds/reaadb_crd.yaml
+    kubectl apply -f crds/rerc_crd.yaml
+    ```
+
+1. Enable the Active-Active and remote cluster controllers on the operator ConfigMap.
+
+    ```sh
+    kubectl patch cm  operator-environment-config --type merge --patch "{\"data\": \
+    {\"ACTIVE_ACTIVE_DATABASE_CONTROLLER_ENABLED\":\"true\", \
+    \"REMOTE_CLUSTER_CONTROLLER_ENABLED\":\"true\"}}"
+
+
+### REAADB custom resource
+
+Redis Enterprise Active-Active database (REAADB) contains a link to the RERC for each participating cluster, and provides configuration and status to the management plane.
+
+For a full list of fields and options, see the [REAADB API reference]({{<relref "/operate/kubernetes/reference/redis_enterprise_active_active_database_api">}}).
+
+### RERC custom resource
+
+Redis Enterprise remote cluster (RERC) custom resource contains configuration details for all the participating clusters.
+
+For a full list of fields and options, see the [RERC API reference]({{<relref "/operate/kubernetes/reference/redis_enterprise_remote_cluster_api">}}).
+
+### Limitations
+
+* Existing Redis databases cannot be migrated to a REAADB. (DOC-3594)
+* Admission is not blocking REAADB with `shardCount` which exceeds license quota. (RED-96301)
+    Workaround: Fix the problems with the REAADB and reapply.
+* The `<rec-name>/<rec-namespace>` value must be unique for each RERC resource. (RED-96302)
+* Only global database options are supported, no support for specifying configuration per location.
+* No support for migration from old (`crdb-cli`) Active-Active database method to new Active-Active controller.
+* No support for REAADB with participating clusters co-located within the same Kubernetes cluster, except for a single designated local participating cluster.
+
+## More info
+
+For more general information about Active-Active, see the [Redis Enterprise Software docs]({{< relref "/operate/rs/databases/active-active/" >}}).