Skip to Content

Changes for page R20 Docker - Single Lane

Last modified by Erik Bakker on 2026/06/29 09:44
From version 13.1
edited by Erik Bakker
on 2023/04/28 08:34
Change comment: There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2026/06/29 09:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R7 - Docker Single lane
1 +R20 Docker - Single Lane
Content
... ... @@ -1,15 +1,20 @@
1 -Non service affecting final template to use the R7 single lane release.
2 -Process: To use the new R7 release of our cloud template we upgrade in one steps, the update is non service affecting.
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
3 3  
4 -**Overview**
5 -This update improves the security by disabling SSH access to cloud machines.
3 +**Non-Service affecting** final template to use the **R20** single lane release. This upgrade is non-service-affecting.
6 6  
7 -**Updates**
8 -* Improve security by disabling SSH access to cloud machines.
5 +**Process**
6 +We upgrade in one step to use the new **R20** release of the cloud template. This step is non-service affecting.
9 9  
8 +**Overview**
9 +* Improve internal monitoring and alerting capabilities
10 +* Improve management of users and permissions
11 +
10 10  **Update Steps**
11 -* Use the final R7 template (non service affecting) (duration: 4 minutes)
13 +* Use the final **R20** template (non-service affecting) (duration: 10 minutes)
14 +** None of the runtimes will be touched.
15 +** Authorization servers will perform a rolling update.
12 12  * User actions after applying the final template:
13 13  ** Check if all runtimes are reachable by Deploy Architecture.
14 -** Check if all images have been installed according to the active release.
15 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
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.
20 +