K8s: architecture rewrite (#758)

Author: kaitlynmichael

content/operate/kubernetes/architecture/_index.md

@@ -9,17 +9,17 @@ description: Redis Enterprise for Kubernetes allows you to deploy to multiple na
   This article describes flexible deployment options you can use to meet your specific
   needs.
 linkTitle: Deployment options
+aliases: [ /operate/kubernetes/architecture/deployment-options/, ]
 weight: 12
 ---
 You can deploy Redis Enterprise for Kubernetes in several different ways depending on your database needs.
 
-Multiple Redis Enterprise database resources (REDB) can be associated with single Redis Enterprise cluster resource (REC) even if they reside in different namespaces.
+Multiple RedisEnterpriseDatabase (REDB) resources can be associated with a single Redis Enterprise cluster resource (REC) even if they reside in different namespaces.
 
 The Redis Enterprise cluster (REC) custom resource must reside in the same namespace as the Redis Enterprise operator.
 
 {{<warning>}} Multi-namespace installations don't support Active-Active databases (REEADB). Only databases created with the REDB resource are supported in multi-namespace deployments at this time.{{</warning>}}
 
-
 ## Single REC and single namespace (one-to-one)
 
 The standard and simplest deployment deploys your Redis Enterprise databases (REDB) in the same namespace as the Redis Enterprise cluster (REC). No additional configuration is required for this, since there is no communication required to cross namespaces. See [Deploy Redis Enterprise for Kubernetes]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}).

content/operate/kubernetes/deployment/deployment-options.md renamed to content/operate/kubernetes/architecture/deployment-options.md

@@ -15,23 +15,6 @@ weight: 11
 
 This section lists the different ways to set up and run Redis Enterprise for Kubernetes. You can deploy on variety of Kubernetes distributions both on-prem and in the cloud via our Redis Enterprise operator for Kubernetes.
 
-## Operator overview {#overview}
-
-Redis Enterprise for Kubernetes uses [custom resource definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions) (CRDs) to create and manage Redis Enterprise clusters (REC) and Redis Enterprise databases (REDB).
-
-The operator is a deployment that runs within a given namespace. These operator pods must run with sufficient privileges to create the Redis Enterprise cluster resources within that namespace.
-
-When the operator is installed, the following resources are created:
-
-* a service account under which the operator will run
-* a set of roles to define the privileges necessary for the operator to perform its tasks
-* a set of role bindings to authorize the service account for the correct roles (see above)
-* the CRD for a Redis Enterprise cluster (REC)
-* the CRD for a Redis Enterprise database (REDB)
-* the operator itself (a deployment)
-
-The operator currently runs within a single namespace and is scoped to operate only on the Redis Enterprise cluster in that namespace.
-
 ## Compatibility
 
 Before installing, check [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) to see which Redis Enterprise operator version supports your Kubernetes distribution.

content/operate/kubernetes/architecture/operator.md

@@ -7,14 +7,15 @@ categories:
 - kubernetes
 description: null
 hideListLinks: true
+hidden: true
 linkTitle: FAQs
 weight: 100
 ---
 Here are some frequently asked questions about Redis Enterprise on integration platforms.
 
 ## What is an Operator?
 
-An operator is a [Kubernetes custom controller](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources#custom-controllers) which extends the native K8s API. Refer to the article [Redis Enterprise K8s Operator-based deployments – Overview]({{< relref "/operate/kubernetes/architecture/operator.md" >}}).
+An operator is a [Kubernetes custom controller](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources#custom-controllers) which extends the native K8s API. Refer to the article [Redis Enterprise K8s Operator-based deployments – Overview]({{< relref "/operate/kubernetes/architecture/" >}}).
 
 ## Does Redis Enterprise operator support multiple RECs per namespace?
 

content/operate/kubernetes/deployment/_index.md

@@ -14,7 +14,7 @@ weight: 17
 
 Multiple Redis Enterprise database resources (REDBs) can be associated with a single Redis Enterprise cluster resource (REC) even if they reside in different namespaces.
 
-To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/deployment/deployment-options.md" >}}).
+To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/architecture/deployment-options.md" >}}).
 
 {{<warning>}} Multi-namespace installations don't support Active-Active databases (REEADB). Only databases created with the REDB resource are supported in multi-namespace deployments at this time.{{</warning>}}
 

content/operate/kubernetes/faqs/_index.md

@@ -32,7 +32,7 @@ If the database [custom resource is deleted]({{< relref "/operate/kubernetes/re-
 
 Databases in multiple namespaces can be managed by the same operator. To learn more, see [Manage databases in multiple namespaces]({{<relref "/operate/kubernetes/re-clusters/multi-namespace">}}).
 
-To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/deployment/deployment-options.md" >}}).
+To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/architecture/deployment-options.md" >}}).
 
 ## Create a database