Skip to content

Commit 3a5b4a9

Browse files
Fixed comments
1 parent 61f6676 commit 3a5b4a9

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/aks/use-network-policies.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,8 @@ Azure NPM for Linux uses Linux *IPTables* and Azure NPM for Windows uses *Host N
4848

4949
## Limitations:
5050

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:
5353
* named ports
5454
* SCTP protocol
5555
* 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
7777

7878
### Create an AKS cluster with Azure NPM enabled - Linux only
7979

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.
8181

8282
To begin, you should replace the values for *$RESOURCE_GROUP_NAME* and *$CLUSTER_NAME* variables.
8383

@@ -101,7 +101,7 @@ az aks create \
101101

102102
### Create an AKS cluster with Azure NPM enabled - Windows Server 2022 (Preview)
103103

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.
105105

106106
Please execute the following commands prior to creating a cluster:
107107

@@ -132,7 +132,7 @@ Create a username to use as administrator credentials for your Windows Server co
132132
echo "Please enter the username to use as administrator credentials for Windows Server containers on your cluster: " && read WINDOWS_USERNAME
133133
```
134134

135-
Use the following command to create a cluster :
135+
Use the following command to create a cluster:
136136

137137
```azurecli
138138
az aks create \
@@ -202,15 +202,15 @@ When the cluster is ready, configure `kubectl` to connect to your Kubernetes clu
202202
```azurecli-interactive
203203
az aks get-credentials --resource-group $RESOURCE_GROUP_NAME --name $CLUSTER_NAME
204204
```
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.
206206

207207
Firstly, let's create a namespace called *demo* to run the example pods:
208208

209209
```console
210210
kubectl create namespace demo
211211
```
212212

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*.
214214

215215
>[!NOTE]
216216
> 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
284284
/agnhost connect <server-ip>:80 --timeout=3s --protocol=tcp
285285
```
286286

287-
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:
288288

289289
```output
290290
TIMEOUT

0 commit comments

Comments
 (0)