Changes for page R17 Docker - Single Lane
                  Last modified by Erik Bakker on 2025/10/23 08:46
              
      
      From version  17.1 
    
    
              edited by Erik Bakker
        
on 2023/07/10 15:13
     on 2023/07/10 15:13
      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 (2 modified, 0 added, 0 removed)
Details
- Page properties
- 
      - Title
-   ... ... @@ -1,1 +1,1 @@ 1 -R 8Docker - Singlelane1 +R16 Docker - Single Lane 
- Content
-   ... ... @@ -1,24 +1,19 @@ 1 - ServiceR8template that improvessecurityand allows fortheretrievalof Static IP addressesfrom Deploy Architecture.1 +**Non-service-affecting** final template to use the **R16** single lane release. 2 2 3 3 **Process** 4 - We upgrade inonestep touse the new R8release ofthecloud template. This step is 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 - Itimproves the ease with which Static IP Addresses can be gatheredand distributed by a userwhile at thesame time improvingthesecurity andauto-healing functionality.7 +* Update versions of dependencies. 8 8 9 -**Updates** 10 -* Ability to fetch Static IP Addresses 11 -* New ubuntu version with new security patches. 12 -* Disable IPv6 on startup 13 -* Enable new Out of Memory killer to protect instance becoming unhealthy 14 -* Added new version of the deployment agent, solving a known portainer bug where all containers are replaced instead of one. 15 - 16 16 **Update Steps** 17 -* Use the final template (service affecting) (duration: 10 minutes) 18 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. 19 -** The runtimes on the machines will be restored using the active release in the eMagiz portal. 10 +* Use the final R16 template (non-service affecting)(duration: < 5 minutes) 11 + 20 20 * User actions after applying the final template: 21 -** Check if all runtimes are reachablebyDeploy Architecture.22 -** Check if all flows have been installed according to the active release.23 -** 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 24 24 17 +**Remarks** 18 + 19 +Deadline of December 14th, 2025 
 
