You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure IoT Layered Network Management Preview is one of the Azure IoT Operations Preview components. However, it can be deployed individually to the top network layer for supporting the Azure IoT Operations in the lower layer. In the top level of your network layers (usually level 4 of the ISA-95 network architecture), the cluster and Layered Network Management service have direct internet access. Once the setup is completed, the Layered Network Management service is ready for receiving network traffic from the child layer and forwards it to Azure Arc.
19
+
Azure IoT Layered Network Management Preview is a component to support Azure IoT Operations Preview. However, it needs to be deployed individually to the top network layer for supporting the Azure IoT Operations in the lower layer. In the top level of your network layers (usually level 4 of the ISA-95 network architecture), the cluster and Layered Network Management service have direct internet access. Once the setup is completed, the Layered Network Management service is ready for receiving network traffic from the child layer and forwards it to Azure Arc.
20
20
21
21
## Prerequisites
22
22
Meet the following minimum requirements for deploying the Layered Network Management individually on the system.
@@ -50,7 +50,6 @@ The following steps for setting up [AKS Edge Essentials](/azure/aks/hybrid/aks-e
@@ -60,6 +59,8 @@ The following steps for setting up [AKS Edge Essentials](/azure/aks/hybrid/aks-e
60
59
curl -sfL https://get.k3s.io | sh -s - --disable=traefik --write-kubeconfig-mode 644
61
60
```
62
61
62
+
Refer to the [K3s quick-start guide](https://docs.k3s.io/quick-start) for more detail.
63
+
63
64
> [!IMPORTANT]
64
65
> Be sure to use the `--disable=traefik` parameter to disable treafik. Otherwise, you might have an issue when you try to allocate public IP forthe Layered Network Management servicein later steps.
65
66
@@ -78,64 +79,47 @@ The following steps for setting up [AKS Edge Essentials](/azure/aks/hybrid/aks-e
78
79
79
80
# [AKS Edge Essentials](#tab/aksee)
80
81
81
-
## Prepare Windows 11
82
-
83
-
1. Install [Windows 11](https://www.microsoft.com/software-download/windows11) on your device.
84
-
1. Install [Helm](https://helm.sh/docs/intro/install/) 3.8.0 or later.
For hosting the Layered Network Management service, you need a single machine deployment of AKS Edge Essentials. You can follow the AKS Edge Essentials documentation to create your cluster with default confiurations.
96
83
97
-
## Create the AKS Edge Essentials cluster
84
+
## Prepare Windows 11
98
85
99
-
1. Verify you meet the [Prerequisites](/azure/aks/hybrid/aks-edge-quickstart#prerequisites) section of the AKS Edge Essentials quickstart.
100
-
1. Follow the [Prepare your machines for AKS Edge Essentials](/azure/aks/hybrid/aks-edge-howto-setup-machine) steps to install AKS Edge Essentials on your Windows 11 machine.
101
-
1. Follow the steps in the [Single machine deployment](/azure/aks/hybrid/aks-edge-howto-single-node-deployment) article.
102
-
Use the *New-AksEdgeDeployment* PowerShell command to create a file named **aks-ee-config.json**, make the following modifications:
103
-
- In the **Init** section, change the **ServiceIPRangeSize** property to **10**.
86
+
1. Follow the steps in [Prepare your machines for AKS Edge Essentials](/azure/aks/hybrid/aks-edge-howto-setup-machine) to setup your Windows machine.
104
87
105
-
```json
106
-
"Init": {
107
-
"ServiceIPRangeSize": 10
108
-
},
88
+
1. In addition, you need to install the Azure CLI and extensions for later steps.
89
+
1. Install Azure CLI. Follow the steps in [Install Azure CLI on Windows](/cli/azure/install-azure-cli-windows).
90
+
1. Install connectedk8s using the following command:
91
+
```bash
92
+
az extension add --name connectedk8s
93
+
az extension add --name k8s-extension
109
94
```
110
95
111
-
- In the **Network** section, verify the following properties are added or set. Replace the placeholder text with your values. Confirm that the *Ip4AddressPrefix***A.B.C** doesn't overlap with the IP range that is assigned within network layers.
112
-
113
-
```json
114
-
"Network": {
115
-
"NetworkPlugin": "flannel",
116
-
"Ip4AddressPrefix": "<A.B.C.0/24>",
117
-
"Ip4PrefixLength": 24,
118
-
"InternetDisabled": false,
119
-
"SkipDnsCheck": false,
120
-
```
96
+
## Create the AKS Edge Essentials cluster
121
97
122
-
For more information about deployment configurations, see [Deployment configuration JSON parameters](/azure/aks/hybrid/aks-edge-deployment-config-json).
98
+
Follow the steps in [Single machine deployment](/azure/aks/hybrid/aks-edge-howto-single-node-deployment) to create your cluster.
99
+
1. You need to complete step 1-3 in this document.
100
+
1. In **aksedge-config.json** from step 1, you only need to make the following adjustment for Layered Network Management. You can keep the default value for the rest of the parameters. Otherwise, make proper adjustments based on your environment.
101
+
```json
102
+
"Init": {
103
+
"ServiceIPRangeSize": 10
104
+
},
105
+
```
123
106
124
107
---
125
108
126
109
## Arc enable the cluster
127
110
111
+
# [K3S Cluster](#tab/k3s)
112
+
128
113
1. Sign in with Azure CLI. To avoid permission issues later, it's important that you sign in interactively using a browser window:
129
114
```powershell
130
115
az login
131
116
```
132
-
1. Set environment variables forthe setup steps. Replace valuesin`<>` with valid values or names of your choice. The `CLUSTER_NAME` and `RESOURCE_GROUP` are created based on the names you provide:
117
+
1. Set environment variables for the setup steps. Replace values in `<>` with valid values or names of your choice. The `CLUSTER_NAME` and `RESOURCE_GROUP` are created based on the names you provide. Refer to [Azure IoT Operations supported regions](../iot-operations/overview-iot-operations#supported-regions) for choosing the `LOCATION`.
133
118
```powershell
134
119
# Id of the subscription where your resource group and Arc-enabled cluster will be created
135
120
$SUBSCRIPTION_ID = "<subscription-id>"
136
121
# Azure region where the created resource group will be located
137
-
# Currently supported regions: : "westus3" or "eastus2"
138
-
$LOCATION = "WestUS3"
122
+
$LOCATION = "<region>"
139
123
# Name of a new resource group to create which will hold the Arc-enabled cluster and Azure IoT Operations resources
140
124
$RESOURCE_GROUP = "<resource-group-name>"
141
125
# Name of the Arc-enabled cluster to create in your resource group
@@ -166,8 +150,12 @@ The following steps for setting up [AKS Edge Essentials](/azure/aks/hybrid/aks-e
> If the `connectedk8s` commands fail, try using the cmdlets in [Connect your AKS Edge Essentials cluster to Arc](/azure/aks/hybrid/aks-edge-howto-connect-to-arc).
153
+
154
+
# [AKS Edge Essentials](#tab/aksee)
155
+
156
+
- Follow the steps in [Connect your AKS Edge Essentials cluster to Arc](/azure/aks/hybrid/aks-edge-howto-connect-to-arc).
157
+
- You need to complete step 1-3 in this document.
158
+
---
171
159
172
160
## Deploy Layered Network Management Preview Service to the cluster
173
161
@@ -186,7 +174,7 @@ Once your Kubernetes cluster is Arc-enabled, you can deploy the Layered Network
186
174
1. Use the *kubectl* command to verify the Layered Network Management operator is running.
### Add iptables configuration for AKS Edge Essentials
284
326
285
327
> [!IMPORTANT]
286
-
> This step is forAKS Edge Essentials only.
328
+
> This step is applicable only when hosting the Layered Network Management in an AKS Edge Essentials cluster.
287
329
288
330
The Layered Network Management deployment creates a Kubernetes service of type *LoadBalancer*. To ensure that the service is accessible from outside the Kubernetes cluster, you need to map the underlying Windows host's ports to the appropriate ports on the Layered Network Management service.
0 commit comments