Changes for page R17 Docker - Single Lane
Last modified by Erik Bakker on 2025/10/23 08:46
From version 33.1
edited by Erik Bakker
on 2025/10/09 10:12
on 2025/10/09 10:12
Change comment:
There is no comment for this version
To version 13.1
edited by Erik Bakker
on 2023/04/28 08:34
on 2023/04/28 08:34
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 16Docker-SingleLane1 +R7 - Docker Single lane - Content
-
... ... @@ -1,19 +1,15 @@ 1 -**Non-service-affecting** final template to use the *R16* double 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 R16 release of our cloud template we upgrade in one step. This step is non-service-affecting. 5 - 6 6 **Overview** 7 - *Update versions ofdependencies.5 +This update improves the security by disabling SSH access to cloud machines. 8 8 9 -**Update Steps**10 -* Use the final R*18* template(non-serviceaffecting)(duration:<5minutes)7 +**Updates** 8 +* Improve security by disabling SSH access to cloud machines. 11 11 10 +**Update Steps** 11 +* Use the final R7 template (non service affecting) (duration: 4 minutes) 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 16 - 17 -**Remarks** 18 - 19 -Deadline of December 14th, 2025 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.