9.1 upgrade docs (orchestrator + cluster)

[shainaraskas]

Description

9.1 needs upgrade docs

We'll need to make sure the upgrade paths are correctly surfaced:

• The only way to upgrade to 9.0 will still be from 8.18 (and not 8.19)
• To upgrade to 9.1, you can be on either 9.0 or 8.19

Admin docs covers orchestrator + cluster upgrade content
Ingest would own the Ingest components
Pages like Overview would have co-ownership

Resources

internal

upgrade paths info: https://support.elastic.dev/knowledge/view/31977c54

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

What release is this request related to?

9.1

Serverless release

Collaboration model

The documentation team

Point of contact.

[shainaraskas]

related: #1608

[eedugon]

In #2296 I'm trying to address the upgrade paths:

Direct link.

Do you think we should add more information from the KB internal link @shainaraskas ? Or even linking to the article? (it's a public article).

The only way to upgrade to 9.0 will still be from 8.18 (and not 8.19)
To upgrade to 9.1, you can be on either 9.0 or 8.19

^^ I think that's addressed.

Ingest would own the Ingest components

I don't think this is applicable to ingest components. For example in Beats and Logstash there's no such restriction in terms of upgrade paths as far as I know (but maybe I'm missing something).

Pages like Overview would have co-ownership

The same PR is also covering the upgrade overview, and other upgrade docs, we can try to refine there.

[shainaraskas]

I think that adding a link to the kb couldn't do any harm. I'd consider it.

otherwise, too much of that linked kb article is not evergreen so we might just want to rely on it to avoid big changes to this page every couple of months. could see something like this being helpful, but your basic "before/after" logic might be enough

[eedugon]

yeah.... maybe something like for extra details and examples of supported upgrade paths, refer to [KB article]... I'll think of it and see if it's really worthy.

[eedugon]

@shainaraskas , should we close this issue? Or do you want us to review some extra pages to be sure?

Take in mind that ingest components do not have any special treatment due to the 8.18 -> 9.0 upgrade path of Elasticsearch.
Ingest components can be upgraded without any restriction, they just need to be compatible with the Elasticsearch version per the support compatibility matrix.

[shainaraskas]

if you think this is done, feel free to close it 👍