DOC-4367 improvements to other pages and new links

Author: andy-stark-redis

content/integrate/redis-data-integration/architecture.md

@@ -136,14 +136,28 @@ traffic. The diagram below shows this configuration:
 
 {{< image filename="images/rdi/ingest/ingest-active-passive-vms.png" >}}
 
+See [Install on VMs]({{< relref "/integrate/redis-data-integration/installation/install-vm" >}})
+for more information.
+
 ### RDI on Kubernetes
 
-You can run RDI in a namespace on your own Kubernetes cluster with
-a separate deployment for each of the control plane
-components (REST API, operator, and metrics exporter). The operator
-creates and configures deployments for the collector and stream processor
-when you start a pipeline from the CLI tool. This means that you must
-provide the operator with a service account that has permissions to create and manipulate pods in the namespace. 
+You can use the RDI [Helm chart](https://helm.sh/docs/topics/charts/) to install
+on [Kubernetes (K8s)](https://kubernetes.io/). This creates:
+
+-   A K8s [namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) named `rdi`.
+-   [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) for the 
+    [RDI operator]({{< relref "/integrate/redis-data-integration/architecture#how-rdi-is-deployed" >}}),
+    [metrics exporter]({{< relref "/integrate/redis-data-integration/observability" >}}), and API server.
+-   A [service account](https://kubernetes.io/docs/concepts/security/service-accounts/) along with a
+    [role](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#restrictions-on-role-creation-or-update)
+    and [role binding](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding) for the RDI operator.
+-   A [Configmap](https://kubernetes.io/docs/concepts/configuration/configmap/)
+    for the different components with RDI Redis database details.
+-   [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/)
+    with the RDI Redis database credentials and TLS certificates.
+
+See [Install on Kubernetes]({{< relref "/integrate/redis-data-integration/installation/install-k8s" >}})
+for more information.
 
 ### Secrets and security considerations
 

content/integrate/redis-data-integration/data-pipelines/deploy.md

@@ -58,10 +58,17 @@ secrets are only relevant to TLS/mTLS connections.
 
 If you are hosting RDI on your own VMs, you can use the
 [`deploy`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-deploy" >}})
-command to deploy a configuration, including the jobs, once you have created them.
+command to deploy a configuration, including the jobs, once you have created them:
 
-If your RDI CLI is deployed as a pod in a Kubernetes cluster, you should perform the following
-steps to deploy a pipeline:
+```bash
+redis-di deploy --dir <path to pipeline folder>
+```
+
+You can also deploy a pipeline using [Redis Insight]({{< relref "/develop/connect/insight/rdi-connector" >}}).
+
+If your RDI CLI is deployed as a pod in a
+[Kubernetes cluster]({{< relref "/integrate/redis-data-integration/installation/install-k8s" >}}),
+you should perform the following steps to deploy a pipeline:
 
 - Create a [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) from the
   YAML files in your `jobs` folder:
@@ -93,4 +100,4 @@ You have two options to update the ConfigMap:
   kubectl create configmap redis-di-jobs --from-file=jobs/ --dry-run=client -o yaml | kubectl apply -f -
   ```
 
-{{< note >}} You must run `kubectl exec -it pod/redis-di-cli -- redis-di deploy` after updating the ConfigMap with either option.{{< /note >}}
+{{< note >}} You must run `kubectl exec -it pod/redis-di-cli -- redis-di deploy` after updating the ConfigMap with either option.{{< /note >}}

content/integrate/redis-data-integration/installation/_index.md

@@ -14,7 +14,7 @@ linkTitle: Installation
 summary: Redis Data Integration keeps Redis in sync with the primary database in near
   real time.
 type: integration
-weight: 1
+weight: 2
 ---
 
 The guides in this section explain the options you have for installing RDI.

content/integrate/redis-data-integration/installation/install-k8s.md

@@ -28,11 +28,11 @@ The installation creates the following K8s objects:
     [metrics exporter]({{< relref "/integrate/redis-data-integration/observability" >}}), and API server.
 -   A [service account](https://kubernetes.io/docs/concepts/security/service-accounts/) along with a
     [role](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#restrictions-on-role-creation-or-update)
-    and [role binding](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding) for the RDI operator
+    and [role binding](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding) for the RDI operator.
 -   A [Configmap](https://kubernetes.io/docs/concepts/configuration/configmap/)
-    for the different components with RDI Redis database details
+    for the different components with RDI Redis database details.
 -   [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/)
-    with the RDI Redis database credentials and TLS certificates
+    with the RDI Redis database credentials and TLS certificates.
 
 You can use this installation on [OpenShift](https://docs.openshift.com/) and other K8s distributions
 including cloud providers' K8s managed clusters.
@@ -51,10 +51,26 @@ Complete the following steps before running Helm:
     more information).
 -   Download the RDI helm chart tar file from the [download center](https://cloud.redis.io/#/rlec-downloads).
 
+### Create the RDI database
+
+RDI uses a database on your Redis Enterprise cluster to store its state
+information. *This requires Redis Enterprise v6.4 or greater*.
+
+Before installing RDI:
+
+- Use the Redis console to create a database with 250MB RAM with 1 primary and 1 replica.
+- If you are deploying RDI for a production environment then secure this database with a password
+  and [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security).
+
+You should then provide the details of this database in [the `values.yaml` file](#the-valuesyaml-file),
+as described below.
+
 ### Using a private image registry
 
 Add the RDI images from [Docker Hub](https://hub.docker.com/) to your local registry.
-The example below shows how to specify the registry and image pull secret in `values.yaml`:
+The example below shows how to specify the registry and image pull secret in the
+[`values.yaml`](https://helm.sh/docs/topics/charts/#templates-and-values) file for the
+Helm chart:
 
 ```yaml
 global:
@@ -85,14 +101,24 @@ To pull images from a local registry, you must provide the image pull secret and
 	tar -xvf rdi-k8s-<rdi-tag>.tar.gz 
     ```
 
-1.  Open the `values.yaml` file and set the appropriate values (see list of values below).
+1.  Open the `values.yaml` file and set the appropriate values for your installation
+    (see [The `values.yaml` file](#the-valuesyaml-file) below for the full set of
+    available values).
 
 1.  Start the installation:
 
     ```bash
     helm install <The logical chart name> rdi-k8s/<rdi-tag>/helm 
     ```
 
+### The `values.yaml` file
+
+The annotated `values.yaml` file below describes the values you can set
+for the RDI Helm installation:
+
+```yaml
+```
+
 ## Check the installation
 
 To verify the status of the K8s deployment, run the following command:
@@ -101,8 +127,7 @@ To verify the status of the K8s deployment, run the following command:
 helm list -n monitoring -n rdi
 ```
 
-The output looks like the following. Check that `<logical_chart_name>` has
-the value `IDT` in the `STATUS` column.
+The output looks like the following. Check that `<logical_chart_name>` is listed.
 
 ```
 NAME 	             NAMESPACE    REVISION    UPDATED                STATUS    CHART   	 APP VERSION

content/integrate/redis-data-integration/quick-start-guide.md

@@ -44,7 +44,7 @@ and is already set up for the RDI collector to use.
 ### Install RDI
 
 Install RDI using the instructions in the
-[installation guide]({{< relref "/integrate/redis-data-integration/installation" >}})
+[VM installation guide]({{< relref "/integrate/redis-data-integration/installation/install-vm" >}}).
 
 RDI will create the pipeline template for your chosen source database type at
 `/opt/rdi/config`. You will need this pathname later when you prepare the pipeline for deployment
@@ -112,7 +112,8 @@ contexts.
 
 ### Deploy the pipeline
 
-You can use Redis Insight to deploy the pipeline by adding a connection to the RDI API
+You can use [Redis Insight]({{< relref "/develop/connect/insight/rdi-connector" >}})
+to deploy the pipeline by adding a connection to the RDI API
 endpoint (which has the same IP address as your RDI VM and uses port 8083) and then clicking the **Deploy** button. You can also deploy it with the following command:
 
 ```bash
@@ -127,6 +128,9 @@ validates your pipeline and then deploys it if the configuration is correct.
 Once the pipeline is running, you can use Redis Insight to view the data flow using the
 pipeline metrics. You can also connect to your target database to see the keys that RDI has written there.
 
+See [Deploy a pipeline]({{< relref "/integrate/redis-data-integration/data-pipelines/deploy" >}})
+for more information about deployment settings.
+
 ### View RDI's response to data changes
 
 Once the pipeline has loaded a *snapshot* of all the existing data from the source,