Changes for page R20 Docker - Single Lane

Last modified by Erik Bakker on 2026/06/29 09:44

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 20.1
edited by CarlijnKokkeler
on 2024/03/25 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Single Lane
1 +R12 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,20 +1,20 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
1 +Non-service affecting template to use the R12 single lane release.
2 2  
3 -**Non-Service affecting** final template to use the **R19** single lane release. This upgrade is non-service-affecting.
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.
4 + To use the new R12 release of our cloud template we upgrade in one step. The update 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.
7 +This version contains the ability to clean H2 infra databases from the portal.
11 11  
9 +**Updates**
10 +* Ubuntu version update including latest security patches.
11 +* This upgrade is non-service affecting, as all instances have to be recreated.
12 +* This upgrade contains the ability to clean H2 infra databases from the portal.
13 +
12 12  **Update Steps**
13 -* Use the final **R19** template (service affecting) (duration: 10 minutes)
14 -** None of the runtimes will be touched.
15 -** The network drive containing the Artemis queue store and your Elastic IPs will remain.
15 +* Use the final R12 template (non-service affecting) (duration: 3 minutes)
16 16  * User actions after applying the final template:
17 -** Check if all runtimes are reachable by Deploy Architecture.
17 +** Check if all runtimes are reachable by the runtime dashboard.
18 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.
19 +** Check if messages pass through the bus by verifying a critical message flow in external systems.
20 20