Skip to content

Commit

Permalink
docs: Create connectivity test is separate namespace in getting start…
Browse files Browse the repository at this point in the history
…ed guide

Signed-off-by: Tom Payne <tom@isovalent.com>
  • Loading branch information
twpayne authored and gandro committed Oct 6, 2020
1 parent e22ee43 commit 803f283
Showing 1 changed file with 9 additions and 2 deletions.
11 changes: 9 additions & 2 deletions Documentation/gettingstarted/k8s-install-connectivity-test.rst
Original file line number Diff line number Diff line change
@@ -1,11 +1,18 @@
Deploy the connectivity test
----------------------------

You can deploy the "connectivity-check" to test connectivity between pods.
You can deploy the "connectivity-check" to test connectivity between pods. It is
recommended to create a separate namespace for this.

.. parsed-literal::
kubectl apply -f \ |SCM_WEB|\/examples/kubernetes/connectivity-check/connectivity-check.yaml
kubectl create ns cilium-test
Deploy the check with:

.. parsed-literal::
kubectl apply -n cilium-test -f \ |SCM_WEB|\/examples/kubernetes/connectivity-check/connectivity-check.yaml
It will deploy a series of deployments which will use various connectivity
paths to connect to each other. Connectivity paths include with and without
Expand Down

0 comments on commit 803f283

Please sign in to comment.