Skip to Content

Changes for page R20 Docker - Single Lane

Last modified by Erik Bakker on 2026/06/29 09:44
From version 19.1
edited by CarlijnKokkeler
on 2023/11/21 11:47
Change comment: There is no comment for this version
To version 42.1
edited by Erik Bakker
on 2026/06/16 13:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R11 Docker - Single Lane
1 +R19 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,18 @@
1 -Service affecting template that introduces faster machine boot up and improved auto-healing.
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
2 2  
3 +**Non-Service affecting** final template to use the **R19** single lane release. This upgrade is non-service-affecting.
4 +
3 3  **Process**
4 -We upgrade in one step to use the new R11 release of the cloud template. This step is service affecting.
6 +We upgrade in one step to use the new **R19** release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
7 -This version contains performance improvements for auto-healing and machine boot up time.
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
8 8  
9 -**Updates**
10 -* Ubuntu version update including latest security patches.
11 -* This upgrade is service-affecting, as all instances have to be recreated.
12 -
13 13  **Update Steps**
14 -* Use the final template (service affecting) (duration: 10 minutes)
15 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
16 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
13 +* Use the final **R19** template (service affecting) (duration: 10 minutes)
14 +** None of the runtimes will be touched.
15 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
17 17  * User actions after applying the final template:
18 18  ** Check if all runtimes are reachable by Deploy Architecture.
19 19  ** Check if all flows have been installed according to the active release.