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: adoc/SAP-Edge-Upgrade.adoc
+71-61Lines changed: 71 additions & 61 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,15 @@
2
2
# tag::intro[]
3
3
== Upgrade guidance
4
4
5
-
When upgrading your SAP edge application related clusters, SUSE advices to follow the order of upgrading Rancher first, then Kubernetes and afterwards the OS.
6
-
At https://www.suse.com/support/kb/doc/?id=000020061 you can find some information that will help you to prepare the upgrade.
5
+
When upgrading your SAP edge application clusters, SUSE advises upgrading Rancher first, followed by Kubernetes,
6
+
and finally the operating system. For helpful preparation guidelines, refer to
If you skipped some versions of {eic}, it might be the case that you will need to take intermidiate steps before you can upgrade to the desired version.
33
-
In this case, you will need to repeat the steps to upgrade {eic} until you have reached your desired version.
33
+
If you have skipped multiple versions of {eic}, you might need to perform intermediate upgrades before installing the desired version.
34
+
In this case, repeat the upgrade steps for {eic} until you reach your target version.
34
35
35
36
# end::eic[]
36
37
@@ -41,73 +42,73 @@ In this case, you will need to repeat the steps to upgrade {eic} until you have
41
42
++++
42
43
=== Upgrading {rke}
43
44
44
-
In this chapter we will describe how to upgrade {rke}.
45
-
46
-
IMPORTANT: It is highly recommended to upgrade one minor version after another. Furthermore you should always upgrade to the highest patch level before upgrading the minor version.
45
+
In this chapter, we describe how to upgrade {rke}.
47
46
47
+
IMPORTANT: It is highly recommended sequentially through each minor version.
48
+
Additionally, always upgrade to the latest patch level of your current version before proceeding to the next minor version.
48
49
49
50
==== Upgrading {rke} using {rancher}
50
51
51
-
IMPORTANT: This is the prefered way to upgrade all {rke} clusters managed by {rancher}.
52
+
IMPORTANT: This is the preferred way to upgrade all {rke} clusters managed by {rancher}.
52
53
53
-
When you deployed your {rke} cluster using {rancher}, you can also upgrade the cluster using {rancher}.
54
-
Therefore enter your *Cluster Management* view in {rancher}.
54
+
If you deployed your {rke} cluster using {rancher}, you can also upgrade it through the same interface.
55
+
To begin, navigate to the *Cluster Management* view.
Depending on the way you installed {rke}, the upgrade is performed differently.
126
-
For more information about the manual upgrade please refer to https://docs.rke2.io/upgrades/manual_upgrade.
126
+
The upgrade method depends on how you originally installed {rke}.
127
+
For details on manual upgrades, refer to https://docs.rke2.io/upgrades/manual_upgrade.
127
128
128
-
IMPORTANT: Don't use another method for upgrading than you used to install.
129
-
If you installed {rke} using the RPM, you should not try to upgrade using the installation script.
129
+
IMPORTANT: You must upgrade using the same method used for installation.
130
+
For example, if you installed {rke} via RPM, do not attempt to upgrade using the installation script.
130
131
131
-
In this guide we'll give you an example how to upgrade using the installation script.
132
+
In this guide, we demonstrate how to upgrade using the installation script.
132
133
133
-
To upgrade {rke} using the installation script, connect to your {rke} node and run the command below. Make sure to replace the version
134
-
with your desired target version.
134
+
To proceed, connect to your {rke} node and run the command below.
135
+
Ensure you replace the version placeholder with your desired target version.
135
136
136
137
[source, bash]
137
138
----
@@ -155,14 +156,14 @@ To restart the service on a worker node, run:
155
156
sudo systemctl restart rke2-agent
156
157
----
157
158
158
-
After the service was restarted, you can uncordon your node, so it can be used for scheduling again:
159
+
When the service has restarted, uncordon the node to resume scheduling:
159
160
160
161
[source, bash]
161
162
----
162
163
kubectl uncordon <node-name>
163
164
----
164
165
165
-
These steps need to be repeated for every machine of the cluster.
166
+
Repeat these steps for every machine of the cluster.
166
167
167
168
++++
168
169
<?pdfpagebreak?>
@@ -177,9 +178,10 @@ These steps need to be repeated for every machine of the cluster.
177
178
++++
178
179
=== Upgrading {rancher}
179
180
180
-
IMPORTANT: We strongly recommend taking a backup before upgrading your {rancher} instance. Please refer to https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher for further information.
181
+
IMPORTANT: We strongly recommend backing up your {rancher} instance before upgrading. For instructions, refer to the Rancher Backup and Restore Guide:
WARNING: Make sure to verify your {harvester} version is supported with your coupled {rancher} instance. You can check this at https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/harvester-v1-5-x/ under *Harvester & Rancher Support Matrix*.
224
+
WARNING: Ensure your {harvester} version is supported and compatible with your {rancher} instance.
225
+
Verify this in the *Harvester & Rancher Support Matrix* at https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/harvester-v1-5-x/.
221
226
222
-
Before upgrading {harvester}, it is highly recommended to use the pre-check script available at https://github.com/harvester/upgrade-helpers/tree/main/pre-check/v1.x.
223
-
This will make sure that your cluster is in a healthy state and ready to be upgrade. If the check finds any issues, please make sure to fix the issue before running an upgrade.
224
-
It is not necessary to run the script on all nodes - just one is enough.
227
+
Before upgrading {harvester}, we highly recommend running the pre-check script available at
This script ensures that your cluster is in a healthy state and ready to be upgraded.
230
+
If any issues are found, resolve them before proceeding.
231
+
It is not necessary to run the script on all nodes, you only need to run it on a single node.
225
232
226
-
Besides running the check script, we highly recommend to check the official upgrade documentation at https://docs.harvesterhci.io/v1.5/upgrade/index and in particular the sections that refer the upgrade from your current version to the target version.
233
+
In addition to running the pre-check script, review the official upgrade documentation at
234
+
https://docs.harvesterhci.io/v1.5/upgrade/index, specifically the sections covering the
235
+
upgrade path from your current version to your target version.
227
236
228
-
The upgrade itself can be easily triggered from the {harvester} UI, once an upgrade is available.
229
-
If there is an upgrade availabe, the UI will show an *Upgrade* button in the upper right corner of the Dashboard, as shown below:
237
+
You can trigger the upgrade directly from the {harvester} UI. When an upgrade is available, an *Upgrade* button will appear
238
+
in the upper right corner of the Dashboard, as shown below:
After selecting the target version, click on *Upgrade* again, to start the upgrade process.
246
+
After selecting the target version, click *Upgrade* again to start the upgrade process.
238
247
239
248
240
249
# end::harvester[]
@@ -243,28 +252,29 @@ After selecting the target version, click on *Upgrade* again, to start the upgra
243
252
++++
244
253
<?pdfpagebreak?>
245
254
++++
246
-
=== Upgrading the OS
247
-
248
-
Depending on the operating system used, the commands and procedures for the upgrade differs.
249
-
In this guide we'll describe how to upgrade {slem}, as it's the operating system that we already used to explain how to set up your landscapes.
255
+
=== Upgrading the operating system
250
256
251
-
NOTE: If you want to familiarize with {slem} and the concept of transactional updates, we recommend to read https://documentation.suse.com/sle-micro/{slem_version}/html/Micro-transactional-updates/transactional-updates.html .
257
+
Upgrade procedures and commands differ depending on the operating system used.
258
+
In this guide, we focus on upgrading {slem}, as this is the operating system used in our landscape setup examples.
252
259
260
+
NOTE: To familiarize yourself with {slem} and the concept of transactional updates, we recommend reading
0 commit comments