Skip to Content

Changes for page R21 Docker - Single Lane

Last modified by Erik Bakker on 2026/07/31 13:51
From version 44.1
edited by Erik Bakker
on 2026/07/31 13:51
Change comment: There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2023/09/13 07:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R21 Docker - Single Lane
1 +R9 Docker - Single 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 R9 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 **R21** single lane release. This upgrade is non-service-affecting.
4 -
5 5  **Process**
6 -We upgrade in one step to use the new **R21** release of the cloud template. This step is non-service affecting.
4 +We upgrade in one step to use the new R9 release of the cloud template. This step is service affecting.
7 7  
8 8  **Overview**
9 -* Update authorization server to version 1.2.4, providing a bugfix for certificate rotation.
7 +It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
10 10  
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 +
11 11  **Update Steps**
12 -* Use the final **R21** template (non-service affecting) (duration: 10 minutes)
13 -** None of the runtimes will be touched.
14 -** Authorization servers will perform a rolling update.
15 +* Use the final template (service affecting) (duration: 10 minutes)
16 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
17 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
15 15  * User actions after applying the final template:
16 16  ** Check if all runtimes are reachable by Deploy Architecture.
17 17  ** Check if all flows have been installed according to the active release.
18 18  ** Check if messages pass through the model by verifying a critical message flow in external systems.
22 +