Changes for page R22 Docker - Double Lane
Last modified by Erik Bakker on 2026/06/29 09:47
From version 35.1
edited by Erik Bakker
on 2026/06/29 09:46
on 2026/06/29 09:46
Change comment:
There is no comment for this version
To version 26.1
edited by Erik Bakker
on 2025/06/30 09:51
on 2025/06/30 09:51
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 22Docker - Double Lane1 +R17 Docker - Double Lane - Content
-
... ... @@ -1,20 +1,17 @@ 1 - {{info}}Thisenvironmenttemplateneedstobeappliedonallenvironmentsof all (your) models before August 29th, 2026{{/info}}1 +**Service affecting** final template to use the R16 double lane release. 2 2 3 -**Non-service affecting** final template to use the **R22** double lane release. This is the only step for your upgrade to the new **R22** template. 4 - 5 5 **Process** 6 - Weupgradeinonestepto usethenew**R22**release ofthe cloud template. Thisstepisnon-service affecting.4 +o use the new R17 template on your environment, we replace all connections to activate the new configuration. This update is service affecting and aims to enable data traffic via our new carwash. 7 7 8 8 **Overview** 9 -* Improve internal monitoring and alerting capabilities 10 -* Improve management of users and permissions 7 +* New connections to a **new** carwash. 11 11 12 12 **Update Steps** 13 -* Use the final **R22**template (non-service affecting)(duration: 10 minutes)14 -** None of theruntimeswillbetouched.15 - ** Authorization servers will perform a rolling update.16 -* User actions after applying the in termediatetemplate:17 -** Check if all runtimes are reachablebythe runtimedashboard18 -** Check if all flows have been installed according to the active release10 +* Use the final template (non service affecting)(duration: < 10 minutes) 11 +** This step will replace all connections. 12 + 13 +* User actions after applying the final template: 14 +** Check if all runtimes are up via the runtime overview or Deploy Architecture 15 +** Check if all runtimes have been installed according to the active release 19 19 ** Check if messages pass through the bus by verifying a critical message flow in external systems 20 20