Skip to Content

Changes for page R20 Docker - Single Lane

Last modified by Erik Bakker on 2026/06/29 09:44
From version 37.1
edited by Erik Bakker
on 2026/02/10 10:46
Change comment: There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2026/06/29 09:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R18 Docker - Single Lane
1 +R20 Docker - Single Lane
Content
... ... @@ -1,18 +1,20 @@
1 -**Service affecting** final template to use the **R18** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
2 2  
3 +**Non-Service affecting** final template to use the **R20** single lane release. This upgrade is non-service-affecting.
4 +
3 3  **Process**
4 -We upgrade in one step to use the new **R18** release of the cloud template. This step is service affecting.
6 +We upgrade in one step to use the new **R20** 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 Ubuntu version
9 -* Update Docker version
10 -* Update control agent version
11 -* Update Authorization Server (if applicable)
9 +* Improve internal monitoring and alerting capabilities
10 +* Improve management of users and permissions
12 12  
13 13  **Update Steps**
14 -* Use the final **R18** template (service affecting) (duration: 15 minutes)
13 +* Use the final **R20** template (non-service affecting) (duration: 10 minutes)
14 +** None of the runtimes will be touched.
15 +** Authorization servers will perform a rolling update.
15 15  * User actions after applying the final template:
16 16  ** Check if all runtimes are reachable by Deploy Architecture.
17 17  ** Check if all flows have been installed according to the active release.
18 18  ** Check if messages pass through the model by verifying a critical message flow in external systems.
20 +