Changes for page R19 Docker - Double Lane
                  Last modified by Erik Bakker on 2025/10/23 08:47
              
      
      From version  9.1 
    
    
              edited by Erik Bakker
        
on 2023/04/28 08:36
     on 2023/04/28 08:36
      Change comment:
              There is no comment for this version
          
         
      To version  27.1 
    
    
              edited by Erik Bakker
        
on 2025/10/09 10:11
     on 2025/10/09 10:11
      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 -R8 Docker - Double lane1 +R18 Docker - Double Lane 
- Content
-   ... ... @@ -1,16 +1,16 @@ 1 -Non service affecting final template to use the R8 double lane release. 2 -Process: To use the new R8 release of our cloud template we upgrade in one steps, the update is non service affecting. 1 +**Non-service-affecting** final template to use the *R18* double lane release. 3 3 3 +**Process** 4 +To use the new R18 release of our cloud template we upgrade in one step. This step is non-service-affecting. 5 + 4 4 **Overview** 5 - Thisupdateimproves the security and enhancesthe auto-healingfunctionalityon our 3rdgenerationruntimes.7 +* Update versions of dependencies. 6 6 7 -**Updates** 8 -* Improve Locking mitigation in the Artemis server (autohealing). 9 -* Improve security by disabling SSH access to cloud machines. 10 - 11 11 **Update Steps** 12 -* Use the final R8 template (non service affecting) (duration: 4 minutes) 10 +* Use the final R*18* template (non-service affecting)(duration: < 5 minutes) 11 + 13 13 * User actions after applying the final template: 14 -** Check if all runtimes are reachable by Deploy Architecture. 15 -** Check if all images have been installed according to the active release. 16 -** 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 16 + 
 
