There is no way currently to add a node to an all-in-one. You could either deploy a duplex setup or a standard setup with one controller, but as Greg has already pointed out that has some availability issues. From: Rai, Ankush <Ankush.Rai@commscope.com> Sent: Friday, November 6, 2020 9:51 PM To: Waines, Greg <Greg.Waines@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] starlingx Standard deployment with one controller Thanks Greg. I have one more question, is there a provision to add the worker node in all-in-one simplex deployment? Our intention to have only one controller node and one or more worker node. Thanks, Ankush From: Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>> Sent: Friday, November 6, 2020 5:58 PM To: Rai, Ankush <Ankush.Rai@commscope.com<mailto:Ankush.Rai@commscope.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] starlingx Standard deployment with one controller Not really ... . I mean you could just configure 1x controller in a standard configuration ... and you could even suppress the alarms related to the second controller missing ... BUT you would not be able to make any post-install configuration changes to the controller that requires the controller to be locked, because the system will not allow you to lock the last controller in a system configuration ( ... suspect it won’t even allow you to force lock it ...). AND you would not be able to apply a ‘reboot-required’ patch or upgrade with a single controller in standard configuration. ... so not really. Greg. From: "Rai, Ankush" <Ankush.Rai@commscope.com<mailto:Ankush.Rai@commscope.com>> Date: Thursday, November 5, 2020 at 10:07 AM To: "starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>" <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: [Starlingx-discuss] starlingx Standard deployment with one controller [Please note this e-mail is from an EXTERNAL e-mail address] Hi, I understand that we should have the high-availability for the controller in the real edge-deployment, but just wanted to check the possibility of having only one controller in “bare metal Standard with Controller Storage” deployment? Is this kind of deployment possible and what all changes we need to have for single controller deployment? Regards, Ankush