Skip to content

Commit

Permalink
Merge pull request #960 from jnoller/05062019
Browse files Browse the repository at this point in the history
Network Policies GA 🍰 :shipit:
  • Loading branch information
jnoller authored May 10, 2019
2 parents 5c2738a + 3b06a4c commit 07a5b2a
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 20 deletions.
5 changes: 5 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down
21 changes: 1 addition & 20 deletions previews.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 07a5b2a

Please sign in to comment.