Skip to Content

Changes for page R22 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/29 09:47
From version 36.1
edited by Erik Bakker
on 2026/06/29 09: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 -R22 Docker - Double Lane
1 +R11 Docker - Double lane
Content
... ... @@ -1,18 +1,22 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
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 -**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 -
5 5  **Process**
6 -We upgrade in one step to use the new **R22** release of the cloud template. This step is 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.
7 7  
8 8  **Overview**
9 -* Improve internal monitoring and alerting capabilities
10 -* Improve management of users and permissions
7 +It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
11 11  
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 +
12 12  **Update Steps**
13 -* Use the final **R22** template (non-service affecting) (duration: 10 minutes)
14 -** None of the runtimes will be touched.
15 -** Authorization servers will perform a rolling update.
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.
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.