github.com/cilium/cilium@v1.16.2/Documentation/installation/kubectl-connectivity-test.rst (about)

     1  You can deploy the "connectivity-check" to test connectivity between pods. It is
     2  recommended to create a separate namespace for this.
     3  
     4  .. code-block:: shell-session
     5  
     6     kubectl create ns cilium-test
     7  
     8  Deploy the check with:
     9  
    10  .. parsed-literal::
    11  
    12     kubectl apply -n cilium-test -f \ |SCM_WEB|\/examples/kubernetes/connectivity-check/connectivity-check.yaml
    13  
    14  It will deploy a series of deployments which will use various connectivity
    15  paths to connect to each other. Connectivity paths include with and without
    16  service load-balancing and various network policy combinations. The pod name
    17  indicates the connectivity variant and the readiness and liveness gate
    18  indicates success or failure of the test:
    19  
    20  .. code-block:: shell-session
    21  
    22     $ kubectl get pods -n cilium-test
    23     NAME                                                     READY   STATUS    RESTARTS   AGE
    24     echo-a-76c5d9bd76-q8d99                                  1/1     Running   0          66s
    25     echo-b-795c4b4f76-9wrrx                                  1/1     Running   0          66s
    26     echo-b-host-6b7fc94b7c-xtsff                             1/1     Running   0          66s
    27     host-to-b-multi-node-clusterip-85476cd779-bpg4b          1/1     Running   0          66s
    28     host-to-b-multi-node-headless-dc6c44cb5-8jdz8            1/1     Running   0          65s
    29     pod-to-a-79546bc469-rl2qq                                1/1     Running   0          66s
    30     pod-to-a-allowed-cnp-58b7f7fb8f-lkq7p                    1/1     Running   0          66s
    31     pod-to-a-denied-cnp-6967cb6f7f-7h9fn                     1/1     Running   0          66s
    32     pod-to-b-intra-node-nodeport-9b487cf89-6ptrt             1/1     Running   0          65s
    33     pod-to-b-multi-node-clusterip-7db5dfdcf7-jkjpw           1/1     Running   0          66s
    34     pod-to-b-multi-node-headless-7d44b85d69-mtscc            1/1     Running   0          66s
    35     pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82            1/1     Running   0          65s
    36     pod-to-external-1111-d56f47579-d79dz                     1/1     Running   0          66s
    37     pod-to-external-fqdn-allow-google-cnp-78986f4bcf-btjn7   1/1     Running   0          66s
    38  
    39  .. note::
    40  
    41      If you deploy the connectivity check to a single node cluster, pods that check multi-node
    42      functionalities will remain in the ``Pending`` state. This is expected since these pods
    43      need at least 2 nodes to be scheduled successfully.
    44  
    45  Once done with the test, remove the ``cilium-test`` namespace:
    46  
    47  .. code-block:: shell-session
    48  
    49     kubectl delete ns cilium-test