Changes for page R20 Docker - Single Lane

Last modified by Erik Bakker on 2026/06/29 09:44

From version 16.1
edited by Erik Bakker
on 2023/06/19 14:29
Change comment: There is no comment for this version
To version 41.1
edited by Erik Bakker
on 2026/06/15 09:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R8 Docker - Single lane
1 +R19 Docker - Single Lane
Content
... ... @@ -1,21 +1,16 @@
1 -Service affecting R8 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
2 2  
3 +**Non-Service affecting** final template to use the **R19** single lane release. This upgrade is non-service-affecting.
4 +
3 3  **Process**
4 -We upgrade in one step to use the new R8 release of the cloud template. This step is service affecting.
6 +We upgrade in one step to use the new **R19** release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
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.
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
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 -
15 15  **Update Steps**
16 -* Use the final template (service affecting) (duration: 10 minutes)
17 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
18 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
13 +* Use the final **R19** template (service affecting) (duration: 10 minutes)
19 19  * User actions after applying the final template:
20 20  ** Check if all runtimes are reachable by Deploy Architecture.
21 21  ** Check if all flows have been installed according to the active release.