Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

Commit

Permalink
Merge pull request #764 from lachie83/update-calico-docs
Browse files Browse the repository at this point in the history
update calico docs
  • Loading branch information
seanknox authored Jun 14, 2017
2 parents 2ac382d + f8c1cec commit 579e8b8
Showing 1 changed file with 1 addition and 8 deletions.
9 changes: 1 addition & 8 deletions docs/kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,14 +72,7 @@ All VMs are in the same private VNET and are fully accessible to each other.

Using the default configuration, Kubernetes allows communication between all
Pods within a cluster. To ensure that Pods can only be accessed by authorized
Pods, a policy enforcement is needed. To enable policy enforcement using Calico
`azuredeploy.parameters.json` needs to be modified like that:

```json
"networkPolicy": {
"value": "calico"
}
```
Pods, a policy enforcement is needed. To enable policy enforcement using Calico refer to the [cluster definition](https://github.com/Azure/acs-engine/blob/master/docs/clusterdefinition.md#kubernetesconfig) document under networkPolicy. There is also a reference cluster definition available [here](https://github.com/Azure/acs-engine/blob/master/examples/networkpolicy/kubernetes-calico.json).

This will deploy a Calico node controller to every instance of the cluster
using a Kubernetes DaemonSet. After a successful deployment you should be able
Expand Down

0 comments on commit 579e8b8

Please sign in to comment.