Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
From version 28.1
edited by Erik Bakker
on 2025/01/13 09:26
Change comment: There is no comment for this version
To version 13.1
edited by Erik Bakker
on 2023/04/28 08:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R13 Docker - Single Lane
1 +R7 - Docker Single lane
Content
... ... @@ -1,20 +1,15 @@
1 -Service affecting template to use the R13 single lane release.
1 +Non service affecting final template to use the R7 single lane release.
2 +Process: To use the new R7 release of our cloud template we upgrade in one steps, the update is non service affecting.
2 2  
3 -**Process**
4 -To use the new R13 template on your environment, we upgrade the control agent of **all** machines and disk encryption on **cloud** machines. This update is service affecting. The goal of this update is to increase the security of the disks related to your machine by encrypting them and to update the control agent version to 2.21.4.
5 -
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
5 +This update improves the security by disabling SSH access to cloud machines.
9 9  
10 -**Update Steps**
11 -* Use the final template (service affecting)(duration: 10 minutes)
12 -** This step will upgrade the primary machines in the first Availability Zone in your cloudslot
13 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
14 -*** The runtimes on the machines will be restored using the active release in the eMagiz portal
7 +**Updates**
8 +* Improve security by disabling SSH access to cloud machines.
15 15  
10 +**Update Steps**
11 +* Use the final R7 template (non service affecting) (duration: 4 minutes)
16 16  * User actions after applying the final template:
17 -** Check if all runtimes are up via the runtime overview
18 -** Check if all runtimes have been installed according to the active release
19 -** Check if messages pass through the bus by verifying a critical message flow in external systems
20 -
13 +** Check if all runtimes are reachable by Deploy Architecture.
14 +** Check if all images 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.