search

Azure / AKS-Edge

Welcome to the Azure Kubernetes Service (AKS) Edge repo.
MIT License
53 stars 34 forks source link

Unable to provision a new AKSEdge Deployment due to network problems #152

Closed andyleadbetter-elekta closed 8 months ago

andyleadbetter-elekta commented 8 months ago

Describe scenario Using

New-AksEdgeConfig -DeploymentType SingleMachineCluster -outFile .\aksedge-config.json

followed by

PS C:\dev\andy-edge> New-AksEdgeDeployment -JsonConfigFilePath .\aksedge-config.json

[11/07/2023 22:01:56] All required host features are installed

[11/07/2023 22:01:56] Attention - Azure Arc properties are specified. These will not be used. The cluster currently needs to be connected in a separate step after deployment via Connect-AksEdgeArc

[11/07/2023 22:01:56] Validating AksEdge network parameters...

[11/07/2023 22:05:19] 1 errors found in the deployment configuration. Fix errors before deployment

[11/07/2023 22:05:19] AksEdge - JSON configuration contains errors

PS C:\dev\andy-edge>

A clear and concise description of what your scenario is.

Question

What is missing in the JSON, and how do I configure the host PC to install a edge simgle machine cluster?

erwinkersten commented 8 months ago

@andyleadbetter-elekta : It appears that you're facing difficulty in automatically detecting a free IP address range in your environment. In situations like this, you can address the issue by modifying the configuration within the "Network" section of you aksedge-config. Please follow these steps:

  1. Add the following line to the "Network" section:
"SkipAddressFreeCheck": true
  1. To ensure that you have a free IP address range specified, set the "Ip4AddressPrefix" as follows:
"Ip4AddressPrefix": "192.168.0.0/24"

These changes should help you resolve the issue you're encountering with IP address range detection

An overview of a example network section for your specific situation appears as follows:

"Network": {
    "InternetDisabled": false,
    "Ip4AddressPrefix": "192.168.0.0/24",
    "SkipAddressFreeCheck": true,
    "SkipDnsCheck": false,
    "NetworkPlugin": "flannel",
    "Proxy": {
      "Http": null,
      "Https": null,
      "No": "localhost,127.0.0.0/8,192.168.0.0/16,172.17.0.0/16,10.42.0.0/16,10.43.0.0/16,10.96.0.0/12,10.244.0.0/16,.svc"
    },
  }
andyleadbetter-elekta commented 8 months ago

Ok, that worked, a bit surprising that the checks also failed to identify this subnet and IP configuration.

rcheeran commented 8 months ago

Thanks @erwinkersten! Love it when the community has answers :)