Changes for page R20 Docker - Single Lane

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-R20 Docker - Single Lane
	1	+R16 Docker - Single Lane

Content

...	...	@@ -1,20 +1,19 @@
1		-{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
	1	+**Non-service-affecting** final template to use the **R16** single lane release.
2	2
3		-**Non-Service affecting** final template to use the **R20** single lane release. This upgrade is non-service-affecting.
4		-
5	5	**Process**
6		-We upgrade in one step to use the new **R20** release of the cloud template. This step is non-service affecting.
	4	+To use the new R16 release of our cloud template we upgrade in one step. This step is non-service-affecting.
7	7
8	8	**Overview**
9		-* Improve internal monitoring and alerting capabilities
10		-* Improve management of users and permissions
	7	+* Update versions of dependencies.
11	11
12	12	**Update Steps**
13		-* Use the final **R20** template (non-service affecting) (duration: 10 minutes)
14		-** None of the runtimes will be touched.
15		-** Authorization servers will perform a rolling update.
	10	+* Use the final R16 template (non-service affecting)(duration: < 5 minutes)
	11	+
16	16	* User actions after applying the final template:
17		-** Check if all runtimes are reachable by Deploy Architecture.
18		-** Check if all flows have been installed according to the active release.
19		-** Check if messages pass through the model by verifying a critical message flow in external systems.
	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
20	20
	17	+**Remarks**
	18	+
	19	+Deadline of December 14th, 2025