Skip to Content

Changes for page R23 Docker - Double Lane

Last modified by Erik Bakker on 2026/07/31 13:52
From version 37.1
edited by Erik Bakker
on 2026/07/31 13:52
Change comment: There is no comment for this version
To version 29.1
edited by Erik Bakker
on 2025/10/10 09:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R23 Docker - Double Lane
1 +R18 Docker - Double Lane
Content
... ... @@ -1,18 +1,19 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
1 +**Non-service-affecting** final template to use the **R18** double lane release.
2 2  
3 -**Non-Service affecting** final template to use the **R23** single lane release. This upgrade is non-service-affecting.
4 -
5 5  **Process**
6 -We upgrade in one step to use the new **R23** release of the cloud template. This step is non-service affecting.
4 +To use the new R18 release of our cloud template we upgrade in one step. This step is non-service-affecting.
7 7  
8 8  **Overview**
9 -* Update authorization server to version 1.2.4, providing a bugfix for certificate rotation.
7 +* Update versions of dependencies.
10 10  
11 11  **Update Steps**
12 -* Use the final **R23** template (non-service affecting) (duration: 10 minutes)
13 -** None of the runtimes will be touched.
14 -** Authorization servers will perform a rolling update.
10 +* Use the final R18 template (non-service affecting)(duration: < 5 minutes)
11 +
15 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.
13 +** Check if all runtimes are up via the runtime overview or Deploy Architecture
14 +** Check if all runtimes have been installed according to the active release
15 +** Check if messages pass through the bus by verifying a critical message flow in external systems
16 +
17 +**Remarks**
18 +
19 +Deadline of December 14th, 2025