remove AA preview note

Author: kaitlynmichael

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

@@ -52,27 +52,6 @@ For versions 6.4.2 or earlier, this Active-Active setup method includes the foll
 
 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" >}}) then [create an Active-Active database]({{< relref "/operate/kubernetes/active-active/create-reaadb" >}}).
 
-### 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.

content/operate/kubernetes/active-active/edit-rerc.md

@@ -73,10 +73,13 @@ If the credentials are changed or updated for a REC participating cluster, you n
 
     ```sh
     kubectl get reaadb reaadb-boeing
-
-    NAME              STATUS   SPEC STATUS   LINKED REDBS   REPLICATION STATUS
-    reaadb-boeing     active   Valid                        up
     ```
+    The output should look similar to:
+
+      ```sh
+      NAME              STATUS   SPEC STATUS   LINKED REDBS   REPLICATION STATUS
+      reaadb-boeing     active   Valid                        up
+      ```
 
     To troubleshoot invalid configurations, view the RERC custom resource events and the [Redis Enterprise operator logs]({{< relref "/operate/kubernetes/logs/" >}}).
 

content/operate/kubernetes/active-active/prepare-clusters.md

@@ -29,26 +29,6 @@ Next you'll [collect credentials](#collect-rec-credentials) for your participati
 
 For a list of example values used throughout this article, see the [Example values](#example-values) section.
 
-### 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\"}}"
-
 ## Collect REC credentials
 
 To communicate with other clusters, all participating clusters will need access to the admin credentials for all other clusters.