Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
From version 17.1
edited by Erik Bakker
on 2023/07/10 15:13
Change comment: There is no comment for this version
To version 26.1
edited by Carlijn Kokkeler
on 2024/04/23 11:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R8 Docker - Single lane
1 +R13 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,24 +1,19 @@
1 -Service affecting R8 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
1 +Non-service affecting template to use the R13 single lane release.
2 2  
3 3  **Process**
4 -We upgrade in one step to use the new R8 release of the cloud template. This step is service affecting.
4 +To use the new R13 template on your environment, we upgrade the agent of external machines. This update is not 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.
7 +* Non service-affecting template that updates the on-premise machine agents.
8 +* The cloud-environment for this template does not contain any changes compared to the R12 template.
8 8  
9 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.
11 +* This upgrade updates the machine agent to version 2.18.4.
12 +* This upgrade is non-service affecting.
15 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.
15 +* Use the final R13 template (non-service affecting) (duration: approx. 1 minute per machine)
20 20  * User actions after applying the final template:
21 -** Check if all runtimes are reachable by Deploy Architecture.
22 -** Check if all flows have been installed according to the active release.
23 -** Check if messages pass through the model by verifying a critical message flow in external systems.
17 +** Check if all on-premise runtimes are reachable by the runtime overview.
18 +** Check if messages pass through the bus by verifying a critical message flow in external systems.
24 24