-
Notifications
You must be signed in to change notification settings - Fork 702
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emphasize the importance of having snapshot #8051
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,6 +8,8 @@ endif::[] | |
[id="{p}-{page_id}"] | ||
= Create automated snapshots | ||
|
||
NOTE: Snapshots are important to ensure that your Elasticsearch indices can be recovered in the event of an accidental deletion, or to migrate data across clusters. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we have this note as a header of the "Run Elasticsearch on ECK" section here. I'm asking because my feeling is that if someone is looking at the snapshot documentation then it may mean that this person is already aware that it's an important topic (or maybe because it's too late 🙃 ) |
||
|
||
To set up automated snapshots for Elasticsearch on Kubernetes you have to: | ||
|
||
. Register the snapshot repository with the Elasticsearch API. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's up to you to decide, but here's another suggestion that's a little more direct and concise.