Skip to Content

Changes for page R20 Docker - Single Lane

Last modified by Erik Bakker on 2026/06/29 09:44
From version 40.1
edited by Erik Bakker
on 2026/06/15 09:20
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 -R19 Docker - Single Lane
1 +R20 Docker - Single Lane
Content
... ... @@ -1,16 +1,18 @@
1 -{{info}}This deadline needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
2 2  
3 -**Non-Service affecting** final template to use the **R19** single lane release. This upgrade is non-service-affecting.
3 +**Non-Service affecting** final template to use the **R20** single lane release. This upgrade is non-service-affecting.
4 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.
6 +We upgrade in one step to use the new **R20** release of the cloud template. This step is 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.
9 +* Improve internal monitoring and alerting capabilities
10 +* Improve management of users and permissions
11 11  
12 12  **Update Steps**
13 -* Use the final **R19** template (service affecting) (duration: 10 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.
14 14  * User actions after applying the final template:
15 15  ** Check if all runtimes are reachable by Deploy Architecture.
16 16  ** Check if all flows have been installed according to the active release.