You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md
+18-22Lines changed: 18 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
navigation_title: "Upgrade on {{ece}}"
3
3
---
4
4
5
-
# Upgrade on {{ece}} (ECE)
5
+
# Upgrade your deployment on {{ece}} (ECE)
6
6
7
7
Similar to {{ech}}, a single click in the {{ecloud}} console can upgrade a deployment running on ECE to a newer version, add more processing capacity, change plugins, and enable or disable high availability, all at the same time. During the upgrade process, {{es}}, {{kib}}, and all of your deployment components are upgraded simultaneously.
8
8
@@ -12,37 +12,33 @@ Once you're prepared to upgrade, do the following:
12
12
13
13
1. Ensure your current ECE and Docker or Podman versions are [compatible](https://www.elastic.co/support/matrix/#elastic-cloud-enterprise) with the {{stack}} version you're upgrading to. For example, if you're upgrading to 9.0.0, the minimum required version is ECE 3.0. If you don’t have a compatible version installed, [upgrade your orchestrator](/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md).
14
14
2. Download the most recent [stack pack](/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md#ece_most_recent_elastic_stack_packs) for the version you’re upgrading to, then [add the stack pack](/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md#ece-manage-elastic-stack-add) to your installation using the Cloud UI.
15
-
3.[Configure a snapshot repository](/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md) to enable snapshots and back up your data.
15
+
3.If not configured already, [assign a snapshots repository](/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md) to your deployment to enable snapshots and back up your data. Although this is optional, we recommend this step.
16
16
17
-
## Perform the upgrade
17
+
## Perform the upgrade
18
18
19
-
1.[Log in to the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
20
-
2. On the Deployments page, select your deployment.
21
-
22
-
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
23
-
24
-
To upgrade a deployment:
19
+
1.[Log in to the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
20
+
2. On the **Deployments** page, select your deployment.
21
+
22
+
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
25
23
26
24
1. In the **Deployment version** section, click **Upgrade**.
27
25
2. Select the version you're upgrading to. For example, `9.0.0`.
28
-
3. Click **Upgrad**e, then **Confirm upgrade**. The new configuration takes a few minutes to create.
26
+
3. Click **Upgrade**, then **Confirm upgrade**. The new configuration takes a few minutes to create.
29
27
30
-
::::{note}
31
-
If any incompatibilities are detected when you attempt to upgrade, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. After resolving the issues, return to the **Deployments** page and restart the upgrade.
32
-
::::
28
+
::::{note}
29
+
If any incompatibilities are detected when you attempt to upgrade, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. After resolving the issues, return to the **Deployments** page and restart the upgrade.
30
+
::::
33
31
34
-
Security realm settings
35
-
: During the upgrade process, you are prompted to update the security realm settings if your user settings include a `xpack.security.authc.realms` value.
32
+
**Security realm settings**
36
33
37
-
If the security realms are configured in `user_settings`, you’ll be prompted to modify the settings:
34
+
During the upgrade process, you are prompted to update the security realm settings if your user settings include a `xpack.security.authc.realms` value.
38
35
39
-
1. On the **Update security realm settings** window, edit the settings.
40
-
2. Click **Update settings**. If the security realm settings are located in `user_settings_override`, contact support to help you upgrade.
36
+
If the security realms are configured in `user_settings`, you’ll be prompted to modify the settings:
41
37
42
-
## Next steps [next-steps-ece]
38
+
1. On the **Update security realm settings** window, edit the settings.
39
+
2. Click **Update settings**. If the security realm settings are located in `user_settings_override`, contact support to help you upgrade.
43
40
44
-
Once you've successfully upgraded on {{ece}}, do the following:
*[Upgrade your ingest components](/deploy-manage/upgrade/ingest-components.md)
43
+
Once you've successfully upgraded your deployment, [upgrade your ingest components](/deploy-manage/upgrade/ingest-components.md), such as {{ls}}, {{agents}}, or {{beats}}.
Copy file name to clipboardExpand all lines: deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,8 @@ Log in to your {{ecloud}} environment:
18
18
19
19
1. Log in to the [{{ech}} console](https://cloud.elastic.co/login).
20
20
2. Select your deployment on the home page in the {{ech}} card or go to the **Deployments** page.
21
-
22
-
Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
21
+
22
+
Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
23
23
24
24
25
25
To upgrade a deployment:
@@ -45,9 +45,6 @@ Security realm settings
45
45
1. On the **Update security realm settings** window, edit the settings.
46
46
2. Click **Update settings**. If the security realm settings are located in `user_settings_override`, contact support to help you upgrade.
47
47
48
-
### Next steps[next-steps-ech]
48
+
### Next steps
49
49
50
-
Once you've successfully upgraded on {{ech}}, do the following:
*[Upgrade your ingest components](/deploy-manage/upgrade/ingest-components.md)
50
+
Once you've successfully upgraded on {{ech}}, [upgrade your ingest components](/deploy-manage/upgrade/ingest-components.md), such as {{ls}}, {{agents}}, or {{beats}}.
Copy file name to clipboardExpand all lines: deploy-manage/upgrade/deployment-or-cluster/upgrade-on-eck.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
navigation_title: "Upgrade on {{eck}}"
3
3
---
4
4
5
-
# Upgrade on {{eck}} (ECK)
5
+
# Upgrade your deployment on {{eck}} (ECK)
6
6
7
7
The ECK orchestrator can safely perform upgrades to newer versions of the {{stack}}.
8
8
@@ -138,3 +138,6 @@ ECK will ensure that {{stack}} components are upgraded in the correct order. Upg
138
138
139
139
Check out [Nodes orchestration](/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration.md) for more information on how ECK manages upgrades and how to tune its behavior.
140
140
141
+
## Next steps
142
+
143
+
Once you've successfully upgraded your deployment, [upgrade your ingest components](/deploy-manage/upgrade/ingest-components.md), such as {{ls}}, {{agents}}, or {{beats}}.
0 commit comments