From e6fe8a24ee7bad6d9252bba0f14ee73e935e3921 Mon Sep 17 00:00:00 2001 From: Tejeev Date: Tue, 28 Jul 2020 14:58:57 +0100 Subject: [PATCH] synchronised and updated overlay test RKE and Rancher had different versions of the test. I synced them and changed them so that they utilize Murali's swiss-army-knife which allows much more freedom for troubleshooting. --- .../v2.x/en/troubleshooting/networking/_index.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/content/rancher/v2.x/en/troubleshooting/networking/_index.md b/content/rancher/v2.x/en/troubleshooting/networking/_index.md index 7259b61a3e0..23e6e6bed02 100644 --- a/content/rancher/v2.x/en/troubleshooting/networking/_index.md +++ b/content/rancher/v2.x/en/troubleshooting/networking/_index.md @@ -15,7 +15,7 @@ Double check if all the [required ports]({{}}/rancher/v2.x/en/cluster-p The pod can be scheduled to any of the hosts you used for your cluster, but that means that the NGINX ingress controller needs to be able to route the request from `NODE_1` to `NODE_2`. This happens over the overlay network. If the overlay network is not functioning, you will experience intermittent TCP/HTTP connection failures due to the NGINX ingress controller not being able to route to the pod. -To test the overlay network, you can launch the following `DaemonSet` definition. This will run a `busybox` container on every host, which we will use to run a `ping` test between containers on all hosts. +To test the overlay network, you can launch the following `DaemonSet` definition. This will run a `swiss-army-knife` container on every host (image was developed by Rancher engineers), which we will use to run a `ping` test between containers on all hosts. 1. Save the following file as `ds-overlaytest.yml` @@ -34,11 +34,16 @@ To test the overlay network, you can launch the following `DaemonSet` definition name: overlaytest spec: tolerations: - - operator: Exists + - effect: NoExecute + key: "node-role.kubernetes.io/etcd" + value: "true" + - effect: NoSchedule + key: "node-role.kubernetes.io/controlplane" + value: "true" containers: - - image: busybox:1.28 + - image: leodotcloud/swiss-army-knife imagePullPolicy: Always - name: busybox + name: swiss-army-knife command: ["sh", "-c", "tail -f /dev/null"] terminationMessagePath: /dev/termination-log ```