Skip to Content

Changes for page R17 Docker - Single Lane

Last modified by Erik Bakker on 2025/10/23 08:46
From version 36.1
edited by Erik Bakker
on 2025/10/23 08:46
Change comment: There is no comment for this version
To version 12.2
edited by Erik Bakker
on 2023/03/03 11:29
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R17 Docker - Single Lane
1 +R6 - Docker Single lane
Content
... ... @@ -1,15 +1,17 @@
1 -**Non-service-affecting** final template to use the **R17** single lane release.
1 +Non service affecting final template to use the R6 double lane release.
2 +Process: To use the new R6 release of our cloud template we upgrade in one steps, the update is non service affecting.
2 2  
3 -**Process**
4 -To use the new R17 release of our cloud template we upgrade in one step. This is a rolling update, making it non-service affecting.
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.
5 +This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes.
9 9  
10 -**Update Steps**
11 -* Use the final R17 template (non-service affecting)(duration: < 5 minutes)
7 +**Updates**
8 +* Cloud Port check: When the software does not expose the right ports, it will be restarted
9 +* Coordnation failed: When the runtimes failes to startup due to a corrupted startup order, the runtime will restart freshly to remove the corrupted state.
10 +* Clean store: The functionality to clean a store is added for generation 3 runtimes. See [[this link>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.expert-emagiz-cloud-management-clean-store||target="blank"]]
12 12  
13 -**Remarks**
14 -
15 -Deadline of December 14th, 2025
12 +**Update Steps**
13 +* Use the final R6 template (non service affecting) (duration: 4 minutes)
14 +* User actions after applying the final template:
15 +** Check if all runtimes are reachable by the runtime dashboard.
16 +** Check if all flows have been installed according to the active release.
17 +** Check if messages pass through the bus by verifying a critical message flow in external systems.