From 8ed0bcc7004a7af7e6eead7bed266d9ac51588eb Mon Sep 17 00:00:00 2001 From: Jack Francis Date: Mon, 25 Jun 2018 14:26:48 -0700 Subject: [PATCH] add doc note --- docs/clusterdefinition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/clusterdefinition.md b/docs/clusterdefinition.md index 29de840659..fa1f1d27bb 100644 --- a/docs/clusterdefinition.md +++ b/docs/clusterdefinition.md @@ -53,7 +53,7 @@ Here are the valid values for the orchestrator types: |kubeletConfig|no|Configure various runtime configuration for kubelet. See `kubeletConfig` [below](#feat-kubelet-config)| |kubernetesImageBase|no|Specifies the base URL (everything preceding the actual image filename) of the kubernetes hyperkube image to use for cluster deployment, e.g., `k8s-gcrio.azureedge.net/`| |networkPlugin|no|Specifies the network plugin implementation for the cluster. Valid values are:
`"azure"` (default), which provides an Azure native networking experience
`"kubenet"` for k8s software networking implementation.
`"flannel"` for using CoreOS Flannel
`"cilium"` for using the default Cilium CNI IPAM | -|networkPolicy|no|Specifies the network policy enforcement tool for the cluster (currently Linux-only). Valid values are:
`calico` for Calico network policy.
`cilium` for cilium network policy (Lin).
See [network policy examples](../examples/networkpolicy) for more information| +|networkPolicy|no|Specifies the network policy enforcement tool for the cluster (currently Linux-only). Valid values are:
`"calico"` for Calico network policy.
`"cilium"` for cilium network policy (Lin), and `"azure"` (experimental) for Azure CNI-compliant network policy (note: Azure CNI-compliant network policy requires explicit `"networkPlugin": "azure"` configuration as well).
See [network policy examples](../examples/networkpolicy) for more information| |privateCluster|no|Build a cluster without public addresses assigned. See `privateClusters` [below](#feat-private-cluster).| |schedulerConfig|no|Configure various runtime configuration for scheduler. See `schedulerConfig` [below](#feat-scheduler-config)| |serviceCidr|no|IP range for Service IPs, Default is "10.0.0.0/16". This range is never routed outside of a node so does not need to lie within clusterSubnet or the VNET|