Skip to Content

Changes for page R22 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/29 09:47
From version 34.1
edited by Erik Bakker
on 2026/06/16 11:56
Change comment: There is no comment for this version
To version 36.1
edited by Erik Bakker
on 2026/06/29 09:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R21 Docker - Double Lane
1 +R22 Docker - Double Lane
Content
... ... @@ -1,21 +1,20 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
2 2  
3 -**Non-service affecting** final template to use the **R21** double lane release. This is the only step for your upgrade to the new **R21** template.
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.
4 4  
5 5  **Process**
6 -We upgrade in one step to use the new **R21** release of the cloud template. This step is non-service affecting.
6 +We upgrade in one step to use the new **R22** release of the cloud template. This step is non-service affecting.
7 7  
8 8  **Overview**
9 -* Upgrade cloud environment to prepare for IP address migration.
10 -* Update authorization server to enable future certificate rotations.
9 +* Improve internal monitoring and alerting capabilities
10 +* Improve management of users and permissions
11 11  
12 12  **Update Steps**
13 -* Use the final **R21** template (non-service affecting) (duration: 10 minutes)
13 +* Use the final **R22** template (non-service affecting) (duration: 10 minutes)
14 14  ** None of the runtimes will be touched.
15 -** The network drive containing the Artemis queue store and your Elastic IPs will remain.
16 16  ** Authorization servers will perform a rolling update.
17 -* User actions after applying the intermediate template:
18 -** Check if all runtimes are reachable by the runtime dashboard
19 -** Check if all flows have been installed according to the active release
20 -** Check if messages pass through the bus by verifying a critical message flow in external systems
16 +* User actions after applying the final template:
17 +** Check if all runtimes are reachable by Deploy Architecture.
18 +** Check if all flows have been installed according to the active release.
19 +** Check if messages pass through the model by verifying a critical message flow in external systems.
21 21