With the advent of release 7, DS will now be easier to scale (expansion and contraction). Some customers will make use of this feature.
However, from an AM perspective if connection strings to enable affinity for the User, App and CTS stores are configured then AM will not make any use of these new DS nodes because the connection strings are both static and not hot-swappable.
The AM documentation should highlight this and also highlight how best to overcome:
In an FBC and K8S world perhaps the best approach would be to track DS instance expansion/contraction and on completion trigger a new commit to the FBC Git Config, along with a new pipeline to roll out a new set of AM pods with the new configuration to take into account the additional/removed DS instances.
In a non FBC or K8S world then the appropriate Amster commands to add/remove instances along with the requirement to restart AM containers should be documented.
Suspect this behaviour will catch out lots of customers.
Longer term perhaps the DS SDK should handle discovery and AM relied on the SDK.