Changes for page R19 Docker - Double Lane
                  Last modified by Erik Bakker on 2025/10/23 08:47
              
      
      From 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
          
         
      To version  29.1 
    
    
              edited by Erik Bakker
        
on 2025/10/10 09:12
     on 2025/10/10 09:12
      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 0Docker - Doublelane1 +R18 Docker - Double Lane 
- Content
-   ... ... @@ -1,19 +1,19 @@ 1 -Non-service R10template thatunlocks thepossibilityof running a failoverconfigurationon an MQTT Broker.1 +**Non-service-affecting** final template to use the **R18** double lane release. 2 2 3 3 **Process** 4 - We upgrade inonestep touse the new R10release ofthecloud template. This step is non-service4 +To use the new R18 release of our cloud template we upgrade in one step. This step is non-service-affecting. 5 5 6 6 **Overview** 7 - Itaddsthepossibilityofhosting an MQTT broker ina failoversetting.7 +* Update versions of dependencies. 8 8 9 -**Updates** 10 -* Run an MQTT broker in a failover setting 11 - 12 12 **Update Steps** 13 -* Use the final template (non-service affecting) 10minutes)14 - ** This step will update your cloud slot configuration to allow an MQTT broker with failover settings.10 +* Use the final R18 template (non-service affecting)(duration: < 5 minutes) 11 + 15 15 * User actions after applying the final template: 16 -** Check if all runtimes are reachablebyDeploy Architecture.17 -** Check if all flows have been installed according to the active release.18 -** Check if messages pass through the modelby verifying a critical message flow in external systems.13 +** Check if all runtimes are up via the runtime overview or Deploy Architecture 14 +** Check if all runtimes have been installed according to the active release 15 +** Check if messages pass through the bus by verifying a critical message flow in external systems 19 19 17 +**Remarks** 18 + 19 +Deadline of December 14th, 2025 
 
