DOC-7104: Migrate content/operate/rs/7.8/ (excl. references) to render hooks

content/operate/rs/7.8/_index.md

@@ -24,39 +24,39 @@ With Redis Enterprise, you get many enterprise-grade capabilities, including:
 
 You can run self-managed Redis Enterprise Software in an on-premises data center or on your preferred cloud platform.
 
-If you prefer a fully managed Redis database-as-a-service, available on major public cloud services, consider setting up a [Redis Cloud]({{<relref "/operate/rc">}}) subscription. You can [try Redis Cloud](https://redis.io/try-free/) for free.
+If you prefer a fully managed Redis database-as-a-service, available on major public cloud services, consider setting up a [Redis Cloud](/content/operate/rc/_index.md) subscription. You can [try Redis Cloud](https://redis.io/try-free/) for free.
 
 ## Get started
 Build a small-scale cluster with the Redis Enterprise Software container image.
-- [Linux quickstart]({{< relref "/operate/rs/7.8/installing-upgrading/quickstarts/redis-enterprise-software-quickstart" >}})
-- [Docker quickstart]({{< relref "/operate/rs/7.8/installing-upgrading/quickstarts/docker-quickstart" >}})
-- [Get started with Active-Active]({{< relref "/operate/rs/7.8/databases/active-active/get-started" >}})
+- [Linux quickstart](/content/operate/rs/7.8/installing-upgrading/quickstarts/redis-enterprise-software-quickstart.md)
+- [Docker quickstart](/content/operate/rs/7.8/installing-upgrading/quickstarts/docker-quickstart.md)
+- [Get started with Active-Active](/content/operate/rs/7.8/databases/active-active/get-started.md)
 
 ## Install & setup
-[Install & set up]({{< relref "/operate/rs/7.8/installing-upgrading" >}}) a Redis Enterprise Software cluster.
-- [Networking]({{< relref "/operate/rs/7.8/networking" >}})
-- [Set up]({{< relref "/operate/rs/7.8/clusters/new-cluster-setup" >}}) & [configure]({{< relref "/operate/rs/7.8/clusters/configure" >}}) a [cluster]({{< relref "/operate/rs/7.8/clusters" >}})
+[Install & set up](/content/operate/rs/7.8/installing-upgrading/_index.md) a Redis Enterprise Software cluster.
+- [Networking](/content/operate/rs/7.8/networking/_index.md)
+- [Set up](/content/operate/rs/7.8/clusters/new-cluster-setup.md) & [configure](/content/operate/rs/7.8/clusters/configure/_index.md) a [cluster](/content/operate/rs/7.8/clusters/_index.md)
 - [Release notes](https://redis.io/docs/latest/operate/rs/release-notes/)
 
 ## Databases
-Create and manage a [Redis database]({{< relref "/operate/rs/7.8/databases" >}}) on a cluster.
-- [Create a Redis Enterprise Software database]({{< relref "/operate/rs/7.8/databases/create" >}})
-- [Configure database]({{< relref "/operate/rs/7.8/databases/configure" >}})
-- [Create Active-Active database]({{< relref "/operate/rs/7.8/databases/active-active/create" >}})
-- [Edit Active-Active database]({{< relref "/operate/rs/7.8/databases/active-active/manage.md" >}})
+Create and manage a [Redis database](/content/operate/rs/7.8/databases/_index.md) on a cluster.
+- [Create a Redis Enterprise Software database](/content/operate/rs/7.8/databases/create.md)
+- [Configure database](/content/operate/rs/7.8/databases/configure/_index.md)
+- [Create Active-Active database](/content/operate/rs/7.8/databases/active-active/create.md)
+- [Edit Active-Active database](/content/operate/rs/7.8/databases/active-active/manage.md)
 
 ## Security
-[Manage secure connections]({{< relref "/operate/rs/7.8/security" >}}) to the cluster and databases.
-- [Access control]({{< relref "/operate/rs/7.8/security/access-control" >}})
-- [Users]({{< relref "/operate/rs/7.8/security/access-control/manage-users" >}}) & [roles]({{< relref "/operate/rs/7.8/security/access-control" >}})
-- [Certificates]({{< relref "/operate/rs/7.8/security/certificates" >}})
-- [TLS]({{< relref "/operate/rs/7.8/security/encryption/tls" >}}) & [Encryption]({{< relref "/operate/rs/7.8/security/encryption" >}})
+[Manage secure connections](/content/operate/rs/7.8/security/_index.md) to the cluster and databases.
+- [Access control](/content/operate/rs/7.8/security/access-control/_index.md)
+- [Users](/content/operate/rs/7.8/security/access-control/manage-users/_index.md) & [roles](/content/operate/rs/7.8/security/access-control/_index.md)
+- [Certificates](/content/operate/rs/7.8/security/certificates/_index.md)
+- [TLS](/content/operate/rs/7.8/security/encryption/tls/_index.md) & [Encryption](/content/operate/rs/7.8/security/encryption/_index.md)
 
 ## Reference
 Use command-line utilities and the REST API to manage the cluster and databases.
-- [rladmin]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin" >}}), [crdb-cli]({{< relref "/operate/rs/7.8/references/cli-utilities/crdb-cli" >}}), & [other utilities]({{< relref "/operate/rs/7.8/references/cli-utilities" >}})
-- [REST API reference]({{< relref "/operate/rs/7.8/references/rest-api" >}}) & [examples]({{< relref "/operate/rs/7.8/references/rest-api/quick-start" >}})
-- [Redis commands]({{< relref "/commands" >}})
+- [rladmin](/content/operate/rs/7.8/references/cli-utilities/rladmin/_index.md), [crdb-cli](/content/operate/rs/7.8/references/cli-utilities/crdb-cli/_index.md), & [other utilities](/content/operate/rs/7.8/references/cli-utilities/_index.md)
+- [REST API reference](/content/operate/rs/7.8/references/rest-api/_index.md) & [examples](/content/operate/rs/7.8/references/rest-api/quick-start.md)
+- [Redis commands](/content/commands)
 
 ## Archive
 
@@ -74,10 +74,10 @@ To view documentation earlier than version 7.4, see the archived website:
 
 
 ## Related info
-- [Redis Cloud]({{< relref "/operate/rc" >}})
-- [Redis Open Source]({{< relref "/operate/oss_and_stack" >}})
-- [Redis Stack]({{< relref "/operate/oss_and_stack/stack-with-enterprise" >}})
-- [Glossary]({{< relref "/glossary" >}})
+- [Redis Cloud](/content/operate/rc/_index.md)
+- [Redis Open Source](/content/operate/oss_and_stack/_index.md)
+- [Redis Stack](/content/operate/oss_and_stack/stack-with-enterprise/_index.md)
+- [Glossary](/content/glossary/_index.md)
 
 ## Continue learning with Redis University
 

content/operate/rs/7.8/clusters/_index.md

@@ -16,5 +16,5 @@ url: '/operate/rs/7.8/clusters/'
 You can manage your Redis Enterprise Software clusters with several different tools:
 
 - Cluster Manager UI (the web-based user interface)
-- Command-line tools ([rladmin]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin" >}}), [redis-cli]({{< relref "/develop/tools/cli" >}}), [crdb-cli]({{< relref "/operate/rs/7.8/references/cli-utilities/crdb-cli" >}}))
-- [REST API]({{< relref "/operate/rs/7.8/references/rest-api/_index.md" >}})
+- Command-line tools ([rladmin](/content/operate/rs/7.8/references/cli-utilities/rladmin/_index.md), [redis-cli](/content/develop/tools/cli.md), [crdb-cli](/content/operate/rs/7.8/references/cli-utilities/crdb-cli/_index.md))
+- [REST API](/content/operate/rs/7.8/references/rest-api/_index.md)

content/operate/rs/7.8/clusters/add-node.md

@@ -17,12 +17,12 @@ After you install the first node, you can add more nodes to the cluster.
 
 Before you add a node to the cluster:
 
-- The clocks on all nodes must always be [synchronized]({{< relref "/operate/rs/7.8/clusters/configure/sync-clocks.md" >}}).
+- The clocks on all nodes must always be [synchronized](/content/operate/rs/7.8/clusters/configure/sync-clocks.md).
 
     If the clock in the node you are trying to join to the cluster is not synchronized with the nodes already in the cluster,
     the action fails and an error message is shown indicating that you must synchronize the clocks first.
 
-- You must [update the DNS records]({{< relref "/operate/rs/7.8/networking/cluster-dns" >}})
+- You must [update the DNS records](/content/operate/rs/7.8/networking/cluster-dns.md)
     each time a node is added or replaced.
 
 - We recommend that you add nodes one after the other rather than in parallel
@@ -32,18 +32,18 @@ Before you add a node to the cluster:
 
 To add a node to an existing cluster:
 
-1. [Install the Redis Enterprise Software installation package]({{< relref "/operate/rs/7.8/installing-upgrading" >}}) on a clean installation
-    of a [supported operating system]({{< relref "/operate/rs/7.8/installing-upgrading/install/plan-deployment/supported-platforms.md" >}}).
+1. [Install the Redis Enterprise Software installation package](/content/operate/rs/7.8/installing-upgrading/_index.md) on a clean installation
+    of a [supported operating system](/content/operate/rs/7.8/installing-upgrading/install/plan-deployment/supported-platforms.md).
 
 1. To connect to the Cluster Manager UI of the new Redis Enterprise Software installation, go to: <https://URL or IP address:8443>
 
     For example, if you installed Redis Enterprise Software on a machine with IP address 10.0.1.34, go to `https://10.0.1.34:8443`.
 
-    {{< tip >}}
-The management UI uses TLS encryption with a default certificate.
-You can also [replace the TLS certificate]({{< relref "/operate/rs/7.8/security/certificates/updating-certificates" >}})
-with a custom certificate.
-    {{< /tip >}}
+    > [!TIP]
+    > The management UI uses TLS encryption with a default certificate.
+    > You can also [replace the TLS certificate](/content/operate/rs/7.8/security/certificates/updating-certificates.md)
+    > with a custom certificate.
+    >
 
 1. Select **Join cluster**.
 
@@ -59,15 +59,15 @@ with a custom certificate.
 
 1. Configure storage and network settings:
 
-    1. Enter a path for [*Ephemeral storage*]({{< relref "/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}), or leave the default path.
+    1. Enter a path for [*Ephemeral storage*](/content/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage.md), or leave the default path.
 
-    1. Enter a path for [*Persistent storage*]({{< relref "/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}),
+    1. Enter a path for [*Persistent storage*](/content/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage.md),
         or leave the default path.
 
-    1. To enable [*Auto Tiering*]({{< relref "/operate/rs/7.8/databases/auto-tiering/" >}}),
+    1. To enable [*Auto Tiering*](/content/operate/rs/7.8/databases/auto-tiering/_index.md),
         select **Enable flash storage** and enter the path to the flash storage.
 
-    1. If the cluster is configured to support [rack-zone awareness]({{< relref "/operate/rs/7.8/clusters/configure/rack-zone-awareness.md" >}}), set the **Rack-zone ID** for the new node.
+    1. If the cluster is configured to support [rack-zone awareness](/content/operate/rs/7.8/clusters/configure/rack-zone-awareness.md), set the **Rack-zone ID** for the new node.
 
     1. If your machine has multiple IP addresses, assign a single IPv4 type address for **Node-to-node communication (internal traffic)** and multiple IPv4/IPv6 type addresses for **External traffic**.
 
@@ -92,4 +92,4 @@ We recommend that you verify the node is functioning properly using one of the f
 
 - Command-line method:
 
-    Run the [`rlcheck`]({{< relref "/operate/rs/7.8/references/cli-utilities/rlcheck" >}}) utility from the node's command line.
+    Run the [`rlcheck`](/content/operate/rs/7.8/references/cli-utilities/rlcheck/_index.md) utility from the node's command line.

content/operate/rs/7.8/clusters/cluster-recovery.md

@@ -14,9 +14,8 @@ url: '/operate/rs/7.8/clusters/cluster-recovery/'
 When a Redis Enterprise Software cluster fails,
 you must use the cluster configuration file and database data to recover the cluster.
 
-{{< note >}}
-For cluster recovery in a Kubernetes deployment, see [Recover a Redis Enterprise cluster on Kubernetes]({{< relref "/operate/kubernetes/re-clusters/cluster-recovery" >}}).
-{{< /note >}}
+> [!NOTE]
+> For cluster recovery in a Kubernetes deployment, see [Recover a Redis Enterprise cluster on Kubernetes](/content/operate/kubernetes/re-clusters/cluster-recovery.md).
 
 Cluster failure can be caused by:
 
@@ -26,15 +25,15 @@ Cluster failure can be caused by:
 To recover a cluster and re-create it as it was before the failure,
 you must restore the cluster configuration `ccs-redis.rdb` to the cluster nodes.
 To recover databases in the new cluster, you must restore the databases from persistence files such as backup files, append-only files (AOF), or RDB snapshots.
-These files are stored in the [persistent storage location]({{< relref "/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}).
+These files are stored in the [persistent storage location](/content/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage.md).
 
 The cluster recovery process includes:
 
 1. Install Redis Enterprise Software on the nodes of the new cluster.
 1. Mount the persistent storage with the recovery files from the original cluster to the nodes of the new cluster.
 1. Recover the cluster configuration on the first node in the new cluster.
 1. Join the remaining nodes to the new cluster.
-1. [Recover the databases]({{< relref "/operate/rs/7.8/databases/recover.md" >}}).
+1. [Recover the databases](/content/operate/rs/7.8/databases/recover.md).
 
 ## Prerequisites
 
@@ -51,7 +50,7 @@ The cluster recovery process includes:
 
 1. (Optional) If you want to recover the cluster to the original cluster nodes, uninstall Redis Enterprise Software from the nodes.
 
-1. [Install Redis Enterprise Software]({{< relref "/operate/rs/7.8/installing-upgrading/install/install-on-linux" >}}) on the new cluster nodes.
+1. [Install Redis Enterprise Software](/content/operate/rs/7.8/installing-upgrading/install/install-on-linux.md) on the new cluster nodes.
 
     The new servers must have the same basic hardware and software configuration as the original servers, including:
 
@@ -60,21 +59,21 @@ The cluster recovery process includes:
     - The same Redis Enterprise Software version
     - The same installation user and paths
 
-    {{< note >}}
-The cluster recovery can fail if these requirements are not met.
-    {{< /note >}}
+    > [!NOTE]
+    > The cluster recovery can fail if these requirements are not met.
+    >
 
 1. Mount the persistent storage drives with the recovery files to the new nodes.
     These drives must contain the cluster configuration backup files and database persistence files.
 
-    {{< note >}}
-Make sure that the user redislabs has permissions to access the storage location
-of the configuration and persistence files on each of the nodes.
-    {{< /note >}}
+    > [!NOTE]
+    > Make sure that the user redislabs has permissions to access the storage location
+    > of the configuration and persistence files on each of the nodes.
+    >
 
     If you use local persistent storage, place all of the recovery files on each of the cluster nodes.
 
-1. To recover the original cluster configuration, run [`rladmin cluster recover`]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin/cluster/recover" >}}) on the first node in the new cluster:
+1. To recover the original cluster configuration, run [`rladmin cluster recover`](/content/operate/rs/7.8/references/cli-utilities/rladmin/cluster/recover.md) on the first node in the new cluster:
 
     ```sh
     rladmin cluster recover filename [ <persistent_path> | <ephemeral_path> ]<filename> node_uid <node_uid> rack_id <rack_id>
@@ -89,7 +88,7 @@ of the configuration and persistence files on each of the nodes.
     When the recovery command succeeds,
     this node is configured as the node from the old cluster that has ID 1.
 
-1. To join the remaining servers to the new cluster, run [`rladmin cluster join`]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin/cluster/join" >}}) from each new node:
+1. To join the remaining servers to the new cluster, run [`rladmin cluster join`](/content/operate/rs/7.8/references/cli-utilities/rladmin/cluster/join.md) from each new node:
 
     ```sh
     rladmin cluster join nodes <cluster_member_ip_address> username <username> password <password> replace_node <node_id>
@@ -101,15 +100,15 @@ of the configuration and persistence files on each of the nodes.
     rladmin cluster join nodes 10.142.0.4 username admin@example.com password mysecret replace_node 2
     ```
 
-1. Run [`rladmin status`]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin/status" >}}) to verify the recovered nodes are now active and the databases are pending recovery:
+1. Run [`rladmin status`](/content/operate/rs/7.8/references/cli-utilities/rladmin/status.md) to verify the recovered nodes are now active and the databases are pending recovery:
 
     ```sh
     rladmin status
     ```
 
-    {{< note >}}
-Make sure that you update your [DNS records]({{< relref "/operate/rs/7.8/networking/cluster-dns" >}})
-with the IP addresses of the new nodes.
-    {{< /note >}}
+    > [!NOTE]
+    > Make sure that you update your [DNS records](/content/operate/rs/7.8/networking/cluster-dns.md)
+    > with the IP addresses of the new nodes.
+    >
 
-After the cluster is recovered, you must [recover the databases]({{< relref "/operate/rs/7.8/databases/recover.md" >}}).
+After the cluster is recovered, you must [recover the databases](/content/operate/rs/7.8/databases/recover.md).

content/operate/rs/7.8/clusters/configure/_index.md

@@ -14,8 +14,8 @@ url: '/operate/rs/7.8/clusters/configure/'
 You can manage your Redis Enterprise Software clusters with several different tools:
 
 - Cluster Manager UI (the web-based user interface)
-- Command-line tools ([rladmin]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin" >}}), [redis-cli]({{< relref "/develop/tools/cli" >}}), [crdb-cli]({{< relref "/operate/rs/7.8/references/cli-utilities/crdb-cli" >}}))
-- [REST API]({{< relref "/operate/rs/7.8/references/rest-api/_index.md" >}})
+- Command-line tools ([rladmin](/content/operate/rs/7.8/references/cli-utilities/rladmin/_index.md), [redis-cli](/content/develop/tools/cli.md), [crdb-cli](/content/operate/rs/7.8/references/cli-utilities/crdb-cli/_index.md))
+- [REST API](/content/operate/rs/7.8/references/rest-api/_index.md)
 
 
 

content/operate/rs/7.8/clusters/configure/cluster-settings.md

@@ -23,7 +23,7 @@ you can upload the cluster license key, either during initial
 cluster creation or at any time afterward. The license key defines various
 cluster settings, such as the maximum number of shards you can have in
 the cluster. For more detailed information see [Cluster license
-keys]({{< relref "/operate/rs/7.8/clusters/configure/license-keys.md" >}}).
+keys](/content/operate/rs/7.8/clusters/configure/license-keys.md).
 
 ### View max number of allowed shards
 
@@ -44,7 +44,7 @@ You can change the **Time zone** field to ensure the date, time fields, and log
 
 The **Alert Settings** tab lets you configure alerts that are relevant to the entire cluster, such as alerts for cluster utilization, nodes, node utilization, security, and database utilization.
 
-You can also configure email server settings and [send alerts by email]({{< relref "/operate/rs/7.8/monitoring/v1_monitoring#send-alerts-by-email" >}}) to relevant users.
+You can also configure email server settings and [send alerts by email](/content/operate/rs/7.8/monitoring/v1_monitoring.md#send-alerts-by-email) to relevant users.
 
 ### Configure email server settings