Skip to Content

Changes for page R21 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/16 11:56
From version 21.1
edited by CarlijnKokkeler
on 2024/04/23 11:18
Change comment: There is no comment for this version
To version 33.1
edited by Erik Bakker
on 2026/06/15 09:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R15 Docker - Double Lane
1 +R21 Docker - Double Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,21 @@
1 -Non-service affecting final template to use the R15 double lane release.
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 **R21** double lane release. This is the only step for your upgrade to the new **R21** template.
4 +
3 3  **Process**
4 -To use the new R15 template on your environment, we upgrade the agent of external machines. This update is not 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 -* Non service-affecting template that updates the on-premise machine agents.
8 -* The cloud-environment for this template does not contain any changes compared to the R14 template.
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
9 9  
10 -**Updates**
11 -* This upgrade updates the machine agent to version 2.18.4.
12 -* This upgrade is non-service affecting.
13 -
14 14  **Update Steps**
15 -* Use the final R15 template (non-service affecting) (duration: approx. 1 minute per machine).
16 -* User actions after applying the final template:
17 -** Check if all on-premise runtimes are reachable by the runtime overview.
18 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
13 +* Use the final **R19** template (non-service affecting) (duration: 10 minutes)
14 +** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot.
15 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
16 +** The runtimes on the machines will be restored using the active release in the eMagiz portal
17 +* User actions after applying the intermediate template:
18 +** Check if all ".02" runtimes are reachable by the runtime dashboard
19 +** Check if all flows have been installed according to the active release
20 +** Check if messages pass through the bus by verifying a critical message flow in external systems
19 19