From 6046c0524b2d4758b988a7e9596e69c2765c3b75 Mon Sep 17 00:00:00 2001 From: Brian Presley <42596015+sumobrian@users.noreply.github.com> Date: Wed, 13 Sep 2023 13:39:16 -0500 Subject: [PATCH] Remove steps for migrating cluster, targeted for later release (#5012) Signed-off-by: Brian Presley Co-authored-by: Brian Presley --- _tools/index.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/_tools/index.md b/_tools/index.md index 1e4a4b64..e4675337 100644 --- a/_tools/index.md +++ b/_tools/index.md @@ -117,10 +117,4 @@ The OpenSearch Kubernetes Operator is an open-source Kubernetes operator that he OpenSearch migration tools facilitate migrations to OpenSearch and upgrades to newer versions of OpenSearch. These can help you can set up a proof-of-concept environment locally using Docker containers or deploy to AWS using a one-click deployment script. This empowers you to fine-tune cluster configurations and manage workloads more effectively before migration. - After setup and deployment of the migration’s tools and test environment, you can perform the following steps to begin migrating your OpenSearch target cluster: - -1. Redirect your production traffic from a source cluster to a provisioned OpenSearch target cluster, enabling a comparison of results between the two clusters. All traffic directed to the source cluster is stored for future replay. - -2. Meanwhile, traffic to the target cluster is replayed at an identical rate to ensure a direct comparison between the source cluster and the target. - For more information about OpenSearch migration tools, see the documentation in the [OpenSearch Migration GitHub repository](https://github.com/opensearch-project/opensearch-migrations/tree/capture-and-replay-v0.1.0). \ No newline at end of file