[Docs] Provide best practices for the safest way of upgrading the Elastic Stack

Open
#537 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start with the linked high-level Elastic Stack upgrade overview and the upgrade discussion referenced in the issue. Define the safest practices for larger deployments and product-specific guidance, then verify the documentation covers upgrade order and links each product's guidance.

Written by the indexing model from the issue text.

Description

enhancement help wanted

Last week we discussed our upgrade documentation and ways we can improve the upgrade experience; for larger deployments, the proper order becomes important.

While we provide this high level overview for the order of the products, we should also include best practices around the safest way to upgrade the stack, as well as specific guidance for each product.

Regarding product specific guidance, I will link those to this issue once they are opened.

Dominant language
Java
Stars
105
Forks
249
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/stack-docs

All issues in elastic/stack-docs

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.