docs: HOWTO run cilium-cli e2e connectivity tests

[brb]

This PR adds instructions how to run e2e conformance tests locally and on LVH VMs.

A follow-up PR will add info about ci-e2e and some tips how to develop those tests.

[bimmlerd]

Nice! Added some nits, but overall lgtm

[zacharysarah]

@brb 👋🏻 This was quite a large PR to review for documentation. In the future, you can please add smaller sections in smaller commits?

Extensive changes required.

[zacharysarah]

clarity

Suggested change

	Before running the connectivity tests you need to install `Cilium CLI <https://github.com/cilium/cilium-cli#installation>`_.
	Before running the connectivity tests, you must install `Cilium CLI <https://github.com/cilium/cilium-cli#installation>`_.

[zacharysarah]

Use active voice, comma nit, clarity

Suggested change

	Alternatively, ``Cilium CLI`` can be manually built and installed by fetching
	``https://github.com/cilium/cilium-cli``, and then running ``make install``.
	Alternatively, you can manually build and install ``Cilium CLI`` by fetching
	``https://github.com/cilium/cilium-cli`` and running ``make install``.

[zacharysarah]

Clarity, no Latin abbreviations

Suggested change

	Afterwards, you need to install Cilium. The preferred way is to use
	`cilium-cli install <https://github.com/cilium/cilium-cli/#install-cilium>`_,
	as it is able to automate some steps (e.g., detecting ``kube-apiserver`` endpoint
	address which otherwise needs to be specified when running w/o ``kube-proxy``, or
	set an annotation to a K8s worker node to prevent Cilium from being scheduled on it).
	After installing kind, the next step is to install Cilium. The preferred installation method is to use
	`cilium-cli install <https://github.com/cilium/cilium-cli/#install-cilium>`_,
	which can automate some steps (for example, detecting a ``kube-apiserver`` endpoint
	address which otherwise needs to be specified when running without ``kube-proxy``; or
	setting an annotation to a Kubernetes worker node to prevent Cilium from being scheduled on it).

[zacharysarah]

Suggested change

	To run this you can use the following command:
	To run this ssh-config you can use the following command:

[zacharysarah]

Suggested change

	| IPv6 | 0 | 0-1 | If 1 the Kubernetes cluster will use IPv6 |
	| IPv6 | 0 | 0-1 | If 1 the Kubernetes cluster uses IPv6 |

[zacharysarah]

Suggested change

	| CONTAINER\_RUNTIME | docker | containerd | To set the default container runtime in the Kubernetes cluster |
	| CONTAINER\_RUNTIME | docker | containerd | Set the default container runtime in the Kubernetes cluster |

[zacharysarah]

Suggested change

	| KUBEPROXY | 1 | 0-1 | If 0 the Kubernetes' kube-proxy won't be installed |
	| KUBEPROXY | 1 | 0-1 | If 0 the Kubernetes kube-proxy doesn't install |

[zacharysarah]

Suggested change

	testing infrastructure for Cilium? Hop on over to the
	testing infrastructure for Cilium? Join the

[zacharysarah]

@brb 👋🏻 This was quite a large PR to review for documentation. In the future, you can please add smaller sections in smaller commits?

Extensive changes required.

[brb]

This was quite a large PR to review for documentation. In the future, you can please add smaller sections in smaller commits?

@zacharysarah Hey, thanks a lot for the extensive review! I should have mentioned in the PR description that e2e_legacy.rst is an old doc page, and my PR just renamed it from e2e.rst to e2e_legacy.rst. Ideally, I'd like to phase it out, and do not touch it. However, considering that you put a lot of effort in reviewing it, I think I need to address your comments.

[zacharysarah]

@brb

However, considering that you put a lot of effort in reviewing it, I think I need to address your comments.

Ah sorry, my bad, I should have looked more closely at the changes to file structure. If the content is deprecated, then let's leave it alone and not touch it. Out of curiosity though, if the content is deprecated, is there a reason to keep it in the current release as legacy and not just delete it while leaving it intact in previous release branches?

EDIT: Whatever you choose, I'm approving to unblock this PR.

[zacharysarah]

Approving to unblock, with notes about options in the comments.

[brb]

Addressed the feedback. The e2e_legacy.rst will be removed once we convert all ginkgo tests (expected to happen in v1.15). Marking as ready-to-merge.

[aanm]

@brb needs rebase

[brb]

@aanm Rebased. Could you merge it?