Skip to Content

Changes for page R19 Docker - Double Lane

Last modified by Erik Bakker on 2025/10/23 08:47
From version 29.1
edited by Erik Bakker
on 2025/10/10 09:12
Change comment: There is no comment for this version
To version 13.1
edited by Erik Bakker
on 2023/07/10 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R18 Docker - Double Lane
1 +R9 Docker - Double lane
Content
... ... @@ -1,19 +1,28 @@
1 -**Non-service-affecting** final template to use the **R18** double lane release.
1 +Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
2 2  
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.
4 +We upgrade in two steps to use the new R9 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
5 5  
6 6  **Overview**
7 -* Update versions of dependencies.
7 +It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same time improving the security and auto-healing functionality.
8 8  
9 -**Update Steps**
10 -* Use the final R18 template (non-service affecting)(duration: < 5 minutes)
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 +* Improved Cloud instance status check and auto repair
15 +* Added new version of the deployment agent, solving a known portainer bug where all containers are replaced instead of one.
11 11  
17 +**Update Steps**
18 +* Use the intermediate template (non-service affecting) (duration: 10 minutes)
19 +** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
20 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
21 +* Use the final template (service affecting) (duration: 10 minutes)
22 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
23 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
12 12  * User actions after applying the final template:
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
25 +** Check if all runtimes are reachable by Deploy Architecture.
26 +** Check if all flows have been installed according to the active release.
27 +** Check if messages pass through the model by verifying a critical message flow in external systems.
16 16  
17 -**Remarks**
18 -
19 -Deadline of December 14th, 2025