Azure Stack HCI + Kubernetes Scenario - SetAKSHCIConfig Error

[kennycwk1]

Hi there, im trying out the Azure Stack HCI + Kubernetes scenario and coming across error while setting AKSHCIConfig

In the - Setup AKS Region

While running below command -

Invoke-Command -ComputerName $servers[0] -Credential $Credentials -Authentication Credssp -ScriptBlock { $vnet = New-AksHciNetworkSetting -Name $using:vNetName -vSwitchName $using:vSwitchName -vippoolstart $using:vippoolstart -vippoolend $using:vippoolend

Set-AksHciConfig -vnet $vnet -workingDir c:\clusterstorage\$using:VolumeName\Images -imageDir c:\clusterstorage\$using:VolumeName\Images -cloudConfigLocation c:\clusterstorage\$using:VolumeName\Config -ClusterRoleName "$($using:ClusterName)_AKS" -controlPlaneVmSize 'default' # Get-AksHciVmSize

    Set-AksHciConfig -vnet $vnet -imageDir c:\clusterstorage\$using:VolumeName\Images -cloudConfigLocation c:\clusterstorage\$using:VolumeName\Config -ClusterRoleName "$($using:ClusterName)_AKS" -controlPlaneVmSize 'default' # Get-AksHciVmSize
}

Getting error result

For multi-node deployments you must set -workingDir parameter to a network share or CSV path. At line:1 char:1

• Invoke-Command -ComputerName $servers[0] -Credential $Credentials -Au ...

• 
  + CategoryInfo          : OperationStopped: (For multi-node ...re or CSV path.:String) [
  ], RuntimeException
  + FullyQualifiedErrorId : For multi-node deployments you must set -workingDir parameter
  to a network share or CSV path.

Is there a change in requirements? Do i need to change the script to network share or CSV path?

[kennycwk1]

-->(removed #) Set-AksHciConfig -vnet $vnet -workingDir c:\clusterstorage\$using:VolumeName\Images -imageDir c:\clusterstorage\$using:VolumeName\Images -cloudConfigLocation c:\clusterstorage\$using:VolumeName\Config -ClusterRoleName "$($using:ClusterName)_AKS" -controlPlaneVmSize 'default' # Get-AksHciVmSize --> #Set-AksHciConfig -vnet $vnet -imageDir c:\clusterstorage\$using:VolumeName\Images -cloudConfigLocation c:\clusterstorage\$using:VolumeName\Config -ClusterRoleName "$($using:ClusterName)_AKS" -controlPlaneVmSize 'default' # Get-AksHciVmSize }

hi i solved it by removing the hash at the workingDir command, managed to run the region.

However running the install command (install-akshci) still gave me some error. i gave up using powershell after that, Managed to setup AKS using windows Admin center