Skip to content

Commit 38da47f

Browse files
committed
work still in progress
1 parent c7bbf54 commit 38da47f

File tree

1 file changed

+19
-11
lines changed

1 file changed

+19
-11
lines changed

deploy-manage/upgrade/deployment-or-cluster/upgrade-717.md

Lines changed: 19 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -54,38 +54,43 @@ For the 7.17.x → 9.x upgrade path, the main planning outcome is a set of requi
5454

5555
Before the initial upgrade to 8.19.x, ensure that all ingest components ({{beats}}, {{agent}}, {{ls}}, APM) are on version 7.17.x.
5656

57-
Before the final upgrade to {{version.stack}}, upgrade all ingest components to 8.19.x.
57+
After upgrading the cluster to 8.19.x and before proceeding to {{version.stack}}, upgrade all ingest components to 8.19.x.
5858

59-
Refer to [upgrade your ingest components](/deploy-manage/upgrade/ingest-components.md) for more details.
59+
Refer to [Upgrade your ingest components](/deploy-manage/upgrade/ingest-components.md) for detailed upgrade instructions.
6060

6161
* **Client libraries:**
6262

6363
If your use case relies on [{{es}} client libraries](/reference/elasticsearch-clients/index.md), make sure to include them in your plan. Typically, libraries are upgraded to match the {{es}} version after each of the upgrades.
6464

6565
* **Orchestration platforms:**
6666

67-
* {applies_to}`eck:` If you are running an ECK version older than 3.x you need to upgrade ECK before the final upgrade to 9.x. This can be done at the beginning before the initial upgrade or between them.
68-
* {applies_to}`ece:` If you are running an ECE version older than 4.x you need to upgrade your ECE platform before the final upgrade to 9.x. This can be done at the beginning before the initial upgrade or between them.
67+
* {applies_to}`eck:` If you are running an ECK version earlier than 3.x, you need to upgrade ECK before the final upgrade to 9.x.
6968

70-
Finally, it is strongly recommended to [test the full upgrade process in a non-production environment](/deploy-manage/upgrade/plan-upgrade.md#test-in-a-non-production-environment) before applying it to production.
69+
This can be done either at the beginning, before the initial upgrade, or between the two upgrade phases.
70+
71+
* {applies_to}`ece:` If you are running an ECE version earlier than 4.x, you need to upgrade your ECE platform before the final upgrade to 9.x.
72+
73+
This can be done either at the beginning, before the initial upgrade, or between the two upgrade phases.
74+
75+
Finally, we strongly recommend [testing the full upgrade process in a non-production environment](/deploy-manage/upgrade/plan-upgrade.md#test-in-a-non-production-environment) before applying it to production.
7176

7277
## Upgrade Step 1: 7.17.x → 8.19.x
7378

74-
This step assumes that you want to perform the deployment upgrade as part of your [upgrade plan](#planning), and all your ingest components and client libraries are compatible with 8.19.x.
79+
This step covers upgrading your deployment from 7.17.x to 8.19.x, following the [planning phase](#planning) and assuming that all ingest components and client libraries are compatible with 8.19.x.
7580

7681
### 8.19 upgrade preparations
7782

78-
The most important preparation steps for a major upgrade are:
83+
The most important [upgrade preparation steps](/deploy-manage/upgrade/prepare-to-upgrade.md) for a major upgrade are:
84+
7985
* Breaking changes and known issues analysis.
8086
* Run the upgrade assistant in {{kib}} to detect and resolve issues.
8187
* Take a snapshot of your deployment before the upgrade.
8288

8389
{{ech}} and {{ece}} platforms facilitates the upgrade preparations by automatically creating snapshots before the upgrade and by checking the upgrade assistant for critical issues before proceeding.
8490

85-
Also take in mind the following points:
86-
* If you are using dedicated monitoring clusters or remote clusters, upgrade them first.
91+
(upgrade order, you can only upgrade...??)
8792

88-
* Take a cluster snapshot before starting the ugprade
93+
https://www.elastic.co/guide/en/elastic-stack/8.19/upgrading-elastic-stack.html#prepare-to-upgrade
8994

9095
Upgrade 8.19: https://www.elastic.co/guide/en/elasticsearch/reference/8.19/setup-upgrade.html
9196

@@ -136,7 +141,10 @@ On Elastic Cloud Enterprise, you need to [configure a snapshot repository](/depl
136141
:::
137142

138143
:::{applies-item} self:
139-
Follow all preparations per [](/deploy-manage/upgrade/prepare-to-upgrade.md)
144+
145+
Follow the [Prepare to upgrade from 7.x](https://www.elastic.co/guide/en/elastic-stack/8.19/upgrading-elastic-stack.html#prepare-to-upgrade) steps before starting the upgrade.
146+
147+
Also https://www.elastic.co/guide/en/elasticsearch/reference/8.19/setup-upgrade.html ?
140148
:::
141149

142150
::::

0 commit comments

Comments
 (0)