From 2c28eeb7802e2055914d3d71e36d5678cacf326e Mon Sep 17 00:00:00 2001 From: Nicola Kabar Date: Wed, 28 Nov 2018 08:42:11 -0600 Subject: [PATCH] corrected spacing for the --unmanaged-cni option --- reference/ucp/3.1/cli/install.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/ucp/3.1/cli/install.md b/reference/ucp/3.1/cli/install.md index 28df9bf72f..355ec80ed1 100644 --- a/reference/ucp/3.1/cli/install.md +++ b/reference/ucp/3.1/cli/install.md @@ -47,7 +47,7 @@ command. | `--interactive, i` | Run in interactive mode and prompt for configuration values | | `--admin-username` | The UCP administrator username | | `--admin-password` | The UCP administrator password | -| `--san` | Add subject alternative names to certificates (e.g. --san www1.acme.com --san www2.acme.com) | | `--unmanaged-cni` | This determines who manages the CNI plugin, using `true` or `false`. The default is `false`. The `true` value installs UCP without a managed CNI plugin. UCP and the Kubernetes components will be running but pod to pod networking will not function until a CNI plugin is manually installed. This will impact some functionality of UCP until a CNI plugin is running. | +| `--san` | Add subject alternative names to certificates (e.g. --san www1.acme.com --san www2.acme.com) | | `--unmanaged-cni` | This determines who manages the CNI plugin, using `true` or `false`. The default is `false`. The `true` value installs UCP without a managed CNI plugin. UCP and the Kubernetes components will be running but pod to pod networking will not function until a CNI plugin is manually installed. This will impact some functionality of UCP until a CNI plugin is running. | | `--host-address` | The network address to advertise to other nodes. Format: IP address or network interface name | | `--data-path-addr` | Address or interface to use for data path traffic. Format: IP address or network interface name | | `--controller-port` | Port for the web UI and API |