Changes for page R19 Docker - Single Lane
Last modified by Erik Bakker on 2026/03/22 21:42
From version 36.1
edited by Erik Bakker
on 2025/10/23 08:46
on 2025/10/23 08:46
Change comment:
There is no comment for this version
To version 40.1
edited by Erik Bakker
on 2026/03/22 21:42
on 2026/03/22 21:42
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R1 7Docker - Single Lane1 +R19 Docker - Single Lane - Content
-
... ... @@ -1,15 +1,17 @@ 1 -** Non-service-affecting** final template to use the **R17** 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 R17release ofourcloud templatewe upgrade in one step. Thisisa rolling update,makingit non-service affecting.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 -* Non-service-affecting template to upgrade to the latest version of the authorization server. Applying this template only affects customers running on DSH Event Streaming. 8 -* Update the version of authorization server as preparation for the API-Gateway MAM migration. 7 +* Remove need for recycling underlying instance when adding containers to machine 9 9 10 10 **Update Steps** 11 -* Use the final R17 template (non-service affecting)(duration: < 5 minutes) 10 +* Use the final **R19** template (service affecting) (duration: 15 minutes) 11 +* User actions after applying the final template: 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. 12 12 13 13 **Remarks** 14 - 15 -Deadline of December 14th, 2025 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.