From 88858ace8b1cd7b470a937fd17636612cf4bbd2f Mon Sep 17 00:00:00 2001 From: Tejeev Date: Mon, 3 Feb 2020 23:55:30 +0000 Subject: [PATCH 1/2] Fixed alpine/busybox inconsistancies --- content/rancher/v2.x/en/troubleshooting/networking/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/troubleshooting/networking/_index.md b/content/rancher/v2.x/en/troubleshooting/networking/_index.md index a8c5f64a6a5..e317d35ad94 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 an `alpine` 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 `busybox` container on every host, which we will use to run a `ping` test between containers on all hosts. If you want to run tools such as mtr, use the alpine image and you should be able to install the tool with `apk add`. 1. Save the following file as `ds-overlaytest.yml` @@ -38,7 +38,7 @@ To test the overlay network, you can launch the following `DaemonSet` definition containers: - image: busybox:1.28 imagePullPolicy: Always - name: alpine + name: busybox command: ["sh", "-c", "tail -f /dev/null"] terminationMessagePath: /dev/termination-log ``` From 17d8102703fbcd81ec3fc2b479e27021e326d93f Mon Sep 17 00:00:00 2001 From: Tejeev Date: Wed, 5 Feb 2020 12:51:10 +0000 Subject: [PATCH 2/2] Removed further reference to Alpine --- content/rancher/v2.x/en/troubleshooting/networking/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/troubleshooting/networking/_index.md b/content/rancher/v2.x/en/troubleshooting/networking/_index.md index e317d35ad94..d76fbf67773 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. If you want to run tools such as mtr, use the alpine image and you should be able to install the tool with `apk add`. +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. 1. Save the following file as `ds-overlaytest.yml` @@ -75,7 +75,7 @@ NODE1 cannot reach NODE3 => End network overlay test ``` -Cleanup the alpine DaemonSet by running `kubectl delete ds/overlaytest`. +Cleanup the busybox DaemonSet by running `kubectl delete ds/overlaytest`. ### Check if MTU is correctly configured on hosts and on peering/tunnel appliances/devices