Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 46.10
edited by Danniar Firdausy
on 2024/09/13 10:51
Change comment: There is no comment for this version
To version 47.1
edited by Danniar Firdausy
on 2024/09/27 09:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Deploy Possibilities
1 +Grouping - Deploy Possibilities
Content
... ... @@ -59,7 +59,7 @@
59 59  == 4. Key takeaways ==
60 60  
61 61  * Grouping is beneficial when external systems go through maintenance or downtime.
62 -* Failover can have the additional benefit of having a fallback scenario while still adhering to the requirement that there can only be one active connection at a time
62 +* Failover can have the additional benefit of having a fallback scenario while still adhering to the requirement that there can only be one active connection at a time.
63 63  * The role naming in both grouping and failover is crucial. The group name needs to match **exactly** to make it work.
64 64  * You can control group and failover steps from the deployment plan.
65 65  * Container inbounds can have a different failover status.