Skip to content

Commit 889c76a

Browse files
authored
Merge pull request #199959 from zr-msft/zr-aks-rm-aks-engine2
[AKS] remote aks-engine references
2 parents 9a8bf08 + 6968397 commit 889c76a

File tree

2 files changed

+0
-13
lines changed

2 files changed

+0
-13
lines changed

articles/aks/policy-reference.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,10 +25,6 @@ the link in the **Version** column to view the source on the
2525

2626
[!INCLUDE [azure-policy-reference-rp-aks-containerservice](../../includes/policy/reference/byrp/microsoft.containerservice.md)]
2727

28-
### AKS Engine
29-
30-
[!INCLUDE [azure-policy-reference-rp-aks-aksengine](../../includes/policy/reference/byrp/aks-engine.md)]
31-
3228
## Next steps
3329

3430
- See the built-ins on the [Azure Policy GitHub repo](https://github.com/Azure/azure-policy).

articles/aks/use-network-policies.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -18,15 +18,6 @@ This article shows you how to install the network policy engine and create Kuber
1818

1919
You need the Azure CLI version 2.0.61 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
2020

21-
> [!TIP]
22-
> If you used the network policy feature during preview, we recommend that you [create a new cluster](#create-an-aks-cluster-and-enable-network-policy).
23-
>
24-
> If you wish to continue using existing test clusters that used network policy during preview, upgrade your cluster to a new Kubernetes versions for the latest GA release and then deploy the following YAML manifest to fix the crashing metrics server and Kubernetes dashboard. This fix is only required for clusters that used the Calico network policy engine.
25-
>
26-
> As a security best practice, [review the contents of this YAML manifest][calico-aks-cleanup] to understand what is deployed into the AKS cluster.
27-
>
28-
> `kubectl delete -f https://raw.githubusercontent.com/Azure/aks-engine/master/docs/topics/calico-3.3.1-cleanup-after-upgrade.yaml`
29-
3021
## Overview of network policy
3122

3223
All pods in an AKS cluster can send and receive traffic without limitations, by default. To improve security, you can define rules that control the flow of traffic. Back-end applications are often only exposed to required front-end services, for example. Or, database components are only accessible to the application tiers that connect to them.

0 commit comments

Comments
 (0)