From 8acfe40ffb575b76864316c0eb52f9dff81af3ae Mon Sep 17 00:00:00 2001 From: Julien Mailleret <8582351+jmlrt@users.noreply.github.com> Date: Tue, 28 Jul 2020 18:27:10 +0200 Subject: [PATCH] [doc] update doc links (#758) --- elasticsearch/README.md | 7 +++---- elasticsearch/examples/migration/README.md | 4 ++-- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/elasticsearch/README.md b/elasticsearch/README.md index 5fabf48bf..5cfab8b38 100644 --- a/elasticsearch/README.md +++ b/elasticsearch/README.md @@ -347,9 +347,8 @@ automated testing pipeline. 2. Add any required secrets or credentials into an Elasticsearch keystore following the [how to use the keystore][] guide. 3. Configure the [snapshot repository][] as you normally would. -4. To automate snapshots you can use a tool like [curator][]. In the future -there are plans to have Elasticsearch manage automated snapshots with -[Snapshot Lifecycle Management][]. +4. To automate snapshots you can use [Snapshot Lifecycle Management][] or a tool +like [curator][]. ### How to configure templates post-deployment? @@ -445,7 +444,7 @@ about our development and testing process. [secret]: https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets [securityContext]: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ [service types]: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types -[snapshot lifecycle management]: https://github.com/elastic/elasticsearch/issues/38461 +[snapshot lifecycle management]: https://www.elastic.co/guide/en/elasticsearch/reference/7.x/snapshot-lifecycle-management.html [snapshot plugin]: https://www.elastic.co/guide/en/elasticsearch/plugins/7.x/repository.html [snapshot repository]: https://www.elastic.co/guide/en/elasticsearch/reference/7.x/modules-snapshots.html [supported configurations]: https://github.com/elastic/helm-charts/tree/7.x/README.md#supported-configurations diff --git a/elasticsearch/examples/migration/README.md b/elasticsearch/examples/migration/README.md index 59e07e21d..fc417f1ee 100644 --- a/elasticsearch/examples/migration/README.md +++ b/elasticsearch/examples/migration/README.md @@ -163,5 +163,5 @@ working correctly you can cleanup leftover resources from your old cluster. [data.yml]: https://github.com/elastic/helm-charts/blob/7.x/elasticsearch/examples/migration/data.yml [helm/charts]: https://github.com/helm/charts/tree/master/stable/elasticsearch [master.yml]: https://github.com/elastic/helm-charts/blob/7.x/elasticsearch/examples/migration/master.yml -[restoring to a different cluster guide]: https://www.elastic.co/guide/en/elasticsearch/reference/6.6/modules-snapshots.html#_restoring_to_a_different_cluster -[rolling upgrades guide]: https://www.elastic.co/guide/en/elasticsearch/reference/6.6/rolling-upgrades.html +[restoring to a different cluster guide]: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/modules-snapshots.html#_restoring_to_a_different_cluster +[rolling upgrades guide]: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/rolling-upgrades.html