From 3a9566810ee116658dd9f3d05a9bc34fcf6fc8a0 Mon Sep 17 00:00:00 2001 From: Cao Shufeng Date: Tue, 22 Nov 2016 06:03:28 -0500 Subject: [PATCH] [kubenet] add description about non-masquerade-cidr For kubenet, users should run kubelet with argument --non-masquerade-cidr, or pods may have problem when access "10.0.0.0/8" cidr. Also, if --pod-cidr is set outside the scope of --non-masquerade-cidr, node will do ip masquerade for ingress packets, which is not excepted. --- docs/admin/network-plugins.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/admin/network-plugins.md b/docs/admin/network-plugins.md index 6c5f354423..5f138da005 100644 --- a/docs/admin/network-plugins.md +++ b/docs/admin/network-plugins.md @@ -57,6 +57,7 @@ The plugin requires a few things: * The standard CNI `bridge`, `lo` and `host-local` plugins are required, at minimum version 0.2.0. Kubenet will first search for them in `/opt/cni/bin`. Specify `network-plugin-dir` to supply additional search path. The first found match will take effect. * Kubelet must be run with the `--network-plugin=kubenet` argument to enable the plugin * Kubelet must also be run with the `--reconcile-cidr` argument to ensure the IP subnet assigned to the node by configuration or the controller-manager is propagated to the plugin +* Kubelet should also be run with the `--non-masquerade-cidr=` argumment to ensure traffic to IPs outside this range will use IP masquerade. * The node must be assigned an IP subnet through either the `--pod-cidr` kubelet command-line option or the `--allocate-node-cidrs=true --cluster-cidr=` controller-manager command-line options. ### Customizing the MTU (with kubenet)