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/virtual-network/kubernetes-network-policies.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Network policies provide micro-segmentation for pods just like Network Security
14
14
15
15
:::image type="content" source="./media/kubernetes-network-policies/kubernetes-network-policies-overview.png" alt-text="Diagram of Kubernetes network policies overview.":::
16
16
17
-
Azure Network Policy Management implementation works with the Azure CNI that provides VNet integration for containers. Network Policy Manager is supported on Linux and Windows Server. The implementation enforces traffic filtering by configuring allow and deny IP rules based on the defined policies in Linux IPTables or Host Network Service(HNS) ACLPolicies for Windows Server.
17
+
Azure Network Policy Management implementation works with the Azure CNI that provides virtual network integration for containers. Network Policy Manager is supported on Linux and Windows Server. The implementation enforces traffic filtering by configuring allow and deny IP rules based on the defined policies in Linux IPTables or Host Network Service(HNS) ACLPolicies for Windows Server.
18
18
19
19
## Planning security for your Kubernetes cluster
20
20
@@ -39,16 +39,16 @@ Once the cluster is deployed run the following `kubectl` command to download and
The solution is also open source and the code is available on the [Azure Container Networking repository](https://github.com/Azure/azure-container-networking/tree/master/Network Policy Manager).
51
+
The solution is also open source and the code is available on the [Azure Container Networking repository](https://github.com/Azure/azure-container-networking/tree/master/npm).
52
52
53
53
## Monitor and visualize network configurations with Azure NPM
54
54
@@ -127,9 +127,9 @@ integrations: |-
127
127
collect_advanced_metrics = true
128
128
```
129
129
130
-
Advanced metrics are optional, and turning them on automatically turns on basic metrics collection. Advanced metrics currently include only `Network Policy Manager_ipset_counts`
130
+
Advanced metrics are optional, and turning them on automatically turns on basic metrics collection. Advanced metrics currently include only `Network Policy Manager_ipset_counts`.
131
131
132
-
Learn more about [Azure Monitor for containers collection settings in config map](../azure-monitor/containers/container-insights-agent-config.md)
132
+
Learn more about [Azure Monitor for containers collection settings in config map](../azure-monitor/containers/container-insights-agent-config.md).
133
133
134
134
### Visualization options for Azure Monitor
135
135
@@ -146,7 +146,7 @@ Besides viewing the workbook, you can also directly query the Prometheus metrics
146
146
| where Name contains "npm_"
147
147
```
148
148
149
-
You can also query log analytics directly for the metrics. Learn more about it with [Getting Started with Log Analytics Queries](../azure-monitor/containers/container-insights-log-query.md)
149
+
You can also query log analytics directly for the metrics. For more information, see [Getting Started with Log Analytics Queries](../azure-monitor/containers/container-insights-log-query.md).
150
150
151
151
#### Viewing in Grafana dashboard
152
152
@@ -158,7 +158,7 @@ The dashboard has visuals similar to the Azure Workbook. You can add panels to c
158
158
159
159
Some users may choose to collect metrics with a Prometheus server instead of Azure Monitor for containers. You merely need to add two jobs to your scrape config to collect Network Policy Manager metrics.
160
160
161
-
To install a Prometheus server, add this helm repo on your cluster
161
+
To install a Prometheus server, add this helm repo on your cluster:
0 commit comments