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
Copy file name to clipboardExpand all lines: articles/aks/use-network-policies.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,8 @@ Azure NPM for Linux uses Linux *IPTables* and Azure NPM for Windows uses *Host N
48
48
49
49
## Limitations:
50
50
51
-
Azure Network Policy Manager(NPM) does not support IPv6. Otherwise, Azure NPM fully supports the network policy spec in Linux.
52
-
* In Windows, Azure NPM does not support the following:
51
+
Azure Network Policy Manager(NPM) doesn't support IPv6. Otherwise, Azure NPM fully supports the network policy spec in Linux.
52
+
* In Windows, Azure NPM doesn't support the following:
53
53
* named ports
54
54
* SCTP protocol
55
55
* negative match label or namespace selectors (e.g. all labels except "debug=true")
@@ -77,7 +77,7 @@ Instead of using a system-assigned identity, you can also use a user-assigned id
77
77
78
78
### Create an AKS cluster with Azure NPM enabled - Linux only
79
79
80
-
In this section, we will work on creating a cluster with Linux node pools and Azure NPM enabled.
80
+
In this section, we'll work on creating a cluster with Linux node pools and Azure NPM enabled.
81
81
82
82
To begin, you should replace the values for *$RESOURCE_GROUP_NAME* and *$CLUSTER_NAME* variables.
83
83
@@ -101,7 +101,7 @@ az aks create \
101
101
102
102
### Create an AKS cluster with Azure NPM enabled - Windows Server 2022 (Preview)
103
103
104
-
In this section, we will work on creating a cluster with Windows node pools and Azure NPM enabled.
104
+
In this section, we'll work on creating a cluster with Windows node pools and Azure NPM enabled.
105
105
106
106
Please execute the following commands prior to creating a cluster:
107
107
@@ -132,7 +132,7 @@ Create a username to use as administrator credentials for your Windows Server co
132
132
echo "Please enter the username to use as administrator credentials for Windows Server containers on your cluster: " && read WINDOWS_USERNAME
133
133
```
134
134
135
-
Use the following command to create a cluster:
135
+
Use the following command to create a cluster:
136
136
137
137
```azurecli
138
138
az aks create \
@@ -202,15 +202,15 @@ When the cluster is ready, configure `kubectl` to connect to your Kubernetes clu
202
202
```azurecli-interactive
203
203
az aks get-credentials --resource-group $RESOURCE_GROUP_NAME --name $CLUSTER_NAME
204
204
```
205
-
To begin verification of Network Policy, we will create a sample application and set traffic rules.
205
+
To begin verification of Network Policy, we'll create a sample application and set traffic rules.
206
206
207
207
Firstly, let's create a namespace called *demo* to run the example pods:
208
208
209
209
```console
210
210
kubectl create namespace demo
211
211
```
212
212
213
-
We will now create two pods in the cluster named *client* and *server*.
213
+
We'll now create two pods in the cluster named *client* and *server*.
214
214
215
215
>[!NOTE]
216
216
> If you want to schedule the *client* or *server* on a particular node, add the following bit before the *--command* argument in the pod creation [kubectl run][kubectl-run] command:
@@ -284,7 +284,7 @@ Now, in the client's shell, verify connectivity with the server by executing the
Connectivity with traffic will be blocked since the server is labeled with app=server, but the client is not labeled. The connect command above will yield this output:
287
+
Connectivity with traffic will be blocked since the server is labeled with app=server, but the client isn't labeled. The connect command above will yield this output:
0 commit comments