Skip to Content

Changes for page R22 Docker - Single Lane

Last modified by Erik Bakker on 2026/10/09 13:11
From version 42.1
edited by Erik Bakker
on 2026/06/16 13:10
Change comment: There is no comment for this version
To version 45.1
edited by Erik Bakker
on 2026/10/09 13:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Single Lane
1 +R22 Docker - Single Lane
Content
... ... @@ -1,20 +1,17 @@
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 November 18th, 2026{{/info}}
2 2  
3 -**Non-Service affecting** final template to use the **R19** single lane release. This upgrade is non-service-affecting.
3 +**Non-Service affecting** final template to use the **R22** single lane release. This upgrade is non-service-affecting.
4 4  
5 5  **Process**
6 -We upgrade in one step to use the new **R19** 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 +* Preparation for updating our databases underneath the authorization server
11 11  
12 12  **Update Steps**
13 -* Use the final **R19** template (service affecting) (duration: 10 minutes)
12 +* 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  * User actions after applying the final template:
17 17  ** Check if all runtimes are reachable by Deploy Architecture.
18 18  ** Check if all flows have been installed according to the active release.
19 19  ** Check if messages pass through the model by verifying a critical message flow in external systems.
20 -