Add scan for running existing control nodes when choosing primary control node
Summary
Current behaviour in cluster deployment is to choose the first listed control node as the 'primary',
which runs the cluster initialization.
If the first listed node is new to an existing cluster (or is being reinstalled), current behaviour will
cause this node to initialize a new cluster instead of joining the existing cluster.
This PR adds a check for any control nodes currently running the API service, and if so, it will
chose the first of these as the primary control node.
Add scan for running existing control nodes when choosing primary control node
Summary
Current behaviour in cluster deployment is to choose the first listed control node as the 'primary', which runs the cluster initialization.
If the first listed node is new to an existing cluster (or is being reinstalled), current behaviour will cause this node to initialize a new cluster instead of joining the existing cluster.
This PR adds a check for any control nodes currently running the API service, and if so, it will chose the first of these as the primary control node.
Fixes #210