Skip to Content

Changes for page R18 Docker - Single Lane

Last modified by Erik Bakker on 2026/02/10 10:59
From version 27.1
edited by CarlijnKokkeler
on 2024/04/23 11:18
Change comment: There is no comment for this version
To version 39.1
edited by Erik Bakker
on 2026/02/10 10:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R13 Docker - Single Lane
1 +R18 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,21 @@
1 -Non-service affecting template to use the R13 single lane release.
1 +**Service affecting** final template to use the **R18** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
2 2  
3 3  **Process**
4 -To use the new R13 template on your environment, we upgrade the agent of external machines. This update is not service affecting.
4 +We upgrade in one step to use the new **R18** release of the cloud template. This step is service affecting.
5 5  
6 6  **Overview**
7 -* Non service-affecting template that updates the on-premise machine agents.
8 -* The cloud-environment for this template does not contain any changes compared to the R12 template.
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 9  
10 -**Updates**
11 -* This upgrade updates the machine agent to version 2.18.4.
12 -* This upgrade is non-service affecting.
13 -
14 14  **Update Steps**
15 -* Use the final R13 template (non-service affecting) (duration: approx. 1 minute per machine).
14 +* Use the final **R18** template (service affecting) (duration: 15 minutes)
16 16  * User actions after applying the final template:
17 -** Check if all on-premise runtimes are reachable by the runtime overview.
18 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
16 +** Check if all runtimes are reachable by Deploy Architecture.
17 +** Check if all flows have been installed according to the active release.
18 +** Check if messages pass through the model by verifying a critical message flow in external systems.
19 19  
20 +**Remarks**
21 +In case your model is running fully on-premise you need to upgrade your agents by upgrading to the next available template (R3).