Skip to Content

Changes for page R21 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/16 11:56
From version 33.1
edited by Erik Bakker
on 2026/06/15 09:37
Change comment: There is no comment for this version
To version 30.1
edited by Erik Bakker
on 2025/10/23 08: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 +R19 Docker - Double Lane
Content
... ... @@ -1,21 +1,15 @@
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** final template to use the **R19** single lane release.
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.
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 R19 release of our cloud template we upgrade in one step. This is a rolling update, making it 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 +* Non-service-affecting template to upgrade to the latest version of the authorization server. Applying this template only affects customers running on DSH Event Streaming.
8 +* Update the version of authorization server as preparation for the API-Gateway MAM migration.
11 11  
12 12  **Update Steps**
13 -* Use the final **R19** template (non-service affecting) (duration: 10 minutes)
14 -** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot.
15 -** The network drive containing the Artemis queue store and your Elastic IPs will remain.
16 -** The runtimes on the machines will be restored using the active release in the eMagiz portal
17 -* User actions after applying the intermediate template:
18 -** Check if all ".02" 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
11 +* Use the final R19 template (non-service affecting)(duration: < 5 minutes)
21 21  
13 +**Remarks**
14 +
15 +Deadline of December 14th, 2025