Markup corrections to the Kubernetes gap analyzis

Some fixes to the markup in the table.
I've moved CNF to the main text to the multi network row,
as it is not an implementation option.

Change-Id: I97193a9494b1a018aeaca75b3b90d2e240b2f2b7
Signed-off-by: csatari <gergely.csatari@nokia.com>

1 files changed, 29 insertions, 32 deletions

diff --git a/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst b/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst
index 2d4039c..f8fb85a 100644
--- a/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst
+++ b/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst
@@ -14,35 +14,32 @@ analysis with Kubernetes Official Release.
 .. table::
   :class: longtable
 
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
-  |Use Case / Requirement                                     |Supported in v1.5  |Notes                                                               |
-  +===========================================================+===================+====================================================================+
-  |Manage conainter and virtual machine in the same platform. |No                 | There are some ways how Kubernetes could manage VM-s:              |
-  |                                                           |                   | 1) Kubevirt [1]                                                    |
-  |                                                           |                   | 2) Kubernetes can start rkt and with rkt it is possible to start   |
-  |                                                           |                   |    VM-s [2]                                                        |
-  |                                                           |                   | 3) Virtlet [3]                                                     |
-  |                                                           |                   | 4) Hypercontainer [4]                                              |
-  |                                                           |                   |  [1] https://github.com/kubevirt/kubevirt                          |
-  |                                                           |                   |  [2] https://coreos.com/rkt/docs/latest/running-kvm-stage1.html    |
-  |                                                           |                   |  [3] https://github.com/Mirantis/virtlet                           |
-  |                                                           |                   |  [4] https://github.com/kubernetes/frakti                          |
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
-  |Kubernetes support multiple networks.                      |No                 | As VNF needs at least three interfaces. Management,control plane,  |
-  |                                                           |                   |data plane.                                                         |
-  |                                                           |                   | (1) Multus https://github.com/Intel-Corp/multus-cni                |
-  |                                                           |                   | (2) CNI-Genie https://github.com/Huawei-PaaS/CNI-Genie             |
-  |                                                           |                   | (3) A solution built into Kubernetes                               |
-  |                                                           |                   | https://docs.google.com/document/d/1TW3P4c8auWwYy-w_5afIPDcGNLK3LZf0m14943eVfVg/ |
-  |                                                           |                   | (4) CNI                                                            |
-  |                                                           |                   | https://github.com/containernetworking/cni/blob/master/SPEC.md     |
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
-  |Kubernetes support NAT-less connections to a container     |No                 | SIP/SDP and SCTP are not working with NAT-ed networks              |
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
-  |Kubernetes scheduling support CPU binding，NUMA features   |No                 |The kubernetes schedular don't support these features               |
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
-  |DPDK need to support CNI                                   |No                 |DPDK is the technology to accelerate the data plane. Container need |
-  |                                                           |                   |support it, the same with virtual machine.                          |
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
-  |SR-IOV can support CNI (Optional)                          |No                 |SR-IOV could let container get high performance                     |
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
+  |Use Case / Requirement                                     |Supported in v1.5  |Notes                                                                                                |
+  +===========================================================+===================+=====================================================================================================+
+  |Manage conainter and virtual machine in the same platform. |No                 | There are some ways how Kubernetes could manage VM-s:                                               |
+  |                                                           |                   |                                                                                                     |
+  |                                                           |                   | 1. `Kubevirt <https://github.com/kubevirt/kubevirt>`_                                               |
+  |                                                           |                   | 2. Kubernetes can start rkt and with                                                                |
+  |                                                           |                   |    `rkt it is possible to start VM-s <https://coreos.com/rkt/docs/latest/running-kvm-stage1.html>`_ |
+  |                                                           |                   | 3. `Virtlet <https://github.com/Mirantis/virtlet>`_                                                 |
+  |                                                           |                   | 4. `Hypercontainer <https://github.com/kubernetes/frakti>`_                                         |
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
+  |Kubernetes support multiple networks.                      |No                 | As VNF needs at least three interfaces. Management,control plane, data plane. `CNI                  |
+  |                                                           |                   | <https://github.com/containernetworking/cni/blob/master/SPEC.md>`_ already supports multiple        |
+  |                                                           |                   | interfaces in the API definition.                                                                   |
+  |                                                           |                   |                                                                                                     |
+  |                                                           |                   | 1. `Multus <https://github.com/Intel-Corp/multus-cni>`_                                             |
+  |                                                           |                   | 2. `CNI-Genie <https://github.com/Huawei-PaaS/CNI-Genie>`_                                          |
+  |                                                           |                   | 3. A `solution built into Kubernetes                                                                |
+  |                                                           |                   |    <https://docs.google.com/document/d/1TW3P4c8auWwYy-w_5afIPDcGNLK3LZf0m14943eVfVg/>`_             |
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
+  |Kubernetes support NAT-less connections to a container     |No                 | SIP/SDP and SCTP are not working with NAT-ed networks                                               |
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
+  |Kubernetes scheduling support CPU binding，NUMA features   |No                 | The kubernetes schedular don't support these features                                               |
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
+  |DPDK need to support CNI                                   |No                 | DPDK is the technology to accelerate the data plane. Container need                                 |
+  |                                                           |                   | support it, the same with virtual machine.                                                          |
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
+  |SR-IOV can support CNI (Optional)                          |No                 | SR-IOV could let container get high performance                                                     |
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+