Document retired node replacement in ES

[zackkrida]

Description

This PR documents the procedure to follow for replacing a retired Elasticsearch node in our custom, self-managed Elasticsearch cluster.

Testing Instructions

Review the plan and make sure the instructions are clear.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (just catalog/generate-docs for catalog
  PRs) or the media properties generator (just catalog/generate-docs media-props
  for the catalog or just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[github-actions]

Full-stack documentation: https://docs.openverse.org/_preview/4326

Please note that GitHub pages takes a little time to deploy newly pushed code, if the links above don't work or you see old versions, wait 5 minutes and try again.

You can check the GitHub pages deployment action list to see the current status of the deployments.

Changed files 🔄:

• https://docs.openverse.org/_preview/4326/meta/maintenance/elasticsearch_cluster.html

[AetherUnbound]

Thanks for adding this documentation! It all makes sense, just a few small notes.

[zackkrida]

Drafting this PR while I:

• Make adjustments to the specific deployment process
• Reconsider it's existence; this might be better suited as an ansible playbook in the infra repository

[AetherUnbound]

@zackkrida Since the node replacement is complete, do you think we can undraft this? Even if we eventually move this to a playbook, it'd be good to have the documentation in the meantime just in case, IMO!

[zackkrida]

@AetherUnbound it's updated, undrafted, and ready for review 😄

[sarayourfriend]

LGTM 👍

@zackkrida do you plan to create an issue to convert this to a playbook (with prompts as we discussed)? I think that's a good idea, and a fine interim solution for this until we can fix how we deploy Elasticsearch.

[zackkrida]

@sarayourfriend issue here https://github.com/WordPress/openverse-infrastructure/issues/911