Skip to Content

Changes for page R13 Docker - Double Lane

Last modified by Carlijn Kokkeler on 2023/11/21 11:51
From version 15.1
edited by Erik Bakker
on 2023/09/13 07:27
Change comment: There is no comment for this version
To version 13.1
edited by Erik Bakker
on 2023/07/10 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R11 Docker - Double lane
1 +R9 Docker - Double lane
Content
... ... @@ -1,22 +1,26 @@
1 -Service affecting R11 template that improves stability of AWS EFS mounts in running instances when a reconnect to EFS is triggered.
1 +Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
2 2  
3 3  **Process**
4 -We upgrade in two steps to use the new R11 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
4 +We upgrade in two steps to use the new R9 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
5 5  
6 6  **Overview**
7 -It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
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.
8 8  
9 9  **Updates**
10 -* Updated mount configurations of EFS to adhere to provider's standards.
11 -* Ubuntu version update including latest security patches.
12 -* This upgrade is service-affecting, as all instances have to be recreated.
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 +* Improved Cloud instance status check and auto repair
15 +* Added new version of the deployment agent, solving a known portainer bug where all containers are replaced instead of one.
13 13  
14 14  **Update Steps**
15 15  * Use the intermediate template (non-service affecting) (duration: 10 minutes)
16 16  ** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
17 17  ** The network drive containing the Artemis queue store and your Elastic IPs will remain.
18 -* Use the final template (non-service affecting) (duration: 10 minutes)
19 -** This step will update your cloud slot configuration to allow an MQTT broker with failover settings.
21 +* Use the final template (service affecting) (duration: 10 minutes)
22 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
23 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
20 20  * User actions after applying the final template:
21 21  ** Check if all runtimes are reachable by Deploy Architecture.
22 22  ** Check if all flows have been installed according to the active release.