Skip to Content

Changes for page R18 Docker - Single Lane

Last modified by Erik Bakker on 2026/02/10 10:59
From version 3.1
edited by eMagiz
on 2022/10/04 08:18
Change comment: There is no comment for this version
To version 38.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 -R5 - Docker All lanes
1 +R18 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,12 +1,21 @@
1 -Service affecting template to use the R5 Docker lane release (Single and Double Lane). In order to update to this cloud template there is only a single step required.
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 -This update changes the Carwash (See https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Fundamentals/fundamental-emagiz-cloud-inner-workings). Note that using this new version of the Carwash involves a DNS change, and thus relies on clients honoring TTLs of DNS records. This update also changes the IP adresses used in the infrastructure. For more details, please contact Expert Services. Furthermore, TLSv1.0 is disabled in this update. Verify legacy software can handle atleast TLSv1.1 before updating.
3 +**Process**
4 +We upgrade in one step to use the new **R18** release of the cloud template. This step is service affecting.
4 4  
5 -Updates
6 -• Changed ciphers and cipher suites
7 -• Disabled TLS V1.0 support and enable TLS V1.3 support.
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)
8 8  
9 -Technical notes
10 -• Supported Ciphers in OpenSSL Format: ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:DHE-RSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS@SECLEVEL=1
11 -• Supported TLS Versions: TLSv1.1, TLSv1.2 and TLSv1.3
13 +**Update Steps**
14 +* Use the final **R18** template (service affecting) (duration: 15 minutes)
15 +* User actions after applying the final template:
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.
12 12  
20 +**Remarks**
21 +In case your model running fully on-premise you need to upgrade your agents by upgrading to the next available template (R3).