Skip to Content

Changes for page R17 Docker - Single Lane

Last modified by Erik Bakker on 2025/10/23 08:46
From version 35.1
edited by Erik Bakker
on 2025/10/10 09:12
Change comment: There is no comment for this version
To version 27.1
edited by Carlijn Kokkeler
on 2024/04/23 11:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R16 Docker - Single Lane
1 +R13 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,19 +1,19 @@
1 -**Non-service-affecting** final template to use the **R16** single lane release.
1 +Non-service affecting template to use the R13 single lane release.
2 2  
3 3  **Process**
4 -To use the new R16 release of our cloud template we upgrade in one step. This step is non-service-affecting.
4 +To use the new R13 template on your environment, we upgrade the agent of external machines. This update is not service affecting.
5 5  
6 6  **Overview**
7 -* Update versions of dependencies.
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 R12 template.
8 8  
9 -**Update Steps**
10 -* Use the final R16 template (non-service affecting)(duration: < 5 minutes)
10 +**Updates**
11 +* This upgrade updates the machine agent to version 2.18.4.
12 +* This upgrade is non-service affecting.
11 11  
14 +**Update Steps**
15 +* Use the final R13 template (non-service affecting) (duration: approx. 1 minute per machine).
12 12  * User actions after applying the final template:
13 -** Check if all runtimes are up via the runtime overview or Deploy Architecture
14 -** Check if all runtimes 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
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.
16 16  
17 -**Remarks**
18 -
19 -Deadline of December 14th, 2025