Remove steps for migrating cluster, targeted for later release (#5012)

Signed-off-by: Brian Presley <bjpres@amazon.com>
Co-authored-by: Brian Presley <bjpres@amazon.com>
This commit is contained in:
Brian Presley 2023-09-13 13:39:16 -05:00 committed by GitHub
parent 58789e75d2
commit 6046c0524b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 6 deletions

View File

@ -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 migrations 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).