Skip to Content

Changes for page R19 Docker - Double Lane

Last modified by Erik Bakker on 2025/10/23 08:47
From version 30.1
edited by Erik Bakker
on 2025/10/23 08:47
Change comment: There is no comment for this version
To version 15.1
edited by Erik Bakker
on 2023/09/13 07:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Double Lane
1 +R11 Docker - Double lane
Content
... ... @@ -1,15 +1,24 @@
1 -**Non-service-affecting** final template to use the **R19** single lane release.
1 +Service affecting R11 template that improves stability of AWS EFS mounts in running instances when a reconnect to EFS is triggered.
2 2  
3 3  **Process**
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.
4 +We upgrade in two steps to use the new R11 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
5 5  
6 6  **Overview**
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.
7 +It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
9 9  
9 +**Updates**
10 +* Updated mount configurations of EFS to adhere to provider's standards.
11 +* Ubuntu version update including latest security patches.
12 +* This upgrade is service-affecting, as all instances have to be recreated.
13 +
10 10  **Update Steps**
11 -* Use the final R19 template (non-service affecting)(duration: < 5 minutes)
15 +* Use the intermediate template (non-service affecting) (duration: 10 minutes)
16 +** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
17 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
18 +* Use the final template (non-service affecting) (duration: 10 minutes)
19 +** This step will update your cloud slot configuration to allow an MQTT broker with failover settings.
20 +* User actions after applying the final template:
21 +** Check if all runtimes are reachable by Deploy Architecture.
22 +** Check if all flows have been installed according to the active release.
23 +** Check if messages pass through the model by verifying a critical message flow in external systems.
12 12  
13 -**Remarks**
14 -
15 -Deadline of December 14th, 2025