From 0673b89cd4ac096d5b22794fa697925278b70d50 Mon Sep 17 00:00:00 2001 From: Manish Kumar Date: Wed, 23 Feb 2022 01:12:29 +0530 Subject: [PATCH] follow-up of #31667 --- .../extend-kubernetes/compute-storage-net/network-plugins.md | 2 +- content/en/docs/setup/best-practices/node-conformance.md | 2 -- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md index fef6cb64a2..0dcfc3ca6f 100644 --- a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md +++ b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md @@ -21,7 +21,7 @@ You must use a CNI plugin that is compatible with the ## Installation -The kubelet has a single default network plugin, and a default network common to the entire cluster.The CRI manages its own CNI plugins. There are two Kubelet command line parameters to keep in mind when using plugins: +The kubelet has a single default network plugin, and a default network common to the entire cluster. The CRI manages its own CNI plugins. There are two Kubelet command line parameters to keep in mind when using plugins: * `cni-bin-dir`: Kubelet probes this directory for plugins on startup * `network-plugin`: The network plugin to use from `cni-bin-dir`. It must match the name reported by a plugin probed from the plugin directory. For CNI plugins, this is `cni`. diff --git a/content/en/docs/setup/best-practices/node-conformance.md b/content/en/docs/setup/best-practices/node-conformance.md index d127304bfa..e1140664cb 100644 --- a/content/en/docs/setup/best-practices/node-conformance.md +++ b/content/en/docs/setup/best-practices/node-conformance.md @@ -30,8 +30,6 @@ To run the node conformance test, perform the following steps: Because the test framework starts a local control plane to test the kubelet, use `http://localhost:8080` as the URL of the API server. There are some other kubelet command line parameters you may want to use: - * `--pod-cidr`: The CIDR to use for pod IP addresses, only used in standalone mode. - In cluster mode, this is obtained from the master. For IPv6, the maximum number of IP's allocated is 65536. For example `--pod-cidr=10.180.0.0/24`. * `--cloud-provider`: If you are using `--cloud-provider=gce`, you should remove the flag to run the test.