Changes for page R23 Docker - Double Lane
Last modified by Erik Bakker on 2026/07/31 13:52
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 37.1
edited by Erik Bakker
on 2026/07/31 13:52
on 2026/07/31 13:52
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 -R 19Docker - Double Lane1 +R23 Docker - Double Lane - Content
-
... ... @@ -1,15 +1,18 @@ 1 - **Non-service-affecting**finaltemplate tousethe**R19**singlelanerelease.1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}} 2 2 3 +**Non-Service affecting** final template to use the **R23** single lane release. This upgrade is non-service-affecting. 4 + 3 3 **Process** 4 - To use the new R19release ofourcloud templatewe upgrade in one step. Thisisa rolling update,makingitnon-service affecting.6 +We upgrade in one step to use the new **R23** release of the cloud template. This step is non-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. 9 +* Update authorization server to version 1.2.4, providing a bugfix for certificate rotation. 9 9 10 10 **Update Steps** 11 -* Use the final R19 template (non-service affecting)(duration: < 5 minutes) 12 - 13 -**Remarks** 14 - 15 -Deadline of December 14th, 2025 12 +* Use the final **R23** template (non-service affecting) (duration: 10 minutes) 13 +** None of the runtimes will be touched. 14 +** Authorization servers will perform a rolling update. 15 +* User actions after applying the final template: 16 +** Check if all runtimes are reachable by Deploy Architecture. 17 +** Check if all flows have been installed according to the active release. 18 +** Check if messages pass through the model by verifying a critical message flow in external systems.