From 3b06a4c48f1bc8c405cb0228991c7717cb60b0a7 Mon Sep 17 00:00:00 2001 From: Jesse Noller Date: Fri, 10 May 2019 11:17:31 -0600 Subject: [PATCH] Network Policies GA --- CHANGELOG.md | 5 +++++ previews.md | 21 +-------------------- 2 files changed, 6 insertions(+), 20 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a7174e6e..0e4610af 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,11 @@ ## Release 2019-05-06 +* New Features + * Kubernetes Network Policies are GA + * See https://docs.microsoft.com/en-us/azure/aks/use-network-policies + for documentation. + * Bug Fixes * An issues customers reported with CoreDNS entering CrashLoopBackoff has been fixed. This was related to the upstream move to `klog` diff --git a/previews.md b/previews.md index 0391b9f2..78caaa0e 100644 --- a/previews.md +++ b/previews.md @@ -119,26 +119,7 @@ To create a cluster with VMSS enabled, use the `--enable-vmss` switch in `az aks ### Kubernetes Network Policy -[Network policy][4] enables network segmentation of a Kubernetes cluster. -Network policy uses a plugin model, with different providers implementing the -core Kubernetes API. In AKS, we offer two plugins: a native `azure` solution -and the open-source `calico` project. - -You can opt into the preview by registering the feature flag: - -``` -az feature register -n EnableNetworkPolicy --namespace Microsoft.ContainerService -``` - -Then refresh your registration of the AKS resource provider: - -``` -az provider register -n Microsoft.ContainerService -``` - -To create a cluster with network policy enabled, use the `--network-policy` -switch in `az aks create` and specify the network policy plugin you would like -to use, `azure` or `calico`. Note that both require the `azure` network plugin. +Kubernetes network policies is now GA, please see: https://docs.microsoft.com/en-us/azure/aks/use-network-policies ### Kubernetes Audit Log