RS: Add RS 7.8 versioned docs (#1351)

* DOC-4928 RS: Add RS 7.8 versioned docs

* DOC-4928 Removed duplicate aliases from 7.8 versioned docs

* DOC-4928 Added missing prometheus metrics references to RS 7.8 versioned docs

* DOC-4928 Added missing networking docs to RS 7.8 versioned docs

* DOC-4928 Added missing v1 monitoring doc to RS 7.8 versioned docs

* Fix versioned relrefs

* DOC-4928 Added 7.8 version banner

* DOC-5034 Copy missing job_scheduler REST API references to RS v7.8

* Fixed links to RS release notes in versioned docs

* DOC-3605 Copy support package CM UI options to RS 7.8 version

* DOC-4986 Copy rladmin cluster config s3_ca_cert step to import/export/backup DB in 7.4/7.8 versions

* Copy certificate landing page edits to RS v7.8 docs

* Copied required_version bootstrap API deprecation to RS v7.8 docs

* Copied fix for broken download center link to RS 7.8 version

* DOC-5216 Copied bigstore_enabled to RS 7.8 node REST API reference

* DOC-5232 RS: Copied ccs directory typo fix for cluster recovery to 7.8 version

* DOC-4692 RS: Copied certificate-based authentication to 7.8 version

* DOC-5159 Copy update DNS step for rolling upgrades to RS 7.8 and 7.4 versions

* DOC-5216 Copied additional bigstore_enabled details to 7.8 version

* Fixed some versioned RS links

* Copied Redis Open Source name to RS 7.8 version

* Copied updated configure proxy policy REST API example with endpoint to RS 7.8 version

---------

Co-authored-by: paoloredis <[email protected]>

Author: rrelledge

content/operate/rs/7.4/_index.md

@@ -36,7 +36,7 @@ Build a small-scale cluster with the Redis Enterprise Software container image.
 [Install & set up]({{< relref "/operate/rs/7.4/installing-upgrading" >}}) a Redis Enterprise Software cluster.
 - [Networking]({{< relref "/operate/rs/7.4/networking" >}})
 - [Set up]({{< relref "/operate/rs/7.4/clusters/new-cluster-setup" >}}) & [configure]({{< relref "/operate/rs/7.4/clusters/configure" >}}) a [cluster]({{< relref "/operate/rs/7.4/clusters" >}})
-- [Release notes]({{< relref "/operate/rs/release-notes" >}})
+- [Release notes](https://redis.io/docs/latest/operate/rs/release-notes/)
 
 ## Databases
 Create and manage a [Redis database]({{< relref "/operate/rs/7.4/databases" >}}) on a cluster.

content/operate/rs/7.4/clusters/configure/rack-zone-awareness.md

@@ -31,7 +31,7 @@ Rack-zone awareness affects various cluster, node, and database actions, such as
 The rack-zone ID must comply with the following rules:
 
 - Maximum length of 63 characters.
-- Characters consist of letters, digits, and hyphens ('-'). Underscores ('_') are also accepted as of Redis Enterprise Software [6.4.2-61]({{< relref "/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-61" >}}).
+- Characters consist of letters, digits, and hyphens ('-'). Underscores ('_') are also accepted as of Redis Enterprise Software 6.4.2-61.
 - ID starts with a letter and ends with a letter or a digit.
 
 {{< note >}}

content/operate/rs/7.4/databases/auto-tiering/_index.md

@@ -24,7 +24,7 @@ Redis Enterprise’s auto tiering is based on a high-performance storage engine
 
 Just like all-RAM databases, databases with Auto Tiering enabled are compatible with existing Redis applications.
 
-Auto Tiering is also supported on [Redis Cloud]({{< relref "/operate/rc/" >}}) and [Redis Enterprise Software for Kubernetes]({{< relref "/operate/rs/" >}}).
+Auto Tiering is also supported on [Redis Cloud]({{< relref "/operate/rc/" >}}) and [Redis Enterprise Software for Kubernetes]({{< relref "/operate/kubernetes/" >}}).
 
 ## Use cases
 

content/operate/rs/7.4/databases/import-export/export-data.md

@@ -161,13 +161,25 @@ To export data to an [Amazon Web Services](https://aws.amazon.com/) (AWS) Simple
 
     - In the **Secret access key** field, enter the secret access key.
 
-You can also connect to a storage service that uses the S3 protocol but is not hosted by Amazon AWS. The storage service must have a valid SSL certificate. To connect to an S3-compatible storage location, run [`rladmin cluster config`]({{<relref "/operate/rs/7.4/references/cli-utilities/rladmin/cluster/config">}}): 
+You can also connect to a storage service that uses the S3 protocol but is not hosted by Amazon AWS. The storage service must have a valid SSL certificate.
 
-```sh
-rladmin cluster config s3_url <URL>
-```
+To connect to an S3-compatible storage location:
+
+1. Configure the S3 URL with [`rladmin cluster config`]({{<relref "/operate/rs/7.4/references/cli-utilities/rladmin/cluster/config">}}): 
+
+    ```sh
+    rladmin cluster config s3_url <URL>
+    ```
+
+    Replace `<URL>` with the hostname or IP address of the S3-compatible storage location.
+
+1. Configure the S3 CA certificate:
+
+    ```sh
+    rladmin cluster config s3_ca_cert <filepath>
+    ```
 
-Replace `<URL>` with the hostname or IP address of the S3-compatible storage location.
+    Replace `<filepath>` with the location of the S3 CA certificate `ca.pem`.
 
 ### Google Cloud Storage
 

content/operate/rs/7.4/databases/import-export/import-data.md

@@ -156,13 +156,25 @@ In the Redis Enterprise Software Cluster Manager UI, when you enter the export l
 
 - In the **Secret access key** field, enter the secret access key.
 
-You can also connect to a storage service that uses the S3 protocol but is not hosted by Amazon AWS. The storage service must have a valid SSL certificate. To connect to an S3-compatible storage location, run [`rladmin cluster config`]({{<relref "/operate/rs/7.4/references/cli-utilities/rladmin/cluster/config">}}): 
+You can also connect to a storage service that uses the S3 protocol but is not hosted by Amazon AWS. The storage service must have a valid SSL certificate.
 
-```sh
-rladmin cluster config s3_url <URL>
-```
+To connect to an S3-compatible storage location:
+
+1. Configure the S3 URL with [`rladmin cluster config`]({{<relref "/operate/rs/7.4/references/cli-utilities/rladmin/cluster/config">}}): 
+
+    ```sh
+    rladmin cluster config s3_url <URL>
+    ```
+
+    Replace `<URL>` with the hostname or IP address of the S3-compatible storage location.
+
+1. Configure the S3 CA certificate:
+
+    ```sh
+    rladmin cluster config s3_ca_cert <filepath>
+    ```
 
-Replace `<URL>` with the hostname or IP address of the S3-compatible storage location.
+    Replace `<filepath>` with the location of the S3 CA certificate `ca.pem`.
 
 ### Google Cloud Storage
 

content/operate/rs/7.4/databases/import-export/schedule-backups.md

@@ -210,13 +210,25 @@ To store backups in an Amazon Web Services (AWS) Simple Storage Service (S3) [bu
 
     - In the **Secret Access Key** field, enter the secret access key.
 
-You can also connect to a storage service that uses the S3 protocol but is not hosted by Amazon AWS. The storage service must have a valid SSL certificate. To connect to an S3-compatible storage location, run [`rladmin cluster config`]({{<relref "/operate/rs/7.4/references/cli-utilities/rladmin/cluster/config">}}): 
+You can also connect to a storage service that uses the S3 protocol but is not hosted by Amazon AWS. The storage service must have a valid SSL certificate.
 
-```sh
-rladmin cluster config s3_url <URL>
-```
+To connect to an S3-compatible storage location:
+
+1. Configure the S3 URL with [`rladmin cluster config`]({{<relref "/operate/rs/7.4/references/cli-utilities/rladmin/cluster/config">}}): 
+
+    ```sh
+    rladmin cluster config s3_url <URL>
+    ```
+
+    Replace `<URL>` with the hostname or IP address of the S3-compatible storage location.
+
+1. Configure the S3 CA certificate:
+
+    ```sh
+    rladmin cluster config s3_ca_cert <filepath>
+    ```
 
-Replace `<URL>` with the hostname or IP address of the S3-compatible storage location.
+    Replace `<filepath>` with the location of the S3 CA certificate `ca.pem`.
 
 ### Google Cloud Storage
 

content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-cluster.md

@@ -23,7 +23,7 @@ Before upgrading a cluster:
 
 - Verify access to [rlcheck]({{< relref "/operate/rs/7.4/references/cli-utilities/rlcheck/" >}}) and [rladmin]({{< relref "/operate/rs/7.4/references/cli-utilities/rladmin/#use-the-rladmin-shell" >}}) commands
 
-- Verify that you meet the upgrade path requirements for your desired cluster version and review the relevant [release notes]({{< relref "/operate/rs/release-notes" >}}) for any preparation instructions.
+- Verify that you meet the upgrade path requirements for your desired cluster version and review the relevant [release notes](https://redis.io/docs/latest/operate/rs/release-notes/) for any preparation instructions.
 
 - Avoid changing the database configuration or performing other cluster management operations during the upgrade process, as this might cause unexpected results.
 

content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md

@@ -40,7 +40,7 @@ The upgrade policy is only relevant for Redis Enterprise Software versions 6.2.4
 
 Before upgrading a database:
 
-- Review the relevant [release notes]({{< relref "/operate/rs/release-notes" >}}) for any preparation instructions.
+- Review the relevant [release notes](https://redis.io/docs/latest/operate/rs/release-notes/) for any preparation instructions.
 
 - Verify that the database version meets the minimums specified earlier.
 

content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-os.md

@@ -25,7 +25,7 @@ Before you upgrade a cluster's operating system:
 
 1. If the cluster contains databases that use modules:
 
-    1. Update all nodes in the cluster to [Redis Enterprise Software version 7.2.4-52]({{< relref "/operate/rs/release-notes/rs-7-2-4-releases" >}}) or later before you upgrade the OS.
+    1. Update all nodes in the cluster to [Redis Enterprise Software version 7.2.4-52](https://redis.io/docs/latest/operate/rs/release-notes/rs-7-2-4-releases) or later before you upgrade the OS.
 
     1. Check the status of modules using [`rladmin`]({{< relref "/operate/rs/7.4/references/cli-utilities/rladmin" >}}):
 
@@ -79,6 +79,8 @@ To upgrade the cluster's operating system, use one of the following rolling upgr
 
 1. [Add the new node]({{< relref "/operate/rs/7.4/clusters/add-node" >}})  to the cluster.
 
+1. If the [cluster uses DNS]({{<relref "/operate/rs/7.4/networking/cluster-dns">}}), add the new node’s IP address to the DNS records.
+
 1. [Remove one node]({{< relref "/operate/rs/7.4/clusters/remove-node#remove-a-node" >}}) running the earlier OS version from the cluster.
 
 1. Repeat the previous steps until all nodes with the earlier OS version are removed.
@@ -105,6 +107,8 @@ To upgrade the cluster's operating system, use one of the following rolling upgr
     rladmin cluster join nodes <cluster_member_ip_address> username <username> password <password> replace_node <node_id>
     ```
 
+1. If the [cluster uses DNS]({{<relref "/operate/rs/7.4/networking/cluster-dns">}}), add the new node’s IP address to the DNS records.
+
 1. Verify node health:
 
     1. Run `rlcheck` on all nodes:

content/operate/rs/7.4/references/rest-api/objects/cluster/_index.md

@@ -55,6 +55,7 @@ An API object that represents the cluster.
 | proxy_max_ccs_disconnection_time | integer | Cluster-wide proxy timeout policy between proxy and CCS |
 | rack_aware | boolean | Cluster operates in a rack-aware mode (read-only) |
 | reserved_ports | array of strings | List of reserved ports and/or port ranges to avoid using for database endpoints (for example `"reserved_ports": ["11000", "13000-13010"]`) |
+| s3_ca_cert | string | Filepath to the PEM-encoded CA certificate to use for validating TLS connections to the S3 server |
 | s3_url | string | Specifies the URL for S3 export and import |
 | saslauthd_ldap_conf | string | saslauthd LDAP configuration |
 | sentinel_cipher_suites | array | Specifies the list of enabled ciphers for the sentinel service. The supported ciphers are those implemented by the [cipher_suites.go](<https://golang.org/src/crypto/tls/cipher_suites.go>) package. |