Changes for page R19 Docker - Double Lane
Last modified by Erik Bakker on 2025/10/23 08:47
From version 30.1
edited by Erik Bakker
on 2025/10/23 08:47
on 2025/10/23 08:47
Change comment:
There is no comment for this version
To version 21.1
edited by CarlijnKokkeler
on 2024/04/23 11:18
on 2024/04/23 11:18
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R1 9Docker - Double Lane1 +R15 Docker - Double Lane - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,15 +1,19 @@ 1 - **Non-service-affecting**final template to use the**R19**single lane release.1 +Non-service affecting final template to use the R15 double lane release. 2 2 3 3 **Process** 4 -To use the new R1 9release ofourcloud template we upgradein onestep.This isa rollingupdate,makingitnon-service affecting.4 +To use the new R15 template on your environment, we upgrade the agent of external machines. This update is not service affecting. 5 5 6 6 **Overview** 7 -* Non -service-affecting template toupgrade to the latestversion oftheauthorizationserver. Applying thistemplate only affects customers running on DSH EventStreaming.8 -* Update theversionofauthorizationserveras preparationfortheAPI-Gateway MAMmigration.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 9 10 +**Updates** 11 +* This upgrade updates the machine agent to version 2.18.4. 12 +* This upgrade is non-service affecting. 13 + 10 10 **Update Steps** 11 -* Use the final R19 template (non-service affecting)(duration: < 5 minutes) 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. 12 12 13 -**Remarks** 14 - 15 -Deadline of December 14th, 2025