Changes for page R17 Docker - Single Lane
                  Last modified by Erik Bakker on 2025/10/23 08:46
              
      
      From version  20.1 
    
    
              edited by Carlijn Kokkeler
        
on 2024/03/25 11:56
     on 2024/03/25 11:56
      Change comment:
              There is no comment for this version
          
         
      To 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
          
         Summary
- 
          Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
- 
      - Title
-   ... ... @@ -1,1 +1,1 @@ 1 -R1 2Docker - Single Lane1 +R16 Docker - Single Lane 
- Author
-   ... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker 
- Content
-   ... ... @@ -1,20 +1,19 @@ 1 -Non-service 2single lane release.1 +**Non-service-affecting** final template to use the **R16** single lane release. 2 2 3 3 **Process** 4 - 2release of our cloud template we upgrade in one step. Theupdate is non-service4 +To use the new R16 release of our cloud template we upgrade in one step. This step is non-service-affecting. 5 5 6 6 **Overview** 7 - Thisversioncontainsthe ability tocleanH2 infradatabases from theportal.7 +* Update versions of dependencies. 8 8 9 -**Updates** 10 -* Ubuntu version update including latest security patches. 11 -* This upgrade is non-service affecting, as all instances have to be recreated. 12 -* This upgrade contains the ability to clean H2 infra databases from the portal. 13 - 14 14 **Update Steps** 15 -* Use the final R12 template (non-service affecting) (duration: 3 minutes) 10 +* Use the final R16 template (non-service affecting)(duration: < 5 minutes) 11 + 16 16 * User actions after applying the final template: 17 -** Check if all runtimes are reachablebythe runtimedashboard.18 -** Check if all flows have been installed according to the active release.19 -** Check if messages pass through the bus by 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 20 20 17 +**Remarks** 18 + 19 +Deadline of December 14th, 2025 
 
