Skip to content

Commit 848ad2f

Browse files
committed
fixing broken bookmarks
1 parent fe40e7c commit 848ad2f

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

articles/aks/support-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Microsoft provides technical support for the following examples:
5858
* Connectivity to other Azure services and applications
5959
* Ingress controllers and ingress or load balancer configurations
6060
* Network performance and latency
61-
* [Network policies](use-network-policies.md#differences-between-azure-network-policy-manager-and-calico-network-policy-and-their-capabilities)
61+
* [Network policies](use-network-policies.md#compare-azure-network-policy-manager-and-calico-network-policy)
6262

6363
> [!NOTE]
6464
> Any cluster actions taken by Microsoft/AKS are made with your consent under a built-in Kubernetes role `aks-service` and built-in role binding `aks-service-rolebinding`. This role enables AKS to troubleshoot and diagnose cluster issues, but can't modify permissions nor create roles or role bindings, or other high privilege actions. Role access is only enabled under active support tickets with just-in-time (JIT) access.

articles/aks/use-network-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Azure provides two ways to implement network policy. You choose a network policy
3434

3535
To enforce the specified policies, Azure Network Policy Manager for Linux uses Linux *IPTables*. Azure Network Policy Manager for Windows uses *Host Network Service (HNS) ACLPolicies*. Policies are translated into sets of allowed and disallowed IP pairs. These pairs are then programmed as `IPTable` or `HNS ACLPolicy` filter rules.
3636

37-
## Differences between Azure Network Policy Manager and Calico network policy and their capabilities
37+
## Compare Azure Network Policy Manager and Calico network policy
3838

3939
| Capability | Azure Network Policy Manager | Calico network policy |
4040
|------------------------------------------|----------------------------|-----------------------------|

articles/aks/windows-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ To learn more about Windows containers on AKS, see the following resources:
111111
[azure-cni-choose-network-model]: ./azure-cni-overlay.md#choosing-a-network-model-to-use
112112
[network-concepts-for-aks-applications]: ./concepts-network.md
113113
[windows-vs-linux]: ./windows-vs-linux-containers.md
114-
[azurenpm-vs-calico]: ./use-network-policies.md#differences-between-azure-network-policy-manager-and-calico-network-policy-and-their-capabilities
114+
[azurenpm-vs-calico]: ./use-network-policies.md#compare-azure-network-policy-manager-and-calico-network-policy
115115
[network-policies-aks]: ./use-network-policies.md
116116
[dsr]: ../load-balancer/load-balancer-multivip-overview.md#rule-type-2-backend-port-reuse-by-using-floating-ip
117117
[upgrade-aks-cluster]: ./upgrade-cluster.md

0 commit comments

Comments
 (0)