Skip to Content

Changes for page R19 Docker - Single Lane

Last modified by Erik Bakker on 2026/03/22 21:42
From version 31.1
edited by Erik Bakker
on 2025/06/30 09:49
Change comment: There is no comment for this version
To version 40.1
edited by Erik Bakker
on 2026/03/22 21:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R15 Docker - Single Lane
1 +R19 Docker - Single Lane
Content
... ... @@ -1,16 +1,17 @@
1 -**Service affecting** template to use the R15 single lane release.
1 +**Service affecting** final template to use the **R19** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
2 2  
3 3  **Process**
4 -To use the new R15 template on your environment, we replace all connections to activate the new configuration. This update is service affecting and aims to enable data traffic via our new carwash.
4 +We upgrade in one step to use the new **R19** release of the cloud template. This step is service affecting.
5 5  
6 6  **Overview**
7 -* New connections to a **new** carwash.
7 +* Remove need for recycling underlying instance when adding containers to machine
8 8  
9 9  **Update Steps**
10 -* Use the final template (service affecting)(duration: < 10 minutes)
11 -** This step will replace all connections.
12 -
10 +* Use the final **R19** template (service affecting) (duration: 15 minutes)
13 13  * User actions after applying the final template:
14 -** Check if all runtimes are up via the runtime overview
15 -** Check if all runtimes have been installed according to the active release
16 -** Check if messages pass through the model by verifying a critical message flow in external systems
12 +** Check if all runtimes are reachable by Deploy Architecture.
13 +** Check if all flows have been installed according to the active release.
14 +** Check if messages pass through the model by verifying a critical message flow in external systems.
15 +
16 +**Remarks**
17 +Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.