We have a situation where a project is creating a service mesh, and dynamically adding new service mesh nodes, while a previously added service mesh node is offline.

This RFE is a request to change the behavior of the AAP 2.4 installer to issue a warning that a previously added service mesh node is offline/unreachable at the moment, instead of the installer erroring out completely.

In this case, we are testing AAP 2.4 on VMs.  The controller is a VM running bare-metal (non containerized).   The execution nodes are running as containers in VMs.

We would love an early workaround if possible.