Changes for page R17 Docker - Single Lane
                  Last modified by Erik Bakker on 2025/10/23 08:46
              
      
      From version  35.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
          
         
      To version  23.1 
    
    
              edited by Carlijn Kokkeler
        
on 2024/03/29 13:47
     on 2024/03/29 13:47
      Change comment:
              There is no comment for this version
          
         Summary
- 
          Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
- 
      - Title
-   ... ... @@ -1,1 +1,1 @@ 1 -R1 6Docker - Single Lane1 +R12 Docker - Single Lane 
- Author
-   ... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler 
- Content
-   ... ... @@ -1,19 +1,19 @@ 1 - **Non-service-affecting**finaltemplate to use the**R16**single lane release.1 +Non-service affecting template to use the R12 single lane release. 2 2 3 3 **Process** 4 -To use the new R1 6release of our cloud template we upgrade in one step. Thisstepis non-service-affecting.4 + To use the new R12 release of our cloud template we upgrade in one step. The update is non-service affecting. 5 5 6 6 **Overview** 7 - *Updateversions ofdependencies.7 +This version contains the ability to clean H2 infra databases from the portal. 8 8 9 -**Update Steps** 10 -* Use the final R16 template (non-service affecting)(duration: < 5 minutes) 9 +**Updates** 10 +* This upgrade contains the ability to clean H2 infra databases from the portal. 11 +* This upgrade is non-service affecting. 11 11 13 +**Update Steps** 14 +* Use the final R12 template (non-service affecting) (duration: 3 minutes) 12 12 * User actions after applying the final template: 13 -** Check if all runtimes are up via the runtime overviewor Deploy Architecture14 -** Check if all runtimes have been installed according to the active release15 -** Check if messages pass through the bus by verifying a critical message flow in external systems 16 +** Check if all runtimes are reachable by the runtime overview. 17 +** Check if all flows have been installed according to the active release. 18 +** Check if messages pass through the bus by verifying a critical message flow in external systems. 16 16 17 -**Remarks** 18 - 19 -Deadline of December 14th, 2025 
 
