Skip to Content

Changes for page R20 Docker - Single Lane

Last modified by Erik Bakker on 2026/06/29 09:44
From version 29.1
edited by Erik Bakker
on 2025/01/20 07:40
Change comment: There is no comment for this version
To version 40.1
edited by Erik Bakker
on 2026/06/15 09:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R13 Docker - Single Lane
1 +R19 Docker - Single Lane
Content
... ... @@ -1,21 +1,18 @@
1 -Service affecting template to use the R13 single lane release.
1 +{{info}}This deadline needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
2 2  
3 +**Non-Service affecting** final template to use the **R19** single lane release. This upgrade is non-service-affecting.
4 +
3 3  **Process**
4 -To use the new R13 template on your environment, we upgrade the control agent of **all** machines and disk encryption on **cloud** machines. This update is service affecting. The goal of this update is to increase the security of the disks related to your machine by encrypting them and to update the control agent version to 2.21.4.
6 +We upgrade in one step to use the new **R19** release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
9 9  
10 10  **Update Steps**
11 -* Use the final template (service affecting)(duration: 10 minutes)
12 -** This step will upgrade the primary machines in the first Availability Zone in your cloudslot
13 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
15 -*** The runtimes on the machines will be restored using the active release in the eMagiz portal
16 -
13 +* Use the final **R19** template (service affecting) (duration: 10 minutes)
17 17  * User actions after applying the final template:
18 -** Check if all runtimes are up via the runtime overview
19 -** Check if all runtimes have been installed according to the active release
20 -** Check if messages pass through the bus by verifying a critical message flow in external systems
15 +** Check if all runtimes are reachable by Deploy Architecture.
16 +** Check if all flows have been installed according to the active release.
17 +** Check if messages pass through the model by verifying a critical message flow in external systems.
21 21