From 7a759be2c578dfc81849e9ee1aaecc8a4f546c07 Mon Sep 17 00:00:00 2001 From: David Yu Date: Tue, 6 Dec 2022 13:51:31 -0800 Subject: [PATCH] docs: K8s CNI namespace (#15696) --- website/content/docs/k8s/installation/install.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/content/docs/k8s/installation/install.mdx b/website/content/docs/k8s/installation/install.mdx index 621439a01a..a2b9e721ed 100644 --- a/website/content/docs/k8s/installation/install.mdx +++ b/website/content/docs/k8s/installation/install.mdx @@ -181,6 +181,7 @@ The following table describes the available CNI plugin options: | --- | --- | --- | | `cni.enabled` | Boolean value that enables or disables the CNI plugin. If `true`, the plugin is responsible for redirecting traffic in the service mesh. If `false`, redirection is handled by the `connect-inject init` container. | `false` | | `cni.logLevel` | String value that specifies the log level for the installer and plugin. You can specify the following values: `info`, `debug`, `error`. | `info` | +| `cni.namespace` | Set the namespace to install the CNI plugin into. Overrides global namespace settings for CNI resources. Ex: `kube-system` | `consul` | | `cni.multus` | Boolean value that enables multus CNI plugin support. If `true`, multus will be enabled. If `false`, Consul CNI will operate as a chained plugin. | `false` | | `cni.cniBinDir` | String value that specifies the location on the Kubernetes node where the CNI plugin is installed. | `/opt/cni/bin` | | `cni.cniNetDir` | String value that specifies the location on the Kubernetes node for storing the CNI configuration. | `/etc/cni/net.d` |