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
     on 2025/10/23 08:46
      Change comment:
              There is no comment for this version
          
         
      To version  21.1 
    
    
              edited by Carlijn Kokkeler
        
on 2024/03/25 14:49
     on 2024/03/25 14:49
      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 7Docker - Single Lane1 +R12 Docker - Single Lane 
- Author
-   ... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler 
- Content
-   ... ... @@ -1,15 +1,19 @@ 1 - **Non-service-affecting**finaltemplate to use the**R17**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 7release of our cloud template we upgrade in one step. Thisis a rollingupdate,makingitnon-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 -* 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 +This version contains the ability to clean H2 infra databases from the portal. 9 9 9 +**Updates** 10 +* This upgrade contains the ability to clean H2 infra databases from the portal. 11 +* This upgrade is non-service affecting, as all instances have to be recreated. 12 + 10 10 **Update Steps** 11 -* Use the final R17 template (non-service affecting)(duration: < 5 minutes) 14 +* Use the final R12 template (non-service affecting) (duration: 3 minutes) 15 +* User actions after applying the final template: 16 +** Check if all runtimes are reachable by the runtime dashboard. 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. 12 12 13 -**Remarks** 14 - 15 -Deadline of December 14th, 2025 
 
