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  14.1 
    
    
              edited by Erik Bakker
        
on 2023/08/03 16:16
     on 2023/08/03 16:16
      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 9Docker - DoubleLane1 +R10 Docker - Double lane 
- Content
-   ... ... @@ -1,15 +1,19 @@ 1 - **Non-service-affecting**finaltemplate tousethe**R19**singlelanerelease.1 +Non-service affecting R10 template that unlocks the possibility of running a failover configuration on an MQTT Broker. 2 2 3 3 **Process** 4 - To use the new R19release ofourcloud templatewe upgrade in one step. Thisisa rolling update,makingitnon-service affecting.4 +We upgrade in one step to use the new R10 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. 7 +It adds the possibility of hosting an MQTT broker in a failover setting. 9 9 9 +**Updates** 10 +* Run an MQTT broker in a failover setting 11 + 10 10 **Update Steps** 11 -* Use the final R19 template (non-service affecting)(duration: < 5 minutes) 13 +* Use the final template (non-service affecting) (duration: 10 minutes) 14 +** This step will update your cloud slot configuration to allow an MQTT broker with failover settings. 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. 12 12 13 -**Remarks** 14 - 15 -Deadline of December 14th, 2025 
 
