diff options
| author |   jdenisco <jdenisco@cisco.com> | 2019-05-13 12:40:21 -0400 |
|---|---|---|
| committer |   Dave Barach <openvpp@barachs.net> | 2019-05-16 17:42:13 +0000 |
| commit | 8a6e1b190c63cc596aed33f84b5989b64d276423 (patch) | |
| tree | 016c181103861da2791c090a3b874b9bc385234e /docs/usecases/contiv/K8s_Overview.md | |
| parent | 8fa01c17aa65c03b1f25f9accaa5bb0f9d0862c4 (diff) | |
docs: Update sphinx, requirements, support markdown tables
Change-Id: Ie7c546f5720b10fe5423397204e1ab5c22d7a2ba
Signed-off-by: jdenisco <jdenisco@cisco.com>
Diffstat (limited to 'docs/usecases/contiv/K8s_Overview.md')
| -rw-r--r-- | docs/usecases/contiv/K8s_Overview.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/usecases/contiv/K8s_Overview.md b/docs/usecases/contiv/K8s_Overview.md index f9cf9c5a9ba..e3d8e1a0d44 100644 --- a/docs/usecases/contiv/K8s_Overview.md +++ b/docs/usecases/contiv/K8s_Overview.md @@ -78,7 +78,7 @@ network stack, and data-plane NIC interface controlled by VPP: - data-plane NIC is controlled directly by VPP using DPDK. Note, this means that this interface is not visible to the host Linux network stack, and the node either needs another management interface for k8s control plane communication, or - [STN (Steal The NIC)](SINGLE_NIC_SETUP.html) deployment must be applied. + \[STN (Steal The NIC)\](SINGLE_NIC_SETUP.html) deployment must be applied. **Contiv VPP Agent** is the control plane part of the vSwitch container. It is responsible for configuring the VPP according to the information gained from ETCD, and requests @@ -99,11 +99,11 @@ and replies with a response, which is then forwarded back to Kubelet. ### Contiv STN Daemon -This section discusses how the Contiv [STN (Steal The NIC)](SINGLE_NIC_SETUP.html) daemon operation works. As already mentioned, the default setup of Contiv/VPP requires two network interfaces +This section discusses how the Contiv \[STN (Steal The NIC)\](SINGLE_NIC_SETUP.html) daemon operation works. As already mentioned, the default setup of Contiv/VPP requires two network interfaces per node: one controlled by VPP for data facing PODs, and one controlled by the host network stack for k8s control plane communication. In case that your k8s nodes do not provide two network interfaces, Contiv/VPP can work in the single NIC setup, when the interface will be "stolen" from the host network stack just before starting the VPP and configured with the same IP address on VPP, as well as on the host-VPP interconnect TAP interface, as it had in the host before it. -For more information on STN setup, read the [Single NIC Setup README](./SINGLE_NIC_SETUP.html) +For more information on STN setup, read the \[Single NIC Setup README\](./SINGLE_NIC_SETUP.html) |