Skip to Content

Changes for page R24 Docker - Double Lane

Last modified by Erik Bakker on 2026/10/09 13:13
From version 35.1
edited by Erik Bakker
on 2026/06/29 09:46
Change comment: There is no comment for this version
To version 38.1
edited by Erik Bakker
on 2026/10/09 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R22 Docker - Double Lane
1 +R24 Docker - Double Lane
Content
... ... @@ -1,20 +1,17 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before November 18th, 2026{{/info}}
2 2  
3 -**Non-service affecting** final template to use the **R22** double lane release. This is the only step for your upgrade to the new **R22** template.
3 +**Non-service affecting** final template to use the **R24** double lane release. This is the only step for your upgrade to the new R24 template.
4 4  
5 5  **Process**
6 -We upgrade in one step to use the new **R22** release of the cloud template. This step is non-service affecting.
6 +To use the new **R24** release of our cloud template we upgrade in one step, which is non-service affecting
7 7  
8 8  **Overview**
9 -* Improve internal monitoring and alerting capabilities
10 -* Improve management of users and permissions
9 +* Preparation for updating our databases underneath the authorization server
11 11  
12 12  **Update Steps**
13 -* Use the final **R22** template (non-service affecting) (duration: 10 minutes)
12 +* Use this final R24 template (non-service affecting) (duration: 10 minutes)
14 14  ** None of the runtimes will be touched.
15 -** Authorization servers will perform a rolling update.
16 -* User actions after applying the intermediate template:
17 -** Check if all runtimes are reachable by the runtime dashboard
18 -** Check if all flows have been installed according to the active release
19 -** Check if messages pass through the bus by verifying a critical message flow in external systems
20 -
14 +* User actions after applying the final template:
15 +** Check if all runtimes are reachable by Deploy Architecture.
16 +** Check if all flows have been installed according to the active release.
17 +** Check if messages pass through the model by verifying a critical message flow in external systems.