Skip to Content

Changes for page R12 Docker - Single Lane

Last modified by Carlijn Kokkeler on 2024/03/29 13:47
From version 21.1
edited by Carlijn Kokkeler
on 2024/03/25 14:49
Change comment: There is no comment for this version
To version 3.1
edited by eMagiz
on 2022/10/04 08:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R12 Docker - Single Lane
1 +R5 - Docker All lanes
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.eMagiz
Content
... ... @@ -1,19 +1,12 @@
1 -Non-service affecting template to use the R12 single lane release.
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.
2 2  
3 -**Process**
4 - To use the new R12 release of our cloud template we upgrade in one step. The update is non-service affecting.
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.
5 5  
6 -**Overview**
7 -This version contains the ability to clean H2 infra databases from the portal.
5 +Updates
6 +• Changed ciphers and cipher suites
7 +• Disabled TLS V1.0 support and enable TLS V1.3 support.
8 8  
9 -**Updates**
10 -* This upgrade contains the ability to clean H2 infra databases from the portal.
11 -* This upgrade is non-service affecting, as all instances have to be recreated.
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
12 12  
13 -**Update Steps**
14 -* Use the final R12 template (non-service affecting) (duration: 3 minutes)
15 -* User actions after applying the final template:
16 -** Check if all runtimes are reachable by the runtime dashboard.
17 -** Check if all flows have been installed according to the active release.
18 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
19 -